From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] [RFC] GLEP 76: Copyright Policy [v4]
Date: Thu, 27 Sep 2018 16:32:35 +0200 [thread overview]
Message-ID: <1538058755.26937.7.camel@gentoo.org> (raw)
In-Reply-To: <4683a4e7-c752-8735-4bcf-1ee7cb4837f9@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 3820 bytes --]
On Thu, 2018-09-27 at 09:52 -0400, NP-Hardass wrote:
> On 09/27/2018 08:42 AM, Rich Freeman wrote:
> > On Thu, Sep 27, 2018 at 8:00 AM NP-Hardass <NP-Hardass@gentoo.org> wrote:
> > >
> > > On 09/26/2018 03:25 PM, Ulrich Mueller wrote:
> > > > Here is another small update of the copyright GLEP, resulting from a
> > > > recent discussion on IRC. This is not a change of policy, but merely
> > > > a clarification of the real name requirement:
> > > >
> > > > - The Signed-off-by line must contain the name of a natural person.
> > > >
> > > > - A copyright holder can be a legal entity (e.g., a company) in some
> > > > jurisdictions.
> > > >
> > >
> > > IANAL, but as per the Berne Convention, anonymous and pseudonymous works
> > > are granted copyright protection. What's the rationale behind mandating
> > > a real name?
> >
> > The DCO/GCO have nothing to do with obtaining copyright protection.
> > This is always present if not waived.
> >
> > It is about showing due diligence in the event somebody claims that
> > somebody ripped off their work and contributed it to Gentoo without
> > authorization.
> >
> > If your real name is attached to a statement saying that you didn't
> > steal the work, and you did steal the work, then they can go after you
> > as well as Gentoo. That deters contributing stuff without checking on
> > its legality. That same deterrence also helps show good faith on
> > Gentoo's part. This is why organizations generally pursue these
> > policies.
> >
> > If somebody violates a copyright anonymously, then they have no skin
> > in the game. They can just disappear if anything bad happens. If a
> > contributor isn't willing to stake their own money and reputation on
> > the statement that something is legal to contribute, then why should
> > Gentoo assume that they've put a lot of effort into the accuracy of
> > that statement?
> >
>
> And, AFAICT, this only applies to the Signed-off-by line (the
> committer). The author may be anonymous or pseudonymous... So, your
> statement is that people making commits to Gentoo must have real
> names... and be public. This doesn't have any impact on whether the
> source of the code is legit, just gives you a point of blame for who
> actually committed it (which, TBH, doesn't mean much). I can say John
> Doe committed code that wasn't legal. But i_steal_code_1337 authored
> it... I guess we know not to accept code from him... or do we... since
> we have no way of vetting authors. Making the restriction of names for
> committers and not authors, IMO, has no weight. Requiring that all
> contributions be from real named sources is a pretty drastic change, and
> not what is being proposed, TTBOMK.
>
> But that's really besides the point... The current status quo (as is the
> case with me) is that a committer may be pseudonymous under the
> condition that the Foundation have that individual's name in the event
> of a copyright issue. So, I still don't understand how forcing everyone
> to publicly use a real name achieves something that we aren't currently
> achieving... Is that incorrect?
>
Gentoo publishes a number of open source projects. The code of those
projects is used beyond Gentoo and beyond Gentoo Foundation. Therefore,
it is natural that we need all the copyright assessments and agreements
to be *public* and not hidden behind some opaque Foundation which may or
may not actually have the data (how can a regular Gentoo user be sure of
that?), and which may or may not choose to actually disclose it.
As for the case with you, I think the 'status quo' is more complex but
that's beside the point, and I don't think it would be helpful to anyone
expanding on that.
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
next prev parent reply other threads:[~2018-09-27 14:32 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
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 [this message]
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=1538058755.26937.7.camel@gentoo.org \
--to=mgorny@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