public inbox for
 help / color / mirror / Atom feed
From: Maxim Kuvyrkov <>
To: GNU C Library <>
Subject: [RFC] Patch review volunteers
Date: Mon, 5 Feb 2024 21:45:11 +0400	[thread overview]
Message-ID: <> (raw)

Hi All,

TL;DR: Answer "yes, I volunteer" to this email.

Glibc community has a "Patchwork Review Meeting" [1] where we try to assign patches waiting for review to various glibc developers.  One challenge, though, is that the current practice is to pick reviewers from the people who happened to join a particular meeting.  This process doesn't scale since the number of patches glibc project is receiving is substantially bigger than the number of developers joining the patch review meeting.

We are seeking volunteers to join the patch reviewer pool to whom we can distribute the load of incoming patches.  You agree to be assigned a few patches per week and review them in a reasonable timeframe.  If you start joining the review meetings (on Mondays) -- even better!

We are guessing that a pool of 20 volunteers would be enough to cope with Glibc's current patch influx.  This would translate into each volunteer reviewing 1-2 patches (or short patch series) per week.

You don't have to be a senior developer to join patch review.  We will have a smaller pool of senior developers who will help with advice and mentorship when you get assigned to a particularly difficult patch.  Joining the patch reviewer pool is a great way to develop your upstream skills.

Are you joining the patch review volunteers?

Note, that "patch review" and "patch approval" are different things.  Being assigned as patch reviewer is not a grant of a right to unilaterally approve the patch.  The usual patch approval process still applies.


Maxim Kuvyrkov

             reply	other threads:[~2024-02-05 17:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05 17:45 Maxim Kuvyrkov [this message]
2024-02-12 14:08 ` Carlos O'Donell
2024-02-12 14:09 ` Arjun Shankar
2024-03-11 18:31 ` Florian Weimer
2024-03-11 19:25   ` Maxim Kuvyrkov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).