public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Oskari Pirhonen <xxc3ncoredxx@gmail.com>
To: "Michał Górny" <mgorny@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: banning "AI"-backed (LLM/GPT/whatever) contributions to Gentoo
Date: Tue, 27 Feb 2024 21:05:16 -0600	[thread overview]
Message-ID: <Zd6i7GMVrNXwoicc@dj3ntoo> (raw)
In-Reply-To: <a2b8c68b1649213cf237f40e41f9a460a5667c34.camel@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1829 bytes --]

On Tue, Feb 27, 2024 at 15:45:17 +0100, Michał Górny wrote:
> Hello,
> 
> Given the recent spread of the "AI" bubble, I think we really need to
> look into formally addressing the related concerns.  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.
> 
> Just to be clear, I'm talking about our "original" content.  We can't do
> much about upstream projects using it.
> 

I agree.

But for the sake of discussion:

What about cases where someone, say, doesn't have an excellent grasp of
English and decides to use, for example, ChatGPT to aid in writing
documentation/comments (not code) and puts a note somewhere explicitly
mentioning what was AI-generated so that someone else can take a closer
look?

I'd personally not be the biggest fan of this if it wasn't in something
like a PR or ml post where it could be reviewed before being made final.
But the most impportant part IMO would be being up-front about it.

> 
> Rationale:
> 
> 1. Copyright concerns.  At this point, the copyright situation around
> generated content is still unclear.  What's pretty clear is that pretty
> much all LLMs are trained on huge corpora of copyrighted material, and
> all fancy "AI" companies don't give shit about copyright violations.
> In particular, there's a good risk that these tools would yield stuff we
> can't legally use.
> 

I really dislike the lack of audit trail for where the bits and pieces
come from. Not to mention the examples from early on where Copilot was
filling in incorrect attribution.

- Oskari

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  parent reply	other threads:[~2024-02-28  3:05 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 [this message]
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=Zd6i7GMVrNXwoicc@dj3ntoo \
    --to=xxc3ncoredxx@gmail.com \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=mgorny@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