From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 4819A158041 for ; Sat, 9 Mar 2024 15:00:12 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 64586E2A3D; Sat, 9 Mar 2024 15:00:08 +0000 (UTC) Received: from smtp.gentoo.org (dev.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 01317E2A34 for ; Sat, 9 Mar 2024 15:00:07 +0000 (UTC) Message-ID: <5ea67def67d55e994d4603d752b4c87f3b464e2e.camel@gentoo.org> Subject: Re: [gentoo-dev] RFC: banning "AI"-backed (LLM/GPT/whatever) contributions to Gentoo From: =?UTF-8?Q?Micha=C5=82_G=C3=B3rny?= To: gentoo-dev@lists.gentoo.org, Matt Jolly Date: Sat, 09 Mar 2024 16:00:02 +0100 In-Reply-To: <875xy6sa6x.fsf@gentoo.org> References: <076b8ede8f3e2d6d49571d516132a96a08b4d591.camel@gentoo.org> <875xy6sa6x.fsf@gentoo.org> Organization: Gentoo Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=-WxXeHAiS5yt+MEOnVkz7" User-Agent: Evolution 3.50.4 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 X-Archives-Salt: 900f8127-6e65-4350-90f1-981c44195a85 X-Archives-Hash: 13139ff21fcbd072b0a6a6e62817ba6d --=-WxXeHAiS5yt+MEOnVkz7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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? --=20 Best regards, Micha=C5=82 G=C3=B3rny --=-WxXeHAiS5yt+MEOnVkz7 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- iQFGBAABCgAwFiEEx2qEUJQJjSjMiybFY5ra4jKeJA4FAmXseXISHG1nb3JueUBn ZW50b28ub3JnAAoJEGOa2uIyniQOzIgIAINqoJ2MJtEzCMlDLJacn1l78F09fVUv XJOz4MQimGhwbX7mMiUL1KiNsev1kRrzIBy7lWhAfFbfVdFupKG9LE/qt81PlDIb RLQlMHbSkXOWBzOhxinUSbE6xiTVBAIIPIDvKY/aL6JzKfJ2j8pTVoWSpGwoJFMz 4ZFO9W+AJwmLLlzevm/ZEHVl512Ep/OtRg9oz912Ewe0+JiknCnF85BXixbj6Pof PTz030vIrbzAbAW2W2IM8cCbsBYU2iqHSqmWVY/6d2Q3ZqFK1YgiM2ARDUBY12M1 QGQ2381hBSEL76ogBqabcOK3bpM3GzCGgcrpSlk7aE5qeOx55aVoByo= =6diG -----END PGP SIGNATURE----- --=-WxXeHAiS5yt+MEOnVkz7--