Debian’s proposed LLM ban exposes a harder question: what counts as assistance?
A Debian General Resolution proposal would forbid LLM-assisted direct contributions, from packages to documentation and translations. The proposal is not a decision, and its breadth immediately forces a boundary problem: analysis, bug-finding, and generated text do not look alike.
The proposal argues that uncertain licensing, error-prone output, reviewer burden, and scraping-driven infrastructure costs conflict with Debian’s stability and community values. It excludes upstream projects using LLMs, but would cover Debian’s own software, web resources, documentation, and translations.
HN’s most useful response was practical: instead of asking whether a tool was involved, ask what a maintainer is personally prepared to certify and support.
A proposal, not a settled Debian policy
Matthias Geiger’s General Resolution proposal would expressly forbid direct Debian contributions made with LLMs or other generative AI. Its scope includes source packages, official project software, web resources, documentation, translations, and official communication; it explicitly excludes upstream projects that use LLMs.
The rationale has four parts: copyright and licensing uncertainty, quality failures in packaging and documentation, review burden on a volunteer community, and the web-infrastructure costs associated with large-scale training crawls. It presents the restriction as a way to preserve Debian’s stability and social contract, while admitting that enforcement would be a challenge and would rely on good faith.
The definition is the real vote
HN readers quickly identified the ambiguity. Is asking a model to locate a bug assistance? Is using it for conversation or search different from accepting generated code? A fully categorical rule can also affect contributors who rely on translation assistance.
"The debate shouldn’t be LLMs or no LLMs, but rather what level of human accountability is required." — a reader comparing AI tools with established developer tools
Simon Willison added a vital procedural correction: the link represents one of three proposals that will be debated and voted on, not a final decision. Whatever Debian chooses, the durable question is likely to be accountability. A maintainer who understands, tests, and takes responsibility for a change occupies a different position from a reviewer asked to absorb an untraceable stream of generated output.
Get breakdowns like this every day
The top Hacker News stories, unpacked — by email, Telegram, or RSS.
Brolly’s compact weather page wins HN, then gets asked to become a real text service
Brolly is a deliberately plain weather forecast interface: compact enough to glance at, but still interactive and mobile-friendly. HN liked the old-web feel—and immediately asked for the one feature that would make it infrastructure: a useful curl response.