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 v4] CONTRIBUTING.d/ai: Add guidelines banning AI for contributing
Date: Wed, 15 Oct 2025 20:11:47 +0100	[thread overview]
Message-ID: <87tt0056a4.fsf@gentoo.org> (raw)
In-Reply-To: <pzpqnukol5vapop3js7vmnwtlvagmivpqpwr3uy7idntrls6jp@vmfilg5dvobt>

Alejandro Colomar <alx@kernel.org> writes:

> On Wed, Oct 15, 2025 at 09:03:28PM +0200, Alejandro Colomar wrote:
>> Hi Sam,
>> 
>> On Wed, Oct 15, 2025 at 07:49:50PM +0100, Sam James wrote:
>> > >> 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.
>
> BTW, I assume TTS means text-to-speech.  Please don't use abbreviations
> not supported by wtf(1), or parenthesize their meaning in the first use.

I normally try to honour that. Anyway, I'm not interested in discussing
further at this time. I don't think the way you've suggested this
subproposal is constructive.

>
>> 
>> The following is enough, IMO, as justification:
>> 
>> 	Ethical concerns.
>> 		The business side of AI boom is creating serious ethical
>> 		concerns.  Among them:
>> 
>> 		-  Commercial AI projects are frequently indulging in
>> 		   blatant copyright violations to train their models.
>> 		-  Their operations are causing concerns about the huge
>> 		   use of energy, water, and other natural resources.
>> 		-  The advertising and use of AI models has caused
>> 		   a significant harm to employees and reduction of
>> 		   service quality.
>> 		-  LLMs have been empowering all kinds of spam and scam
>> 		   efforts.
>> 
>> 	Quality concerns.
>> 		Popular LLMs are really great at generating plausibly
>> 		looking, but meaningless content.  They pose both the
>> 		risk of lowering the quality of a project, and of
>> 		requiring an unfair human effort from contributors and
>> 		maintainers to review contributions and detect the
>> 		mistakes resulting from the use of AI.
>> 
>> 		AI tools should be considered adversarial, as if they
>> 		were a black box with Jia Tan inside them.
>> 
>> 
>> Cheers,
>> Alex
>> 
>> -- 
>> <https://www.alejandro-colomar.es>
>> Use port 80 (that is, <...:80/>).

  reply	other threads:[~2025-10-15 19:11 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
2025-10-15 19:03         ` Alejandro Colomar
2025-10-15 19:04           ` Alejandro Colomar
2025-10-15 19:11             ` Sam James [this message]
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=87tt0056a4.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