342
KDE is actively proposing a Pro-AI contribution policy, with most rejecting any suggestions for AI use to be disclosed, or any consideration for environmental concerns (invent.kde.org)
submitted 1 week ago* (last edited 1 week ago) by to c/linux@programming.dev
182 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 1 week ago (6 children)

Realistically, I think everything actively maintained is going to have some LLM code in it by now. You can either accept it or go mad, tbh.

Art is one thing, and I can see why we wouldn't want the computer doing that if you have the resources to employ people, but code is rarely art. Most of it was already slop. It's had things shoehorned into it by shouty managers decades ago. Claude is far from perfect, but so are most of the people doing the gruntwork.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 10 points 1 week ago*

    Most of it was already slop. It's had things shoehorned into it by shouty managers decades ago.

    Manager: You have to get this done by end of week...

    Dev: itll be really shitty and kind of work. Can we clean it up after?

    Manager: of course!

    Dev: its done, we can ship it. Ill start cleaning it up.

    Manager: No, you need to do this other thing by tomorrow!

    Ive had some good ones that did honor the agreement when pushed to rush things, but its not common.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 8 points 1 week ago* (3 children)

    "accept it or go mad" always just comes across as extremely desperate, lol

    nooooo you don't understand you HAVE to accept it! There's no other choice!! Nooo stop rejecting it you're not allowed to do that!!!!

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 1 week ago (2 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 1 week ago

    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.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 1 week ago

    I can accept some trace amount of rat shit is going to get into my granola, but I am not willing to say that means I'm allowing rat shit in my cereal.

    Please at least try to keep it out, as I do when I'm making my own granola. Yes I know it's hard, but let's just try.

  • permalink
  • fedilink
  • source
  • parent