Respect to Antoine. Having principles that are worth a damn is a rare trait amongst developers these days.
The without disclosure part tells everything you need to know here. If it’s such a benign and maybe even beneficial thing to do then why are you hiding it? What possible reason could you have not to label that? In an open source Community shouldn’t everything like that be known?
There are so many levels of LLM involvement and once you make this distinction you actually have to devote some of your limited resources to define and enforce it. So I think it might not be strictly beneficial, but possibly also have downsides.
Where would you draw the line at which point it counts as LLM involvement? Having one run as some sort of spell/syntax checker? Doing some research (and being influenced by it) before hand coding something? Having it create a working prototype and then reimplementing it by hand? If you use code from somewhere else to solve a problem and ai use has not been disclosed for this code, do you automatically have to assume LLM usage was involved or is there plausible deniability?
I think in the end you’d have to use too many resources check it and debate where the line is drawn, when the real question is how you retain human knowledge and engagement within your community.
Just disclose how you used it.
“Just” like with GDPR, “just” follow the rules for personal data management. In reality, compliance stuff like that is expensive to implement.
So if you are going to require it, don’t pretend it is without cost. Which is exactly what you seem to be doing.
I wonder what’s the reason to make it optional? I think I’ve seen this approach with other projects as well. Isn’t transparency and accountability a good thing? Also, this kind of information helps immensely when reading pull requests or silly bug reports. And Debian acknowledge there might be licensing issues. So it might become some sort of liability to them once it taints everything and we can’t even tell?! So why? What’s the upside? Adorn oneself with borrowed plumes and not being forced to disclose the fact? Or too much bookkeeping?
Because the idea is to judge the code by its quality, not by who or what wrote it.
Conversely… if it’s so benign, why should it have a label?
Not really worth discussing - it’s not benign, and it can be made purposefully not benign by a third party without notification or knowledge. A third party who has already demonstrated a penchant for world domination, both technologically and physically.
We saw this play out with GMO foods:
If it’s such a benign and maybe even beneficial thing to do then why are you hiding it? What possible reason could you have not to label that?
later:
It’s specifically labelled, therefore it must be bad right? If we didn’t need to worry about it, it wouldn’t be labelled.
The world needs more people that act on principles and take a stance.
So Open-Source and FOSS projects collectively decided that they want to jump on half-sunken ship in the middle of the ocean?
Amazing.
half-sunken ship
If you think the ship is ever sinking I’ve got bad news for you…
