1 |
On Thu, Oct 27, 2016 at 7:00 AM, Mart Raudsepp <leio@g.o> wrote: |
2 |
> |
3 |
> Projects that want explicit copyright or copyright assignments or CLAs |
4 |
> are those that want to be able to re-license the code without getting |
5 |
> permissions from everyone (some of whom might not be possible to |
6 |
> contact at a future date) or be able to sue someone for license |
7 |
> violations without the original developers of the affected parts having |
8 |
> to be involved. Are we pursuing those option, or why do we care? |
9 |
|
10 |
These are useful options to have available. The ability to pursue |
11 |
violators would not require 100% signing of FLAs to work. Relicensing |
12 |
probably would, or close to it, so that might not ever be practical |
13 |
unless FLA acceptance is very widespread. |
14 |
|
15 |
> We don't need bogus or |
16 |
> non-bogus copyright headers, just a "Gentoo project and contributors" |
17 |
> copyright notice or optionally allowing explicit ones to those that |
18 |
> want it, together with a license notice. |
19 |
|
20 |
Actually, that isn't allowed, and was the very issue that kicked off |
21 |
the entire matter. You can't just take somebody else's code and |
22 |
change the copyright to "Gentoo project and contributors" if the |
23 |
Gentoo project's only contribution to the file is changing the |
24 |
copyright notice. From my reading on the topic you generally need to |
25 |
list the largest contributor on the copyright line, which may or may |
26 |
not be the Gentoo Foundation. |
27 |
|
28 |
> |
29 |
> And yes, the headers are currently completely bogus. You can consider |
30 |
> it to be as such to any file I have contributed copyrightable work to, |
31 |
> and the Gentoo Foundation does not have copyright to such work of mine. |
32 |
|
33 |
If you don't think your contributions are copyrighted by the Gentoo |
34 |
Foundation, you probably shouldn't be putting that statement in the |
35 |
files you commit. I don't see why your commits are any less legally |
36 |
binding on you than your statements in emails like the one above. |
37 |
|
38 |
And this is why improving the policy in this space is important. |
39 |
|
40 |
-- |
41 |
Rich |