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 C1CBD138334 for ; Wed, 20 Jun 2018 14:19:17 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5A58AE0AB5; Wed, 20 Jun 2018 14:19:15 +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 18707E0AB4 for ; Wed, 20 Jun 2018 14:19:14 +0000 (UTC) Received: from a1i15.kph.uni-mainz.de (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 AA93A335C81; Wed, 20 Jun 2018 14:19:12 +0000 (UTC) Message-ID: <23338.25180.848200.115544@a1i15.kph.uni-mainz.de> Date: Wed, 20 Jun 2018 16:19:08 +0200 To: gentoo-project@lists.gentoo.org Subject: Re: [gentoo-project] Date-of-birth in developer applications In-Reply-To: References: <1529482561.2506.17.camel@gentoo.org> <756a345e-0209-9643-c94f-1cf94321eb2a@gentoo.org> <1529483543.2506.23.camel@gentoo.org> <29af132e-824d-3be5-9d11-3c80880ce9be@gentoo.org> <23338.20801.443208.509771@a1i15.kph.uni-mainz.de> X-Mailer: VM 8.2.0b under 24.3.1 (x86_64-pc-linux-gnu) From: Ulrich Mueller 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="pgp+signed+rFLbIZpL/zUZocY"; micalg=pgp-sha256; protocol="application/pgp-signature" X-Archives-Salt: 71cb707c-423b-4327-ae3d-e1b3a6f2a7b0 X-Archives-Hash: 7a09d94627b499ef9ac4c5e2568d56ec This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --pgp+signed+rFLbIZpL/zUZocY Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit >>>>> On Wed, 20 Jun 2018, Rich Freeman wrote: > Past developers may not be reachable, cooperative, or even alive. > If we need information or assurances from them, we should obtain it > BEFORE we accept commits, not try to chase it down years later. Right, but we can do so only for the future, but not fix any past mistakes. > I'd be interested in any cases where we felt this was necessary. > I know that a lot of work was done recently to try to figure out the > license history of the tree, but honestly I'm not convinced it was > necessary, and legally digging into messy situations can sometimes > even be harmful. In general I think forward-looking solutions tend > to be best unless there is a clear legal duty to look backwards. The tree may be the least of our problems, because all files have a license notice there. For other things like documentation, I had contacted some retired devs. For example, parts of the devmanual were under CC-BY-SA-1.0 and needed explicit relicensing by its author. Another example, a few days ago I stumbled upon this: https://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo/xml/htdocs/dtd/ (It's in https://gitweb.gentoo.org/data/dtd.git/tree/ nowadays, without its history.) Assuming that these files are copyrightable (and I would say so, for a file with 300+ lines and 10 kB size), they should really have a license header. So, should we try to contact all authors, or continue to ignore the issue? (Or even, rewrite everything from scratch?) Ulrich --pgp+signed+rFLbIZpL/zUZocY Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBCAAGBQJbKmJZAAoJEMMJBoUcYcJzLn0H/iUDB/7KiuAQ4yywOST1ZoTI BqbcbS0YaaNOYbXC7fnPSy1Zq+BmUeRJPZdRJ+kzWlygBO6eisabsH3Crgjc8vXL 5yAd5NWFhiSHKjemXmjw1uzMeB17QF+Z0FtZDgkDx3FC94RN6VX7DjVl/+354jcm 1z9LoZa0XWsxTCsrgxQw6QYxcRWa77aAd2I+1kRobqkrcLFh7M4MlT49vP+1Ue3d a1dZkmcG8i64nVvyNLv2caf7lo84YuYPmDyJaBpPaI0HG0ly7+3WHALJwB/MNFvB ZBebjrv06VVC+ZQTfKbmYIsDKpT2qiyl0DbvvxbiDOu9VTf/zUgPIGv16pagr3s= =1dlh -----END PGP SIGNATURE----- --pgp+signed+rFLbIZpL/zUZocY--