public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sam James <sam@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 16:29:56 +0000	[thread overview]
Message-ID: <8734td98fv.fsf@gentoo.org> (raw)
In-Reply-To: <8f080af1-5d67-45ac-94a1-6bb072bfb410@gentoo.org> (Marek Szuba's message of "Tue, 27 Feb 2024 16:11:15 +0000")

Marek Szuba <marecki@gentoo.org> writes:

> On 2024-02-27 14:45, Michał Górny wrote:
>
>> In my opinion, at this point the only reasonable course of action
>> would be to safely ban "AI"-backed contribution entirely.  In other
>> words, explicitly forbid people from using ChatGPT, Bard, GitHub
>> Copilot, and so on, to create ebuilds, code, documentation, messages,
>> bug reports and so on for use in Gentoo.
>
> I very much support this idea, for all the three reasons quoted.
>
>> 2. Quality concerns.  LLMs are really great at generating plausibly
>> looking bullshit.  I suppose they can provide good assistance if you
>> are careful enough, but we can't really rely on all our contributors
>> being aware of the risks.
>
> https://arxiv.org/abs/2211.03622
>
>> 3. Ethical concerns.
>
> ...yeah. Seeing as we failed to condemn the Russian invasion of
> Ukraine in 2022, I would probably avoid quoting this as a reason for
> banning LLM-generated contributions. Even though I do, as mentioned
> above, very much agree with this point.

That's not a technical topic and we had an extended discussion about
what to do in -core, which included the risks of making life difficult
for Russian developers and contributors.

I don't think that's a helpful intervention here, sorry.


  reply	other threads:[~2024-02-27 16:30 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 [this message]
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

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=8734td98fv.fsf@gentoo.org \
    --to=sam@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