Re: [RFC] How to accellerate the patch flow (or should we?)

From: Taylor Blau <me@ttaylorr.com>
Date: Sep 30, 2025, 20:04 UTC
Message-ID: <aNw3z0E/xvJ/OChO@nand.local>
In-Reply-To: <aNsG8JGvpzui7XJA@pks.im>

On Tue, Sep 30, 2025 at 12:23:44AM +0200, Patrick Steinhardt wrote:

Show 11 quoted lines

> On Sat, Sep 27, 2025 at 05:32:36PM -0400, Taylor Blau wrote:
> > That would leave topics which do not have active reviewers in a lurch,
> > but I think that is sort of the point. Contributors should expect to do
> > some of the work of making sure their topics get reviewed themselves,
> > and that shouldn't fall entirely on the maintainer.
>
> I guess this is a realistic expectation for oldtimers on the mailing
> list. And it especially is a possibility for developers that work in a
> team, as they can basically tell others to do a review. But newcomers
> already have a hard time to contribute to Git, so we should make sure
> that we don't put more of the burden on them.

I think the roles would change slightly. I agree that newcomers should not be entirely responsible for finding reviewers, and I don't think that asking them to do that is entirely practical either.

But it's also impractical IMHO to expect that the maintainer doesn't happen to lose track of a topic from time to time. Perhaps other seasoned contributors could step in to say, "hey, this topic hasn't gotten reviewed. Perhaps X, Y, or Z might want to chime in?".

I dunno.

Thanks, Taylor