From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org, Matt Jolly <kangie@gentoo.org>
Subject: Re: [gentoo-dev] RFC: banning "AI"-backed (LLM/GPT/whatever) contributions to Gentoo
Date: Sat, 09 Mar 2024 16:00:02 +0100 [thread overview]
Message-ID: <5ea67def67d55e994d4603d752b4c87f3b464e2e.camel@gentoo.org> (raw)
In-Reply-To: <875xy6sa6x.fsf@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 620 bytes --]
On Fri, 2024-03-01 at 07:06 +0000, Sam James wrote:
> Another person approached me after this RFC and asked whether tooling
> restricted to the current repo would be okay. For me, that'd be mostly
> acceptable, given it won't make suggestions based on copyrighted code.
I think an important question is: how is it restricted? Are we talking
about a tool that was clearly trained on specific code, or about a tool
that was trained on potentially copyright material, then artificially
restricted to the repository (to paper over the concerns)? Can we trust
the latter?
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
next prev parent reply other threads:[~2024-03-09 15:00 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 [this message]
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=5ea67def67d55e994d4603d752b4c87f3b464e2e.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=kangie@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