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

Re: [PATCH] Documentation: propose community voting process

From
Emily Shaffer <nasamuffin@google.com>
Date
Oct 30, 2026, 16:50 UTC
Message-ID
<CAJoAoZnqzKv8ocsi1a-nC6LaRnpKKCO0Bxt-Pdn0dDUziEcpAg@mail.gmail.com>
In-Reply-To
<at8IBMQZtJP3bQ9-@pks.im>
On Mon, Oct 26, 2026 at 12:58 AM Patrick Steinhardt <ps@pks.im> wrote:
Show 63 quoted lines
>
> On Sun, Oct 25, 2026 at 09:17:31PM -0400, Jeff King wrote:
> > On Sat, Oct 24, 2026 at 02:18:56PM +0300, Tuomas Ahola wrote:
> >
> > > 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'm a bit behind on the list and haven't been following this discussion
> > closely yet, but I'll just say: the number 50 was made up by me on the
> > spot. So I wouldn't read too much into it.
> >
> > But if somebody is picking a number, looking at "git shortlog -ns
> > --no-merges | sort -rn" may be interesting, just to get a sense of how
> > many people we are talking about:
> >
> >   - there are 44 people with >= 200 commits
> >   - there are 133 people with >= 50 commits
> >   - there are 439 people with >= 10 commits
> >   - there are 2388 people with >= 1 commit
> >
> > At some point it gets kind of unwieldy.
> >
> > I saw proposals elsewhere to cut it by time. I think "N commits in the
> > last M years" is awkward, because there are people who have been around
> > for a long time with steady but slow participation steady-but-slow
> > participation. But if you just intersect "N commits over all time" and
> > "has _any_ commits in the last M years", then you can get a table like:
> >
> > total    | Active in the last N years
> > commits  |  N=1    N=2    N=3    N=5
> > ----------------------------------------------------
> >     200  |   17     22     24     30
> >      50  |   34     47     56     67
> >      10  |   71    104    124    155
> >       1  |  239    357    457    628
> >
> > Those aren't necessarily perfect metrics, but if we consider them good
> > enough and just want to tune the parameters, we could probably pick a
> > spot in the table that has about the number of votes we'd want to deal
> > with.
>
> 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.

Show 9 quoted lines
>
> I think it's fair to say that everyone has a single vote to cast no
> matter their seniority so that the vote doesn't get overly skewed
> towards the opinion of long-term contributors, as those tend to be
> employed to work on Git. But the other side of the coin is that the vote
> would get overly skewed towards newcomers in case we set the total
> commit bar too low. So picking the right spot in the table would
> essentially be balancing out the interests of oldtimers versus
> newcomers.

Right - Junio mentioned in <xmqqv76taubb.fsf@gitster.g> that being too picky about the time the contribution was made can eventually make the vote somewhat equivalent to a weighted vote based on total number of contributions anyways.

Junio also posted in <xmqq4iedc99a.fsf@gitster.g> - do you really care about the policy of a project you don't contribute to anymore? And I think that answer would depend. If I think of a project that I used to serve as a subsystem maintainer of, and I receive a voting link for that project, and I see that one of the proposals in that vote would substantially harm the people I worked with for multiple years and still presumably care for the well-being of, I would probably want to vote on it. If I think of a project I left a drive-by commit on, I would probably abstain, especially if in order to vote I would need to read five long complex proposals for alternative policies ;) So I 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.

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.

 - Emily
Show 10 quoted lines
>
> How exactly we want to balance that is a different question. I am of
> course heavily biased as an oldtimer and would thus think that 10
> commits is a rather low bar. So from that table I myself would probably
> pick 50 with N=2 or N=3, but maybe a commit count of 25 or 30 would be
> more reasonable as a middle ground.
>
> In any case, there is no "correct" value anyway.
>
> Patrick
Previous: Tuomas AholaNext: Junio C Hamano
Message 30 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.