Gentoo Archives: gentoo-project

From: "Michał Górny" <mgorny@g.o>
To: gentoo-project@l.g.o, Ulrich Mueller <ulm@g.o>, gentoo-dev-announce@l.g.o
Subject: Re: [gentoo-project] [RFC] GLEP 76: Copyright Policy
Date: Mon, 11 Jun 2018 17:45:27
Message-Id: 1528739118.3031.3.camel@gentoo.org
In Reply to: Re: [gentoo-project] [RFC] GLEP 76: Copyright Policy by NP-Hardass
1 W dniu pon, 11.06.2018 o godzinie 12∶25 -0400, użytkownik NP-Hardass
2 napisał:
3 > On 06/10/2018 04:34 PM, Ulrich Mueller wrote:
4 >
5 > [...]
6 >
7 > > Copyright Attribution
8 > > ---------------------
9 > >
10 > > All files included in Gentoo projects must contain an appropriate
11 > > copyright notice, as defined by this policy.
12 > >
13 > > A proper copyright notice appears near the top of the file, and reads::
14 > >
15 > > Copyright YEARS LARGEST-CONTRIBUTOR [OTHER-CONTRIBUTORS] and others
16 > >
17 > > The largest contributor is whatever entity owns copyright to some
18 > > portion of the largest number of lines in the file. Additional
19 > > contributors can be listed, but this is neither required nor
20 > > recommended. The "and others" text may be omitted if the explicitly
21 > > listed contributors hold copyright to the entire file.
22 >
23 > Why is this not recommended? Here are a couple of scenarios that came to
24 > mind that lead to me to question how that would play out:
25 > If developer A writes 51% of the lines of an ebuild and developer B
26 > writes 49%, should B not be listed?
27 > What if all the metadata lines defining variables consists of 75% of the
28 > file and was written by A, but the core functionality of the ebuild (25%
29 > by size) was written by B?
30 > If A writes an ebuild, and B replaces a majority (>50%) of the ebuild,
31 > should B remove A from attribution?
32 > I think that specifying that substantial (though not necessarily
33 > specific in defining this) contributions/contributors should included in
34 > the copyright attribution and that substantial contribution attribution
35 > *is* recommended.
36 >
37
38 Note that line attribution is not a very precise measure anyway. For
39 example, you can easily update all lines in the ebuild without making
40 any substantial change to it. Therefore, according to 'git blame' you'd
41 be 100% owner but at the same time the previous author would have far
42 more original contribution than you did.
43
44 --
45 Best regards,
46 Michał Górny