From: Phillip Wood Date: Thu, 22 Oct 2026 10:01:44 GMT Subject: Re: [PATCH] Documentation: propose community voting process Message-ID: In-Reply-To: Hi Emily Thanks for working on this On 21/10/2026 21:05, Emily Shaffer wrote: > On Wed, Oct 21, 2026 at 1:03 PM Emily Shaffer wrote: >> >> +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. >> + >> +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. > > The specifics of this eligibility rule can change a little. I'm trying > to figure a balance between a few principles: > * Not all contributions are code (e.g. community moderation is > contribution but a moderator may never send a patch). I think in the > Git project we have less issue with that, because we don't have a > community moderator unless we're counting the mods in the low-traffic > Discord, and I believe all of those mods have code or review > contributions anyways. I agree we want to include those who contribute more widely, but I think restricting the criteria to contributions on the mailing list where the development of git takes place and the impact of any decision will be felt the most is a reasonable place to draw the line. I'm not sure how easy it is going to be to count reviews - does posting "LGTM" count or do we want a more substantial contribution? Should verified bug reports count? - that's also a useful contribution to the project. I agree with Junio that we should count patch series, rather than individual patches and I think it would be easier to measure when they're merged to master rather than next. > * Avoiding dogpiling. This is my biggest fear, Git is a very > well-known project and there will be a lot of big opinions on the open > internet once people know we're voting on this policy. I want us to > measure the opinions of those who participate in the project, not the > opinions of random passers-by. I agree this is important. Before a vote is proposed it is likely that there will be some (possibly contentious) discussion on the list so I wonder if we should require that eligible contributions are made at least a month before the first draft of a proposal is posted. Junio's suggestion that we restrict eligibility to released code has a similar effect but I'm not sure how that would work for non code contributions. 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. > * 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. I think this is tricky even for mailing list contributions, as I said above what constitutes a useful review? I'm afraid I don't have any useful suggestions. (It would be interesting to see if an LLM can usefully classify the emails on the list but I don't think we want to be using an LLM determining eligibility to vote on a proposal about whether to accept AI!) Thanks Phillip >> diff --git a/Documentation/DecisionMaking.adoc b/Documentation/DecisionMaking.adoc >> index b43c472ae5..c08fb7abd5 100644 >> --- a/Documentation/DecisionMaking.adoc >> +++ b/Documentation/DecisionMaking.adoc >> @@ -72,3 +72,9 @@ We prefer that "official" discussion happens on the list so that the full >> community has opportunity to engage in discussion. This also means that the >> mailing list archives contain a more-or-less complete history of project >> discussions and decisions. >> + >> +Formal Voting >> +------------- >> +When a decision cannot be reached by general consensus or compromise, a formal >> +vote may be called. See link:CommunityVoting.adoc[Community Voting] for details >> +of this process. >> diff --git a/Documentation/Makefile b/Documentation/Makefile >> index f8dea4b395..314b8dc8f5 100644 >> --- a/Documentation/Makefile >> +++ b/Documentation/Makefile >> @@ -113,6 +113,7 @@ SP_ARTICLES += $(API_DOCS) >> >> TECH_DOCS += BreakingChanges >> TECH_DOCS += DecisionMaking >> +TECH_DOCS += CommunityVoting >> TECH_DOCS += ReviewingGuidelines >> TECH_DOCS += MyFirstContribution >> TECH_DOCS += MyFirstObjectWalk >> -- >> 2.56.0.rc1.315.gc6ed9934b7-goog >> >