Debian is using its most formal procedure to settle a question that has been argued for over a year: can contributions written with LLM assistance enter the distribution? On July 23, a General Resolution titled “LLM usage in Debian” entered its discussion period. Voting is scheduled for August 15 through 28. The General Resolution is a rarely used, charter-level instrument in Debian — its most famous outing was the init system debate. This time the protagonist is generative AI.
Eight Options Plus “None of the Above”
This ballot is not two extremes dueling. It carries eight proposals plus “None of the above,” spanning the full range from outright prohibition, to disclosure requirements, to explicit welcome. Votes are tallied with the Condorcet (Schwartz) method, so voters rank their preferences instead of being forced to pick a side. The proposals came out of the debian-vote mailing list, and several drafters are among the project’s most senior developers.
Three Representative Proposals
Proposal one, drafted by Matthias Geiger, takes the hardest line: amend the Social Contract to expressly forbid any contribution written with LLM assistance. The scope covers package source, Debian’s own software, web resources, documentation and translations, and official communication. Because it touches the Social Contract, it needs a 3:1 supermajority to pass. The rationale lists four concerns: unclear copyright status, unverifiable quality and accuracy, reviewer burnout, and the DoS-like strain LLM crawlers have placed on Debian’s infrastructure.
Proposal two, drafted by Lucas Nussbaum, would allow AI-assisted contributions under conditions: tool terms must not conflict with Debian’s use; contributors carry full accountability; disclosure is required when a significant portion is AI-generated, for example via a Generated-By: trailer in the git history; bulk or automated changes need prior discussion on the lists; and confidential data must not be sent to untrusted AI providers.
Proposal three, drafted by Ian Jackson, asks contributors to reject LLMs as far as practical and adds a Code of Conduct supplement: messages addressed to humans must be drafted solely by humans without LLM assistance, any LLM use must be disclosed, per-project bans must be respected, and violations are treated as conduct breaches.
Between proposal three and the permissive end of the ballot sit five more options, including a middle-ground choice titled “Responsible Use of Generative AI.” That spread is deliberate. Debian’s process forces the project to enumerate positions rather than collapse the argument into a binary, and the Condorcet tally then finds whichever option beats every alternative head-to-head. For a question where nearly everyone holds a “but” — yes, but ban it; no, but disclose it — ranked ballots are a better fit than a yes/no referendum.
Why Debian Cares So Much
On the surface this is a philosophical fight. Underneath it is reviewer bandwidth. Debian’s packages are maintained by volunteers, and low-quality AI-generated bug reports and patches land directly on their desks — proposal one even cites cases from other projects where AI contributions pushed maintainers out. The other side argues that AI assistance is already everyday practice, and that pretending otherwise helps nobody; better to make the responsibility and disclosure rules explicit. The proposal texts cite plenty of precedent: the GNOME Loupe contribution dispute, Gentoo’s AI policy, Codeberg’s related changes, and the AI usage policies GCC and Rust have each published.
What makes Debian’s answer unusual is the instrument. Most projects settle this in a maintainer meeting or a README. Debian is settling it in its constitution, where the result binds the whole project and can only be overturned by another vote. That is slower, louder, and much harder to quietly walk back — which is exactly why the rest of the open-source world is watching the discussion thread.
Timeline and Thresholds
The discussion period runs through August 13; voting opens August 15 and closes August 28. Proposal one needs a 3:1 supermajority because it amends the Social Contract; the other options need a simple majority, and every option must clear Debian’s quorum requirements against “None of the Above.” Amendments can still land during the discussion window, which is one reason the ballot grew to eight choices in the first place.
Whatever the outcome, Debian will be the first major distribution to define a formal, project-wide stance on LLM contributions through its governance process. For open-source communities still stuck at the “each maintainer decides” level, the ballot design and the debate record are a ready-made reference.
Sources
- Debian — General Resolution: LLM usage in Debian
- Proposal-one — no LLM contributions via the Social Contract
- Proposal-two — AI-assisted contributions with conditions
- Proposal-three — reject LLMs, update the Code of Conduct
AI-assisted summary compiled from the sources above, reviewed by a human before publishing.