Hi This thread is only for coming up a piece of text to point at when someone asks about these tools.
This was sparked by someone asking what the policy is and our promo team not knowing what to reply. Other projects already have such policies, so I'd like us to have something too. For example: Fedora: https://docs.fedoraproject.org/en-US/council/policy/ai-contribution-policy/ Mesa: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/37233/diffs The point is, the genie is out of the bottle. The worms have escaped the can. So, what we need in my opinion is have something that we can show for the regular user or new contributor that has questions about these tools and how they're used within KDE ecosystem. It's easy for us developers to think some things are just common sense when it comes to this, but we need to approach this from a point of view where someone is completely new to it. Here's my draft for starters, following closely to the Mesa policy: ``` Contributor is always responsible for the code changes and creation, regardless where the code came from, such as: - Code was written completely by the contributor. - Code was generated by an LLM/"AI" or any other tool. - Code was given to contributor by someone else. - Code was copy-pasted from the internet. Contributor must try their best to understand what their contribution is changing and they must be able to justify the changes. Using any tools to help understand and justify those changes does not change or reduce the expectations. The changes are attributed to the contributor, no matter whatever tools they have used. To make sure you understand what you're doing, follow these tutorials: (And then we could add some links to guides etc here) ``` (I do not know where this text should be placed, so let me know and I'll make a proper MR.) Now clearly this is for many of us already normal thing and a normal expectation. But the point is to make it clear for newcomers and non-developers alike! There are going to be, and already are, a lot of newcomers who think they can ask the magic box to generate fixes for everything. Having some ground rules and guidelines can help them learn programming. I also don't care if it's called policy or guideline or oath or whatever, just have some text somewhere that people (even the non-devs) can look at. We can of course just ignore whole thing and carry on, but then what do we reply to those who ask about this? I hope for a flamewar free discussion, - Akseli ps. Before someone sends me hatemail for "liking/disliking AI" or something like that, I have never used these tools and they do not interest me at all. I just want to have some ground rules for those who are interested in them to avoid any potential issues in future.
