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 14CC3138334 for ; Wed, 10 Apr 2019 01:12:42 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BDF33E08A6; Wed, 10 Apr 2019 01:12:40 +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 7626EE087B for ; Wed, 10 Apr 2019 01:12:40 +0000 (UTC) Received: from [IPv6:2a03:8600:1001:4000::1867] (unknown [IPv6:2a03:8600:1001:4000::1867]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: alicef@gentoo.org) by smtp.gentoo.org (Postfix) with ESMTPSA id AAC2F335D52; Wed, 10 Apr 2019 01:12:36 +0000 (UTC) Date: Wed, 10 Apr 2019 10:12:24 +0900 User-Agent: K-9 Mail for Android In-Reply-To: References: <80ed2e482e96c96555bf4fd9331731c4c9ad0d7f.camel@gentoo.org> <232747ba-063c-821f-a66d-5f106ed2aa82@gentoo.org> <465cf0eb-3323-d71f-e6a7-862f0940f54b@iee.org> <9b6b02c8-bc96-6e5d-d99a-56e9290479b0@gentoo.org> <20190410001756.GH8129@monkey> 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 X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----QV2PVN0BJJ4K3SK6OB4S63HTWH6UOF" Content-Transfer-Encoding: 7bit Subject: Re: [gentoo-project] call for agenda items -- council meeting 2019-04-14 To: gentoo-project@lists.gentoo.org,Michael Everitt From: Alice Ferrazzi Message-ID: <0317EBF1-30A8-4635-B90B-7D3E37CB085A@gentoo.org> X-Archives-Salt: a7997782-8b5a-4c55-8885-978562fdc391 X-Archives-Hash: e9bca90fa1e299d1af7ce6b09edc170a ------QV2PVN0BJJ4K3SK6OB4S63HTWH6UOF Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On April 10, 2019 9:31:26 AM GMT+09:00, Michael Everitt wrote: >On 10/04/19 01:17, Aaron Bauman wrote: >> On Tue, Apr 09, 2019 at 06:49:11PM -0400, Chris Reffett wrote: >>> On 4/9/2019 6:10 PM, Kristian Fiskerstrand wrote: >>>> On 4/10/19 12:05 AM, Michael Everitt wrote: >>>>> Not all cases are simply ones where a person does not wish to use >their >>>>> full given name, there are perfectly decent arguments for using a >pseudonym >>>>> when there could be mild or severe ramifications if their true >identity was >>>>> in the public domain=2E I'm thinking as obvious examples of those >involved in >>>>> security/penetration work, where it may be required, and not >simply >>>>> desirable to keep ones primary identity confidential=2E Are we >really so >>>>> draconian to eliminate these (often very well-skilled individuals) >for >>>>> making a specialist contribution to Gentoo Linux?! >>>> The ultimate goal is to ensure that contributions are actually by >the >>>> ones holding a valid copyright, or the contribution being of a >license >>>> that is allowed under a license from the copyright holder=2E As >mentioned >>>> in the link in prior post, GPL itself doesn't explicitly exclude >the >>>> warranty of non-infridgement under UCC which can have severe legal >>>> consequences if a third party relies on the contribution, and as >such >>>> puts Gentoo in a legal liability if we can't reasonably explain >such >>>> contributions=2E As long as the copyright is valid and we can >document it, >>>> it is fine, but as soon as things gets murky=2E=2E=2E >>>> >> Michael, I would be very intrigued to read about such pseudonyms >being >> required by cybersecurity folks=2E=2E=2E references? >> >I was only using that as a [poor] example of ramifications of persons >in >high security fields having their public identity freely waved around >=2E=2E >(depending very much on what that particular field happened to be, and >who >you're working for; but now we're splitting hairs as well as building >straw >men =2E=2E and I'm not sure how thin this straw is =2E=2E=2E=2E=2E=2E=2E= =2E) maybe we could also try contacting the Free Software Foundation on the mat= ters=2E This is probably what they are doing=2E """ If a contributor wants the FSF to publish only a pseudonym, that is ok=2E = The contributor should say this, and state the desired pseudonym, when answ= ering the request- form=2E The actual legal papers will use the real name, = but the FSF will publish only the pseudonym=2E When using one of the other = forms, fill in the real name but ask the contributor to discuss the use of = a pseudonym with assign@gnu=2Eorg before sending back the signed form=2E [1= ] """ =EF=BC=BB1=EF=BC=BDhttps://www=2Egnu=2Eorg/prep/maintain/html_node/Copyrig= ht-Papers=2Ehtml --=20 Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E ------QV2PVN0BJJ4K3SK6OB4S63HTWH6UOF Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
--
Sent from my Android device with K-9 Mail=2E Please excuse my br= evity=2E ------QV2PVN0BJJ4K3SK6OB4S63HTWH6UOF--