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 5 days 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
[–] 19 points 1 week ago (2 children)

As a user, I think this is the biggest issue I have with this policy. Disclosure is a big part of open source and hiding whatever tools are used is fundamentally against that philosophy.

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

    Would you be willing to expand on what you mean by disclosure being a big part of open source?

    I ask because it has not been my experience that OSS developers have ever had a habit of disclosing what tools they use. If you are lucky then a repo has instructions for contributors, that may describe tools being used, or CI configuration for running tests and linters, but most projects have neither. Mostly you just get instructions for building the project, but sometimes not even that

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 3 points 6 days ago

    In some projects you'll see a kind of a colophon section listing all the tools used in making some software. Not just obviously things like libraries, but OS, text editor, IDE, art tools, or even inspirations.

    It's not everywhere, but it's frequent enough, and different from how proprietary software credits (or doesn't) to make it a distinction imo.

  • permalink
  • fedilink
  • source
  • parent