this post was submitted on 20 Sep 2026
326 points (87.7% liked)

Linux

15022 readers
563 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 3 years ago
MODERATORS
 

Direct link to the LLM Policy Discussion: https://invent.kde.org/plasma/plasma-workspace/-/work_items/187

Example of a KDE dev not wanting environmental concerns to play any role, despite KDE having an environmental project:

Devs rejecting any notion of transparency by disclosing AI usage in code submissions (in direct opposition to advice from the FSFE):

And all of this is coming right after the debacle with an AI slop project being allowed to give a presentation at Akademy, and the person asking how this was allowed being blocked by KDE:

https://lemmy.nz/post/42029517

as well as the discussion thread bringing up legitimate concerns about AI usage being closed:

https://discuss.kde.org/t/sorry-to-bring-up-a-contentious-topic-kde-ai-llm-policy/46333/164

As someone who genuinely loves KDE, and has even donated to the project multiple times, I sadly have to accept that the majority of KDE have hopped onto the Pro-AI train, and they will not be dissuaded otherwise.

(page 2) 50 comments
sorted by: hot top controversial new old
[–] ZombieCyborgFromOuterSpace@piefed.ca 85 points 1 day ago (9 children)

This is EXTREMELY disappointing. KDE is my favourite DE.

load more comments (9 replies)
[–] Toga77@lemmy.world 12 points 1 day ago (12 children)

World sees AI doing awful things like nudifying children, making nearly every software we use worse, and stealing the world's knowledge to sell back to us, and generally dislikes AI.

Moronic software devs with massive egos: "WE SHOULD USE AI SEE HOW EASY THIS MAKES MY LIFE NOW I DONT HAVE TO LEARN. "

Also them: "I swear I just use it to augment my work! I'd never take a shortcut and eventually keep taking shortcuts and outsource my thinking! Humans notoriously NEVER take shortcuts!"

Guys wtf are we even doing anymore.

[–] NewOldGuard@lemmy.ml 9 points 1 day ago

And it wrecks the environment, and it stunts the user's intelligence without actually being able to do anything truly original or novel, and it makes worse, buggier, less secure, less maintainable software. The list goes on and on

load more comments (11 replies)
[–] esc@piefed.social 22 points 1 day ago* (last edited 1 day ago) (1 children)

Actual proposed policy:

Nobody in KDE should know if you use an LLM — not because you're concealing it, but because your usage of it produces output indistinguishable from what you could produce yourself. Contributions with obvious and lazy LLM usage may be ignored or closed.

Generally, don't. What you are willing to write is generally the upper limit of what others are willing to read. LLMs, on the other hand, often produce long, rambling, soulless, corporate-sounding nonsense that nobody wants to read; don't do it. This includes:

Don't use an LLM to "organize your thoughts" and copy-paste the output somewhere. Organize them yourself. Don't use an LLM to generate commit messages and merge request descriptions. Write them yourself. Don't use an LLM to generate a reply to someone's question or comment, then copy-paste that as if it were your response. Understand and reply yourself.

The one acceptable usage is to write text in your native language and then machine-translate it into English, with no stylistic or tonal changes.

But of course reading is for the LLM, it's far better to be outraged about 'hopping on the Pro-AI train'.

[–] ProdigalFrog@slrpnk.net 18 points 1 day ago (1 children)

That section only relates to descriptions of pull requests, not the AI code itself. They don't want long rambly AI generated explanations of how the code works, but they are fine if the code itself is AI generated.

load more comments (1 replies)
[–] DmMacniel@feddit.org 47 points 1 day ago* (last edited 1 day ago) (12 children)

this is quite... disappointing, and I say that as someone who uses primarily GNOME :(

load more comments (12 replies)
[–] richardisaguy@lemmy.world 18 points 1 day ago (1 children)

It's a actually completely reasonable proposal

It all comes down to one thing - understand the LLM generated code you want to submit, and use the LLM for nothing else than write code, like making other people having to read LLM text. This is a whole lot like the kernel's LLM policy.

Niko is right, the environmental corcern is not something this policy should go against - what can they do despite ban LLM usage altoguether (and per consequence get LLM generated code submitted anyway), they can't have a blacklist for models, or force contributors to run them on their local hardware.

[–] tyler@programming.dev 23 points 1 day ago (3 children)

what can they do despite ban LLM usage altoguether (and per consequence get LLM generated code submitted anyway), they can't have a blacklist for models, or force contributors to run them on their local hardware.

But they can? Like OP pointed out, wine forbids contributions from those that have seen Windows source code. How in the world are they supposed to enforce that? Turns out the open source community is pretty good at self enforcing.

[–] black0ut@pawb.social 3 points 22 hours ago (1 children)

I'm with you, but the sad reality is that, unlike Wine devs, AI devs can't be assumed to act in good faith.

Potential Wine devs who have seen Windows source code will self enforce the rules, because they care about their integrity and the integrity of the project.

AI devs already don't have an integrity, and they feel smug and superior for actively trying to fool any sort of measure against AI. They also seem to believe AI is the future and isn't going away, so why bother regulating it if it won't matter soon.

We need to come up with stricter and more effective ways to regulate and ban AI use, and that's gonna be the difference between an unusable codebase and a great one in a few years.

[–] tyler@programming.dev 4 points 21 hours ago

Sure, but that doesn’t mean that it can’t go into the contribution guidelines. If they don’t listen then ok, you remove commits that have claude watermarking. Without that guideline you can’t stop the PRs at all.

load more comments (2 replies)
[–] statelesz@slrpnk.net 30 points 1 day ago (4 children)

I do kinda get Niccolo's point that a contribution policy is not the place to decide environmental concerns even though it feels contradictory at first glance. He's generally very critical and nuanced when it comes to LLMs so I wouldn't call him "pro-AI". Just watch his YouTube content.

[–] ProdigalFrog@slrpnk.net 45 points 1 day ago* (last edited 1 day ago) (1 children)

The contribution policy is the only place where anything meaningful can be done, as that is ultimately what will influence developers trying to contribute. Putting environmental concerns anywhere else is, IMHO, just toothless virtue signalling.

I personally consider advocating for non-disclosure of AI use to be Pro-AI. Advocating for disclosure but still allowing it would be neutral.

load more comments (1 replies)
load more comments (3 replies)
load more comments
view more: ‹ prev next ›