1 |
On April 10, 2019 9:31:26 AM GMT+09:00, Michael Everitt <m.j.everitt@×××.org> wrote: |
2 |
>On 10/04/19 01:17, Aaron Bauman wrote: |
3 |
>> On Tue, Apr 09, 2019 at 06:49:11PM -0400, Chris Reffett wrote: |
4 |
>>> On 4/9/2019 6:10 PM, Kristian Fiskerstrand wrote: |
5 |
>>>> On 4/10/19 12:05 AM, Michael Everitt wrote: |
6 |
>>>>> Not all cases are simply ones where a person does not wish to use |
7 |
>their |
8 |
>>>>> full given name, there are perfectly decent arguments for using a |
9 |
>pseudonym |
10 |
>>>>> when there could be mild or severe ramifications if their true |
11 |
>identity was |
12 |
>>>>> in the public domain. I'm thinking as obvious examples of those |
13 |
>involved in |
14 |
>>>>> security/penetration work, where it may be required, and not |
15 |
>simply |
16 |
>>>>> desirable to keep ones primary identity confidential. Are we |
17 |
>really so |
18 |
>>>>> draconian to eliminate these (often very well-skilled individuals) |
19 |
>for |
20 |
>>>>> making a specialist contribution to Gentoo Linux?! |
21 |
>>>> The ultimate goal is to ensure that contributions are actually by |
22 |
>the |
23 |
>>>> ones holding a valid copyright, or the contribution being of a |
24 |
>license |
25 |
>>>> that is allowed under a license from the copyright holder. As |
26 |
>mentioned |
27 |
>>>> in the link in prior post, GPL itself doesn't explicitly exclude |
28 |
>the |
29 |
>>>> warranty of non-infridgement under UCC which can have severe legal |
30 |
>>>> consequences if a third party relies on the contribution, and as |
31 |
>such |
32 |
>>>> puts Gentoo in a legal liability if we can't reasonably explain |
33 |
>such |
34 |
>>>> contributions. As long as the copyright is valid and we can |
35 |
>document it, |
36 |
>>>> it is fine, but as soon as things gets murky... |
37 |
>>>> |
38 |
>> Michael, I would be very intrigued to read about such pseudonyms |
39 |
>being |
40 |
>> required by cybersecurity folks... references? |
41 |
>> |
42 |
>I was only using that as a [poor] example of ramifications of persons |
43 |
>in |
44 |
>high security fields having their public identity freely waved around |
45 |
>.. |
46 |
>(depending very much on what that particular field happened to be, and |
47 |
>who |
48 |
>you're working for; but now we're splitting hairs as well as building |
49 |
>straw |
50 |
>men .. and I'm not sure how thin this straw is ........) |
51 |
|
52 |
maybe we could also try contacting the Free Software Foundation on the matters. |
53 |
This is probably what they are doing. |
54 |
""" |
55 |
If a contributor wants the FSF to publish only a pseudonym, that is ok. The contributor should say this, and state the desired pseudonym, when answering the request- form. The actual legal papers will use the real name, but the FSF will publish only the pseudonym. 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@×××.org before sending back the signed form. [1] |
56 |
""" |
57 |
[1]https://www.gnu.org/prep/maintain/html_node/Copyright-Papers.html |
58 |
|
59 |
|
60 |
|
61 |
|
62 |
-- |
63 |
Sent from my Android device with K-9 Mail. Please excuse my brevity. |