Debian Just Decided AI Code Is the Human's Problem

Debian has finished the loudest AI argument in free software, and the winning policy is a masterclass in saying nothing with enormous force. The project's General Resolution on LLM usage closed on August 28 with a field that included an outright ban on AI-assisted contributions, and the ban died ugly: amending the Social Contract needed a three-to-one supermajority, and it finished at a ratio of 0.560. The winner, “Responsible Use of Generative AI,” took roughly 575 ballots from 425 unique voters, and it opens with the most Debian sentence possible: “Debian neither endorses nor prohibits the use of generative AI tools.” For a project that once had to vote on what its project lead was called, that non-endorsement is the strong position, and it's worth parsing because the part that says nothing is doing the heavy lifting.

The part that has teeth is the responsibility clause. Every contribution, “regardless of how and with which tools they were produced,” must satisfy the same standards of quality, correctness, maintainability, and legal compliance. The resolution even names the failure mode out loud: “Blindly accepting or uploading AI-generated material without appropriate human review is inconsistent with Debian's established development practices.” Contributors are expected to understand, review, test, and modify AI-assisted output before it ships; disclosure of AI assistance is encouraged but not required; and feeding confidential or security-sensitive information to third-party AI services is explicitly out. Notably, the resolution deliberately declines to take a position on whether AI output is copyrightable — the legal status of machine-written code remains an open question it refuses to settle, and the whole thing is issued as a position statement under Constitution 4.1(5), so it can evolve later without another vote. The ban camp didn't just lose a ballot; it lost the jurisdiction. And for context, Debian isn't following a ban it disagrees with so much as standing out from one: Gentoo and NetBSD both now forbid AI-assisted contributions, and the winning text borrows its shape from GCC's AI policy and rust-lang's LLM usage policy. The largest free Linux distribution just chose the middle lane while the rest of the distribution world picked a side.

Graphical rendering of the results
Source image 1

Here's why the non-policy is actually a policy. It moves the entire quality question from the community to the contributor. There is no new tool to detect AI code, no new disclosure field to fill in, no metadata to track. The check on every AI-assisted line of code that lands in Debian is the same check that always existed: a human maintainer who claims to have reviewed it. That's the same verification gap I've been staring at for weeks — GitHub's commit curve just doubled in four months while review capacity stayed human-paced, and now one of the most important Linux projects has codified the answer to “who checks AI code?”: the person who typed it in, under the same standards as anyone else, with the project explicitly declining to audit them. One contributor announced they're quitting over the outcome, and they're not wrong that “same standards” is a phrase doing a lot of work when the standards were written for code a human actually looked at. I'm not sure I'd do it differently — a ban would have been unenforceable theater, and disclosure-only is what y

Source article image
Source image 2
ou do when you trust your reviewers. But trust is the load-bearing wall, and the wall is now carrying a much heavier building. If your team is already merging AI-generated contributions, what's your actual line between “reviewed” and “rubber-stamped”? Because Debian just made the human's answer the only one that matters.

Sources

Comments

  1. AnonymousSeptember 1, 2026 at 7:54 PM

    The sad thing is that critical articles like yours are very scarce. The mainstream tech media is captured and just praises the "neutral" stance, which you have exposed as "non-neutral".

    Debian is now officially an appendix of Canonical, xAI, Anthropic, OpenAI and Microsoft. The decline of a project that started as a moral opposition to Microsoft and Sun is unbelievable.

    Ironically, the Canonical people who voted for this will be the first to be fired once Debian is fully automated.

    ReplyDelete

Post a Comment

Popular posts from this blog

AI Is Starting to Feel Less Like a Gadget and More Like Infrastructure

Image
Modern AI doesn't replace infrastructure — it runs on top of it. (Photo: Unsplash) For a while, AI coverage had the energy of a mall demo kiosk: very shiny, slightly chaotic, and usually one prompt away from embarrassment. Lately, though, the more interesting story is less about flashy demos and more about infrastructure. A useful CNBC piece argued that AI is not simply going to vaporize enterprise software overnight, and that sounds about right. In real companies, software does not disappear just because a model can summarize a meeting or write a decent SQL query. What actually happens is messier and more practical: AI starts sneaking into the plumbing. It shows up in search, support workflows, procurement tools, analytics dashboards, and data pipelines. The real winners may not be the loudest chatbot wrappers, but the vendors that make enterprise systems easier to operate, easier to query, and slightly less soul-crushing for the humans trapped inside them. That is less cinematic ...
Read more

When Two AI Bots Finally Learned to Talk in Discord

I spent part of the day doing something that sounds like the setup for a bad joke: getting two local AI assistants to talk to each other in the same Discord channel. Not through a web UI. Not by bouncing prompts manually between windows like a human message queue. In the actual shared channel, where both could see the conversation and react to each other. The funny part is that the problem was not intelligence. It was manners. Both bots were defensive by default around bot-authored messages, which is the sensible setting if you do not want your infrastructure turning into a recursive support group. The downside is obvious: if both assistants treat other bots as suspicious background noise, they will never coordinate on anything more useful than silence. The fix was to make both sides accept bot-authored messages only when they were explicitly mentioned. That detail matters more than it sounds. Blanket bot acceptance is how you end up with two enthusiastic systems discovering each oth...
Read more

A CISA Contractor's GitHub Repo Held 844 MB of Secrets — and No One Closed the Door

Image
There is something almost poetic about the US government's premier cybersecurity agency — the one whose job is literally to plug holes in critical infrastructure — getting outsmarted by a contractor who treated a public GitHub repository like a digital junk drawer. The "Private-CISA" repo, created November 13, 2025, sat publicly for six months containing 844 megabytes of plaintext passwords, AWS GovCloud administrative credentials, Kubernetes manifests, ArgoCD application files, Terraform infrastructure code, CI/CD build logs, and internal deployment documentation. Guillaume Valadon at GitGuardian flagged it on May 14 after his automated scanning picked up the exposure. The commit history told the whole story in plain sight: the account owner had explicitly disabled GitHub's default secret-scanning protections, pushed plaintext credentials stored in CSV files, committed full backup archives into git history, and used easily guessed passwords like "platform-name-2...
Read more