Bonum Certa Men Certa

Debian: Plagiarism OK, Just be "Responsible" About It

posted by Roy Schestowitz on Aug 29, 2026,
updated Aug 29, 2026

So the results are in and a bot announced them (probably supervised/operated by some "human factor" or 'meat'):

Responsible Use of Generative AI

The result isn't the worst, but it's not good either. They basically tolerate LLM plagiarism, they just leave it down to what "responsible" means (a rather meaningless or ill-defined, vaguely-described non-legal term).

This is how it is formally described:

>
Choice 5: Responsible Use of Generative AI

Using its power under Constitution section 4.1 (5), the project issues the following statement describing its current position on AI-assisted contributions. This statement describes the position of the project at the time it is adopted. That position may evolve as time passes without the need to resort to future general resolutions. The GR process remains available if the project needs a decision and cannot come to a consensus.

Debian neither endorses nor prohibits the use of generative AI tools in the development, maintenance, or documentation of software, packaging, documentation, and other media published within the Debian Project. We recognize that such tools can substantially improve the productivity of contributors when used responsibly, allowing volunteers to spend more of their limited time on work that requires technical expertise, judgment, review, and collaboration.

The Debian Project nevertheless expects that all contributions submitted to Debian, regardless of how and with which tools they were produced, satisfy the same standards of quality, correctness, maintainability, and legal compliance. The use of a generative AI tool does not diminish the contributor's responsibility for the work they submit. Contributors are expected to understand, review, test, and, where appropriate, modify AI-assisted output before incorporating it into Debian. Blindly accepting or uploading AI-generated material without appropriate human review is inconsistent with Debian's established development practices. We enourage our contributors to disclose whether a contribution was made with AI assitance, but do not require them to do so.

Debian acknowledges that the legal status of material produced by generative AI systems remains the subject of ongoing discussion in many jurisdictions, including questions relating to copyright, authorship, licensing, and potential reproduction of training material. The Project does not seek to resolve these unsettled legal questions through this General Resolution, nor does it adopt a position on whether AI-generated output is, in whole or in part, copyrightable or derived from copyrighted works.

Instead, Debian continues to rely on the judgment and responsibility of its individual contributors. Project members are expected to exercise appropriate care when using generative AI tools, to consider the provenance and licensing implications of material they contribute, and to avoid introducing content whose legal status they cannot reasonably justify. Existing Debian policies governing licensing, copyright, software freedom, and the acceptance of contributions continue to apply irrespective of the tools used to produce those contributions.

Contributors are expected to exercise appropriate care when designing and implementing workflows that incorporate generative AI tools. In particular, they should ensure that confidential information, private communications, security-sensitive information (such as embargoed information about security bugs that is not yet public), cryptographic keys, credentials, and other non-public material relating to the Debian Project, its infrastructure, or its community are not disclosed to third-party AI services unless such disclosure has been explicitly authorized and is consistent with Debian's security and privacy requirements.

The use of generative AI does not alter Debian's established expectations regarding large-scale or automated project actions. Contributors intending to perform actions with broad project impact, such as mass bug filing or patch submission, large-scale code modifications, or other automated changes or requests affecting many packages or contributors, should seek prior discussion and consensus through the appropriate project channels before proceeding. Any such automated process should be overseen by a human who remains accountable for its behavior and output.

This resolution therefore affirms that generative AI is neither exempt from nor subject to special rules beyond the standards already expected of Debian contributors. The 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.

One issue is, when they pass such a GR they let people get away with a lot.

Suppose I catch someone sending a CG (computer-generated, don't say "hey hi") bug report or code. I then say, "no!" (or "please don't!"). I am then told it was "responsible" slop and maybe I infringe the CoC for not accepting slop. "That's intolerance !!"

Where does this leave us? Real developers getting pissed off and projects losing contributors as a result.

QEMU has been hit by a single reporter filing over 125 separate bug reports in under 10 minutes, all for ubsan reports. The reports ignored the bug template and showed no sign of any human analysis of the ubsan output and had no proposed fix.

Other Recent Techrights' Posts

Michael Catanzaro's Latest Blog Post Affirms Rumours of Red Hat Changes and RAs/PIPs at IBM
reading between the lines, IBM is "spitting out" Red Hat staff
 
Debian: Plagiarism OK, Just be "Responsible" About It
The result isn't the worst, but it's not good either
Don't Let Them Kill Activism
Are the oligarchs shutting the lid on activism and whistleblowers?
SLAPP Censorship - Part 165 Out of 200: Two Years Since My Wife and I Sued
In early September 2024 we hit back
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Friday, August 28, 2026
IRC logs for Friday, August 28, 2026
Gemini Links 29/08/2026: Death Notice, Systems Biology, and Gopher
Links for the day
Links 28/08/2026: Chatbot Pushers Admit They're Used Heavily for Social Engineering Scams, Strong Backlash Against "Smart Glasses" (CCTV on Legs)
Links for the day
If Linux Was Written in Rust, 80% or More of Linux Developers Would Not Understand It (Same If It's Composed by LLM Slop)
The licence (GPL) is not enough when there are ways to bypass it
Gemini Links 28/08/2026: Absurd Tomodachi Summer, Screen Piggery, and Jugulans 1.0.3 Released
Links for the day
Links 28/08/2026: "UK Power Grid Has a Phantom Data Center Problem" and "Growth at All Costs is Cancer"
Links for the day
SLAPP Censorship - Part 164 Out of 200: Patent Troll SLAPPs, Defamation Trolls, and Stranglers From America
You start to wonder if the core issue is insecurity
Rumours of More PIPs and Layoffs at Confluent Just Months After IBM Bought It
It is meanwhile apparent IBM will have mass layoffs next week (September)
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Thursday, August 27, 2026
IRC logs for Thursday, August 27, 2026
After Many Waves of PIPs (Silent Layoffs) IBM Makes Non-Silent Layoffs, Effective Next Week (September)
What we heard is turning out to be true
Gemini Links 27/08/2026: Oklahoma, Tennessee, Haiku OS, Digital Resistance, and Staying Offline
Links for the day
Links 27/08/2026: Facebook to Pay Up to $17.1 Billion to Cover Up Known Harms, Nepal Landslide Kills Many
Links for the day
The Register MS Has Just Published Paid Spam That Says "AI" 19 Times
1.5 hours ago
Mainstream Media is Paid to Link "AI" Criticism/Boosting to Jeffrey Epstein Enablers, in Effect Showing How Corrupt This Media Became
Many readers will have noticed what was a paid-for PR campaign of a global scale
RSS is King: Why Having Subscribers or Followers in Sites You Neither Own Nor Control is Loss of Autonomy and Search is Mostly Slop (Plagiarising Sites, Not Linking to Them)
Because digital connections in third parties aren't assets; they endow another party with tremendous power over people (e.g. MElon getting to decide who can and cannot reach people or what messages to "dim down")
Claims of Tens of Thousands of 'Silent Layoffs' at IBM (and Red Hat)
Looking at recent activity in thelayoff.com, about 80% of the comments and posts are about PIPs
Links 27/08/2026: "Flock’s CEO Is Lying to Cops" and Microsoft's GitHub Actions Breaks Down Again (Too Many Layoffs, Loss of Knowledge)
Links for the day
Clownflare Sees GNU/Linux and ChromeOS at Over 13% in Bahamas
Narrowing down to desktops and laptops, and judging by Web requests that go through Clownflare, many people there use GNU/Linux or Google's 'bastardised' version of it (with spyware preloaded)
Richard Stallman Complains That Linux Gives a Bad Name to GNU and Asks for Feedback on What's Wrong with Systemd (and Wayland)
Maybe some people want to send him a detailed, polite explanation
GNU/Linux Does Not Need Social Control Media to Succeed
When it comes to Social Control Media, Richard Stallman was right
Increasing Focus on Patent Injustices
We'll soon cover the EPO a lot more
SLAPP Censorship - Part 163 Out of 200: Attack on Computer Science and on Computer Security (or Associating Back Doors and Kill Switches With "Security")
Nowadays there are many who pretend to be security professionals
There's No "Next XBox"
Nothing comes ahead except layoffs and price hikes
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Wednesday, August 26, 2026
IRC logs for Wednesday, August 26, 2026
Gemini Links 27/08/2026: Conditioning, Lagrange 1.21, and Computer Games
Links for the day