Process for aliases, auto-connections and tracks

Hi all,

I recognize this topic is over 2 years old, but it makes sense to keep related information together.

Similar to the the approved Simplified track request process, I’d like to propose a change to the process for auto-connections to encourage more active participation in the review process by @reviewers, and to the extent possible without compromising the integrity of the process, accelerate the granting of declarations under certain circumstances, ie: fast-tracking approval.

Rationale:

As jdstrand has stated previously, we have a 7 day voting period at least partly because:

The one week waiting period is in place so reviewers have a chance to vote (ie, we want to support the case where 2 quick ‘yea’ votes are cast and then a ‘nay’ vote later).

In practice however, rarely are architects or more than 2 reviewers (beyond those rostered on for reviews) assessing and voting on requests during the voting period. Therefore, we rarely benefit from the opportunity provided by a 7 day voting period.

Conversely, some requests sit stalled awaiting a vote that comes right at the end of the 7 day period, and are then actioned almost immediately. The intention with this change in process is to encourage more reviewers to attend to the forum more regularly (see the propsoal below), with the knowledge that their input will be immediately impactful. In doing so, we will improve the publisher experience by processing requests sooner, and the quality of reviews by increasing the number of reviewers involved in (some) requests.

Proposal (the details are welcome to be tweaked)

  1. The standard review period remains 7 days, with the following exception:
  2. auto-connection requests may be completed sooner, under the following conditions:
    1. The request be well-understood and deemed likely to be supported by at least 3 reviewers: (ie: three +1s)
    2. The request is consistent with similar, already approved requests
    3. If any reviewers do not support the request (ie: vote -1) the request is not eligible for fast-track processing.
  3. When a reviewer identifies a request they believe satisfies 2.1 and 2.2, they should mention other @reviewers to get more votes citing the request as a candidate for fast-tracking.
  4. If three +1 votes are received for a post identified as such, the reviewer may grant the declarations, waiving the remainder of the voting period.
  5. Reviewers are encouraged to request that the entire voting period apply, should they require more time to assess a request.

Feedback from @reviewers, architects (@pedronis) and @advocacy welcomed.

2 Likes