1 |
On Mon, Nov 19, 2012 at 12:06 PM, Greg KH <gregkh@g.o> wrote: |
2 |
> On Mon, Nov 19, 2012 at 07:03:12AM -0500, Rich Freeman wrote: |
3 |
>> That's my main concern here. Can somebody say, "sure, go ahead and |
4 |
>> remove my name from the copyright line" and then sue you for doing it? |
5 |
> |
6 |
> Just removing the name doesn't remove the copyright itself, but, and |
7 |
> this is the important thing, it shows "intent". Intent is a very |
8 |
> powerful thing when it comes to legal enforcement. If you remove a |
9 |
> copyright line, or add your own line, you are showing what you are |
10 |
> wanting to do here. |
11 |
> |
12 |
> So if you remove a copyright line, you are showing your "intent" to |
13 |
> remove the legal notification of the original copyright holders of the |
14 |
> file, which, in numerous juristictions, can be a very serious offence. |
15 |
> |
16 |
> Again, talk to a lawyer for all of the details if you are curious. |
17 |
|
18 |
So, I give you a file. Then I tell you IN WRITING that you can go |
19 |
ahead and remove my name from the copyright line if you want to. |
20 |
|
21 |
I think it would be hard for me to argue that I should be able to |
22 |
obtain damages when I gave you authorization to remove my name. |
23 |
|
24 |
I think the general intent is not to pretend that others did not |
25 |
contribute to the work before, but rather to avoid cluttering the file |
26 |
with a laundry list of names. |
27 |
|
28 |
That said, I'd be happy to chat with a lawyer about this, and if you |
29 |
know of any who wouldn't mind having such a conversation free of |
30 |
charge, let me know, or feel free to point them to the list. |
31 |
|
32 |
> No one has to "fight" at all here, the law is very clear, and a quick |
33 |
> consultation with a copyright lawyer can provide us with a very good set |
34 |
> of rules and boundry conditions that all of us need to follow in order |
35 |
> to ensure that the Foundation does not get into any trouble when it |
36 |
> comes to copyrights. |
37 |
|
38 |
The only way to avoid trouble when it comes to copyright is to never |
39 |
copy anything, or link to anything, and make sure that anybody else |
40 |
using your internet connection does the same. |
41 |
|
42 |
Everything after that is just an exercise in risk mitigation. I don't |
43 |
think there is any basis in law for getting in trouble for removing |
44 |
names from copyrights for GPL works. That said, there doesn't need to |
45 |
be a basis in law for being sued, or even for losing a lawsuit. So, |
46 |
if I had to vote on this as a trustee I'd likely take the conservative |
47 |
approach. However, I'll reserve my right to whine about the problems |
48 |
with the legal system all the same. :) |
49 |
|
50 |
From my general interactions with lawyers in the US they're very |
51 |
pragmatic. They aren't about "right and wrong" but rather what you |
52 |
can and can't get away with. It really doesn't matter if I'm |
53 |
completely right and you're completely wrong, if in order for me to |
54 |
exercise my rights I have to spend $100k fighting in courts, and |
55 |
perhaps even losing in the process. In the US, your rights are |
56 |
whatever you can afford for them to be. |
57 |
|
58 |
On the topic of risk mitigation - it is all about what you get vs what |
59 |
you could lose. Honestly I don't see much reason for removing people |
60 |
from copyright lines other than for the sake of decluttering. That |
61 |
being the case, the wisest move might be to just add the Foundation to |
62 |
copyright statements and leave the rest alone. For ebuilds I'd |
63 |
probably keep the headers in accordance with the standard format, and |
64 |
just move any existing copyright statements further down in the file. |
65 |
If clutter gets really bad we should consider whether we can just move |
66 |
excessive copyright statements to the end of the file, perhaps with a |
67 |
reference at the top next to a single line copyright statement |
68 |
(Copyright 2012 Gentoo Foundation, et al - Licensed under... - see end |
69 |
of file for further details). |
70 |
|
71 |
Rich |