public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
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 v3] CONTRIBUTING.d/ai: Add guidelines banning AI for contributing
Date: Wed, 15 Oct 2025 17:09:00 +0100	[thread overview]
Message-ID: <87a51s87vn.fsf@gentoo.org> (raw)
In-Reply-To: <zbo53h5pugwczbscyg4n7tgydrnnaf6v3enc4stckobwswu377@dt4itqfzh7k3>

Alejandro Colomar <alx@kernel.org> writes:

> Hi Carlos, Sam,
>
> On Wed, Oct 15, 2025 at 03:51:33PM +0100, Sam James wrote:
>> >>> Though it has been discussed on-list that this policy could be seen as
>> >>> forbiding assistive technologies, but that this was not the intent of
>> >>> the Gentoo Council's wording.
>> >> Didn't they?  Do you have a source for that?
>> >
>> > https://inbox.sourceware.org/libc-alpha/5523336.irdbgypaU6@kona/
>> > ~~~
>> > As someone who was present at the initital discussion, I can assure that
>> > banning accessibility helps was not the intention.
>> > ~~~
>> > - Andreas Huettel
>> 
>> +1 (as someone else who also voted on it). We may amend it to make this
>> part clear in future.
>
> Thanks.  I find the wording to imply that it also prohibits assistive
> technologies (and I like that sense).  I'd add a paragraph claifying it
> in the sense of disallowing them:

Eh? We're saying we *don't* want to do that.

>
> 	It is expressly forbidden to contribute to this project any
> 	content that has been created with the assistance of artificial
> 	intelligence tools.
>
> 	This also includes AI-based assistive tools used in the
> 	contributing process, even if such tools do not generate the
> 	contributed code.
>
> This includes for example AI-based linters and static analyzers.
>
>
> Cheers,
> Alex

  reply	other threads:[~2025-10-15 16:09 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 [this message]
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
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=87a51s87vn.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