Direct link to the LLM Policy Discussion: https://invent.kde.org/plasma/plasma-workspace/-/work_items/187
Example of KDE dev rejecting environmental consideration:
Example of KDE devs not wanting to require LLM use be disclosed.
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.
So, who’s gonna start a fork?
Starting a fork is easy, but who is gonna maintain it? KDE is huge, at 8 million lines of code for the core software, so you’ll need a large amount of people who are willing to work on the fork to keep parity with KDE
That seems like a significant LoC to wrangle. Maybe you can swing some tools at it to reduce your workload. OOPS YOU’RE A SLOPERATOR NOW
/s cause some of y’all need it