{"slug": "debian-developers-are-voting-on-eight-ai-rules", "title": "Debian developers are voting on eight AI rules", "summary": "Debian's developers are voting on eight proposals that would ban, limit, disclose, or permit LLM-assisted contributions to the project, with the vote extended to August 26, 2026, by Debian Project Leader Sruthi Chandran. Fewer than 350 ballots had been received when the count was checked, and only recognized Debian developers can participate. The proposals range from an outright ban (Proposal A) to permissive rules requiring disclosure and accountability (Proposals B, D, E), with Debian 13 containing 69,830 packages, 403 GB, and 1,463,291,186 lines of code.", "body_md": "• 5 min read\n\n# Debian developers are voting on eight AI rules\n\nDebian’s developers are choosing among eight proposals that would ban, limit, disclose or permit LLM-assisted contributions to the project.\n\nImage: [The Register](https://www.theregister.com/ai-and-ml/2026/08/26/debian-polls-its-developers-on-whether-to-burn-the-bots-tame-the-bots-or-let-em-loose/5292270)\n\nDebian’s developers are voting on whether AI-assisted work belongs in the project at all—and the ballot offers eight different answers, from an outright ban to rules designed to make contributors fully accountable for machine-assisted patches.\n\nThe General Resolution on LLM usage in Debian is still open on August 26, 2026, after Debian Project Leader Sruthi Chandran extended the deadline by one week. Fewer than 350 ballots had been received when the vote count was checked, and only recognized Debian developers can participate.\n\nThe debate involves a large codebase where a policy cannot be applied informally. Debian 13 contains 69,830 packages, occupying 403 GB and comprising 1,463,291,186 lines of code. Any rule would have to cover everything from handwritten patches and documentation to bulk changes, generated text and automated maintenance work.\n\nThe ballot also has an unusual structure. Proposal A requires a three-to-one majority; the other seven proposals need a simple majority. The proposals overlap, however, and several differ more in emphasis than in outcome.\n\n## Eight proposals, from prohibition to disclosure\n\nProposal A would explicitly forbid contributions written with or assisted by large language models or other generative AI tools. Its stated goal is to prohibit LLM involvement in contributions to Debian rather than merely regulate how contributors disclose it.\n\nProposal C takes a similarly hard line, calling for Debian to reject LLMs “as far as practical.” Proposal G is narrower: it would require contributions directly to Debian to be created by humans, while allowing developers to use LLMs in other parts of their work. Under that approach, generated output could help with surrounding tasks but could not be submitted as the direct contribution.\n\nProposal F takes a less absolute position, encouraging contributors to avoid generative AI where practical. Proposal H focuses on environmental cost instead of authorship or licensing. It describes LLM usage as accelerating damage to the planet and treats that impact as a deal-breaker. The proposal does not distinguish between local models and cloud services, even though their operational resource use can differ; the text instead centers on the broader environmental cost of LLM development and use.\n\nThe permissive proposals put the burden on the person submitting the work. Proposal B would allow LLM-assisted contributions if they satisfy six conditions: legal compatibility, licensing and attribution, contributor accountability, disclosure, prior discussion of bulk or automated changes, and confidentiality and privacy.\n\nProposal D argues that LLM use is already happening and cannot be effectively banned. It would permit the practice while requiring contributors to describe their work clearly, comply with the Debian Free Software Guidelines and accept responsibility for the result. Proposal E follows a similar model, explicitly leaving the contributor responsible for a contribution’s technical quality, legal acceptability and suitability for Debian.\n\n“responsibility for every contribution rests with the contributor who submits it, who remains accountable for its technical quality, legal acceptability, and suitability for inclusion in Debian.”\n\nProposal A’s preamble makes the opposing position equally direct:\n\n“This proposal aims to expressly forbid any contributions to Debian written with the use or assistance of large language models (LLMs) or other generative AI tools.”\n\n## The hard part is enforcement, not wording\n\nThe ballot raises a practical problem for any open-source project trying to regulate generated code: a prohibition can define an acceptable principle without providing a reliable way to determine how a patch was produced. The more limited proposals therefore shift the policy from detecting AI output to assigning responsibility, requiring disclosure and reviewing the contribution under Debian’s existing technical and legal standards.\n\nThat still leaves unresolved questions. The source material does not establish how Debian would verify disclosures, handle contributors who do not disclose LLM assistance, or distinguish a generated patch from code that was merely reviewed or explained by an LLM. Proposal B addresses confidentiality and privacy, but the ballot does not provide a technical mechanism for proving that sensitive project material was not sent to an external service.\n\nThe number of choices may itself make a decisive result less likely. Proposal A needs a three-to-one majority, while the other options divide the less absolutist positions across several overlapping formulations. A contributor who wants restrictions but not a total ban could reasonably fit Proposal B, D, E, F or G, making the final mandate dependent on how those votes aggregate rather than on a single clearly opposed pair of policies.\n\n## Debian is not deciding in isolation\n\nOther free and open-source projects have already taken positions. Gentoo prohibited LLM-assisted contributions in April 2024, and NetBSD followed with a similar policy. OpenBSD has said that AI-generated code cannot be copyrighted and therefore cannot be committed, although it grandfathered code from the Tmux project, whose contribution policy permits LLM-assisted work. That exception illustrates how difficult it is to apply a simple authorship rule across inherited code and external projects.\n\nFreeBSD previously indicated that it did not want AI-generated code, but its official guidance had not been updated with an explicit policy. Linux has not adopted an anti-AI position, while Red Hat has embraced AI-assisted development. Those decisions limit how much control any individual distribution has over the wider software supply chain, even if it can impose rules on contributions made directly to its own repositories.\n\nDebian’s vote is therefore less a referendum on whether LLMs exist than a choice about where to put the boundary: at the tool itself, at generated output, or at the contributor’s legal and technical accountability. The vote remains open for several days, and its outcome will depend on whether Debian’s developers can turn eight overlapping positions into one policy the project can actually administer.\n\n[Tomas Berg](/authors/tomas-berg/)\n\nComputing Editor\n\nTomas lives in the terminal. He covers chips, laptops, and operating systems with a focus on performance and efficiency. He reads kernel changelogs the way other people read fiction, and he's always on the hunt for the perfect mechanical keyboard switch. If it processes data, Tomas has an opinion on it.", "url": "https://wpnews.pro/news/debian-developers-are-voting-on-eight-ai-rules", "canonical_source": "https://forgeeks.net/debian-llm-contribution-vote/", "published_at": "2026-08-26 17:24:44+00:00", "updated_at": "2026-08-26 17:44:55.583169+00:00", "lang": "en", "topics": ["artificial-intelligence", "ai-policy", "ai-ethics", "generative-ai", "large-language-models"], "entities": ["Debian", "Sruthi Chandran", "The Register"], "alternates": {"html": "https://wpnews.pro/news/debian-developers-are-voting-on-eight-ai-rules", "markdown": "https://wpnews.pro/news/debian-developers-are-voting-on-eight-ai-rules.md", "text": "https://wpnews.pro/news/debian-developers-are-voting-on-eight-ai-rules.txt", "jsonld": "https://wpnews.pro/news/debian-developers-are-voting-on-eight-ai-rules.jsonld"}}