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

Re: [PATCH] Documentation: propose community voting process

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Oct 22, 2026, 22:59 UTC
Message-ID
<atqVZYU3YfuyFdvU@fruit.crustytoothpaste.net>
In-Reply-To
<CAJoAoZnhc6Tjm9m9dmTA6UD18HzkxAv2_ifB5x74ectqX8YieA@mail.gmail.com>
On 2026-10-21 at 20:05:06, Emily Shaffer wrote:
Show 8 quoted lines
> There are a few appealing options.
> 
> * Debian uses devotee (https://salsa.debian.org/debian/devotee), which
> appears to require hosting. Finding neutral hosting may prove tricky.
> * Konstantin let me know that The Linux Foundation's Technical
> Advisory Board has used CIVS (https://civs1.civs.us/) in the past. He
> says he wasn't involved in setting it up but doesn't think it looks
> too challenging. CIVS and devotee use the same tallying algorithm.

I'm not volunteering to set this up or maintain things, but I do follow Debian stuff reasonably closely and I have a positive opinion of devotee.

> * jj used voting on a GitHub poll in the past. That would just give us
> simple majority, and it would require GitHub accounts, which may be a
> barrier.

I think some people who are contributors will not want to use GitHub and we've historically been neutral on forges and tooling, so we should continue that policy here.

Show 5 quoted lines
> > +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.

I think this is too few contributions. Other projects use a much tighter mechanism for choosing contributors and some even restrict access to a core team. I'm not saying that we should do that here, but we should put a threshold in place where people are not incentivized to contribute only to vote. That is, we want contributors to contribute for the sake of contributing and have voting be merely a consequence of being a serious contributor.

At this moment, I'm not sure exactly where that threshold should be set, though.

> * Easy (scriptable) eligibility determination. If we start to explore
> other types of contribution, like user support in non-mailing-list
> platforms, it becomes really difficult to send a ballot to everyone
> who's supposed to get one.
Scriptability is important, I agree.
-- 
brian m. carlson (they/them)
Toronto, Ontario, CA
Speaking for myself only
Previous: Phillip WoodNext: Junio C Hamano
Message 36 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.