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

Re: [PATCH] Documentation: propose community voting process

From
KHKristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date
Oct 23, 2026, 14:18 UTC
Message-ID
<037a97bb-af3e-4e20-9845-c2d92ed3a2c4@app.fastmail.com>
In-Reply-To
<f192e10b-c7d0-45d8-8f67-21383474d16e@gmail.com>
On Fri, Oct 23, 2026, at 15:49, Phillip Wood wrote:
Show 31 quoted lines
> Hi Junio
>
> On 23/10/2026 05:48, Junio C Hamano wrote:
>> Phillip Wood <phillip.wood123@gmail.com> writes:
>>[snip]
>>> I also think it would be sensible to restrict eligibility to the current
>>> set of active contributors, who will have to live with the consequences
>>> of the decision, by requiring eligible contributions to have been made
>>> in the previous two years. I have historic contributions in a couple of
>>> projects that I'm not active in anymore and I would not expect to be
>>> able to influence an decisions those projects make now.
>>
>> But do you care about these past projects enough to (1) notice that
>> they are having a policy discussion, (2) bother visiting them again
>> to learn their current voting procedures, and (3) actually cast a
>> vote to help improve them?  You may not have been active recently,
>> but if you care enough, and if your past knowledge of how the
>> project works still applies, wouldn't the project participants
>> appreciate your input?
>
> As I understand it the voting systems that are being proposed
> automatically send a voting link to those eligible to vote so I would be
> aware because I'd have received a voting link. Having a time limit also
> limits the amount of admin for the person running the vote, for example
> handling messages from someone claiming to be a past contributor whose
> email address has changed. The voting system is only going to be used
> when we cannot reach a consensus. Having seen how much time and energy
> people, with no real interest in contributing to git, put into posting
> to the list when we we first discussing changing the default branch
> name, I think we should be careful to limit the potential for bad actors
> to try and derail the vote.

And this is a very relevant example since everyone can have an opinion on GenAI, just like main branch name bikeshedding. Contrast with some technical topic that you would have to be involved in the project to even care about.

Some people care whether software projects that they use but don’t contribute to use GenAI.

>
>>[snip]
Previous: Phillip WoodNext: Junio C Hamano
Message 15 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.