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 65525158041 for ; Wed, 28 Feb 2024 19:27:01 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 70E69E2A23; Wed, 28 Feb 2024 19:26:57 +0000 (UTC) Received: from mail-lj1-f182.google.com (mail-lj1-f182.google.com [209.85.208.182]) (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 4197EE29D1 for ; Wed, 28 Feb 2024 19:26:57 +0000 (UTC) Received: by mail-lj1-f182.google.com with SMTP id 38308e7fff4ca-2d28e465655so1355751fa.0 for ; Wed, 28 Feb 2024 11:26:57 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709148415; x=1709753215; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=iZn5IefjOdWsnsD5aVHNm6UeBw6qltNr/hEq5TeZQ/0=; b=AvFlXVnxRTsfCBAi3+6Bvvoo2MBWG331FP7G3068MKW4l9B0ad73C3CWjVmCxTX2iC XFV7CHK7r6qC8JiTltAijHpnxr27dVE1B206LATiow70CglFb2WZ/BLJaX93ZEdm9ydA lWNHeZ4+jLHns7NgE63lPXnKoNkx8nmvc1p+qCikMotGC/68mLE7OlRPv08Hldww3UH1 uH7oifzkp8jgIoiM/pVAIax2TahBPLDWcyC2L4YGu6HIPwk5Prz+HHfsbN5LfI8KK9DD frkj1lthoVYNtmeUpOJ4ugqbR5sg1wlAcBuw7H/UcagVZuTmBrA/mtY2w4A3T/7Nc7X7 hMMA== X-Gm-Message-State: AOJu0Yy0ACokmFR1VRU9RZg433gkDeEV1tUppOfUY01/CuSxn5ZNlXia 9vfk/q+NK6FDXe6fSkh4JYYTUKaB8PN1uxV3X59bB7qQOii/l/XbSu7oVsUyNks0v+RSV3M5/SX xMA47JQVHY2z5yBo20qu/qkfgtrZC0FNt X-Google-Smtp-Source: AGHT+IFk/RBX0f3bXMXkbQzcdJ635xDST9U3/LvEhd6jhMKfh70o5HDlcVnwRDEaikRWLOXfrcZ/QbFRWfLkPolyHzI= X-Received: by 2002:a2e:855a:0:b0:2d2:e4fa:15c5 with SMTP id u26-20020a2e855a000000b002d2e4fa15c5mr659098ljj.43.1709148414861; Wed, 28 Feb 2024 11:26:54 -0800 (PST) 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 References: In-Reply-To: From: Rich Freeman Date: Wed, 28 Feb 2024 14:26:42 -0500 Message-ID: Subject: Re: [gentoo-dev] RFC: banning "AI"-backed (LLM/GPT/whatever) contributions to Gentoo To: gentoo-dev@lists.gentoo.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 8653c2dd-7c1d-464f-abcc-761ded17df9c X-Archives-Hash: b074270cceca27a031a8adf5851dadcc On Wed, Feb 28, 2024 at 1:50=E2=80=AFPM Arthur Zamarin wrote: > > I know that GitHub Copilot can be limited to licenses, and even to just > the current repository. Even though, I'm not sure that the copyright can > be attributed to "me" and not the "AI" - so still gray area. So, AI copyright is a bit of a poorly defined area simply due to a lack of case law. I'm not all that confident that courts won't make an even bigger mess of it. There are half a dozen different directions I think a court might rule on the matter of authorship and derived works, but I think it is VERY unlikely that a court will rule that the copyright will be attributed to the AI itself, or that the AI itself ever was an author or held any legal rights to the work at any point in time. An AI is not a legal entity. The company that provides the service, its employees/developers, the end user, and the authors and copyright holders of works used to train the AI are all entities a court is likely to consider as having some kind of a role. That said, we live in a world where it isn't even clear if APIs can be copyrighted, though in practice enforcing such a copyright might be impossible. It could be a while before AI copyright concerns are firmly settled. When they are, I suspect it will be done in a way that frustrates just about everybody on every side... IMO the main risk to an organization (especially a transparent one like ours) from AI code isn't even whether it is copyrightable or not, but rather getting pulled into arguments and debates and possibly litigation over what is likely to be boilerplate code that needs a lot of cleanup anyway. Even if you "win" in court or the court of public opinion, the victory can be pyrrhic. -- Rich