[$] Git considers voting to determine its LLM policy
One of the dominant themes of 2026 has been the debate within development projects about the terms under which LLM-written contributions should be…
Why am I seeing this Ranked on source trust — LWN
It ranks mainly on source trust: LWN is the most reliable outlet we track on this subject, and is the only one on the story so far.
Single-sourced. No second organisation has confirmed it yet.
Link-outLink-out, because only one organisation carries it and no first-party source is on it. Link-out means we point at the publisher and say nothing of our own.
| Factor | Weight | Score | Contribution | Where it came from |
|---|---|---|---|---|
| Corroboration | 0.35 | 0.39 | +0.135 25% | 1 independent org on the story. Tier-3 aggregators never corroborate — they can show something is circulating, never that it is true. |
| Source trustleads | 0.25 | 0.85 | +0.212 40% | LWN is the highest-trust source on this story. Trust is taken from the best source, not averaged. |
| Pickup rate | 0.20 | 0.00 | +0.000 0% | One counted organisation, so there is no spread to measure — nothing has picked this up to set a rate. |
| Freshness | 0.20 | 0.92 | +0.183 34% | Halves every 10 hours from the newest item on the story. This is the only factor that rewards a story for nothing more than being recent. |
Corroboration counts distinct organisations, once each, and only from tiers 1 and 2. Freshness halves every 10 hours, so this ranking is a snapshot and will differ at the next build.
林慧 (Wai Lin) https://linuxreviews.org/User:WaiLin · CC BY-SA 4.0 · Wikimedia Commons · illustrativeThe Git project is weighing a formal voting process to settle disagreements over how to handle contributions written by large language models. The topic emerged during the recent Git Contributor's Summit as part of a broader industry debate about whether and under what conditions LLM-generated code should be merged into projects. This would mark a shift for Git, which has not previously used democratic voting to make decisions.
The discussion reflects a wider trend across development communities in 2026 regarding LLM contributions. Projects have grappled with establishing clear policies on accepting such work, with some rejecting it entirely and others setting specific terms. Git's consideration of a voting mechanism suggests the project sees this as an issue requiring broad consensus rather than top-down resolution.
The voting approach represents an unusual governance move for Git. By introducing a democratic process specifically for this decision, the project appears to be treating the LLM policy question as significant enough to warrant a departure from its established decision-making methods. The outcome of any vote could influence how other projects approach similar policy questions.
What happened
One of the dominant themes of 2026 has been the debate within development projects about the terms under which LLM-written contributions should be accepted — if, indeed, they should be accepted at all. The Git project has not been immune to this trend; the topic was discussed at the recent Git Contributor's Summit. In this case, the path to a resolution may be somewhat circuitous; the project, which has never been governed as a democracy, is considering adopting a voting process as a way of bringing the discussion to an acceptable conclusion.
How this story arrived
Ordered by when each source was first observed, which is what the velocity figure is computed from. Publishers backdate; observed order does not.
- 01 Lwn first seen [$] Git considers voting to determine its LLM policy
Overclock clusters coverage from independent sources and grades it automatically. The figures above are computed, not editorial. This page summarises and links to reporting by the outlets named — follow the links for the original work.