Debian maintainers are considering banning AI contributions altogether

Debian is weighing four proposals ranging from banning AI-assisted contributions entirely to allowing them with strict safeguards.

Debian is a pretty popular Linux distribution that has been actively supported by developers and maintainers for over 30 years. It is the second most-used distro after Ubuntu, and powers a lot of servers and personal devices across the world. As the Linux and open-source community (and perhaps, even the world) continues to wrestle with the idea of AI-assisted coding in enterprise environments, Debian Project is considering four proposals which aim to restrict or block AI usage in contributions altogether.

Proposal A is attempting to ban AI-assisted Debian contributions altogether, across software as well as documentation. Upstream patches are projects are out of scope, though. The rationale behind this decision not only revolves around the questionable legality of AI outputs, but also the community's belief that Debian has a reputation to maintain when it comes to stability, whereas LLM contributions typically accelerate development without caring about bugs or regressions. While enforcement is a challenge, the Debian community wants this to be a statement of intent that expresses its strong position on this topic.

Proposal B allows AI-assisted contributions, under certain conditions. It admits some of the drawbacks of AI explained in Proposal A, it says that this technology could ultimately contribute to the betterment of the project. As such, it allows AI usage as long as there is accountability, proper disclosure, legal compatibility and licensing, and prior discussion around bulk or automated changes.

Proposal C is similar to Proposal A wants to "reject LLMs as far as practical." What this means is that maintainers should make all possible effort to discourage AI usage, even in upstream projects. A contributor who does not use English as their first language should communicate in their native language and rely on readers to leverage translation tools rather than generating an English-based message using an LLM. This proposal acknowledges that "practicality is a judgement call and we recognise that it will involve uncomfortable compromises."

Finally, Proposal D understands that AI in coding is here to stay, regardless of what anyone feels about it. It believes that banning AI is counter-productive and cannot be enforced. As such, it allows AI-assisted contributions under the following conditions:

• All code and work assisted by a generative AI agent or tool must comply with the DFSG.
• The submitter is solely responsible for the submitted work and:
  • they sufficiently evaluated and properly understand the work they intend to submit, and are able to explain and defend it;
  • they put any potential Signed-off-by tag and GPG signatures on the contributions they send to the Debian infrastructure (package, commit, mail, …) themselves;
  • any content uploaded that would end up in production on Debian infrastructure (main git branch, package upload) has been submitted by them explicitly.
• Work assisted by a generative AI agent or tool should be marked as such in the adapted place (commit message, changelog, …). Some lightweight generative tools, such as tab-completion in Copilot, may be used without the contributor realising they rely on generative AI models; we therefore trust submitters to assess when this rule applies. When in doubt, add such marking;
• No cloud-based AI shall be used when the data transmitted could either be sensitive to the project (personal data, information under embargo, …) or not public (debian-private discussions, …).

This entire topic is certainly fascinating and may set precedents for other Linux and open-source communities too, once a decision is reached. People hold varying views over this subject. For example, Linux head honcho Linus Torvalds leverages AI tools himself and regularly criticizes the anti-AI crowd. It will be interesting to see what the Debian community ends up on choosing.

Source

Hope you enjoyed this news post. Feedback welcome.

Posted Monday 27 July 2026 at 8:19 am AEST (my time).

News posts: 2023 5,800+ | 2024 5,700+ | 2025 5,700+ | 2026 (to end of June) 2,475

RIP Matrix