Proposed KDE LLM guidelines (#187) · Issues · Plasma / Plasma Workspace · GitLab
invent.kde.org
This is a continuation of this mailing list thread about "fully LLM-generated merge requests, preserved at https://mail.kde.org/pipermail/kde-devel/2026-September/004496.html There, I proposed...

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.

  • Otter@lemmy.ca
    0·
    8 hours ago

    I don’t really see why environmental policy shouldn’t be mentioned in the contribution policy. If it’s there as the justification for why a part of the policy exists and it is accurate about what the environmental impacts actually are, it seems to fit in fine within the policy? Not wanting the point there doesn’t make KDE pro-AI (since they might just want to mention it elsewhere), but it is valid criticism if they don’t acknowledge it anywhere.

    However I do feel that the other points in the post are weaker. KDE’s stance is in line with what the SFC recommends when it comes to AI in FOSS, specifically around contributions. I came across the SFC recommendations a while back and it’s held up well in similar discussions so far: https://sfconservancy.org/llm-gen-ai/llm-backed-generative-ai-recommendations.html

    Devs rejecting any notion of transparency by disclosing AI usage in code submissions

    I don’t think they rejected the transparency part? I agree that transparency is necessary. Rather their reply is telling the commenter to not shun people. Both of those points are reflected in the SFC recommendations (point 5 on disclosure and point 3 on shunning)

    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

    I get the feeling that KDE does not curate much of anything, for better or for worse. There is a good bit of content in the KDE ecosystem that is outdated or straight up shovelware.

    On top of that, Akademy is a conference that is intended for discussion, rather than a presentation about KDE.

    Akademy features a 2-day conference with presentations on the latest KDE developments, followed by 4 days of workshops, Birds of a Feather (BoF) and coding sessions. It is an opportunity to meet key KDE contributors, learn about the latest features and enjoy the great atmosphere. You will meet developers, artists, translators, upstream and downstream maintainers, users, and free and open software industry leaders from all over the world

    It wouldn’t work well if they had to curate every presentation at such an event. It is indeed deceitful to imply that the presenter is going to change the direction of KDE if in reality they rarely contribute and have little say in the direction of KDE. Also IMO it’s good that they let that guy participate in the conversation because it let everyone else raise points about why the idea is bad.