git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Documentation: propose community voting process

From
Jeff King <peff@peff.net>
Date
Nov 4, 2026, 06:34 UTC
Message-ID
<20261104063417.GB1543013@coredump.intra.peff.net>
In-Reply-To
<auha0Ze6xksBXaVx@pks.im>
On Mon, Nov 02, 2026 at 10:41:37AM +0100, Patrick Steinhardt wrote:
Show 18 quoted lines
> 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.

Yeah, that was my gut feeling in the original suggestion, and I could go either way on the logic of it. Linus might be an extreme special case there.

Show 10 quoted lines
> > 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.
Yeah, that is along the lines I was thinking when I said the above.
-Peff
Previous: Patrick SteinhardtNext: Phillip Wood
Message 34 of 52 in “Notes from the Git Contributor's Summit, 2026”
  1. Taylor BlauOct 6, 2026
  2. 01/07 Security mailing list and security processTaylor Blau, Oct 6, 2026
  3. 02/07 Git 3.0Taylor Blau, Oct 6, 2026
  4. 03/07 DocumentationTaylor Blau, Oct 6, 2026
  5. Todd ZullingerOct 7, 2026
  6. Junio C HamanoOct 7, 2026
  7. 04/07 Outreachy sponsorshipTaylor Blau, Oct 6, 2026
  8. 05/07 What can we do next with pluggable ODB?Taylor Blau, Oct 6, 2026
  9. 06/07 AI contribution policyTaylor Blau, Oct 6, 2026
  10. Documentation: propose community voting processEmily Shaffer, Oct 21, 2026
  11. Emily ShafferOct 21, 2026
  12. Phillip WoodOct 22, 2026
  13. Junio C HamanoOct 23, 2026
  14. Phillip WoodOct 23, 2026
  15. Kristoffer HaugsbakkOct 23, 2026
  16. Junio C HamanoOct 23, 2026
  17. Kristoffer HaugsbakkOct 23, 2026
  18. Junio C HamanoOct 23, 2026
  19. Kristoffer HaugsbakkOct 23, 2026
  20. Tuomas AholaOct 24, 2026
  21. Weijie YuanOct 24, 2026
  22. Toon ClaesOct 30, 2026
  23. Weijie YuanOct 30, 2026
  24. Junio C HamanoOct 24, 2026
  25. Weijie YuanOct 24, 2026
  26. Jeff KingOct 26, 2026
  27. Junio C HamanoOct 26, 2026
  28. Patrick SteinhardtOct 26, 2026
  29. Tuomas AholaOct 26, 2026
  30. Emily ShafferOct 30, 2026
  31. Junio C HamanoOct 30, 2026
  32. Jeff KingOct 30, 2026
  33. Patrick SteinhardtNov 2, 2026
  34. Jeff KingNov 4, 2026
  35. Phillip WoodOct 26, 2026
  36. brian m. carlsonOct 22, 2026
  37. Junio C HamanoOct 21, 2026
  38. Junio C HamanoOct 21, 2026
  39. Justin ToblerOct 22, 2026
  40. Junio C HamanoOct 23, 2026
  41. Emily ShafferOct 30, 2026
  42. Kristoffer HaugsbakkOct 22, 2026
  43. Patrick SteinhardtOct 22, 2026
  44. brian m. carlsonOct 22, 2026
  45. Junio C HamanoOct 22, 2026
  46. Emily ShafferOct 30, 2026
  47. Kristoffer HaugsbakkOct 23, 2026
  48. Emily ShafferOct 30, 2026
  49. Junio C HamanoOct 30, 2026
  50. Jonathan CorbetOct 30, 2026
  51. Stéphane GlonduNov 9, 2026
  52. 07/07 Protocol v2 for pushesTaylor Blau, Oct 6, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.