Debian votes: AI-assisted code welcome, but maintainers still own the work

The Debian Project has settled its ongoing debate over generative AI with a policy that is notable for what it does not do: it neither blesses nor bans the use of AI tools in maintaining the distribution. The resolution, discussed at length on LWN, acknowledges that AI can make volunteers more productive, but it firmly places the burden of quality on the contributor, not the tool.

At the core is a principle that will feel familiar to anyone who has reviewed code: using an AI does not absolve you of responsibility. The policy expects every contribution, human-written or AI-assisted, to meet Debian’s standards for correctness, maintainability, and legal compliance. That means understanding what the tool produced, testing it, and modifying it before submitting a patch.

Community reaction suggests this was a hard-fought compromise. As one commenter put it, "extremist positions soundly defeated"—the final text strikes a balance between those who wanted to restrict AI outright and those who wanted no policy at all. The vote was conducted using the Condorcet method, and the result was far from unanimous. Comments also wandered into broader concerns, from the energy demands of AI hardware to whether home GPUs with 64–128 GiB of memory would be affordable were it not for the AI boom.

For Debian maintainers, the practical effect is subtle but important. The policy doesn’t give anyone else new authority to reject AI-generated changes; the existing maintainer review process stands. As one maintainer noted, the only body that can force a maintainer to accept a patch is the Technical Committee, and that remains a high bar.

This is a stance worth watching, not just for Debian but for open source generally. It offers a template for how a project can acknowledge the reality of AI tooling without turning every patch into a philosophical debate. The key question—can a community preserve trust in contributions when the author may not have written every line?—is answered here with a simple contract: the contributor vouches for the work, no matter who wrote it.