On Monday 19 May 2025 10:26:19 Eastern European Summer Time Jin Liu wrote:
> Martin Steigerwald <mar...@lichtvoll.de> 于2025年5月19日周一 14:56写道:
> 
> > Everyone: I suggest to assume good intentions.
> 
> My suggestion is to avoid making assessments on "people", and focus on
> code or legal or other aspects.
> 
> - Jin Liu

Jin, I don't think you have done anything wrong.

Your contributions have been accepted and they have been good.
You clearly put *thought* and *effort* in them.

My original point is to try to get rid of the low-hanging fruit, as in
people who spam bug reports with obviously "AI" generated things.

I don't think using "AI" to get a starting point, as long as you modify the
generated items and such yourself, is evil. To me, that is like
using snippets tools, which I do from time to time. 

I do not agree it's the most efficient way, but that's beside this whole 
discussion. 

I'm sorry if this mailing list thread has caused grief. I was rather
annoyed when I wrote this because I had seen bunch of bug reports
and "feature requests" written with a machine, with zero thought behind them.

In the end, "AI" is a tool. And when tool is used properly, by people
who understand how to use these tools, then I do not find too much issue
about it. 
(Honestly I'm more annoyed by the word "AI" because it kind of hides all the 
nuance.)

I wish everyone in this thread assumed good faith amongst each other and
their contributions. 

My hope is to just follow this rule here, as Nate mentioned:
https://ev.kde.org/rules/reimbursement_policy/#after-the-event

>  blog posts obviously written by AI or containing AI-generated art will not 
be accepted.

Turn this into:

>  Contributions, bug reports, etc. obviously written by AI or containing AI-
generated art will not be accepted and will be closed.

That's really it. Notice the word "obviously."

I am actually more bothered by "AI" generated artwork,
than code. We just have to remember that "AI" generated code can
have license issues, but if the human has actively worked on that code
instead of using the "raw" version, I would hope there's no issues.
This in the end is a law thing.

- Akseli



Reply via email to