Crossposted from https://discuss.tchncs.de/post/67911106

Putting shit in your food is OK as long as it is only a little bit of shit and you can't immediately taste it.

you are viewing a single comment's thread
view the rest of the comments
[–] 9 points 5 days ago* (last edited 5 days ago) (1 child)

I REALLY don't understand this part. Not requiring disclosure is one thing (that I already don't approve of).

But out right stating you shouldn't be open with users and contributors just goes against I want in an open-source project. It's already got me looking into Sway.

I also feel a bit bitter since I literally donated money to a project I assumed wasn't huffing the Ai Jenkem and I could keep using and recommending in good faith for the foreseeable future.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 4 days ago* (last edited 4 days ago)

    The intent I read was “contribute as if someone couldn’t tell if it was LLM-assisted or not,” and that they don’t really want to be dictating the software tools contributors are using.

    This is the full text:

    Nobody in KDE should know if you use an LLM — not because you’re concealing it, but because your usage of it produces output indistinguishable from what you could produce yourself. Contributions with obvious and lazy LLM usage may be ignored or closed.

    So yeah, I think the intent isn’t even about disclosure, rather saying “it doesn’t matter if you disclose it, and not an excuse for questionable code, as your code better be indistinguishable from purely human made anyway.”

    Claude Code and other LLM coding frameworks have a habit of inserting themselves into git commits as contributors, so KDE wants to avoid that as well. They deserve as much attribution as your linter; precisely none. Their users also tend to leave unmaintainable “drive by” PRs, and use the AI as an excuse for the low quality. So part of that context you may be missing is “don’t use LLMs as an excuse; we don’t want to hear it.”

  • source
  • parent