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

Re: [PATCH] Documentation: propose community voting process

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 21, 2026, 21:22 UTC
Message-ID
<xmqqtsmelpfe.fsf@gitster.g>
In-Reply-To
<20261021200341.378978-1-emilyshaffer@google.com>
Emily Shaffer <emilyshaffer@google.com> writes:
Show 14 quoted lines
> Not all discussions can be settled by community consensus. For truly
> contentious decisions we need a way to democratically make a decision
> that represents the majority will of the project. This doc outlines the
> methodology we use in the rare case where we need to vote to make a
> decision.
>
> Signed-off-by: Emily Shaffer <emilyshaffer@google.com>
> ---
> I expect the approval of the voting process itself to be fairly non-contentious
> (or else I haven't managed to write a fair process!) so for approving the
> voting process, I suggest we use a similar approach to the one we did with the
> Code of Conduct back in 2019[2][3]: discussing the process itself, ultimately
> coming to general consensus, and collecting a list of Acked-by: to put onto the
> commit outlining the voting process.

Sounds sensible. One request to change the wording of the title is to use a verb stronger than "propose". The act of sending this patch alone is a proposal, but once committed and merged, that is not "propose a process", but "define the process used in this community".

Show 8 quoted lines
> And by the way, I do think that we should
> check in the voting process; it seems likely to me that we will want to revise
> the AI policy again given the pace of development, and it may be useful for
> other discussions that we've had trouble resolving in the past.
>
> BTW, there are some parts of this proposal that I still don't have a good
> answer for, so look for my self-review immediately to follow, highlighting open
> questions.
Thanks for starting the process.
Previous: brian m. carlsonNext: Junio C Hamano
Message 37 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.