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
Oct 30, 2026, 18:00 UTC
Message-ID
<20261030180016.GA7582@coredump.intra.peff.net>
In-Reply-To
<CAJoAoZnqzKv8ocsi1a-nC6LaRnpKKCO0Bxt-Pdn0dDUziEcpAg@mail.gmail.com>
On Fri, Oct 30, 2026 at 09:50:41AM -0700, Emily Shaffer wrote:
Show 9 quoted lines
> > That sounds very reasonable to me. Though I have to say that we
> > shouldn't only consider "the number of votes we'd want to deal with",
> > but also the shape of the voting population that we want to see.
> 
> I agree with this point - I don't think that the number of votes is
> particularly salient, because I assume that any of the vote platforms
> we would choose can handle a much larger audience than ~600 people. I
> think none of these solutions require us to manually email every voter
> or to manually count the results from each.

My thinking was less about the voting itself, but more about the management around the "voter roll": maintaining who is on the list, how we get in touch with them, how we authenticate their votes, and so on. But if the system is just "this is the (possibly mailmapped) email under which you contributed, and we sent an auth token to that email and you got it", then that probably scales without human involvement.

> think it really depends. For example, I could think of a few previous
> very active contributors on the Git project who I would still want to
> collect opinions from even though they haven't been active in years.
Feels like Linus should probably get a vote. ;)
Show 7 quoted lines
> I mentioned this in another thread as well, but for full transparency,
> I'm feeling a little bias here because I haven't had the capacity to
> make meaningful code contributions to the Git project in quite a few
> years now due to my role at Google. But I still consider myself a
> community member and would very much like to vote in this particular
> policy decision. On the other hand, if the eligibility rules we settle
> on mean I can't, I understand and accept that as well.

Yeah. I think for any metric it makes sense to look at the list and see if it includes or excludes people you expect. A metric that excludes you (for example) is an indication that it's flawed or incomplete.

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.

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).

-Peff
Previous: Junio C HamanoNext: Patrick Steinhardt
Message 32 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.