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.

  • ZILtoid1991@lemmy.world
    link
    fedilink
    arrow-up
    7
    arrow-down
    1
    ·
    3 days ago

    One small problem: People are now also using AI to generate summaries of their vibe coded garbage, to push them through checks.

    • Aatube@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      10
      ·
      2 days ago

      Using an LLM to generate text

      Generally, don’t. What you are willing to write is generally the upper limit of what others are willing to read. LLMs, on the other hand, often produce long, rambling, soulless, corporate-sounding nonsense that nobody wants to read; don’t do it. This includes:

      1. Don’t use an LLM to “organize your thoughts” and copy-paste the output somewhere. Organize them yourself.
      2. Don’t use an LLM to generate commit messages and merge request descriptions. Write them yourself.
      3. Don’t use an LLM to generate a reply to someone’s question or comment, then copy-paste that as if it were your response. Understand and reply yourself.

      emphasis mine