← In the News

Debian opened a two-week ballot on whether agent-assisted contributions are allowed

General Resolution: LLM usage in Debian · Debian Project Secretary · debian.org, voting opened August 15, 2026

Machine-readable Download Markdown

Voting runs from 00:00 UTC today to 23:59 UTC on August 28, after a discussion period that opened July 23 and was extended. Eight options are on the ballot, drafted independently by eight different proposers, which is why they do not read as variants of each other.

The spread is wide. Choice 1 amends the Social Contract to forbid contributions written with LLM assistance outright. Choice 2 permits them under six conditions, including disclosure via a Git trailer such as Generated-By: or Assisted-By:. Choice 5 declines to endorse or prohibit and encourages but does not require disclosure. Choice 8 opposes LLM use principally on climate grounds while conceding it "is just a position statement."

The majority requirement is asymmetric: Choice 1 needs a 3:1 supermajority because it amends the Social Contract, and every other option needs a simple majority. None of the options restrict upstream projects Debian packages. Choice 7 states that it "does not cover indirect contributions, i.e. those originating from upstream works," so a kernel or toolchain that accepts agent-assisted patches is not in scope.

Choice 7 draws the line that will matter most to people who already work this way. It disallows generative AI output as a direct contribution while explicitly not restricting contributors from consuming such output when contributing: use the agent to explore, research and critique, but the text you submit is yours. Its acknowledgements name GCC's AI policy and rust-lang's LLM usage policy as its inspirations.

Why it matters: Debian is the first large distribution to put the question to a binding vote with the alternatives written out rather than argued about. If you contribute to Debian and use agents, the outcome decides whether you disclose, refrain, or carry on. The disclosure mechanics being proposed, a commit trailer and an accountability clause naming the submitter, are the shape other projects will copy either way, and the asymmetric majority bar means the outright ban is the hardest of the eight to pass.