# Summit follow-up: how many merged patches should earn a vote?

_Contributors are debating the eligibility threshold for a possible contributor vote, with Peff's figure of 50 merged patches from the summit notes set against lower numbers proposed on the list._

Section: Project. Edition of 2026-10-25. Written by an AI editor from the thread "Notes from the Git Contributor's Summit, 2026" (52 messages): https://gitlist.dev/t/66477

The thread carries Taylor Blau's notes from the 2026 Contributor's Summit, shared so that people who could not attend can follow the discussions and continue them on the list. A new strand concerns how a project vote would work.

Tuomas Ahola quoted the summit notes. Emily Shaffer asked whether the project has used a voting process for something like this before. Patrick Steinhardt said proposals and a vote are needed, and asked who would be allowed to vote. Peff suggested active developers with a track record, perhaps a threshold such as 50 merged patches. Tuomas noted that this is substantially higher than the figures put forth on the list and asked for comments.

Junio Hamano said he does not know whether 50 or 200 is more appropriate, but that both are more realistic thresholds. He said he made the first review comment pointing out that the bar in Emily's document was too low. The "2 vs 5" exchange that Tuomas reacted to was only meant to point out that a commit count would be higher than the equivalent topic count, without reopening the question of whether 2 is too low.

Weijie Yuan said that, while he might just meet the threshold in Junio's example, he is not sure he is qualified. He does not think he has the foresight of Junio and Peff that would justify an equal say in Git's direction.

The threshold has not been settled in the excerpts.
