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:30 UTC
Message-ID
<CAJoAoZmdu5zdUAjNi7d89CH4jYTMmLDa8e7cd2nKwTEk7oO1jA@mail.gmail.com>
In-Reply-To
<xmqqfqxylnct.fsf@gitster.g>
On Wed, Oct 21, 2026 at 3:07 PM Junio C Hamano <gitster@pobox.com> wrote:
Show 65 quoted lines
>
> Emily Shaffer <emilyshaffer@google.com> writes:
>
> Emily Shaffer <emilyshaffer@google.com> writes:
>
> > +Voting in the Git Project
> > +=========================
> > +
> > +For the most part, technical concerns in Git should be resolved by community
> > +consensus - either on the mailing list or in one of the annual-ish Contributor
> > +Summits. Voting should be used as a last resort when the community really and
> > +truly cannot come to a compromise on a policy decision. As such, the initiation
> > +of a vote should be generally agreed on by the mailto:git@sfconservancy.org[Git
> > +PLC] or primary maintainer.
>
> Nicely described.  I particularly like that this prevents us from
> putting technical decisions to a vote, reserving voting strictly for
> policy decisions.
>
>
> > +Phase 2: Voting window
> > +----------------------
> > +
> > +The final version of each seconded proposal will be collected into a ballot at
> > +the end of Phase 1. When the ballot is prepared, eligible voters will be able
> > +to vote by mail for two weeks, to make space for contributors' individual
> > +timezone and availability differences. During this time the proposals may no
> > +longer be altered; the ballot should refer to a specific version of the
> > +proposal (e.g. `[PROPOSAL v4] Require emojis in commit subjects`) and any later
> > +version of the proposal will be ignored.
>
> Or any earlier ones for that matter.  Perhaps there should be a way
> to uniquely identify the version.  By the time the proposal is so
> solidified, it is likely to be in my tree, so we can use the commit
> object name that adds such a proposal document (or the blob ID).
>
> Then we can tell people that
>
>     $ git fetch https://git.kernel.org/pub/scm/git/git.git/ seen
>     $ git cat-file blob $BLOB_OBJECT_NAME
>
> would give them the exact thing they are voting on.
>
> I presume that this can be used for multiple-choice votes easily,
> and can be adjusted for a proposal with multiple things to vote on
> independently (i.e., "allow emojis in commit titles?" and "require
> CamelCase in commit titles?" can be asked at the same time and
> voters can give answers to each question separately).
>
>
> > +Votes will be decided using <mechanism TBD>.
> > +
> > +Phase 3: Implementation
> > +-----------------------
> > +
> > +When the voting window ends, the winning proposal should be merged to `main`
> > +without delay by the maintainer. The commit message should be appended to
> > +include a link to the top of the voting discussion thread so that the
> > +discussion can be revisited by history divers in the future, as well as a brief
> > +summary of the result of the vote (% in favor out of total number of
> > +proposals).
>
> Do you mean "number of votes"?  Or are we envisioning that there
> will be N competing proposals and we vote to find out which one is
> the most favored?

I read the rest of the replies to my proposal this morning and didn't see anybody else clarify it. Yes, I am envisioning N competing proposals. In some cases they could be as simple as the following:

Question: Should the project adopt the policy outlined at
git.kernel.org/pub/scm/git.git/commit?id=12345 ?
Proposal 1: Yes
Proposal 2: No

But in cases like the AI policy I think it's more likely that we will have a number of competing proposals, because the community feels more than two ways about AI use. I'll stick with my silly example about commit messages to avoid inviting criticism for throwaway AI proposal lines here:

Question: How should we format our commit messages?
Proposal 1: Anything goes. No more length restrictions, wrap anywhere
you like or not at all, use special characters if you want. If it's
covered by Unicode it's fair game. In fact, if we can figure out how
to include bitmap images in the commit message, let's do that.
Proposal 2: All commit messages should be written in lojban (despite
that this proposal is not written in lojban).
Proposal 3: Conventional commits, but make it fun: indicate which type
of commit it is using an emoji. Emoji use is mandatory.
Proposal 4: using the shift key is unnecessary energy expenditure and
should be strictly banned, this applies to punctuation that requires
the shift key also.

In this case some might agree with one proposal more than the other, or be okay with a third even if it's not their favorite - both CIVS and devotee use a form of ranked choice voting and solve for the most popular proposal based on voters' ranked choices.

Show 25 quoted lines
>
> > +Voting Eligibility
> > +------------------
> > +
> > +Votes are welcome from contributors who have authored a commit which has been
> > +merged to next, or who have provided 2 or more code reviews, and who have not
> > +been banned from participation in the project. All eligible contributor votes
> > +are weighed equally, regardless of the overall number of contributions they
> > +have landed.
>
> That is a fairly low bar to cross, especially the code review count,
> as it will not be easy to define and enforce some rule that rejects
> a response to a patch that only says "thanks, I like the feature
> this proposes" without reading any parts of the message.
>
> As it is hard to track patches that as in 'next' a few release
> cycles ago without graduating in the end and the authors of such a
> patch should have the same voting power as those whose patch is in
> 'next' in the current cycle, I would suggest strongly against using
> 'next' as a yardstick.
>
> I would have expected to see something like "two or more topics that
> appear in any released versions" instead.  Note that I said "topics"
> here and not "commits", so your topic that consists of 17-patch
> still counts as one.

It seems like Peff's matrix along total commit count and recency of contribution[1] also was quite popular. I tend to agree with you about not wanting to restrict votes to people who have been active X number of years ago, but to be honest, it's for selfish reasons: I haven't been able to write code actively for quite some time because of my role at Google and I still feel invested in (and a welcome member of) the Git community. However, if the eligibility criteria that the community agrees on prevents me from voting, I understand, because I know I have not been contributing as much as the community would have liked :)

I'll continue the discussion in reply to Peff's thread as well. Thanks.
Show 10 quoted lines
>
> > +To prevent dogpiling, contributions are only eligible for a given vote if they
> > +landed before the beginning of the voting process (the kickoff email mentioned
> > +above). That is, the code reviews must have been sent or the patch must have
> > +been accepted before the initial email is sent. The intention is to ensure the
> > +mailing list isn't spammed with low-quality reviews during the voting process
> > +solely to increase the number of eligible voters on one side of the issue.
>
> Hopefully the "in released versions" criteria makes the above a
> non-issue.
Previous: Junio C HamanoNext: Kristoffer Haugsbakk
Message 41 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.