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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id D0192138334 for ; Wed, 14 Nov 2018 08:24:30 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7B2C9E09E7; Wed, 14 Nov 2018 08:24:29 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 2EF16E09AD for ; Wed, 14 Nov 2018 08:24:28 +0000 (UTC) Received: from a1i15 (host2092.kph.uni-mainz.de [134.93.134.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: ulm) by smtp.gentoo.org (Postfix) with ESMTPSA id A7D1D335C5D; Wed, 14 Nov 2018 08:24:26 +0000 (UTC) From: Ulrich Mueller To: gentoo-project@lists.gentoo.org Subject: Re: [gentoo-project] rfc: copyright attribution clarifications References: <20181113183242.GA26771@whubbs1.gaikai.biz> <20181114024643.GA15537@linux1.home> Date: Wed, 14 Nov 2018 09:24:08 +0100 In-Reply-To: <20181114024643.GA15537@linux1.home> (William Hubbs's message of "Tue, 13 Nov 2018 20:46:43 -0600") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Project discussion list X-BeenThere: gentoo-project@lists.gentoo.org Reply-To: gentoo-project@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" X-Archives-Salt: 06e03e7e-ea62-4b8b-9de2-88a07e7b0b11 X-Archives-Hash: 006bd4098b0a29e1f629a2e35a33b7a6 --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable >>>>> On Wed, 14 Nov 2018, William Hubbs wrote: > On Tue, Nov 13, 2018 at 06:17:17PM -0800, Rich Freeman wrote: >> So, the purpose of allowing specific copyright holders to be named >> was to cover cases where we're forking foreign code, not to basically >> introduce a variant on the BSD advertising clause. IMO people who are >> only willing to contribute FOSS if their name gets put in a prominent >> location might do better to contribute elsewhere. +1000 Maybe the policy for the Gentoo repository should just say that, namely that traditional copyright notices are only allowed for imported foreign code. Anything committed directly to the repository and any update of an existing file would be required to carry the simplified "Gentoo Authors" copyright notice, without any exceptions allowed. Can someone come up with a good wording for this? > Do you feel this way about corporations as well? Do you think the > Linux kernel maintainers should go and rip out all copyright notices > other than Linus Torvalds and maybe the Linux Foundation? Why would corporations be different from individual authors? Under the legislation here, corporations cannot even hold copyright (or rather, Urheberrecht) of a work. >> The purpose of a copyright notice is to declare that the file is >> copyrighted, and that is it. Exactly. >> It isn't a comprehensive list of everybody who holds a copyright on >> the file. >>=20 >> It isn't a revision history. >>=20 >> There is no need to list various mixes of years and authors. Just >> list the first and last year, and whatever copyright holders are >> necessary. >> >> [...] >>=20 >> But, if you had to have multiple lines, then just wrap the existing >> notice. Don't turn it into some kind of revision history. Just list >> one year range and whatever list of entities you feel compelled to >> list. That is the proper way to do a notice. > No sir, it isn't. > Look anywhere outside the Gentoo tree. For that matter, take the Linux > kernel, or even in the systemd source, there are several places with > multiple copyright notices in them. Are these the only arguments you have? To say it again, ebuilds have a copyright notice for exactly two reasons: =2D to protect us against the "innocent infringement" defense under U.S. law, and =2D because the GPL-2 requires in section 1 to "appropriately publish on each copy an appropriate copyright notice". For both of these, it is irrelevant what the precise contents of the notice is. If you made a significant contribution to the file, then you can claim copyright for it, even if there is no copyright notice at all, of if you aren't mentioned in it. IANAL, but I think the case for being listed there explicitly is very weak. Ulrich --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEZlHkP3TnuTbxrN0HwwkGhRxhwnMFAlvr26gACgkQwwkGhRxh wnOUtAf7B5NGWfoQkWkSsAwmh4ruuUiIDyzpAygVxYQdNWJXr6jdK2Cv2G27Rd7y QONSxEw5uF+L+SAoOEuRzwMXcsFDOvmot+hXI6UMabFRRNVx4AnGdzKghedETQyk XD5h+8qokNiEwovAUc9SBXquUYaylgWOVjWANEa6QDzzk0gD2S0I0IEbSlrqDqFF GWcuM6BMFeHC8B5Kj/NM9UG7z6nLYaRE6GAnZu1d0Pu/3+p5UrQjRShZMpjhERwC 2dGWy3WRFg2B8z0hzGybdJFGFLjhTyitZiElmnEI9etSYpYKmsykYQmphMmb5/2R c3BIegALkU5myLBOL+40ntRlQduvAA== =5DEu -----END PGP SIGNATURE----- --=-=-=--