From: Andrew Savchenko <bircoph@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Questions for Gentoo Council nominees: GLEP 76
Date: Tue, 25 Jun 2019 01:18:18 +0300 [thread overview]
Message-ID: <20190625011818.73fb7c1948a0a3d124a0d9db@gentoo.org> (raw)
In-Reply-To: <20190615124933.b2f20fde0b47509e6b54f989@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 4311 bytes --]
Hi all!
On Sat, 15 Jun 2019 12:49:33 +0300 Andrew Savchenko wrote:
> On Sat, 15 Jun 2019 12:42:20 +0300 Andrew Savchenko wrote:
> > Hi all!
> >
> > Last year we had a good initiative: it addition to (or even instead
> > of) manifests nominees were asked questions by voters. So let's
> > continue this year.
> >
> > I propose to have one question per thread spawned by this e-mail to
> > keep discussion focused. If you have multiple questions, please
> > start multiple threads. If your question was already asked, please
> > join a thread.
> >
> > I'll ask my questions in subsequent e-mails.
>
> In my opinion GLEP 76 is the most controversial decision made by
> running council. While it fixed some long standing issues like
> copyright headers and proper acknowledgement of out of the tree
> contributors, it created grave problems: now some long-time
> contributors and even developer are seriously discriminated because
> they want to keep their privacy.
>
> What is your opinion on this problem?
> Should GLEP 76 be left as is?
> Should GLEP 76 be cancelled?
> Should GLEP 76 be improved and how?
Since I've accepted the nomination, it's my turn to answer as well.
I'll tell you frankly that GLEP 76 was the main motivation for me
to accept the nomination. I consider it — in the way it exists now —
harmful and in need to be fixed. This is how free software works:
if something is broken and nobody repairs it, go and fix it
yourself.
What is wrong with GLEP 76? It kicks some active contributors and
rejects some of new ones. No, it is not just one developer
affected as someone may assume. We have external contributors
kicked out, we have at least one high quality maintainer who worked
on quizzes, but this work was stopped due to hostility to and
further ban on anonymous contributions.
I believe that for free software development privacy concern is of
paramount importance, especially when we are dealing with security
or privacy oriented software.
One may argue that ban on anonymous contributions was to protect
Gentoo from possible copyright claims in the future. But does it
really gives us such protection? In my opinion NO, because:
1. GLEP 76 was prepared without legal expertise from experts in
this field. (At least such expertise was not published.) Hereby we
have no evidence that it will work if real case will be opened.
2. No law or legal precedent was provided to prove that GLEP 76
will be useful in alleged case or that we have a legal requirement
to put such restrictive demand on our contributors.
3. We objectively have no means to verify developer's credentials.
Current approach is based on realistic-like approach: if someone
names themselve "John Doe" we accept it, if someone names as
"qwerty123" we do not recognize this as an ID. But we have no means
to verify that "John Doe" is real (natural) name. Even GnuPG Web of
Trust doesn't provide such means, because what it really provides
is a link between a person and their GnuPG key, as we're not
authorized legal entities empowered and fully informed to verify
validity of IDs present during GnuPG signing.
So in my opinion current state of affairs is not acceptable and
must be amended. What I propose to do:
1. To mitigate current crisis we should allow developers to commit
under any unique non-offensive id (text string) as long as the
trustees know how it maps to a real name.
The rationale is that the trustees are the legal body to handle all
legal issues of Gentoo, so even if we agree that real names are
mandatory, there is no practical legal need for anyone outside of
trustees to know them. This way we can include people who agree to
keep their privacy from anyone except trustees and in the same way
this will keep the legal effect of GLEP 76 intact.
2. Work together with trustees and possibly some external expertise
(both legal and risk assessment) to clarify if we are really
expected to check all these data and search for a way to accept
private contributions.
My goal is to help Gentoo to be open and inclusive society and not
some bureaucratic club fighting ghosts (I *don't* claim it is that
way now, but there are some alarming tendencies...).
Best regards,
Andrew Savchenko
[-- Attachment #2: Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-06-24 22:18 UTC|newest]
Thread overview: 110+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-15 9:42 [gentoo-project] Questions for Gentoo Council nominees Andrew Savchenko
2019-06-15 9:49 ` [gentoo-project] Questions for Gentoo Council nominees: GLEP 76 Andrew Savchenko
2019-06-15 10:20 ` Ulrich Mueller
2019-06-15 16:17 ` Kristian Fiskerstrand
2019-06-16 22:01 ` Thomas Deutschmann
2019-06-18 14:12 ` William Hubbs
2019-06-18 15:43 ` Luca Barbato
2019-06-18 15:47 ` William Hubbs
2019-06-24 22:18 ` Andrew Savchenko [this message]
2019-06-25 6:15 ` Michał Górny
2019-06-28 11:49 ` Andrew Savchenko
2019-06-28 12:09 ` Rich Freeman
2019-06-28 17:51 ` Andrew Savchenko
2019-06-30 4:48 ` desultory
2019-06-30 18:53 ` Rich Freeman
2019-07-01 5:02 ` desultory
2019-07-01 11:59 ` Rich Freeman
2019-07-02 4:24 ` desultory
2019-07-02 11:57 ` Rich Freeman
2019-07-03 4:31 ` desultory
2019-07-03 11:13 ` Rich Freeman
2019-07-04 4:32 ` desultory
2019-06-30 7:11 ` Patrick Lauer
2019-06-30 7:42 ` Michał Górny
2019-06-30 8:03 ` Patrick Lauer
2019-06-30 22:27 ` Robin H. Johnson
2019-07-01 1:31 ` Thomas Deutschmann
2019-06-15 10:00 ` [gentoo-project] Questions for Gentoo Council nominees: Power balance Andrew Savchenko
2019-06-15 10:34 ` Ulrich Mueller
2019-06-15 21:25 ` Andreas K. Huettel
2019-06-16 7:31 ` Mikle Kolyada
2019-06-16 15:56 ` Roy Bamford
2019-06-16 22:18 ` Thomas Deutschmann
2019-06-17 1:38 ` Kristian Fiskerstrand
2019-06-18 14:41 ` William Hubbs
2019-06-30 7:26 ` Patrick Lauer
2019-06-15 10:24 ` [gentoo-project] Questions for Gentoo Council nominees: Bringing new people Andrew Savchenko
2019-06-15 16:24 ` Kristian Fiskerstrand
2019-06-15 21:23 ` Andreas K. Huettel
2019-06-16 18:51 ` Mikle Kolyada
2019-06-16 22:21 ` Thomas Deutschmann
2019-06-19 2:39 ` William Hubbs
2019-06-16 18:09 ` [gentoo-project] Questions for Gentoo Council nominees: Gentoo as hobbyist distro Michał Górny
2019-06-16 19:13 ` Kristian Fiskerstrand
2019-06-16 22:39 ` Thomas Deutschmann
2019-06-19 6:24 ` Mikle Kolyada
2019-06-19 15:45 ` William Hubbs
2019-06-21 14:55 ` Mikle Kolyada
2019-06-19 14:32 ` William Hubbs
2019-06-20 14:48 ` Andreas K. Huettel
2019-06-21 13:21 ` [gentoo-project] Questions for Gentoo Council nominees: your achievements Michał Górny
2019-06-21 20:46 ` Kristian Fiskerstrand
2019-06-21 22:59 ` Georgy Yakovlev
2019-06-22 6:44 ` Ulrich Mueller
2019-06-22 7:06 ` Michał Górny
2019-06-22 22:57 ` Mikle Kolyada
2019-06-24 11:05 ` Mart Raudsepp
2019-06-24 11:25 ` [gentoo-project] Questions for Gentoo Council nominees: traits of a good Council member Michał Górny
2019-06-24 23:23 ` [gentoo-project] Questions for Gentoo Council nominees: Gentoo Foundation Robin H. Johnson
2019-06-26 19:45 ` Kristian Fiskerstrand
2019-06-26 21:54 ` Matthew Thode
2019-06-26 22:03 ` Kristian Fiskerstrand
2019-06-26 22:06 ` Kristian Fiskerstrand
2019-06-26 22:13 ` Matthew Thode
2019-06-26 22:28 ` Kristian Fiskerstrand
2019-06-30 19:21 ` Andreas K. Huettel
2019-06-26 22:08 ` Matthew Thode
2019-06-26 22:15 ` Michael Everitt
2019-06-26 22:22 ` Kristian Fiskerstrand
2019-06-28 23:49 ` Andreas K. Huettel
[not found] ` <20190630215422.GA22747@bubba.lan>
2019-06-30 21:55 ` Aaron Bauman
2019-07-01 7:50 ` Michał Górny
2019-07-01 9:31 ` Roy Bamford
2019-07-01 9:52 ` Michał Górny
2019-07-01 10:02 ` Michael Everitt
2019-07-01 10:04 ` Michael Everitt
2019-07-01 19:42 ` Andreas K. Huettel
2019-07-01 19:44 ` Andreas K. Huettel
2019-07-01 20:10 ` Alec Warner
2019-07-01 21:14 ` Roy Bamford
2019-07-02 12:40 ` Kristian Fiskerstrand
2019-07-01 11:26 ` Roy Bamford
2019-07-01 12:07 ` Rich Freeman
2019-07-01 19:34 ` Andreas K. Huettel
2019-07-03 4:42 ` desultory
2019-07-03 6:12 ` [gentoo-project] Questions for Gentoo Council nominees: Gentoo Foundation - Treasurer Response! Robin H. Johnson
2019-07-03 9:51 ` Michael Everitt
2019-07-03 10:47 ` Rich Freeman
2019-07-03 11:05 ` Michael Everitt
2019-07-03 11:22 ` Rich Freeman
2019-07-03 11:27 ` Kristian Fiskerstrand
2019-07-03 12:27 ` Rich Freeman
2019-07-03 13:45 ` Kristian Fiskerstrand
2019-07-03 12:56 ` [gentoo-nfp] " Michał Górny
2019-07-03 13:08 ` Rich Freeman
2019-07-03 13:17 ` Michał Górny
[not found] ` <20190703143429.yfieiru7cyykr5ca@gentoo.org>
[not found] ` <6b84c0a026551472a05e776921182ba8dae6fb1e.camel@gentoo.org>
[not found] ` <138757e484f751d567fb2702ce27de3e3e215a15.camel@gentoo.org>
2019-07-04 2:05 ` [gentoo-nfp] Re: [gentoo-project] Questions for Gentoo Council nominees: Gentoo Foundation - Treasurer Response! (part 2) Robin H. Johnson
2019-06-30 10:36 ` [gentoo-project] Questions for Gentoo Council nominees Roy Bamford
2019-06-30 16:48 ` Thomas Deutschmann
2019-06-30 20:17 ` Andreas K. Huettel
2019-07-04 2:14 ` [gentoo-project] Questions for Gentoo Council nominees: Council demands on maintainers & council legal liability Robin H. Johnson
2019-07-04 6:26 ` Michał Górny
2019-07-04 8:03 ` Kristian Fiskerstrand
2019-07-04 20:33 ` Alec Warner
2019-07-04 23:46 ` Kristian Fiskerstrand
2019-07-06 2:54 ` desultory
2019-07-04 13:36 ` Thomas Deutschmann
2019-07-04 16:37 ` Ulrich Mueller
2019-07-04 18:49 ` Thomas Deutschmann
2019-07-04 19:22 ` Ulrich Mueller
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=20190625011818.73fb7c1948a0a3d124a0d9db@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