From: Junio C Hamano Date: Fri, 23 Oct 2026 04:56:40 GMT Subject: Re: [PATCH] Documentation: propose community voting process Message-ID: In-Reply-To: Justin Tobler writes: >> 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. > > I also agree that the proposed eligibility requirements here seem quite > too low. From my point of view, ideally eligible voters would primarily > consist of individuals in the community that have both a vested and > current interest in the project. If an individual submitted a handful of > patches 15 years ago, but have not been involved in the community since, > should they still be eligible to vote? Maybe it would be worth > discussing whether contributions must have come from one of last X > releases in order to be considered eligible? Again, I would urge us to resist the temptation to make the rules more elaborate (see my response to Phillip elsewhere in the thread). Once we start saying "such an ancient contribution alone shouldn't qualify you to vote", it is essentially the same as saying "with more recent involvement, and with more vested and current interest, you should have more influence". With that line of thought, we would end up with rules like "your commit made X days ago earns you 1/X vote" (where influence decays with the age of contribution) or "summing votes earned across all commits in released versions, and that is the number of votes you can cast" (where the more you have contributed, the more valuable your input would be to the project). I do not think we want to go there, and we should instead limit ourselves to "each of you gets one vote, and this is the simple rule to tell if you can vote." That is simpler to explain and makes it hard for any potential detractors to claim unfairness. Thanks.