From: Ulrich Mueller <ulm@gentoo.org>
To: Alec Warner <antarus@gentoo.org>
Cc: gentoo-project <gentoo-project@lists.gentoo.org>
Subject: Re: [gentoo-project] rfc: copyright attribution clarifications
Date: Sun, 25 Nov 2018 00:11:43 +0100 [thread overview]
Message-ID: <w6ga7lydqa8.fsf@kph.uni-mainz.de> (raw)
In-Reply-To: <CAAr7Pr-8bZ2_qTKqfFv2mAwaP9J8Q-LRCf6opJ3_H8C_gWk8vA@mail.gmail.com> (Alec Warner's message of "Sat, 24 Nov 2018 14:41:32 -0500")
[-- Attachment #1: Type: text/plain, Size: 1987 bytes --]
>>>>> On Sat, 24 Nov 2018, Alec Warner wrote:
> I don't believe the technical arguments have much basis; instead the
> argument is about community and humanpower.
> - There is an argument (non technical) that files in the ebuild
> repository should carry a copyright notice to signal that the content
> has a copyright.
> - A GLEP was written (glep76) to standardize what this should be. One
> of the (unstated) goals of the GLEP is to avoid spending time managing
> the copyright declarations; so it was decided to have 2 forms, the
> short form ("Gentoo Authors") and the traditional form (for when we
> import code and cannot remove notices.)
Exactly.
> The crux of the argument is about the maintenance of these copyright
> notices; not about the bytes they occupy or the CPU time spend reading
> them.
> - When is it allowed to add extra notices?
> - When is it allowed to remove extra notices?
> This is ultimately the problem I think we see with the SEI
> attribution. We don't understand *why* Sony wants the notice there and
> because of that we don't understand the answers to the above.
We don't understand it because they refuse to give us an explanation.
Which is not our fault.
> What I want to avoid happening is getting sued by Sony because the
> notices were added and then later removed; but we have not received
> guidance on this and I think it blocks us moving forward.
I don't see anything in the GPL-2 that would prevent us from removing
redundant copyright notices.
For example, the FDL-1.3 requires in section 4.D. to "Preserve all the
copyright notices of the Document", and the CC-BY-SA licenses contain
similar wording. However, such a clause can neither be found in the
GPL-2 nor in the GPL-3. In fact, the GPL-3 clarifies in section 7 that
it can be *supplemented* with terms "requiring preservation of specified
reasonable legal notices or author attributions", but the license itself
doesn't require this.
Disclaimer: IANAL, TINLA.
Ulrich
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-11-24 23:12 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
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 [this message]
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=w6ga7lydqa8.fsf@kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=antarus@gentoo.org \
--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