From: Andrew Savchenko <bircoph@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] rfc: copyright attribution clarifications
Date: Wed, 14 Nov 2018 19:19:03 +0300 [thread overview]
Message-ID: <20181114191903.d8a9e28cbd8dde1bc0bfc6ff@gentoo.org> (raw)
In-Reply-To: <CAGfcS_nuFPFd2koHEqhvKBH_MripD6HzwfpgwYnguT8=Z-q-fQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2814 bytes --]
On Wed, 14 Nov 2018 07:31:02 -0800 Rich Freeman wrote:
> On Wed, Nov 14, 2018 at 6:36 AM Andrew Savchenko <bircoph@gentoo.org> wrote:
> >
> > What's the main problem of most FOSS including Gentoo? Lack of
> > human power. And here you propose to neglect contributions if they
> > want a proper and legal and allowed by GPL attribution.
>
> Where is anybody talking about "attribution?"
>
> This is about copyright notice, which is NOT about crediting anybody
> with anything or giving attribution. It is about communicating the
> fact that code is copyrighted, so that people can't claim that they
> didn't know when the Foundation wants to sue them. I'm sure they're
> about to start doing that anytime...
It is your intent, but not full consequences of such statement.
Lack of proper copyright notice may be considered as a copyright or
authorship violation in some jurisdictions. Gentoo is used not only
in the US.
> Also, this doesn't seem to have been a problem in the past, and yet
> our policy was far less free then.
>
> > A few extra lines in the header doesn't as much as
> > inability to import GPL ebuilds to the tree due to our
> > questionable copyright line policy.
>
> What is it that we want to import but can't today?
I have this problem for years(!!) with hasufel overlay from which I
wanted to take voip-related stuff. Also we have wltjr's overlay
which will be useful for java packages.
> > > But, if you had to have multiple lines, then just wrap the existing
> > > notice. Don't turn it into some kind of revision history.
> >
> > That's what most FOSS software does. I see no reason why we should
> > be different.
>
> Do you have a citation for this? I'm not aware of many FOSS projects
> that use copyright notices as a revision history, let alone "most."
git grep through git repositories of large FOSS projects will be a
citation you requested.
> > IMO the best solution will be to recommend "Gentoo Authors"
> > attribution, but to allow additional copyright lines including the
> > case where "Gentoo Authors" is one of such lines.
>
> IMO doing this will just cause everybody and their uncle to insist on
> putting their names in various places.
There is nothing wrong with this.
> We've done just fine for going on 20 years not allowing any notice
> other than "Copyright xxx Gentoo Foundation."
Except for it was entirely wrong except for early days of Gentoo.
> Now we open things up a
> tiny bit and suddenly everybody and their uncle is saying that their
> employers won't let them contribute code unless they stick their
> company name in there. What have they been doing for the last decade?
They were not contributing or less contributing to Gentoo.
Best regards,
Andrew Savchenko
[-- Attachment #2: Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-11-14 16:19 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
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 [this message]
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=20181114191903.d8a9e28cbd8dde1bc0bfc6ff@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