From: Andrew Savchenko <bircoph@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] [RFC] GLEP 76: Copyright Policy [v3]
Date: Sat, 8 Sep 2018 21:17:05 +0300 [thread overview]
Message-ID: <20180908211705.bd3063681f4d0782ca75af7c@gentoo.org> (raw)
In-Reply-To: <w6gpnxoi01t.fsf@kph.uni-mainz.de>
[-- Attachment #1: Type: text/plain, Size: 1658 bytes --]
On Sat, 08 Sep 2018 15:35:58 +0200 Ulrich Mueller wrote:
> >>>>> On Sat, 08 Sep 2018, Andrew Savchenko wrote:
>
> >> This also requires that they use their real name for signing; an
> >> anonymous certification or one under a pseudonym would not mean
> >> anything.
>
> Yes, that's the rationale. We can simply forget about the whole
> copyright policy effort, if we don't require committers to certify
> their contributions under their real name.
>
> > I don't like this. We have anonymous developers right now (at least
> > their names are not public even in LDAP). The cited requirement will
> > effectively kick them from the project. Moreover we have contributors
> > considering to become developers who prefer to keep their anonymity.
>
> According to recruitment policy [1] (which is in place since 2004 [2]
> at least), there cannot be any anonymous developers doing copyrightable
> work:
>
> # Real names must be provided for all developers, including
> # infrastructure and documentation. Any exceptions to this for
> # extenuating circumstances will be considered on a case-by-case
> # basis. No exceptions will be made for people doing copyrightable
> # work (ebuilds, software, scripts, documentation, etc.).
>
> AFAICS, the GLEP will only confirm the existing policy there.
Real names must be provided != must be publicly available. The
current status is that they are in LDAP, but not viewable outside
of recruiters (and maybe some other limited groups). What you are
proposing demands public availability, so it can be seen as an extra
requirement compared to GLEP.
Best regards,
Andrew Savchenko
[-- Attachment #2: Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-09-08 18:17 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 [this message]
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
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=20180908211705.bd3063681f4d0782ca75af7c@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