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

SLAPP Censorship - Part 190 Out of 200: Plagiarism, Back Doors, and Sabotage of Linux
This can go on for a decade or longer
SLAPP Censorship - Part 189 Out of 200: A Terrible Idea to Condemn Projects for Using Slop 'Code' When Your Own Employer Does This (and Profits From Every Company Doing So) or to Call Distros 'Not Secure' While You Advance Back Doors
"I don’t want a back door. I want a front door."
 
USCIS and Microsoft Rumours: Curbs on Lowering Salaries by Importing Cheaper Replacements?
It seems like Microsoft's mass layoffs and efforts to cheapen the workforce face obstacles
Gemini Links 20/09/2026: "Music While Working" and Radio Silence
Links for the day
Clownflare Data From Canada
We've like to think many people are attempting to install GNU/Linux over the weekend
Linux Kernel Becoming a Slopfest - Part 5 - Kernel Dependency on Plagiarism Giant Microsoft is a Death Blow to Any Kernel
Microsoft is bringing copyright-infringing slop into Linux
GNU/Linux Has Grown a Lot Lately
Based on Clownflare
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Saturday, September 19, 2026
IRC logs for Saturday, September 19, 2026
Links 19/09/2026: Many Patents Become Candidates for Annulment and Linux [sic] Foundation Takes More Slop Money to Promote Malicious Bots
Links for the day
Gemini Links 19/09/2026: The Fundamental Human Assets, The History of Gopher's "i" Type, and ROOPHLOCH 2026
Links for the day
Links 19/09/2026: "OpenAI and Microsoft Knew They Were Starting a ‘Doom Loop’ [of Mass Plagiarism 'Normalised' by Brute Force] for the web", Calling It "Hey Hi"
Links for the day
8 Series Going on at the Moment in Techrights
4 series about SLAPPs and related matters
Linux Kernel Becoming a Slopfest - Part 4 - Outsourcing to Microsoft, Approaching 10 Gigabytes
Can we blame Microsoft for those DDoS attacks? Partly.
Software Freedom Day 2026 is Today, Week-long Celebration in Brazil
In Brazil, Clownflare reckons about 1 in 20 laptops/desktops might use GNU/Linux already
Red Hat Lost 2,000 Staff (Net Loss)
Maybe by year's end it'll be a 20% reduction
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Friday, September 18, 2026
IRC logs for Friday, September 18, 2026
Gemini Links 18/09/2026: Setting Goals, Tiredness, and Admissions From LLM Purveyors It Was All Along About Building Plagiarism Engines Sold as "Intelligence"
Links for the day
Links 18/09/2026: Microsoft Boasted Slop is Just Copyright Infringement/Plagiarism, Floods in Europe
Links for the day
Slop Ruins Development and Reverse Engineering, It Rewards Retarded "Slop Kiddies" (to Quote Andy ‘TheFlow0’ Nguyen)
Slop is just a fatal cancer that kills the body, then dies with the body it killed
Internet Relay Chat (IRC) and Mailing Lists Are Still Better Than Discord, Slack, and Discourse
Discourse is "open" "bossware"
Links 18/09/2026: Disgust Over LLMs and Why "Agents" (Bots) Are Nothing More Than "Spam"
Links for the day
Software Freedom Day is Tomorrow
events coming
Illegal and Unconstitutional Tribunal That SLAPPs Critics Does the Illegal and Unconstitutional: It "Rubberstamps Software Patents"
This is not a legal system. This is mafia.
Privilege in 'Linux' Foundation (Double Standards) and What the FSF Should Avoid Doing
If RMS can talk about politics, others too should be able to talk about politics
Seems Like Many Microsoft Layoffs Are Going On Right Now (Forever Layoffs)
Like IBM, Microsoft hopes shareholders will not know of morale and financial problems
More Threats From the Person of Restricted Boot Infamy
Remember this is the man who is the principal purveyor of restricted boot and who landed restricted boot in Linux
Snooping EPO Management, Sniffing Up Every Staff Action
It this a problem for whistleblowers? Of course.
Don't Do That
Options do exist. People should exercise freedom.
Iran Has Debunked GAFAM and Cloud Computing as Safety of Data
Cloud of smoke?
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Thursday, September 17, 2026
IRC logs for Thursday, September 17, 2026
SLAPP Censorship - Part 188 Out of 200: Used, Then Discarded, by Microsoft (as We Predicted All Along, It's Always Like That)
The longer they carry on with it, the more scandalous this will get
Linux Kernel Becoming a Slopfest - Part 3 - Besieged by LLM Bots, Now Hiding Behind a Wall of JavaScript
The series began 3 days ago
Gemini Links 18/09/2026: Modern Linguistic, Boxing, Turning 40, and Solar MiniServer
Links for the day