public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed

From: Taylor Blau <me@ttaylorr•com>
To: Patrick Steinhardt <ps@pks•im>
Cc: Junio C Hamano <gitster@pobox•com>, git@vger•kernel.org
Subject: Re: [RFC] How to accellerate the patch flow (or should we?)
Date: Tue, 30 Sep 2025 16:04:31 -0400	[thread overview]
Message-ID: <aNw3z0E/xvJ/OChO@nand.local> (raw)
In-Reply-To: <aNsG8JGvpzui7XJA@pks.im>

On Tue, Sep 30, 2025 at 12:23:44AM +0200, Patrick Steinhardt wrote:
> 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

next prev parent reply	other threads:[~2025-09-30 20:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-26 22:24 [RFC] How to accellerate the patch flow (or should we?) Junio C Hamano
2025-09-27 21:32 ` Taylor Blau
2025-09-28  0:19   ` Junio C Hamano
2025-09-28  2:21     ` Taylor Blau
2025-09-29 22:23     ` Patrick Steinhardt
2025-09-29 22:46       ` Junio C Hamano
2025-09-29 23:25         ` Patrick Steinhardt
2025-10-01 20:00           ` Junio C Hamano
2025-09-30 20:02       ` Taylor Blau
2025-09-30 20:28         ` Junio C Hamano
2025-09-29 20:12   ` Kristoffer Haugsbakk
2025-09-29 21:19     ` Ben Knoble
2025-09-29 22:23     ` Patrick Steinhardt
2025-09-29 22:23   ` Patrick Steinhardt
2025-09-30 20:04     ` Taylor Blau [this message]
2025-09-29 20:04 ` Kristoffer Haugsbakk
2025-09-29 22:12   ` Junio C Hamano

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=aNw3z0E/xvJ/OChO@nand.local \
    --to=me@ttaylorr$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=gitster@pobox$(echo .)com \
    --cc=ps@pks$(echo .)im \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox