All of lore.kernel.org
 help / color / mirror / Atom feed
From: Weijie Yuan <wy@wyuan.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Tuomas Ahola <taahol@utu.fi>,
	Phillip Wood <phillip.wood123@gmail.com>,
	Emily Shaffer <nasamuffin@google.com>,
	git@vger.kernel.org, Justin Tobler <jltobler@gmail.com>,
	Jeff King <peff@peff.net>
Subject: Re: [PATCH] Documentation: propose community voting process
Date: Sat, 24 Oct 2026 23:06:55 +0800	[thread overview]
Message-ID: <atzJj546SPgoRAby@wyuan.org> (raw)
In-Reply-To: <xmqqjyn7171g.fsf@gitster.g>

Junio C Hamano <gitster@pobox.com> writes:

> Tuomas Ahola <taahol@utu.fi> writes:
> 
> > Junio C Hamano <gitster@pobox.com> wrote:
> >
> >> [...]
> >> I previously mentioned "topic count", but commits are far easier to
> >> count.  So instead of requiring two topics in released versions,
> >> perhaps requiring five commits would be easier to implement and
> >> explain.
> >> 
> >
> > Quoting the summit notes:
> >
> > } * Emily: Have we used a voting process for something like this before?
> > } 
> > } * Patrick: We need proposals and a vote. Who would be allowed to vote?
> > } 
> > } * Peff: Active developers with a track record; perhaps a threshold such
> > }   as 50 merged patches.
> > } 
> >
> > So it seems that Peff's proposed threshold was substantially higher
> > than what has been put forth in this thread.  Any comments on that?
> 
> I do not know which between 50 or 200 is more appropriate, but I
> think these are more realistic threshold.  FWIW, I made the first
> review comment that pointed out that the bar set by Emily's document
> was too low to cross.  The "2 vs 5" you are reacting to was merely
> to point out that commit count would be higher than equivalent topic
> count and without bringing "2 is too low" topic again, which I
> already gave an input to.

Oh, so sorry that I was misreading.

  reply	other threads:[~2026-10-24 15:07 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-06 18:05 Notes from the Git Contributor's Summit, 2026 Taylor Blau
2026-10-06 18:06 ` [NOTES 01/07] Security mailing list and security process Taylor Blau
2026-10-06 18:06 ` [NOTES 02/07] Git 3.0 Taylor Blau
2026-10-06 18:06 ` [NOTES 03/07] Documentation Taylor Blau
2026-10-07  4:49   ` Todd Zullinger
2026-10-07 17:38     ` Junio C Hamano
2026-10-06 18:06 ` [NOTES 04/07] Outreachy sponsorship Taylor Blau
2026-10-06 18:06 ` [NOTES 05/07] What can we do next with pluggable ODB? Taylor Blau
2026-10-06 18:06 ` [NOTES 06/07] AI contribution policy Taylor Blau
2026-10-21 20:03   ` [PATCH] Documentation: propose community voting process Emily Shaffer
2026-10-21 20:05     ` Emily Shaffer
2026-10-22 10:01       ` Phillip Wood
2026-10-23  4:48         ` Junio C Hamano
2026-10-23 13:49           ` Phillip Wood
2026-10-23 14:18             ` Kristoffer Haugsbakk
2026-10-23 16:26               ` Junio C Hamano
2026-10-23 18:09                 ` Kristoffer Haugsbakk
2026-10-23 22:08                   ` Junio C Hamano
2026-10-23 14:31           ` Kristoffer Haugsbakk
2026-10-24 11:18           ` Tuomas Ahola
2026-10-24 13:03             ` Weijie Yuan
2026-10-24 14:56             ` Junio C Hamano
2026-10-24 15:06               ` Weijie Yuan [this message]
2026-10-26  1:17             ` Jeff King
2026-10-26  3:50               ` Junio C Hamano
2026-10-26  7:57               ` Patrick Steinhardt
2026-10-26  9:23                 ` Tuomas Ahola
2026-10-26 10:41               ` Phillip Wood
2026-10-22 22:59       ` brian m. carlson
2026-10-21 21:22     ` Junio C Hamano
2026-10-21 22:06     ` Junio C Hamano
2026-10-22 15:35       ` Justin Tobler
2026-10-23  4:56         ` Junio C Hamano
2026-10-22  7:29     ` Kristoffer Haugsbakk
2026-10-22 12:44       ` Patrick Steinhardt
2026-10-22 22:51       ` brian m. carlson
2026-10-22 23:17         ` Junio C Hamano
2026-10-23  4:51         ` Kristoffer Haugsbakk
2026-10-06 18:06 ` [NOTES 07/07] Protocol v2 for pushes Taylor Blau

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=atzJj546SPgoRAby@wyuan.org \
    --to=wy@wyuan.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jltobler@gmail.com \
    --cc=nasamuffin@google.com \
    --cc=peff@peff.net \
    --cc=phillip.wood123@gmail.com \
    --cc=taahol@utu.fi \
    /path/to/YOUR_REPLY

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

* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.