JmlrOrg / JmlrOrg/webpage

wish list of suggestions for the reviewer database and invitation email

Open
#6 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
11
Forks
11
PR merge metrics
No merged PRs in 30d

Description

A few suggested improvements (from the point of view of an action editor) regarding how JMLR keeps its database of reviewers, and how invitation emails are sent.

  1. I often find reviewers that appear as duplicate accounts. It would be nice to have a unique account per reviewer. One reason (probably the main one) why duplicate accounts occur is because AEs create a new account for an existing reviewer who has changed email address. The system doesn't allow to update a reviewer's email address.

  2. To add an extra address as .cc when inviting a reviewer. Sometimes I'm not sure whether the address in the system works and I'd like to add an alternative one.

  3. To have the JMLR system let me know if an email address is not working (when inviting a reviewer). Sometimes reviewers don't respond to an invitation and it might be that the address doesn't work. I can email directly to the address to find out, but it would be best to know as soon as the system sends the invitation (by getting a bounced message).

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files or tests; start by locating the reviewer-account and invitation-email entry points in the JMLR webpage. Clarify whether the scope covers separate changes for updating email addresses without duplicate accounts, adding CC recipients, and reporting bounced invitations; done requires agreed behavior and tests for each.

Written by the indexing model from the issue text.

Assessment

Domain
backend, databases
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.