From: "Jérôme Carretero" <cJ-gentoo@zougloub.eu>
To: martin-kokos <martin-kokos@protonmail.com>,
"Michał Górny" <mgorny@gentoo.org>,
"Robin H. Johnson" <robbat2@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: banning "AI"-backed (LLM/GPT/whatever) contributions to Gentoo
Date: Mon, 15 Apr 2024 15:50:06 -0400 [thread overview]
Message-ID: <9007c921a8a57655ecb2027eb4be4bff02673af4.camel@zougloub.eu> (raw)
In-Reply-To: <f756ba8ce323ac57b005a0f81b0b62f4b52854d7.camel@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1752 bytes --]
Hi,
It's a good thing that
https://wiki.gentoo.org/wiki/Project:Council/AI_policy
has been voted, and that it mentions:
> This motion can be revisited, should a case been made over such a
tool that does not pose copyright, ethical and quality concerns.
I wanted to provide some meat to discuss improvements of the specific
phrasing "created with the assistance of Natural Language
Processing artificial intelligence tools" which may not be the most
optimal.
First, I think we should not limit this to LLMs / NLP stuff, when it
should be about all algorithmically/automatically generated content,
which could all cause a flood of time-wasting, low-quality information.
Second, I think we should define what would be acceptable use cases of
algorithmically-generated content; I'd suggest for a starting point,
the combination of:
- The algorithm generating such content is proper F/LOSS
- In the case of a machine learning algorithm, the dataset allowing
to generate such algorithm is proper F/LOSS itself (with traceability
of all of its bits)
- The algorithm generating such content is reproducible (training
produces the exact same bits)
- The algorithm did not publish the content automatically: all the
content was reviewed and approved by a human, who bears responsibility
for their contribution, and the content has been flagged as having been
generated using $tool.
Third, I think a "developer certificate of origin" policy could be
augmented with the "bot did not publish the content automatically" bits
and should also be mandated in the context of bug reporting, so as to
have a "human gate" for issues discovered by automation / tinderboxes.
Best regards,
--
Jérôme
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 854 bytes --]
prev parent reply other threads:[~2024-04-15 19:50 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 14:45 [gentoo-dev] RFC: banning "AI"-backed (LLM/GPT/whatever) contributions to Gentoo Michał Górny
2024-02-27 15:10 ` Arsen Arsenović
2024-02-27 15:21 ` Kenton Groombridge
2024-02-27 15:31 ` Alex Boag-Munroe
2024-02-27 16:11 ` Marek Szuba
2024-02-27 16:29 ` Sam James
2024-02-27 16:48 ` Andreas K. Huettel
2024-02-27 17:02 ` Ionen Wolkens
2024-02-27 17:41 ` Rich Freeman
2024-02-27 18:07 ` Ulrich Mueller
2024-02-27 18:27 ` Kenton Groombridge
2024-02-27 17:46 ` Matthias Maier
2024-02-27 17:50 ` Roy Bamford
2024-02-27 18:40 ` Peter Böhm
2024-02-27 18:04 ` Sam James
2024-03-09 14:57 ` Michał Górny
2024-02-27 19:17 ` Eli Schwartz
2024-02-28 3:05 ` Oskari Pirhonen
2024-02-28 3:12 ` Michał Górny
2024-02-28 10:08 ` Ulrich Mueller
2024-02-28 11:06 ` Matt Jolly
2024-02-28 20:20 ` Eli Schwartz
2024-03-01 7:06 ` Sam James
2024-03-09 15:00 ` Michał Górny
2024-02-28 13:09 ` Michał Górny
2024-02-28 10:34 ` David Seifert
2024-02-28 18:50 ` Arthur Zamarin
2024-02-28 19:26 ` Rich Freeman
2024-03-01 6:33 ` Zoltan Puskas
2024-03-05 6:12 ` Robin H. Johnson
2024-03-06 6:53 ` Oskari Pirhonen
2024-03-08 3:59 ` [gentoo-dev] " Duncan
2024-03-09 15:04 ` Michał Górny
2024-03-09 21:13 ` Duncan
2024-03-10 1:53 ` Eli Schwartz
2024-03-06 13:53 ` [gentoo-dev] " martin-kokos
2024-03-08 7:09 ` Fco. Javier Felix Belmonte
2024-03-21 15:25 ` Michał Górny
2024-04-15 19:50 ` Jérôme Carretero [this message]
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=9007c921a8a57655ecb2027eb4be4bff02673af4.camel@zougloub.eu \
--to=cj-gentoo@zougloub.eu \
--cc=gentoo-dev@lists.gentoo.org \
--cc=martin-kokos@protonmail.com \
--cc=mgorny@gentoo.org \
--cc=robbat2@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