public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Raymond Jennings <shentino@gmail.com>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] rfc: copyright attribution clarifications
Date: Wed, 14 Nov 2018 00:28:31 -0800	[thread overview]
Message-ID: <CAGDaZ_oEgAUTC1r-Wy=Sz9HvVwUASNHEu7xGN+K=cUvEO1tOYw@mail.gmail.com> (raw)
In-Reply-To: <w6g7ehgjcd3.fsf@kph.uni-mainz.de>

[-- Attachment #1: Type: text/plain, Size: 3062 bytes --]

On Wed, Nov 14, 2018 at 12:24 AM Ulrich Mueller <ulm@gentoo.org> wrote:

> >>>>> On Wed, 14 Nov 2018, William Hubbs wrote:
>
> > On Tue, Nov 13, 2018 at 06:17:17PM -0800, Rich Freeman wrote:
> >> So, the purpose of allowing specific copyright holders to be named
> >> was to cover cases where we're forking foreign code, not to basically
> >> introduce a variant on the BSD advertising clause. IMO people who are
> >> only willing to contribute FOSS if their name gets put in a prominent
> >> location might do better to contribute elsewhere.
>
> +1000
>
> Maybe the policy for the Gentoo repository should just say that, namely
> that traditional copyright notices are only allowed for imported foreign
> code. Anything committed directly to the repository and any update of an
> existing file would be required to carry the simplified "Gentoo Authors"
> copyright notice, without any exceptions allowed.
>
> Can someone come up with a good wording for this?


In my opinion the best wording belongs in python as a check in repoman and
the qa scripts monitoring PRs on github ;).


> > Do you feel this way about corporations as well? Do you think the
> > Linux kernel maintainers should go and rip out all copyright notices
> > other than Linus Torvalds and maybe the Linux Foundation?
>
> Why would corporations be different from individual authors? Under the
> legislation here, corporations cannot even hold copyright (or rather,
> Urheberrecht) of a work.
>
> >> The purpose of a copyright notice is to declare that the file is
> >> copyrighted, and that is it.
>
> Exactly.
>
> >> It isn't a comprehensive list of everybody who holds a copyright on
> >> the file.
> >>
> >> It isn't a revision history.
> >>
> >> There is no need to list various mixes of years and authors.  Just
> >> list the first and last year, and whatever copyright holders are
> >> necessary.
> >>
> >> [...]
> >>
> >> But, if you had to have multiple lines, then just wrap the existing
> >> notice.  Don't turn it into some kind of revision history.  Just list
> >> one year range and whatever list of entities you feel compelled to
> >> list.  That is the proper way to do a notice.
>
> > No sir, it isn't.
>
> > Look anywhere outside the Gentoo tree. For that matter, take the Linux
> > kernel, or even in the systemd source, there are several places with
> > multiple copyright notices in them.
>
> Are these the only arguments you have?
>
> To say it again, ebuilds have a copyright notice for exactly two
> reasons:
>
> - to protect us against the "innocent infringement" defense under
> U.S. law, and
>
> - because the GPL-2 requires in section 1 to "appropriately publish
> on each copy an appropriate copyright notice".
>
> For both of these, it is irrelevant what the precise contents of the
> notice is. If you made a significant contribution to the file, then you
> can claim copyright for it, even if there is no copyright notice at all,
> of if you aren't mentioned in it.
>
> IANAL, but I think the case for being listed there explicitly is very
> weak.
>
> Ulrich
>

[-- Attachment #2: Type: text/html, Size: 3907 bytes --]

  reply	other threads:[~2018-11-14  8:29 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-13 18:32 [gentoo-project] rfc: copyright attribution clarifications William Hubbs
2018-11-13 18:47 ` M. J. Everitt
2018-11-14  2:17 ` Rich Freeman
2018-11-14  2:46   ` William Hubbs
2018-11-14  7:18     ` Sarah White
2018-11-14 15:58       ` Rich Freeman
2018-11-14 19:38         ` Patrick McLean
2018-11-14 23:23           ` Rich Freeman
2018-11-15  0:00             ` Patrick McLean
2018-11-15 15:03               ` Rich Freeman
2018-11-15 15:28                 ` William Hubbs
2018-11-15 15:52                 ` Ian Stakenvicius
2018-11-14  8:24     ` Ulrich Mueller
2018-11-14  8:28       ` Raymond Jennings [this message]
2018-11-14 19:47       ` Patrick McLean
2018-11-14 20:09         ` Patrick McLean
2018-11-15 13:38           ` Thomas Deutschmann
2018-11-15 22:25             ` Kristian Fiskerstrand
2018-11-15  6:49         ` Ulrich Mueller
2018-11-15 15:35           ` William Hubbs
2018-11-15 17:50             ` Ulrich Mueller
2018-11-15 18:50               ` William Hubbs
2018-11-15 21:31                 ` M. J. Everitt
2018-11-15 21:56                   ` Andrew Savchenko
2018-11-16  9:16                 ` Ulrich Mueller
2018-11-14 15:50     ` Rich Freeman
2018-11-14 14:45       ` Andrew Savchenko
2018-11-14 15:24         ` Rich Freeman
2018-11-14 15:53           ` Andrew Savchenko
2018-11-23 19:21             ` Sarah White
2018-11-23 19:46               ` Rich Freeman
2018-11-23 20:23                 ` Sarah White
2018-11-23 20:25                   ` Ian Stakenvicius
2018-11-23 20:40                     ` Sarah White
2018-11-24 17:47                       ` William Hubbs
2018-11-24 18:15                         ` Sarah White
2018-11-24 19:41                         ` Alec Warner
2018-11-24 20:12                           ` Rich Freeman
2018-11-24 20:32                             ` Alec Warner
2018-11-24 21:21                               ` Rich Freeman
2018-11-26 12:01                               ` Ulrich Mueller
2018-11-26 13:36                                 ` Alec Warner
2018-11-25 20:36                             ` Matt Turner
2018-11-25 20:52                               ` William Hubbs
2018-11-25 22:58                                 ` Rich Freeman
2018-11-24 23:11                           ` Ulrich Mueller
2018-11-25  1:09                             ` Sarah White
2018-11-25  1:37                               ` Rich Freeman
2018-11-25  2:04                                 ` Sarah White
2018-11-25  2:22                                   ` Rich Freeman
2018-11-25  3:21                                     ` Sarah White
2018-11-25  6:53                                     ` Joonas Niilola
2018-11-25  2:04                         ` Matt Turner
2018-11-26 15:20                           ` William Hubbs
2018-11-26 23:12                             ` William Hubbs
2018-11-27  0:05                               ` Raymond Jennings
2018-11-27  2:38                               ` Matt Turner
2018-11-27  4:51                                 ` William Hubbs
2018-11-27  6:20                                   ` Matt Turner
2018-11-23 20:42                   ` Rich Freeman
2018-11-23 20:51                     ` Sarah White
2018-11-23 21:11                       ` Rich Freeman
2018-11-24 17:49                         ` Sarah White
2018-11-23 20:57                   ` Rich Freeman
2018-11-14 14:36   ` Andrew Savchenko
2018-11-14 15:31     ` Rich Freeman
2018-11-14 16:19       ` Andrew Savchenko
2018-11-14 18:59       ` Ian Stakenvicius
2018-11-14 19:38         ` William Hubbs
2018-11-14 20:02         ` Patrick McLean
2018-11-14 20:11           ` M. J. Everitt
2018-11-15 13:16         ` Thomas Deutschmann
2018-11-15 15:51       ` Brian Dolbec
2018-11-15 16:25         ` Thomas Deutschmann
2018-11-15 16:47           ` William Hubbs

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='CAGDaZ_oEgAUTC1r-Wy=Sz9HvVwUASNHEu7xGN+K=cUvEO1tOYw@mail.gmail.com' \
    --to=shentino@gmail.com \
    --cc=gentoo-project@lists.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