Problem/Motivation

To help keep the momentum of this great initiative and attract more reviewers, we could blog about it.

Sharing the goals and progress via a blog post would spread the word wider about this vital work. And it is more than 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.

Steps to reproduce

Proposed resolution

Publish a blog post about once per minor release on https://www.drupal.org/about/core/blog.

  • One post when we finish drafting it
    This initial post should explain what the initiative is and be an introduction of sorts
  • A second one before the December minor release window
    This next one could then give a progress update and maybe add additional conceptual content

Subjects could be:

  • Initiative changes
  • How the stats are evolving, such as How many issue got fixed and average time tickets sit in review
  • Teach new users how to get started (see "Problem/Motivation" for more)
  • Which new users joined and pledged to review issues
  • Etc.

Get the blog included on Planet Drupal.

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

Comments

ressa created an issue. See original summary.

xjm’s picture

I think this should be lower frequency (say once per minor to start), but published on https://www.drupal.org/about/core/blog.

The initial post should explain what the initiative is and be an introduction of sorts. The next one could then give a progress update and maybe add additional conceptual content. I suggest one when we finish drafting it and a second one before the December minor release window.

ressa’s picture

Issue summary: View changes

Thanks @xjm, sounds great! I attempted to add your suggestions to the Issue Summary, feel free to adjust if some things need tweaking.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.