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.
You can reject it in your own projects. That’s about it. If you’re open source and accepting any submissions, you’ve no idea if they’re LLM generated or not.
You have no idea if they copy pasted proprietary code either, but you try your best to keep it out.
Except for all the open source libraries you probably use that also use LLMs, or you find a blog post someone wrote explaining how to do something and they used LLMs
You can avoid direct knowledgeable usage, but you’ll still have LLM code in your codebase.