Gentoo Archives: gentoo-project

From: kuzetsa <kuzetsa@×××××.com>
To: gentoo-project@l.g.o
Subject: Re: [gentoo-project] [RFC] GLEP 76: Copyright Policy [v4]
Date: Thu, 27 Sep 2018 14:14:18
Message-Id: 3213a040-f131-b9be-b350-4bbcda10427c@gmail.com
In Reply to: Re: [gentoo-project] [RFC] GLEP 76: Copyright Policy [v4] by Rich Freeman
1 On 09/27/2018 09:43 AM, Rich Freeman wrote:
2 > On Thu, Sep 27, 2018 at 9:08 AM kuzetsa <kuzetsa@×××××.com> wrote:
3 >>
4 >> in this case, the GCO (or the DCO from which it borrowed it's ideas)
5 >> should explicitly state its purposes, rather than relying on the
6 >> assumption that a person can be tracked down if the license was is ever
7 >> in doubt.
8 >
9 > While I'm all for having background, I don't see how it actually
10 > changes the situation.
11 >
12 > Also, there is no need to track people down, ever. The purpose of the
13 > GCO/DCO is to make the contributor liable for their contributions, and
14 > this is already accomplished. If the true copyright holder wants to
15 > try to track them down that is their problem.
16
17 This suggests the "real name" requirement from GCO / DCO could be
18 enforced, but isn't. Even if name alone was all that is truly required,
19 without a way to tie a specific name to a specific person who has the
20 same name, the legal meaning is moot due to "real names" not being a
21 unique identifier.
22
23 > If somebody provides us evidence that they are the true copyright
24 > holder and ask us to remove their code, we simply have to remove their
25 > code. No stack of licenses/certificates/attestations/etc will ever
26 > change that.
27 >
28 > It is like buying a house. If you buy a house from somebody, and it
29 > later turns out that they never owned the house, then the owner is
30 > going to be able to take his house back from you free of charge. It
31 > doesn't matter how many documents the "seller" signed in the process -
32 > it was never their house to sell. However, those documents CAN place
33 > some liability on them for such things, or provide you with due
34 > diligence / reasonable care so that it shows that you acted in good
35 > faith and the owner won't go after you beyond just getting back their
36 > house. You're still out the house either way.
37
38 Nobody is proving their name or where they're located. In this metaphor,
39 I believe gentoo is the one buying a house without verifying the
40 identity of the seller. (see above)
41
42 > I believe this is the basic principle behind these kinds of documents.
43 > It is basically an affirmation of compliance, which is a form of
44 > showing reasonable care on the part of the recipient.
45 >
46 >>
47 >> people can and do physically relocate from time to time, and if they're
48 >> no longer a contributor there's no way to track them down, should the
49 >> need arise for any legal or ethical questions (the kind of purpose which
50 >> the policy makes no mention of: a way to reach the contributor)
51 >>
52 >
53 > See above. Tracking down the contributor is unlikely to really get us
54 > far, and it really makes no sense. The purpose of the DCO is to
55 > collect the affirmation of compliance up-front so that we don't have
56 > to try to get it later. It doesn't change who owns copyright. If it
57 > turns out somebody lied to us then bad things will always happen, but
58 > they just won't be as bad as they could have been.
59 >
60
61 It's true that affirmation of compliance would be helpful, but if gentoo
62 doesn't ask for that diligently, relying on the presumed validity of a
63 name (and no other significant metadata) is little use to anyone's legal
64 injury which could've been prevented be a more rigorous policy.
65
66 -