1 |
On Wed, Nov 14, 2018 at 11:38 AM Patrick McLean <chutzpah@g.o> wrote: |
2 |
> |
3 |
> On Wed, 14 Nov 2018 07:58:08 -0800 |
4 |
> Rich Freeman <rich0@g.o> wrote: |
5 |
> |
6 |
> > On Tue, Nov 13, 2018 at 11:18 PM Sarah White <kuzetsa@××××××××××.ovh> |
7 |
> > wrote: |
8 |
> > > |
9 |
> > > |
10 |
> > > multiline (standard form) copyright attribution doesn't have |
11 |
> > > anything to do with licensing, and only serves to strengthen |
12 |
> > > copyleft due to the presence of additional copyright notices which |
13 |
> > > clearly lay out a list of entities / people with a stake in |
14 |
> > > protecting the interests of an opensource project remaining |
15 |
> > > FOSS/Libre. |
16 |
> > |
17 |
> > First, git already does this. |
18 |
> |
19 |
> It does not, it lists authors, not copyright holders which are not the |
20 |
> same thing. |
21 |
|
22 |
Nothing prevents us from adding copyright info to commit messages, and |
23 |
companies that feel strongly about documenting their copyright over |
24 |
their contributions would probably be best off doing it in git where |
25 |
it is less likely to get lost/deleted/etc over time. It would also be |
26 |
out of the way for those not looking for this info. |
27 |
|
28 |
> |
29 |
> > Second, please cite an example of a copyright lawsuit that was won |
30 |
> > because multiple notices were listed, or a law that provides |
31 |
> > protection if multiple notices are provided. Your claim that doing |
32 |
> > this "strengthen[s] copyleft" is baseless as far as I can tell. |
33 |
> |
34 |
> I don't think it's about citing cases, the GPL has never gotten to |
35 |
> trial AFAIK, so under that metric, the GPL is useless. |
36 |
|
37 |
I suggested that you could cite laws as well. GPL is well-grounded in |
38 |
copyright law (the law says basically that users of software have no |
39 |
rights to copy it, and then GPL grants a few extra rights). The law |
40 |
takes away, and the GPL gives the user more freedom than they would |
41 |
have otherwise under the law. |
42 |
|
43 |
Laundry lists of copyright notices have no particular basis in law, in |
44 |
particular because copyright law is already incredibly strong without |
45 |
it. A notice that names any copyright holder defeats an innocent |
46 |
infringement defense (which is already a pretty weak defense to begin |
47 |
with). Adding more names to the copyright line doesn't do anything |
48 |
else. |
49 |
|
50 |
In any case, the claim was made that this "strengthens copyright" and |
51 |
it is up to those making a claim to back it up with some kind of law |
52 |
(statutory or case law), not just argue that more text must be better. |
53 |
|
54 |
If you hold a copyright on something, you can sue somebody for |
55 |
infringement even if you aren't named directly in the copyright |
56 |
notice, or even if you aren't named indirectly (Gentoo authors), or |
57 |
even if there isn't any notice at all. |
58 |
|
59 |
> |
60 |
> > The presence of any copyright notice in the form given in US law |
61 |
> > already defeats the innocent infringement defense, even if it doesn't |
62 |
> > mention you. Beyond that copyright law applies whether there is any |
63 |
> > notice at all. |
64 |
> > |
65 |
> > > gentoo's license policy already |
66 |
> > > requires FOSS/Libre licenses and correctly using copyright law for |
67 |
> > > copyleft purposes makes everything work correctly when it's used |
68 |
> > > correctly. |
69 |
> > |
70 |
> > Indeed, and for this reason I don't actually see any reason under US |
71 |
> > copyright law that we couldn't strip out additional copyright notices |
72 |
> > in code as a result. US law explicitly makes this illegal only if it |
73 |
> > is done to hide infringement, and we don't infringe copyright. I can |
74 |
> > only imagine the wails of the copyright pro-spam crowd if we actually |
75 |
> > tried that (not that I'm suggesting it)... |
76 |
> |
77 |
> Are you suggesting that stripping out copyright headers is permissable? |
78 |
> I would talk to a copyright lawyer before making any such assumptions. |
79 |
|
80 |
Please do. |
81 |
|
82 |
And again, please cite actual laws or case law, not make hand-waving arguments. |
83 |
|
84 |
All things are permissible barring a law that says otherwise. There |
85 |
is no law in the US at least that forbids removing a copyright notice, |
86 |
except for the purpose of concealing infringement. |
87 |
|
88 |
In any case, as I already said I'm not suggesting that we should do |
89 |
this. My point is just that copyright notices aren't nearly as |
90 |
sacrosanct as some people seem to think they are. |
91 |
|
92 |
-- |
93 |
Rich |