Gentoo Archives: gentoo-project

From: Ulrich Mueller <ulm@g.o>
To: gentoo-project@l.g.o
Subject: Re: [gentoo-project] rfc: copyright attribution clarifications
Date: Wed, 14 Nov 2018 08:24:30
Message-Id: w6g7ehgjcd3.fsf@kph.uni-mainz.de
In Reply to: Re: [gentoo-project] rfc: copyright attribution clarifications by William Hubbs
1 >>>>> On Wed, 14 Nov 2018, William Hubbs wrote:
2
3 > On Tue, Nov 13, 2018 at 06:17:17PM -0800, Rich Freeman wrote:
4 >> So, the purpose of allowing specific copyright holders to be named
5 >> was to cover cases where we're forking foreign code, not to basically
6 >> introduce a variant on the BSD advertising clause. IMO people who are
7 >> only willing to contribute FOSS if their name gets put in a prominent
8 >> location might do better to contribute elsewhere.
9
10 +1000
11
12 Maybe the policy for the Gentoo repository should just say that, namely
13 that traditional copyright notices are only allowed for imported foreign
14 code. Anything committed directly to the repository and any update of an
15 existing file would be required to carry the simplified "Gentoo Authors"
16 copyright notice, without any exceptions allowed.
17
18 Can someone come up with a good wording for this?
19
20 > Do you feel this way about corporations as well? Do you think the
21 > Linux kernel maintainers should go and rip out all copyright notices
22 > other than Linus Torvalds and maybe the Linux Foundation?
23
24 Why would corporations be different from individual authors? Under the
25 legislation here, corporations cannot even hold copyright (or rather,
26 Urheberrecht) of a work.
27
28 >> The purpose of a copyright notice is to declare that the file is
29 >> copyrighted, and that is it.
30
31 Exactly.
32
33 >> It isn't a comprehensive list of everybody who holds a copyright on
34 >> the file.
35 >>
36 >> It isn't a revision history.
37 >>
38 >> There is no need to list various mixes of years and authors. Just
39 >> list the first and last year, and whatever copyright holders are
40 >> necessary.
41 >>
42 >> [...]
43 >>
44 >> But, if you had to have multiple lines, then just wrap the existing
45 >> notice. Don't turn it into some kind of revision history. Just list
46 >> one year range and whatever list of entities you feel compelled to
47 >> list. That is the proper way to do a notice.
48
49 > No sir, it isn't.
50
51 > Look anywhere outside the Gentoo tree. For that matter, take the Linux
52 > kernel, or even in the systemd source, there are several places with
53 > multiple copyright notices in them.
54
55 Are these the only arguments you have?
56
57 To say it again, ebuilds have a copyright notice for exactly two
58 reasons:
59
60 - to protect us against the "innocent infringement" defense under
61 U.S. law, and
62
63 - because the GPL-2 requires in section 1 to "appropriately publish
64 on each copy an appropriate copyright notice".
65
66 For both of these, it is irrelevant what the precise contents of the
67 notice is. If you made a significant contribution to the file, then you
68 can claim copyright for it, even if there is no copyright notice at all,
69 of if you aren't mentioned in it.
70
71 IANAL, but I think the case for being listed there explicitly is very
72 weak.
73
74 Ulrich

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies

Subject Author
Re: [gentoo-project] rfc: copyright attribution clarifications Raymond Jennings <shentino@×××××.com>
Re: [gentoo-project] rfc: copyright attribution clarifications Patrick McLean <chutzpah@g.o>