From: Patrick Steinhardt Date: Mon, 02 Nov 2026 09:41:37 GMT Subject: Re: [PATCH] Documentation: propose community voting process Message-ID: In-Reply-To: <20261030180016.GA7582@coredump.intra.peff.net> On Fri, Oct 30, 2026 at 02:00:16PM -0400, Jeff King wrote: > The "X commits and active in the last Y years" one covers you, I think, > but probably excludes Linus (depending on the exact parameters). > > At some point, though, I think there are are always going to be weird > exceptions and it is going to be hard to come up with an algorithmic > rule to get the right set. Perhaps there needs to be some human input > ("we all agree this person is an important part of the community, even > though they do not technically meet the metrics"). If the metric gets us > 99% of the way there, then that keeps the human scaling part down. One counterargument though: is it really that unexpected to eventually exclude people from the voting process if they haven't been active in a long time? I think that the ability to cast an _informed_ vote will quite often require context on how that certain topic has been impacting the community. And sure, a person that hasn't been active in a decade can of course try to discover that context before casting the vote, but that only goes so far. > Of course that opens the can of worms of: how does the human part work. > Which humans? IMHO I would be comfortable with Junio or the PLC just > saying "these people also get a vote" (with probably a big initial list, > and then periodic updates). If we do that it needs to be fully transparent though: who has been added to the list by whom and what is the specific reasoning behind it. But as long as we have that and as long as it's made public well ahead of time so that it can be discussed (and challenged, if needed) I'm fine with such a process. Patrick