Debian launched two competing General Resolutions on LLM usage in its codebase, flagged on Hacker News with 11 points and one comment. The votes address whether code generated by large language models can enter the Debian archive and under what conditions.
What the Resolutions Propose
One resolution seeks to require explicit disclosure when LLM tools assist in code contributions. The competing text proposes treating LLM output the same as any other contributor work, with no additional labeling rules.
Both texts keep existing Debian processes for copyright, licensing, and quality review intact. The difference centers on whether an extra metadata field or commit note becomes mandatory.
Current Discussion Numbers
The Hacker News thread remains small at 11 points. Early comments focus on enforcement cost rather than outright prohibition. No vote tally exists yet because the resolutions are still in the discussion phase.
Pros and Cons for Maintainers
- Disclosure rule adds one extra field per contribution but creates an audit trail for license compliance.
- No-disclosure rule reduces paperwork yet leaves downstream users without visibility into AI-generated sections.
- Both options preserve the existing Debian New Maintainer process and do not alter package upload rights.
How Other Projects Handle Similar Questions
| Project | Policy | Disclosure Required | Notes |
|---|---|---|---|
| Debian (proposed) | Either disclosure or parity | Optional in one text | Two competing GRs |
| Fedora | Case-by-case review | Yes | AI code treated as third-party |
| Linux kernel | No AI-generated patches accepted | N/A | Explicit ban since 2023 |
Fedora requires contributors to note AI assistance during patch submission. The Linux kernel rejects such patches outright to avoid copyright uncertainty.
Who Should Pay Attention
Debian package maintainers and contributors working on core libraries need to track the outcome. Teams shipping Debian-derived distributions should prepare disclosure templates if the stricter resolution passes. Hobby contributors outside Debian infrastructure can ignore the vote.
Practical Next Steps
Watch the Debian vote page for the final ballot text. If disclosure wins, update commit templates to include an "LLM-assisted" tag. If parity wins, continue current contribution practices without change.
Bottom line: Debian is formalizing two clear policy options instead of leaving LLM use in a gray area.
The outcome will likely influence similar votes in other distributions within the next twelve months.
Top comments (0)