From: Sam James <sam@gentoo.org>
To: Alejandro Colomar <alx@kernel.org>
Cc: Carlos O'Donell <carlos@redhat.com>,
linux-man@vger.kernel.org, Collin Funk <collin.funk1@gmail.com>
Subject: Re: [PATCH v4] CONTRIBUTING.d/ai: Add guidelines banning AI for contributing
Date: Wed, 15 Oct 2025 19:49:50 +0100 [thread overview]
Message-ID: <878qhc6lv5.fsf@gentoo.org> (raw)
In-Reply-To: <7n2g7ccnlfcjm2pgptwwuq3pn6dpnrwvqfxa4exa2hnjikajwk@men5xbekuoop>
Alejandro Colomar <alx@kernel.org> writes:
> Hi Carlos,
>
> On Wed, Oct 15, 2025 at 12:03:07PM -0400, Carlos O'Donell wrote:
>> > In v4, I've added a paragraph clarifying that AI assistive tools are
>> > also included in the bad.
>>
>> Isn't this the *opposite* of Gentoo's policy and QEMU's policy?
>
> It is the opposite of what Gentoo claims their policy says. But it's
> what my read of their policy says (and I'm not alone there, as the same
> interpretation was mentioned in libc-alpha@). They should clarify their
> policy if they don't mean what it says.
I already said we plan on it. I thought that was pretty clear.
>
>> We should base the contribution policy on things we can objectively
>> measure and claim.
>>
>> Rejecting AI content in contributions is objective and measurable
>> since you can't attest the DCO clearly with this content.
>
> Rejecting AI content would follow the first concern, but the second and
> third concerns would be entirely ignored by a policy that permits AI
> static analyzers.
>
It is hard in my mind to justify rejecting TTS or similar that may be
based on AI.
>> > diff --git a/CONTRIBUTING.d/ai b/CONTRIBUTING.d/ai
>> > new file mode 100644
>> > index 000000000..faab2df1b
>> > --- /dev/null
>> > +++ b/CONTRIBUTING.d/ai
>> > @@ -0,0 +1,57 @@
>> > +Name
>> > + AI - artificial intelligence policy
>> > +
>> > +Description
>> > + It is expressly forbidden to contribute to this project any
>> > + content that has been created with the assistance of AI tools.
>>
>> This is OK, the forbiddance is on the created content.
>
> "created *with the assistance* of AI tools"
>
> If I write some code, and iterate over it by passing it through static
> analyzers and editing as appropriate, I'd say the code has been created
> with the assistance of those tools.
>
> Let's consider this example from The Lord of the Rings. Did Celebrimbor
> create the three Elven rings with assistance of Sauron? Sauron did not
> produce the rings, but it influenced the author enough to introduce
> vulnerabilities in the rings.
>
>> > +
>> > + This also includes AI assistive tools used in the contributing
>> > + process, even if such tools do not generate the contributed
>> > + code.
>>
>> I object strongly to this paragraph.
>>
>> It is the *opposite* of what Gentoo's policy intended.
>>
>> This is policy over-reach into the lives of contributors.
>
>
> Cheers,
> Alex
next prev parent reply other threads:[~2025-10-15 18:49 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 21:27 [PATCH] CONTRIBUTING.d/ai: Add guidelines banning AI for contributing Alejandro Colomar
2025-10-14 21:32 ` Carlos O'Donell
2025-10-14 21:52 ` Alejandro Colomar
2025-10-14 21:55 ` Carlos O'Donell
2025-10-14 21:39 ` Collin Funk
2025-10-14 21:59 ` Alejandro Colomar
2025-10-14 22:03 ` Carlos O'Donell
2025-10-14 22:10 ` Alejandro Colomar
2025-10-14 22:20 ` Alejandro Colomar
2025-10-14 23:59 ` Carlos O'Donell
2025-10-14 22:00 ` Carlos O'Donell
2025-10-14 22:16 ` Collin Funk
2025-10-14 23:58 ` Carlos O'Donell
2025-10-14 21:54 ` Carlos O'Donell
2025-10-14 22:15 ` Alejandro Colomar
2025-10-15 0:16 ` Carlos O'Donell
2025-10-15 2:13 ` Collin Funk
2025-10-15 10:49 ` Alejandro Colomar
2025-10-14 22:03 ` [PATCH v2] " Alejandro Colomar
2025-10-15 11:21 ` [PATCH v3] " Alejandro Colomar
2025-10-15 12:29 ` Alejandro Colomar
2025-10-15 13:25 ` Carlos O'Donell
2025-10-15 14:03 ` Alejandro Colomar
2025-10-15 14:46 ` Carlos O'Donell
2025-10-15 14:51 ` Sam James
2025-10-15 15:31 ` Alejandro Colomar
2025-10-15 16:09 ` Sam James
2025-10-15 16:20 ` Alejandro Colomar
2025-10-15 16:26 ` Sam James
2025-10-15 15:50 ` [PATCH v4] " Alejandro Colomar
2025-10-15 16:03 ` Carlos O'Donell
2025-10-15 16:56 ` G. Branden Robinson
2025-10-15 18:11 ` Alejandro Colomar
2025-10-15 19:24 ` G. Branden Robinson
2025-10-15 19:50 ` Alejandro Colomar
2025-10-20 18:47 ` Carlos O'Donell
2025-10-20 19:05 ` Carlos O'Donell
2025-10-15 18:22 ` Alejandro Colomar
2025-10-15 18:49 ` Sam James [this message]
2025-10-15 19:03 ` Alejandro Colomar
2025-10-15 19:04 ` Alejandro Colomar
2025-10-15 19:11 ` Sam James
2025-10-15 19:17 ` Alejandro Colomar
2025-10-16 12:26 ` Alejandro Colomar
2025-10-16 16:41 ` [PATCH v5] " Alejandro Colomar
2025-10-20 18:25 ` Carlos O'Donell
2025-10-21 17:01 ` Alejandro Colomar
2025-10-27 17:29 ` [PATCH v6] " Alejandro Colomar
2025-10-28 12:31 ` Carlos O'Donell
2025-10-28 13:09 ` Alejandro Colomar
2025-10-28 13:21 ` [PATCH v7] " Alejandro Colomar
2025-11-10 11:54 ` Alejandro Colomar
2025-11-10 12:01 ` [PATCH v8] " Alejandro Colomar
2025-11-10 13:31 ` Carlos O'Donell
2025-11-10 14:31 ` Alejandro Colomar
2025-11-10 14:36 ` [PATCH v9] " Alejandro Colomar
2025-11-10 16:56 ` Carlos O'Donell
2025-11-10 22:25 ` Alejandro Colomar
2026-03-29 13:42 ` [PATCH] " Günther Noack
2026-03-29 17:55 ` Alejandro Colomar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878qhc6lv5.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=alx@kernel.org \
--cc=carlos@redhat.com \
--cc=collin.funk1@gmail.com \
--cc=linux-man@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox