1 |
On Fri, Oct 12, 2018 at 7:34 AM Sarah White <kuzetsa@××××××××××.ovh> wrote: |
2 |
> |
3 |
> On 10/11/2018 09:59 PM, Rich Freeman wrote: |
4 |
> |
5 |
> I think the confusion / misunderstanding here is evidence |
6 |
> of exactly what I was referring to. Copyright Notices are |
7 |
> notices that a copyright is held, and GLEP 76 is titled: |
8 |
> |
9 |
> "Copyright Policy", and only mentions copyright notices. |
10 |
|
11 |
It also includes the GCO/DCO, which is verification of the right to |
12 |
redistribute and accuracy of the license, which is copyright-related. |
13 |
It originally included an FLA as well, but this was removed. |
14 |
|
15 |
> |
16 |
> Do "gentoo authors" file a lawsuit when there's infringement? |
17 |
> |
18 |
> That was the main / only thing I was referring to. |
19 |
|
20 |
And I answered this in the part you didn't quote inline. "Gentoo |
21 |
authors" would not file a lawsuit. Any copyright holder can file a |
22 |
lawsuit at any time if they wish, and no copyright notice changes |
23 |
that. |
24 |
|
25 |
> "this is mine and I will protect it" - copyright holder |
26 |
|
27 |
Again if you don't have a notice at all you can still sue somebody if |
28 |
you want to if they copy your work outside of fair use. A notice just |
29 |
eliminates the possibility of one of many types of defenses they could |
30 |
argue. IMO the notice we have is sufficient, but really I'm not that |
31 |
concerned if it isn't. |
32 |
|
33 |
> >> |
34 |
> >> Does this mean "gentoo authors" will appear in court when |
35 |
> >> there's infringement? This is not a rhetorical question. |
36 |
> >> |
37 |
> > |
38 |
> |
39 |
> [...] |
40 |
|
41 |
Do you want me to copy the same response again, despite already being |
42 |
accused of redundancy? |
43 |
|
44 |
Fine: |
45 |
|
46 |
"Gentoo authors" would not file a lawsuit. Any copyright holder can |
47 |
file a lawsuit at any time if they wish, and no copyright notice |
48 |
changes that. |
49 |
|
50 |
> |
51 |
> > |
52 |
> > Ultimately though if Gentoo gets sued by somebody, the burden of proof |
53 |
> > is actually on them to prove that THEY owned the copyright. Gentoo's |
54 |
> > burden would probably be to show that reasonable care was exercised |
55 |
> > over accepting code, and that infractions were dealt with in a |
56 |
> > reasonable manner when brought to our attention. |
57 |
> > |
58 |
> |
59 |
> ^ The copyright holder (the legal entity or person in the |
60 |
> copyright notice) would be the one to file lawsuit(s) when |
61 |
> there's infringement. |
62 |
|
63 |
Sure, and if somebody sues Gentoo they would be claiming to be the |
64 |
copyright holder. |
65 |
|
66 |
Now, if Gentoo wanted to sue somebody then Gentoo would need to |
67 |
establish ownership of copyright. IMO that is pretty unlikely to |
68 |
happen. |
69 |
|
70 |
> |
71 |
> I'm specifically / directly asking: |
72 |
> |
73 |
> Is the gentoo foundation the copyright holder? |
74 |
|
75 |
IMO there is no benefit to the Foundation to take a position on this |
76 |
issue. The GLEP does not require assignment to Gentoo. Whether past |
77 |
contributions were assigned might be debated by some. |
78 |
|
79 |
IMO we could argue all day long about that, but there is no benefit in |
80 |
doing so. First, the situation is somewhat vague. Second, I have no |
81 |
idea whether it would ever be important to establish Gentoo ownership |
82 |
of past contributions in a court, but if it were important then the |
83 |
best argument the other side could make would be pointing to |
84 |
Trustees/Officers/etc making statements that hurt its case. So, |
85 |
making statements on the past doesn't help us, and it might hurt us. |
86 |
So, why do it? |
87 |
|
88 |
The GLEP was designed to improve things going forward. |
89 |
|
90 |
Long-term I think there is more interest in using a mechanism like the |
91 |
FLA than doing copyright assignment. IMO that has all of the upside |
92 |
of assignment and none of the downside. |
93 |
|
94 |
> |
95 |
> > Our notices already make this clear, regardless of whose name is listed. |
96 |
> |
97 |
> That's not clear. A lot of people see: "this is free, and |
98 |
> the source code is available", and then make assumptions |
99 |
> about what that means: |
100 |
|
101 |
Those quoted words appear nowhere in the GLEP. |
102 |
|
103 |
What our files ACTUALLY say is something like "Copyright 2018 Gentoo |
104 |
Authors". Then we have a license to allow redistribution. If people |
105 |
don't want to read the license that is on them. If people read |
106 |
"Copyright 2018" and assume that this means that it must be free to |
107 |
copy without any restrictions that is on them also. |
108 |
|
109 |
> There's very little documentation about gentoo's procedure |
110 |
> when FOSS/Libre work (copyleft / copyrightable portions of |
111 |
> gentoo OS and related tools) is mistreated, and a copyright |
112 |
> action is needed in order to enforce the licesnse (copyleft |
113 |
> style: because that's why there's copyright notices) |
114 |
|
115 |
Correct. |
116 |
|
117 |
Committing copyrighted stuff to Gentoo is routine. Gentoo suing |
118 |
people for copyright infringement is not routine. It really doesn't |
119 |
make sense to have a standardized GLEP for something we've never done, |
120 |
and might never do. Why constrain ourselves to that degree in the |
121 |
event we were ever to decide to do such a thing? |
122 |
|
123 |
> What is gentoo's policy when infringement happens? |
124 |
|
125 |
Gentoo has no documented policy I'm aware of. |
126 |
|
127 |
> (when "gentoo authors" are the copyright holder) |
128 |
|
129 |
Ask the Gentoo authors. When I'm the Gentoo author I don't |
130 |
necessarily have any plans to go suing anybody anytime soon, but I |
131 |
reserve the right to do so, and if I do so it would be at my own sole |
132 |
discretion at the time. |
133 |
|
134 |
> If a business entity's name is listed as the copyright |
135 |
> holder, their copyright notice means (at least it should) |
136 |
> that they'll be the ones who show up in court when the |
137 |
> time comes to protect against copyleft infringement: |
138 |
|
139 |
Legally a copyright notice does not have to list the entity who will |
140 |
file a lawsuit. |
141 |
|
142 |
> An infringement suit is when the copyright holder ("gentoo |
143 |
> authors", and I'm questioning how "gentoo authors" hold |
144 |
> a copyright if listed as the "entity" which holds the |
145 |
> copyright) SUES the infringer, not the other way around. |
146 |
|
147 |
You're assuming "Gentoo authors" is a single entity. The policy makes |
148 |
no claim for/against that. |
149 |
|
150 |
> To me, the (main) point of GLEP 76 is to let entities who |
151 |
> are willing/able to file a copyright lawsuit have the |
152 |
> option to do so, partly because gentoo doesn't seem to have |
153 |
> a policy in please for protecting copyleft / copyright. |
154 |
|
155 |
GLEP 76 mostly serves to protect Gentoo against others suing us by |
156 |
demonstrating reasonable care. |
157 |
|
158 |
To the degree that it mentions notice, it is mainly because OTHERS got |
159 |
upset about Gentoo changing THEIR copyright notices, because our |
160 |
previous policy required all ebuilds to name the Gentoo Foundation |
161 |
exclusively. |
162 |
|
163 |
However, the policy still preserves our rights to sue others if |
164 |
necessary, IMO. If we wanted to optimize to be more efficient at |
165 |
suing people we'd probably do more to prepare for this. However, that |
166 |
really isn't the organizations primary purpose. |
167 |
|
168 |
-- |
169 |
Rich |