Debian Votes on Banning AI-Generated Code

Debian, one of the oldest and most widely used Linux distributions, has entered a formal process that could end in a total ban on AI-assisted contributions. On July 24, 2026, the official discussion period opened for a General Resolution on the matter, with developers choosing among four mutually exclusive regulatory options.

Four Proposals on the Table

The toughest option, put forward by Matthias Geiger together with Jesse Rhodes, would write into Debian's Social Contract a ban on direct contributions written with the help of language models. It would cover source packages, packaging work, the project's official web resources, documentation and translations, but would not apply to upstream projects that use AI themselves, nor to externally sourced security patches.

Opposing it is Lucas Nussbaum's proposal, which replaces a ban with a disclosure regime: AI-assisted contributions would be allowed as long as the author clearly discloses it, maintains license compliance, takes full responsibility for code quality and consults the rest of the team on large-scale changes. The two remaining proposals, from Ian Jackson and Pierre-Elliott Becue, fall somewhere between these poles, combining a recommendation of caution with concrete guidelines on compliance with the Debian Free Software Guidelines (DFSG) and on protecting sensitive data from being sent to external AI services.

The Case for a Ban

Supporters of a ban point to four main concerns. The first is legal status: it is unclear who holds copyright, if anyone, over code generated by a language model and under what terms, which is a fundamental problem for a project building an operating system on clearly defined licenses. The second concern is the technical quality of such contributions, which do not always meet the project's standards.

The third argument is maintainer fatigue, since package maintainers would have to review a growing number of submissions of uncertain reliability. The fourth is ethical, covering the use of publicly available code to train models without authors' consent, and the computing resources such tools require to run. Critics of the ban counter that fully enforcing such a rule is practically impossible, and that the real problem is submission quality, not the tool itself.

Linux Takes the Opposite Path

The Debian debate is unfolding in the shadow of a much louder dispute that has played out around the Linux kernel in recent months. Linus Torvalds, the project's creator, firmly rejected calls to restrict AI tools in kernel development, including the Sashiko bot that analyzes submitted changes, and pushed through a policy that explicitly allows AI-assisted contributions, provided they are marked with an "Assisted-by" tag instead of the legally binding "Signed-off-by".

Linux is not one of those anti-AI projects, and if that bothers someone, they can do what open source ethics dictates, which is fork it - Linus Torvalds, creator of the Linux kernel

The contrast shows how far approaches within the open source ecosystem itself have diverged. The Linux kernel, developed with heavy involvement from major hardware and cloud vendors, is betting on pragmatic use of AI with minimal oversight. Debian, maintained largely by volunteers and built around an identity rooted in software freedom, is considering exactly the opposite direction.

What Comes Next

The formal discussion period on the four proposals will run for several more weeks before the project moves to the actual vote, in which Debian developers will rank the options by preference. An earlier, less formal attempt to work out a similar policy within the project ended without a decision, so it is not certain that a majority will form behind any of the options this time either.

The outcome matters beyond Debian itself. The distribution underpins Ubuntu and dozens of other systems, and its packaging and maintenance policies are often treated as a reference point for smaller free software projects. A decision to ban or allow AI could therefore become a template repeated elsewhere, regardless of which way the vote goes.

For Polish developers packaging software for Debian or maintaining derivative distributions, this means keeping an eye on the outcome and potentially adjusting how they work with tools such as coding assistants or review bots, should the project opt for hard restrictions.