From: Carlos O'Donell <carlos@redhat.com>
To: Alejandro Colomar <alx@kernel.org>, linux-man@vger.kernel.org
Cc: Collin Funk <collin.funk1@gmail.com>, Sam James <sam@gentoo.org>
Subject: Re: [PATCH v3] CONTRIBUTING.d/ai: Add guidelines banning AI for contributing
Date: Wed, 15 Oct 2025 09:25:14 -0400 [thread overview]
Message-ID: <4d14273a-ae17-4f68-9a91-e06fac1d9be5@redhat.com> (raw)
In-Reply-To: <a6d76881a06350e807107bdd71d62efee4df485e.1760527144.git.alx@kernel.org>
On 10/15/25 7:21 AM, Alejandro Colomar wrote:
> This policy is based on the Gentoo policy (see link below).
>
> Cc: Carlos O'Donell <carlos@redhat.com>
> Cc: Collin Funk <collin.funk1@gmail.com>
> Cc: Sam James <sam@gentoo.org>
> Link: <https://wiki.gentoo.org/wiki/Project:Council/AI_policy>
> Signed-off-by: Alejandro Colomar <alx@kernel.org>
> ---
Needs a v4 so we can review the final CC-BY-SA-4.0 license requirements.
> Hi!
>
> I changed obvious wording, such as replacing the project name.
> On top of that, I removed a misleading sentence:
>
> They are capable of providing good assistance if you are careful
> enough, but we can't really rely on that.
>
> I don't think it's possible to be careful enough.
>
>
> Have a lovely day!
> Alex
>
> CONTRIBUTING.d/ai | 42 ++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 42 insertions(+)
> create mode 100644 CONTRIBUTING.d/ai
>
> diff --git a/CONTRIBUTING.d/ai b/CONTRIBUTING.d/ai
> new file mode 100644
> index 000000000..92d5d85d6
> --- /dev/null
> +++ b/CONTRIBUTING.d/ai
> @@ -0,0 +1,42 @@
> +Name
> + AI - using artificial intelligence for contributing
> +
> +Description
> + It is expressly forbidden to contribute to this project any
> + content that has been created with the assistance of artificial
> + intelligence tools.
OK.
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.
I don't have better wording.
> +
> + Concerns
> + Copyright concerns.
> + At this point, the regulations concerning copyright of
> + generated contents are still emerging worldwide. Using
> + such material could pose a danger of copyright
> + violations, but it could also weaken claims to copyright
> + and void the guarantees given by copyleft licensing.
> +
> + Quality concerns.
> + Popular LLMs are really great at generating plausibly
> + looking, but meaningless content. At this point, 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.
> +
> + 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 and water.
> + - 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.
> +
> +Caveats
> + This policy can be revisited, should a case been made over such
> + a tool that does not pose copyright, ethical, and quality
> + concerns.
The original content is CC-BY-SA 4.0, and so you need attribution and
a link to the license and a statement that you altered it.
e.g.
This work is licensed under a [Creative Commons Attribution-ShareAlike 4.0 International License](https://creativecommons.org/licenses/by-sa/4.0/).
Text derived from the [Gentoo project AI policy](https://wiki.gentoo.org/wiki/Project:Council/AI_policy), used under the Creative Commons Attribution license.
>
> base-commit: ac6f5c32b3fae7549c5a42d96a3273adc24e5023
--
Cheers,
Carlos.
next prev parent reply other threads:[~2025-10-15 13:25 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 [this message]
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
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=4d14273a-ae17-4f68-9a91-e06fac1d9be5@redhat.com \
--to=carlos@redhat.com \
--cc=alx@kernel.org \
--cc=collin.funk1@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=sam@gentoo.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