From: Patrick Steinhardt <ps@pks.im>
To: Jeff King <peff@peff.net>
Cc: Emily Shaffer <nasamuffin@google.com>,
Tuomas Ahola <taahol@utu.fi>, Junio C Hamano <gitster@pobox.com>,
Phillip Wood <phillip.wood123@gmail.com>,
git@vger.kernel.org, Justin Tobler <jltobler@gmail.com>
Subject: Re: [PATCH] Documentation: propose community voting process
Date: Mon, 2 Nov 2026 10:41:37 +0100 [thread overview]
Message-ID: <auha0Ze6xksBXaVx@pks.im> (raw)
In-Reply-To: <20261030180016.GA7582@coredump.intra.peff.net>
On Fri, Oct 30, 2026 at 02:00:16PM -0400, Jeff King wrote:
> The "X commits and active in the last Y years" one covers you, I think,
> but probably excludes Linus (depending on the exact parameters).
>
> At some point, though, I think there are are always going to be weird
> exceptions and it is going to be hard to come up with an algorithmic
> rule to get the right set. Perhaps there needs to be some human input
> ("we all agree this person is an important part of the community, even
> though they do not technically meet the metrics"). If the metric gets us
> 99% of the way there, then that keeps the human scaling part down.
One counterargument though: is it really that unexpected to eventually
exclude people from the voting process if they haven't been active in a
long time? I think that the ability to cast an _informed_ vote will
quite often require context on how that certain topic has been impacting
the community. And sure, a person that hasn't been active in a decade
can of course try to discover that context before casting the vote, but
that only goes so far.
> Of course that opens the can of worms of: how does the human part work.
> Which humans? IMHO I would be comfortable with Junio or the PLC just
> saying "these people also get a vote" (with probably a big initial list,
> and then periodic updates).
If we do that it needs to be fully transparent though: who has been
added to the list by whom and what is the specific reasoning behind it.
But as long as we have that and as long as it's made public well ahead
of time so that it can be discussed (and challenged, if needed) I'm fine
with such a process.
Patrick
next prev parent reply other threads:[~2026-11-02 9:41 UTC|newest]
Thread overview: 52+ 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-30 6:35 ` Toon Claes
2026-10-30 7:18 ` Weijie Yuan
2026-10-24 14:56 ` Junio C Hamano
2026-10-24 15:06 ` Weijie Yuan
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-30 16:50 ` Emily Shaffer
2026-10-30 17:18 ` Junio C Hamano
2026-10-30 18:00 ` Jeff King
2026-11-02 9:41 ` Patrick Steinhardt [this message]
2026-11-04 6:34 ` Jeff King
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-30 16:30 ` Emily Shaffer
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-30 16:53 ` Emily Shaffer
2026-10-23 4:51 ` Kristoffer Haugsbakk
2026-10-30 17:15 ` Emily Shaffer
2026-10-30 17:44 ` Junio C Hamano
2026-10-30 21:03 ` Jonathan Corbet
2026-11-09 15:21 ` Stéphane Glondu
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=auha0Ze6xksBXaVx@pks.im \
--to=ps@pks.im \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox