From: Andrew Savchenko <bircoph@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] rfc: copyright attribution clarifications
Date: Fri, 16 Nov 2018 00:56:33 +0300 [thread overview]
Message-ID: <20181116005633.27e809089f95f62605651d9a@gentoo.org> (raw)
In-Reply-To: <6e044a84-2c16-ee8b-9682-44719107efb1@iee.org>
[-- Attachment #1: Type: text/plain, Size: 2356 bytes --]
On Thu, 15 Nov 2018 21:31:21 +0000 M. J. Everitt wrote:
> On 15/11/18 18:50, William Hubbs wrote:
> > On Thu, Nov 15, 2018 at 06:50:52PM +0100, Ulrich Mueller wrote:
> >> | * Notice identifies the copyright owner at the time the work was first
> >> | published for parties seeking permission to use the work.
> >> | * Notice identifies the year of first publication, which may be used
> >> | to determine the term of copyright protection in the case of an
> >> | anonymous work, a pseudonymous work, or a work made for hire.
> >> | * Notice may prevent the work from becoming an orphan work by
> >> | identifying the copyright owner and specifying the term of the
> >> | copyright.
> >>
> >> For "indentifying the copyright owner" nothing short of a complete list
> >> will suffice. Especially, a notice like the following (which mentions
> >> only "Gentoo Authors" and "Sony Interactive Entertainment Inc.") does
> >> not help with that at all (i.e., it is no better than the simplified
> >> notice):
> >> https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-cluster/ceph/ceph-13.2.2-r2.ebuild?id=5f77c21f23bf1c4cfb9e68be7aa27669c8146e8e#n1
> > Remember that in the US, SIE is a legal entity, so it can hold
> > copyrights, just like a person can. It is like "Gentoo Foundation, Inc."
> >
> > So, there would be two contributors in that ebuild: "Gentoo Authors"
> > and SIE.
> >
> >> Besides, these last three items are pretty much moot for a work released
> >> under the GPL-2 (which grants "permission to use"), and I think that
> >> even you aren't suggesting that we should go for a complete list of
> >> contributors.
> > You are right, I'm not advocating for a complete list of contributors.
> > I'm just advocating for flexability where contributors want it, and SIE
> > is one of those contributors that wants it.
> >
> > William
> Could we not simply move copyright notices into the metadata.xml, and not
> worry about the ebuild text itself?!
No, because Gentoo is used worldwide. Just for example: in Russia
file without copyright notices is considered proprietary (not
public domain! project wide license may help though in some cases)
and removal of copyright notices without author's agreement is a
felony except for court decision or expiration reasons.
Best regards,
Andrew Savchenko
[-- Attachment #2: Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-11-15 21:56 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 [this message]
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=20181116005633.27e809089f95f62605651d9a@gentoo.org \
--to=bircoph@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