1 |
Ühel kenal päeval, N, 27.10.2016 kell 07:21, kirjutas Rich Freeman: |
2 |
> On Thu, Oct 27, 2016 at 7:00 AM, Mart Raudsepp <leio@g.o> |
3 |
> wrote: |
4 |
> > |
5 |
> > |
6 |
> > Projects that want explicit copyright or copyright assignments or |
7 |
> > CLAs |
8 |
> > are those that want to be able to re-license the code without |
9 |
> > getting |
10 |
> > permissions from everyone (some of whom might not be possible to |
11 |
> > contact at a future date) or be able to sue someone for license |
12 |
> > violations without the original developers of the affected parts |
13 |
> > having |
14 |
> > to be involved. Are we pursuing those option, or why do we care? |
15 |
> |
16 |
> These are useful options to have available. The ability to pursue |
17 |
> violators would not require 100% signing of FLAs to |
18 |
> work. Relicensing |
19 |
> probably would, or close to it, so that might not ever be practical |
20 |
> unless FLA acceptance is very widespread. |
21 |
> |
22 |
> > |
23 |
> > We don't need bogus or |
24 |
> > non-bogus copyright headers, just a "Gentoo project and |
25 |
> > contributors" |
26 |
> > copyright notice or optionally allowing explicit ones to those that |
27 |
> > want it, together with a license notice. |
28 |
> |
29 |
> Actually, that isn't allowed, and was the very issue that kicked off |
30 |
> the entire matter. You can't just take somebody else's code and |
31 |
> change the copyright to "Gentoo project and contributors" if the |
32 |
> Gentoo project's only contribution to the file is changing the |
33 |
> copyright notice. From my reading on the topic you generally need to |
34 |
> list the largest contributor on the copyright line, which may or may |
35 |
> not be the Gentoo Foundation. |
36 |
|
37 |
"and contributors" covers that, and I didn't specify "Foundation". |
38 |
The copyright headers purpose is: |
39 |
|
40 |
"Contrary to popular belief, providing a copyright notice or |
41 |
registering the work with the USCO is not necessary to obtain basic |
42 |
copyright protections. But there are some steps that can be taken to |
43 |
enhance the creator's ability to sue or stop others from copying:" |
44 |
|
45 |
Place a copyright notice on a published work. (...) Placing this notice |
46 |
on a published work (...) prevents others from claiming that they did |
47 |
not know that the work was covered by copyright. This can be important |
48 |
if the author is forced to file a lawsuit to enforce the copyright, |
49 |
since it is much easier to recover significant money damages from a |
50 |
deliberate (as opposed to innocent) copyright infringer." |
51 |
|
52 |
The copyright header has NO LEGAL meaning. IANAL. |
53 |
|
54 |
> > And yes, the headers are currently completely bogus. You can |
55 |
> > consider |
56 |
> > it to be as such to any file I have contributed copyrightable work |
57 |
> > to, |
58 |
> > and the Gentoo Foundation does not have copyright to such work of |
59 |
> > mine. |
60 |
> |
61 |
> If you don't think your contributions are copyrighted by the Gentoo |
62 |
> Foundation, you probably shouldn't be putting that statement in the |
63 |
> files you commit. I don't see why your commits are any less legally |
64 |
> binding on you than your statements in emails like the one above. |
65 |
|
66 |
The copyright header has no meaning on who holds the copyright. The |
67 |
Gentoo tooling automatically puts these lines or refuses to work. Over |
68 |
half of the stuff I commit is not copyrightable work in the first |
69 |
place. |
70 |
Me committing something with repoman commit (especially during CVS |
71 |
times even doing a separate commit for this stuff) ending up with some |
72 |
header doesn't mean I have done any copyright assignment. No court in |
73 |
my jurisdiction would consider this to be the case. Courts in other |
74 |
jurisdictions don't even recognize copyright reassignment and some not |
75 |
even work for hire copyright to the company. |
76 |
|
77 |
The header is only a tool to lower the chances of someone taking the |
78 |
work inappropriately. Stop treating it as some kind of law. |
79 |
|
80 |
> And this is why improving the policy in this space is important. |
81 |
|
82 |
|
83 |
IANAL, |
84 |
Mart |