Debian developers vote on eight rival proposals for LLM-generated contributions

Debian opens a general resolution on LLM use

The Debian project is polling its developers on whether generative AI should have any place in the distribution's contributions. According to The Register, the ballot — formally a general resolution on LLM usage in Debian — is the project's second vote of 2026, and Project Lead Sruthi Chandran has extended the deadline by an extra week. Chandran was herself elected in March, in the year's first poll.

The scale of the decision matches the scale of the project. The Register points to the Debian 13 release announcement, which counts 69,830 packages, 403 GB of disk space and roughly 1.46 billion lines of code.

Eight options on a single ballot

The ballot text runs past 5,000 words and presents eight proposals, each seconded by between six and 17 developers. Proposal A, which would expressly forbid contributions written with or assisted by LLMs under the Debian Social Contract, must clear a 3:1 majority; the other seven need only a simple majority.

• Proposal B would allow LLM-based contributions that meet six conditions covering legal compatibility, licensing and attribution, accountability, disclosure, prior discussion of bulk or automated changes, and confidentiality and privacy.
• Proposal C calls for rejecting LLMs wherever practical and updating the project's code of conduct. It is backed by Ian Jackson, the veteran Debian developer who wrote the dpkg package manager.
• Proposal D takes a pragmatic line, arguing that AI assistance is already in use, that a ban would be counter-productive and unenforceable, and that responsibility should rest with contributors, whose work must be clearly described and comply with the Debian Free Software Guidelines.
• Proposal E similarly leaves accountability with the contributor, who remains answerable for the technical quality, legal acceptability and suitability of what they submit.
• Proposal F adopts a cautious posture and encourages contributors to avoid generative AI where practical.
• Proposal G requires that direct contributions be created by humans, barring generative AI output from being submitted directly while permitting LLM tools in supporting roles.
• Proposal H singles out environmental cost, arguing that LLM usage accelerates the destruction of the planet and that this alone justifies avoidance. The Register notes it does not distinguish between local and cloud-hosted models, while suggesting the training process dominates the environmental impact either way.

Only recognized Debian developers are eligible to vote, and The Register reports that fewer than 350 ballots had arrived at the time of writing. The outlet is sceptical of the format: with eight heavily overlapping options, it doubts Proposal A can reach its supermajority, and it argues the positions would have been better consolidated into a few clear, mutually exclusive choices.

Other projects have already picked a side

Gentoo banned LLM-generated contributions in April 2024, and NetBSD followed soon after, The Register reports. OpenBSD's stance is that AI-generated code cannot be copyrighted and therefore cannot be committed, although the project continues to take code from the Tmux project, which permits LLM-assisted contributions. FreeBSD signalled in September 2025 that it does not want AI code, but its official guidance has not been updated; The Register believes an internal debate, possibly including a Debian-style ballot, is underway, and says the project's leadership had not responded to a request for comment.

The Register also questions how much any single distribution's policy can achieve in practice. The Linux kernel is officially not an anti-AI project, and Red Hat — an IBM subsidiary whose code ships in most distributions — is fully committed to AI tooling.

Why it matters

Debian is one of the largest volunteer-run projects in open source, and this vote forces it to take a position on unsettled questions that affect everyone: the copyright status of machine-generated code, who is accountable when a contributor submits model output, how disclosure should work, and whether the environmental cost of training and running large models is an acceptable price. The Register suggests other projects may yet follow Debian's lead, and the apparent internal debate at FreeBSD indicates the pressure is already spreading. The vote is also a stress test of Debian's own governance: with eight overlapping options and a supermajority requirement attached to the strictest one, the project risks emerging without a decisive mandate no matter which camp wins.