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.
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.
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.