Gentoo Archives: gentoo-project

From: Ulrich Mueller <ulm@g.o>
To: NP-Hardass <NP-Hardass@g.o>
Cc: gentoo-project@l.g.o
Subject: Re: [gentoo-project] [RFC] GLEP 76: Copyright Policy
Date: Mon, 11 Jun 2018 17:28:00
Message-Id: 23326.45334.989265.824533@a1i15.kph.uni-mainz.de
In Reply to: Re: [gentoo-project] [RFC] GLEP 76: Copyright Policy by NP-Hardass
1 >>>>> On Mon, 11 Jun 2018, NP-Hardass wrote:
2
3 > On 06/10/2018 04:34 PM, Ulrich Mueller wrote:
4 > [...]
5
6 >> Copyright Attribution
7 >> ---------------------
8 >>
9 >> All files included in Gentoo projects must contain an appropriate
10 >> copyright notice, as defined by this policy.
11 >>
12 >> A proper copyright notice appears near the top of the file, and reads::
13 >>
14 >> Copyright YEARS LARGEST-CONTRIBUTOR [OTHER-CONTRIBUTORS] and others
15 >>
16 >> The largest contributor is whatever entity owns copyright to some
17 >> portion of the largest number of lines in the file. Additional
18 >> contributors can be listed, but this is neither required nor
19 >> recommended. The "and others" text may be omitted if the explicitly
20 >> listed contributors hold copyright to the entire file.
21
22 > Why is this not recommended? Here are a couple of scenarios that came to
23 > mind that lead to me to question how that would play out:
24 > If developer A writes 51% of the lines of an ebuild and developer B
25 > writes 49%, should B not be listed?
26
27 With the current policy neither of them is listed, so listing A would
28 be an improvement. The goal is to keep things simple, and listing only
29 the largest contributor looks like the simplest solution. For example,
30 listing the two largest contributors would lead to similar problems.
31 What should we do if A and B each write 34% and C writes 32%?
32
33 In a previous version of the draft, we had required a full list of
34 copyright holders to be listed somewhere in the file, and 60% of the
35 lines to be accounted for:
36 https://gitweb.gentoo.org/data/glep.git/commit/?id=bb756839bbd403059f6faeceaa114346d2a840d7
37
38 We changed that because neither tracing the number of lines nor
39 maintaining a list of authors in every ebuild seems feasible.
40
41 > What if all the metadata lines defining variables consists of 75% of the
42 > file and was written by A, but the core functionality of the ebuild (25%
43 > by size) was written by B?
44
45 That would get us into a discussion on which portions of an ebuild are
46 copyrightable and which are not. Again, we want simple rules there.
47
48 > If A writes an ebuild, and B replaces a majority (>50%) of the ebuild,
49 > should B remove A from attribution?
50 > I think that specifying that substantial (though not necessarily
51 > specific in defining this) contributions/contributors should included in
52 > the copyright attribution and that substantial contribution attribution
53 > *is* recommended.
54
55 See above. Explicitly listing only one copyright holder in the
56 copyright line looks like the simplest possible solution. Listing
57 nobody would be even simpler, but I think that you cannot have a
58 copyright line without at least one entity.
59
60 Also note that the exercise is _not_ about giving credit to authors
61 (and we currently don't do that with the Foundation copyright either).
62 The purpose of the copyright notice is to make a statement that the
63 work is copyrighted, in order to defeat a possible defense of
64 "innocent infringement".
65
66 Ulrich

Replies

Subject Author
Re: [gentoo-project] [RFC] GLEP 76: Copyright Policy NP-Hardass <NP-Hardass@g.o>
Re: [gentoo-project] [RFC] GLEP 76: Copyright Policy Ulrich Mueller <ulm@g.o>