From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: banning "AI"-backed (LLM/GPT/whatever) contributions to Gentoo
Date: Tue, 27 Feb 2024 12:41:42 -0500 [thread overview]
Message-ID: <CAGfcS_k-8MmEivL8_MUwGGM9t+Zdd8iPczc=dBNFF1QBbcGdqw@mail.gmail.com> (raw)
In-Reply-To: <a2b8c68b1649213cf237f40e41f9a460a5667c34.camel@gentoo.org>
On Tue, Feb 27, 2024 at 9:45 AM Michał Górny <mgorny@gentoo.org> wrote:
>
> Given the recent spread of the "AI" bubble, I think we really need to
> look into formally addressing the related concerns.
> 1. Copyright concerns.
I do think it makes sense to consider some of this.
However, I feel like the proposal is redundant with the existing
requirement to signoff on the DCO, which says:
>>> By making a contribution to this project, I certify that:
>>> 1. The contribution was created in whole or in part by me, and
>>> I have the right to submit it under the free software license
>>> indicated in the file; or
>>> 2. The contribution is based upon previous work that, to the best of
>>> my knowledge, is covered under an appropriate free software license,
>>> and I have the right under that license to submit that work with
>>> modifications, whether created in whole or in part by me, under the
>>> same free software license (unless I am permitted to submit under a
>>> different license), as indicated in the file; or
>>> 3. The contribution is a license text (or a file of similar nature),
>>> and verbatim distribution is allowed; or
>>> 4. The contribution was provided directly to me by some other person
>>> who certified 1., 2., 3., or 4., and I have not modified it.
Perhaps we ought to just re-advertise the policy that already exists?
> 2. Quality concerns.
As far as quality is concerned, I again share the concerns you raise,
and I think we should just re-emphasize what many other industries are
already making clear - that individuals are responsible for the
quality of their contributions. Copy/pasting it blindly from an AI is
no different from copy/pasting it from some other random website, even
if it is otherwise legal.
> 3. Ethical concerns.
I think it is best to just avoid taking a stand on this. Our ethics
are already documented in the Social Contract.
I think everybody agrees that what is right and wrong is obvious and
clear and universal. Then we're all shocked to find that large
numbers of people have a universal perspective different from our own.
Even if 90% of contributors agree with a particular position, if we
start lopping off parts of our community 10% at a time we'll probably
find ourselves alone in a room sooner or later. We can't make every
hill the one to die on.
> I think adding "made by real people" to the list of our advantages
> would be a good thing
Somehow I doubt this is going to help us steal market share from the
numerous other popular source-based Linux distros. :)
To be clear, I don't think it is a bad idea to just reiterate that we
aren't looking for help from people who want to create scripts that
pipe things into some GPT API and pipe the output into a forum, bug,
issue, PR, or commit. I've seen other FOSS projects struggling with
people trying to be "helpful" in this way. I just don't think any of
this actually requires new policy. If we find our policy to be
inadequate I think it is better to go back to the core principles and
better articulate what we're trying to achieve, rather than adjust it
to fit the latest fashions.
--
Rich
next prev parent reply other threads:[~2024-02-27 17:42 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 [this message]
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
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='CAGfcS_k-8MmEivL8_MUwGGM9t+Zdd8iPczc=dBNFF1QBbcGdqw@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-dev@lists.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