Gentoo Archives: gentoo-project

From: Michael Everitt <m.j.everitt@×××.org>
To: gentoo-project@l.g.o
Subject: Re: [gentoo-project] call for agenda items -- council meeting 2019-04-14
Date: Wed, 10 Apr 2019 00:31:37
Message-Id: adab675c-0b92-9f86-7030-efea33ba99e8@iee.org
In Reply to: Re: [gentoo-project] call for agenda items -- council meeting 2019-04-14 by Aaron Bauman
1 On 10/04/19 01:17, Aaron Bauman wrote:
2 > On Tue, Apr 09, 2019 at 06:49:11PM -0400, Chris Reffett wrote:
3 >> On 4/9/2019 6:10 PM, Kristian Fiskerstrand wrote:
4 >>> On 4/10/19 12:05 AM, Michael Everitt wrote:
5 >>>> Not all cases are simply ones where a person does not wish to use their
6 >>>> full given name, there are perfectly decent arguments for using a pseudonym
7 >>>> when there could be mild or severe ramifications if their true identity was
8 >>>> in the public domain. I'm thinking as obvious examples of those involved in
9 >>>> security/penetration work, where it may be required, and not simply
10 >>>> desirable to keep ones primary identity confidential. Are we really so
11 >>>> draconian to eliminate these (often very well-skilled individuals) for
12 >>>> making a specialist contribution to Gentoo Linux?!
13 >>> The ultimate goal is to ensure that contributions are actually by the
14 >>> ones holding a valid copyright, or the contribution being of a license
15 >>> that is allowed under a license from the copyright holder. As mentioned
16 >>> in the link in prior post, GPL itself doesn't explicitly exclude the
17 >>> warranty of non-infridgement under UCC which can have severe legal
18 >>> consequences if a third party relies on the contribution, and as such
19 >>> puts Gentoo in a legal liability if we can't reasonably explain such
20 >>> contributions. As long as the copyright is valid and we can document it,
21 >>> it is fine, but as soon as things gets murky...
22 >>>
23 > Michael, I would be very intrigued to read about such pseudonyms being
24 > required by cybersecurity folks... references?
25 >
26 I was only using that as a [poor] example of ramifications of persons in
27 high security fields having their public identity freely waved around ..
28 (depending very much on what that particular field happened to be, and who
29 you're working for; but now we're splitting hairs as well as building straw
30 men .. and I'm not sure how thin this straw is ........)

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies