[Plan] Needs review issue queue management

Created on 25 November 2022, over 2 years ago
Updated 20 January 2023, over 2 years ago

Problem/Motivation

There is a huge amount of "ongoing" issues in the core queue, leading to many stale issues, hard work that goes unused, and contributor frustration.

Currently between D9 + D10 there are about 2900 issues in needs review. Many issues have been in "need review" for several years at this point. More than 600 issues have been RTBC at least once. And a bit less than 60% of NR issues have a patch that either do not apply or where commit check fails.

Steps to reproduce

https://www.drupal.org/project/issues/search/drupal?text=&assigned=&subm... β†’

Proposed resolution

The idea is to triage the NR queue so that we mark an issue either RTBC or Needs work/postponed/etc.
The goal is to keep that NR queue around 100-200 issues at any point in time.

Remaining tasks

Determine best approaches

🌱 Plan
Status

Active

Version

10.1 ✨

Component
OtherΒ  β†’

Last updated about 11 hours ago

Created by

πŸ‡ΊπŸ‡ΈUnited States smustgrave

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    I think this can be marked fixed. Queue is current 80

  • πŸ‡©πŸ‡°Denmark ressa Copenhagen

    To help keep the momentum of this great initiative and attract more reviewers, perhaps it's worth considering blogging about it? It could be just a short piece every other month, with an update on how many issue got fixed, how the stats are evolving, which new users joined and pledged to review issues, and so on. The blog could get included on Planet Drupal β†’ ?

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    I mean it would be a small post. Really I imagine it would just be stats or issues tagged for the initiative, maybe average time tickets sit in review, and any initiative changes.

    Like it use to be under 2 months but has shifted to 3

  • πŸ‡³πŸ‡ΏNew Zealand quietone

    Sharing the goals and progress via a blog post would spread the word wider about this vital work. And it is more that statistics, it is an opportunity to discuss each part of the review process, when to ping someone, when not to ping someone, what tags to use, why keeping the issue summary up to date help, how to postpone an issue etc. And maybe there is a sense that reviews or reviewers are improving there skills.

    If the blog posts included more that statistics, then the frequency the post would likely be less. At that can be a good thing.

  • πŸ‡©πŸ‡°Denmark ressa Copenhagen

    Thanks @smustgrave and @quietone for the feedback, I really appreciate it. Based on it, I created an issue.

Production build 0.71.5 2024