public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matt Turner <mattst88@gentoo.org>
To: Gentoo project list <gentoo-project@lists.gentoo.org>
Cc: Ulrich Mueller <ulm@gentoo.org>, gentoo-dev-announce@lists.gentoo.org
Subject: Re: [gentoo-project] [RFC] GLEP 76: Copyright Policy
Date: Mon, 11 Jun 2018 23:01:50 -0700	[thread overview]
Message-ID: <CAEdQ38Gfybk03MnZRF9ePWBPAEPd2nssh7atUOR+WA9gyA5FLQ@mail.gmail.com> (raw)
In-Reply-To: <cb5d93b3-7f1c-dfba-2009-02243632e0af@gentoo.org>

On Mon, Jun 11, 2018 at 9:25 AM, NP-Hardass <NP-Hardass@gentoo.org> wrote:
> On 06/10/2018 04:34 PM, Ulrich Mueller wrote:
>
> [...]
>
>> Copyright Attribution
>> ---------------------
>>
>> All files included in Gentoo projects must contain an appropriate
>> copyright notice, as defined by this policy.
>>
>> A proper copyright notice appears near the top of the file, and reads::
>>
>>     Copyright YEARS LARGEST-CONTRIBUTOR [OTHER-CONTRIBUTORS] and others
>>
>> The largest contributor is whatever entity owns copyright to some
>> portion of the largest number of lines in the file.  Additional
>> contributors can be listed, but this is neither required nor
>> recommended.  The "and others" text may be omitted if the explicitly
>> listed contributors hold copyright to the entire file.
>
> Why is this not recommended? Here are a couple of scenarios that came to
> mind that lead to me to question how that would play out:
> If developer A writes 51% of the lines of an ebuild and developer B
> writes 49%, should B not be listed?
> What if all the metadata lines defining variables consists of 75% of the
> file and was written by A, but the core functionality of the ebuild (25%
> by size) was written by B?
> If A writes an ebuild, and B replaces a majority (>50%) of the ebuild,
> should B remove A from attribution?
> I think that specifying that substantial (though not necessarily
> specific in defining this) contributions/contributors should included in
> the copyright attribution and that substantial contribution attribution
> *is* recommended.

Don't think about the copyright line as attribution or credit. Some
projects I work on have Author: lines in files, which I've always
found irritating because they're often out of date and generally
useless -- if you want attribution just look at git log.


  parent reply	other threads:[~2018-06-12  6:02 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-10 20:34 [gentoo-project] [RFC] GLEP 76: Copyright Policy Ulrich Mueller
2018-06-10 20:49 ` Michał Górny
2018-06-11 16:20 ` Brian Evans
2018-06-11 16:25 ` NP-Hardass
2018-06-11 17:07   ` Rich Freeman
2018-06-11 18:08     ` NP-Hardass
2018-06-11 17:27   ` Ulrich Mueller
2018-06-11 17:57     ` NP-Hardass
2018-06-13 20:35     ` Ulrich Mueller
2018-06-13 20:44       ` William Hubbs
2018-06-17  2:18         ` Kent Fredric
2018-06-11 17:45   ` Michał Górny
2018-06-12  6:01   ` Matt Turner [this message]
2018-06-17  1:03 ` Kent Fredric
2018-06-17  1:39   ` Rich Freeman
2018-06-17  2:14     ` Kent Fredric
2018-06-17  2:34       ` Rich Freeman
2018-06-17  2:17     ` Aaron Bauman
2018-06-17  2:39       ` Rich Freeman
2018-06-17  2:52         ` Aaron Bauman
2018-06-17  3:30         ` Kent Fredric
2018-06-17  7:09           ` Ulrich Mueller
2018-06-17  7:00   ` Ulrich Mueller
2018-06-17  7:15     ` Kent Fredric
2018-06-17  7:38     ` Kent Fredric
2018-06-17  8:45       ` Ulrich Mueller
2018-06-17 20:12         ` Kristian Fiskerstrand
2018-06-17 20:37           ` Ulrich Mueller
2018-06-17 20:41             ` Kristian Fiskerstrand
2018-06-17 23:19               ` Kent Fredric
2018-06-19 17:30 ` [gentoo-project] [RFC] GLEP 76: Copyright Policy [v2] Ulrich Mueller
2018-06-23 19:39   ` Andreas K. Huettel
2018-06-23 21:57     ` Ulrich Mueller
2018-08-31 15:18   ` [gentoo-project] [RFC] GLEP 76: Copyright Policy [v3] Ulrich Mueller
2018-09-03 17:40     ` Ulrich Mueller
2018-09-08 11:43       ` Andrew Savchenko
2018-09-08 13:35         ` Ulrich Mueller
2018-09-08 18:17           ` Andrew Savchenko
2018-09-08 18:55             ` Ulrich Mueller
2018-09-08 19:20               ` Justin Lecher
2018-09-08 23:38               ` Andrew Savchenko
2018-09-09  6:15                 ` Ulrich Mueller
2018-09-08 14:25       ` Michael Orlitzky
2018-09-08 17:09         ` Michał Górny
2018-09-08 17:36         ` Ulrich Mueller
2018-09-26 19:25     ` [gentoo-project] [RFC] GLEP 76: Copyright Policy [v4] Ulrich Mueller
2018-09-27  5:00       ` kuzetsa
2018-09-27 12:00       ` NP-Hardass
2018-09-27 12:42         ` Rich Freeman
2018-09-27 13:08           ` kuzetsa
2018-09-27 13:43             ` Rich Freeman
2018-09-27 14:14               ` kuzetsa
2018-09-27 13:52           ` NP-Hardass
2018-09-27 14:13             ` Rich Freeman
2018-09-27 14:24               ` NP-Hardass
2018-09-27 14:32               ` kuzetsa
2018-09-29  3:15               ` desultory
2018-09-29  7:08               ` Kent Fredric
2018-09-29  9:13                 ` Ulrich Mueller
2018-09-27 14:32             ` Michał Górny
2018-09-27 14:40               ` kuzetsa
2018-09-28  9:39       ` kuzetsa
2018-09-29  7:46         ` Ulrich Mueller
2018-10-02 20:29           ` NP-Hardass
2018-10-02 21:23             ` Michał Górny
2018-10-03 15:48             ` Ulrich Mueller
2018-10-03 19:16               ` Andrew Savchenko
2018-10-03 19:28                 ` Rich Freeman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAEdQ38Gfybk03MnZRF9ePWBPAEPd2nssh7atUOR+WA9gyA5FLQ@mail.gmail.com \
    --to=mattst88@gentoo.org \
    --cc=gentoo-dev-announce@lists.gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    --cc=ulm@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox