1 |
>>>>> On Tue, 02 Oct 2018, NP-Hardass wrote: |
2 |
|
3 |
> On 09/29/2018 03:46 AM, Ulrich Mueller wrote: |
4 |
>> IANAL, but as I understand it, the requirements for the name that |
5 |
>> appears in a copyright notice are rather lax, and your quote from the |
6 |
>> Berne convention seems to confirm that. Also there is nothing in the |
7 |
>> GLEP's wording that would forbid the use of a pseudonym in the copyright |
8 |
>> notice, as long as it will qualify as an identifier of the copyright |
9 |
>> holder. (The Signed-off-by line is a different issue, though.) |
10 |
|
11 |
> "For commits made using a VCS, the committer shall certify agreement to |
12 |
> the Certificate of Origin by adding Signed-off-by: Name <e-mail> to the |
13 |
> commit message as a separate line. Committers must use their real name, |
14 |
> i.e., the name that would appear in an official document like a passport." |
15 |
|
16 |
> "By making a contribution to this project, I certify that: |
17 |
> [...] |
18 |
> The contribution was provided directly to me by some other person who |
19 |
> certified 1., 2., 3., or 4., and I have not modified it." |
20 |
|
21 |
> Which means a contribution of pseudonymous copywritten code cannot be |
22 |
> made. The person making the commit cannot sign off on it unless the |
23 |
> author signs off on it, and the author cannot sign off on it because |
24 |
> that requires that the author not be pseudonymous. |
25 |
|
26 |
That doesn't contradict my statement that the author be listed under a |
27 |
pseudonym in the copyright notice (or in an attribution). |
28 |
|
29 |
> UNLESS you think this falls under #2: |
30 |
> "The contribution is based upon previous work that, to the best of my |
31 |
> knowledge, is covered under an appropriate free software license, and I |
32 |
> have the right under that license to submit that work with |
33 |
> modifications, whether created in whole or in part by me, under the same |
34 |
> free software license (unless I am permitted to submit under a different |
35 |
> license), as indicated in the file; or" |
36 |
> Which, as written, means that the committer must make a modifications to |
37 |
> the pseudonymous work to qualify as "[FOSS licensed and] created in |
38 |
> whole or in part by me." |
39 |
|
40 |
That wording has be copied from the Linux DCO. Presumably it would be |
41 |
clearer if it said "submit that work with or without modifications". |
42 |
If unmodified distribution/submission was not allowed, the license |
43 |
wouldn't qualify as a free software license, in the first place. |
44 |
|
45 |
> The premise of which is that pseudonymous contributions aren't allowed |
46 |
> unless the author submits it as a patch, not using a VCS (as |
47 |
> contributions via VCS must use the Certificate of Origin), and the |
48 |
> committer makes some trivial modification to them, and then, by magic, |
49 |
> we avoid requirements for real names. |
50 |
|
51 |
See above, the right to distribute the work with modifications doesn't |
52 |
preclude its distribution without modifications. |
53 |
|
54 |
The only problem I see is that usually it would not be very polite to |
55 |
sign off someone else's work. However, I don't think there is a real |
56 |
problem with that, as long as the committer can confirm that the |
57 |
contribution is under a free software license. |
58 |
|
59 |
Ulrich |