Eight Answers, Not Two
On July 23, 2026, the Debian Project opened
General Resolution vote_002: LLM usage in Debian.
Six proposals were on the table by August 10, and two more arrived before the extended
discussion period closed on August 13, 2026 — putting eight competing
options (plus "None of the above") on the final ballot, ranging from a
Social Contract prohibition to an explicit statement that the project neither endorses
nor forbids generative AI.
That number is the story. Every other project this site has documented produced exactly one answer. Gentoo banned AI in a single council vote. NetBSD classified it as tainted code in a silent commit. libvirt copied QEMU's ban in a day. Debian took three weeks and generated a spectrum.
The more interesting finding is that the spectrum was not there at the start. It was manufactured by the argument itself — and not in the direction most people would guess.
The Ballot
| Option | Proposer | Position |
|---|---|---|
| A (Choice 1) — Forbid LLM contributions | Matthias Geiger | Social Contract amendment (3:1 supermajority); prohibition with carve-outs for upstreams, AI software, and security patches |
| B (Choice 2) — Allow AI-assisted contributions | Lucas Nussbaum | A position statement that can evolve without a further GR |
| C (Choice 3) — Reject LLMs as far as practical | Ian Jackson | Rejection in principle, conceding that a complete ban is impossible because upstreams disagree |
| D (Choice 4) — Accept AI for Debian-specific work | Pierre-Elliott Bécue | Contributor responsibility with guidelines, scoped to Debian's own work and not upstream |
| E (Choice 5, Winner) — Responsible use of generative AI | Marc Haber | Neither endorses nor prohibits; notes productivity gains for volunteers with limited time and places accountability on the human submitter |
| F (Choice 6) — A cautious approach | Tobias Frost | Encourages avoiding AI "where practical" while relying on contributor judgement rather than rules |
| G (Choice 7) — Debian is created by humans | Gard Spreemann | Disallows LLM output as direct contributions to Debian (inspired by GCC and Rust policies), while allowing assistive use for research/analysis |
| H (Choice 8) — Avoid the use of LLM: climate destruction is a deal breaker | Holger Levsen | Position statement condemning LLM resource/ecological impact and encouraging contributors to avoid LLMs where practical |
The rationales are worth reading against each other. Proposal A argues that LLM usage "comes from the 'move fast, and break things' attitude" that is "contrary to what makes Debian Debian." Proposal C opens with a list of objections — "environmental damage; exploitation of authors; disruption to open web hosting by aggressive scraping; generation and promulgation of bullshit, polluting the information commons" — then concedes that "a complete ban on LLM output" is not achievable because upstreams take a different view.
Proposal D grants the same premise and draws the opposite conclusion: banning AI "seems counter-productive and unenforceable," so the project "chooses to place responsibility on contributors." Proposals B, E and F all invoke Constitution section 4.1(5) to issue a position statement rather than a rule — explicitly designed, in B's words, so that the position "may evolve as time passes without the need to resort to future general resolutions."
How the Ballot Grew
Every proposal and every second is a timestamped message in the debian-vote archive, so the shape of the deliberation is fully recoverable. Ordering the options by first appearance:
| # | Option | Camp | First message |
|---|---|---|---|
| 1 | A — Forbid | Restrictive | 07/msg00001 |
| 2 | B — Allow | Permissive | 07/msg00019 |
| 3 | D — Debian-specific | Middle | 07/msg00090 |
| 4 | C — Reject as practical | Restrictive | 07/msg00119 |
| 5 | E — Responsible use | Permissive | 07/msg00286 |
| 6 | F — Cautious | Middle | 07/msg00344 |
Proposal A's text link points to msg00117, later than its first
seconds. That is Geiger re-posting the proposal PGP-signed after the Project Secretary
asked for a signature — a procedural repost, not a change of position. A was genuinely
first.
The two poles came first and the middle came last. But the path between them was not a gradual convergence.
Polarisation, Then Moderation
Counting signatures — proposer plus seconds — by the window of the archive in which they landed:
| Window | Restrictive | Middle | Permissive | On the table |
|---|---|---|---|---|
| Jul, msg 1–99 | 5 | 1 | 6 | A B D |
| Jul, msg 100–199 | 11 | 5 | 2 | A B C D |
| Jul, msg 200–408 | 1 | 5 | 10 | C D E F |
| August | 0 | 2 | 1 | E F |
The middle phase is a hardening. When Ian Jackson's Proposal C arrived at
msg00119, the restrictive camp collected eleven signatures across a hundred
messages while the permissive side managed two. Read at that moment, Debian looked like a
project heading decisively for a ban.
Only afterwards do E and F appear, and the balance inverts. Moderation on this ballot was not the poles quietly converging — it was a reaction to polarisation, arriving late and winning on volume.
Fifty-Six Signatures, Thirty-Nine People
The six options carry 56 signature slots but only 39 distinct people. Sixteen of the 39 backed more than one option, and six backed options in opposing camps.
Grouping the 39 by the camps they signed for:
- Permissive only — 16 people
- Restrictive only — 11 people
- Middle only — 6 people
- Signed across camps — 6 people
That last row is the reason these numbers should not be read as a poll. In Debian, a second means "this option belongs on the ballot," not "I endorse this option." Pierre-Elliott Bécue seconded Proposal A — the outright ban — and proposed Proposal D, which accepts AI contributions. Johannes Schauer Marin Rodrigues cast the very first signature on the ballot, for A, and later seconded the middle option D.
Individual movement runs in both directions and is modest in size. Lucas Nussbaum proposed
the permissive B, then seconded both E and F. Tiago Bortoletto Vaz seconded the middle
option D at msg00154 and the restrictive C at msg00247.
Why the Interesting Question Cannot Be Answered
A natural hypothesis about a fight like this is that positions track livelihood — that contributors paid by companies to ship software favour AI assistance, while hobbyists, academics and independent consultants oppose it. The public record does not support it.
The permissive Proposal B was authored by Lucas Nussbaum, an associate professor at the Université de Lorraine and a former Debian Project Leader, and seconded by Stefano Zacchiroli, a full professor at Télécom Paris and a three-time former DPL. The outright ban was seconded by David Bremner, a professor of computer science at the University of New Brunswick. The restrictive Proposal C was proposed by Ian Jackson, who spent years employed at Citrix working on Xen. Academics sit on every part of this ballot.
Some cases do fit — Enrico Zini, a freelance consultant, signed only restrictive options, and Julian Andres Klode of Canonical signed only permissive ones. But the confirming cases are the easy half to collect, and the disconfirming ones sit at the top of the ballot.
There is a harder obstacle. Debian's 2022 General Resolution on voting secrecy established that "the identity of a developer casting a particular vote is not made public." The tally published after August 28 will show how the options ranked, and nothing about who ranked them. The 39 people above are the only contributors whose position is public at all — against a current developer count of 1,039 recorded at the 2026 DPL election — and they self-selected by being willing to sign a ballot option. For scale, that election drew 339 ballots, so even turnout leaves most of the electorate silent in public.
Any analysis of who supports what in Debian is therefore an analysis of signature-givers, not of the electorate. It is also sensitive to when someone appeared: a person's camp partly reflects which options existed on the day they read the thread.
What Debian Is Doing Differently
Set against the other cases documented on this site, three things stand out.
The process can express gradations. Debian's Standard Resolution Procedure is Condorcet-based — "each voter's ballot ranks the options being voted on. Not all options need be ranked" — with the winner determined from a Schwartz set over pairwise defeats. A developer who prefers caution to prohibition but prohibition to permission can say exactly that. A council voting yes or no on a single motion cannot represent that view at all. Six options exist because the mechanism can carry six options.
Three of the six deliberately avoid making a rule. Proposals B, E and F all issue position statements under Constitution section 4.1(5) specifically so the project's stance can move without another GR. That is a governance choice about revisability, and it is the same instinct visible in GCC booking a policy review for early 2027 rather than settling the question permanently.
The disagreement is public and dated. Every position, every second and every revision is in a public archive with a message number. That is what made the analysis above possible, and it is precisely what is missing from the projects that decided this in a private meeting or a silent commit.
None of this guaranteed a good outcome in advance: Proposal A was on the ballot with eight seconds, and two more restrictive proposals (G and H) joined before discussion closed on August 13. But the project reached its decision through a process that recorded the disagreement rather than compressing it.
The Result: Choice 5 ("Responsible Use") Wins Decisively
Voting ran from August 15 to August 28, 2026, drawing 425 unique voters out of 1,045 eligible Debian Developers (a 40.7% turnout — noticeably higher than the 339 ballots cast in the 2026 DPL election). On August 30, 2026, Project Secretary Kurt Roeckx published the official results: Choice 5 (Proposal E: "Responsible Use of Generative AI", proposed by Marc Haber) won outright as the sole member of the Condorcet Schwartz set, defeating every other proposal in head-to-head comparisons.
- Proposal E (Choice 5 — Responsible Use of Generative AI) passed majority with the highest ratio on the ballot (281 to 126 over "None of the above", a 2.23 ratio) and beat every competing option pairwise: Choice 2 by 203–148, Choice 4 by 232–115, Choice 6 by 210–130, Choice 7 by 251–139, and Choice 8 by 244–154.
- Both hard-line ban proposals failed even a simple majority against "None of the above": Proposal A (Choice 1 — Social Contract ban, which required a 3:1 supermajority) was rejected 144 to 257 (0.560 ratio), and Proposal C (Choice 3 — Reject LLMs as far as practical) was rejected 176 to 230 (0.765 ratio).
- The position-statement options outranked the restrictive ones across the board: Choices 5, 2, 6, and 4 all comfortably cleared majority and defeated Choices 7 ("Debian is created by humans") and 8 ("Avoid the use of LLM: climate destruction is a deal breaker") in every pairwise matchup.
The adopted statement declares that Debian "neither endorses nor prohibits the use of generative AI tools in the development, maintenance, or documentation of software, packaging, documentation, and other media published within the Debian Project," recognizes that such tools "can substantially improve the productivity of contributors when used responsibly," encourages (but does not mandate) disclosure, and places full responsibility for quality, licensing compliance, and human review on the submitting contributor.
September 2026 Epilogue: The Debian Inference Portal
Less than a month after the vote, on September 23, 2026, Lucas Nussbaum (proposer of Option B and a seconder of the winning Option E) announced the launch of the Debian Inference Portal — a project service giving Debian Developers and Debian Maintainers free, self-service API access to shared open-weight LLM inference (initially hosting DeepSeek V4 Flash and GLM-5.2, sponsored by European cloud provider Scaleway) for packaging, bug triage, tooling, and documentation. Rather than banning the tools or leaving developers reliant on US hyperscalers, Debian voted for human accountability and then provisioned shared infrastructure for its volunteers.
Primary Sources
- Debian: General Resolution — LLM usage in Debian (full ballot, proposal texts, tally and Condorcet matrix)
- debian-devel-announce: General resolution: LLM usage in Debian: Results (August 30, 2026)
- debian-devel-announce: New service: Debian Inference Portal — shared LLM inference for Debian contributors (September 23, 2026)
- debian-vote archive, July 2026 (proposals and seconds)
- debian-vote archive, August 2026
- Debian: General Resolution on voting secrecy (2022) — establishes secret GR ballots
- Debian Constitution (section 4.1(5) position statements; Condorcet vote counting)