From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project <gentoo-project@lists.gentoo.org>
Subject: Re: [gentoo-project] pre-GLEP: Gentoo OpenPGP web of trust
Date: Fri, 1 Feb 2019 15:46:33 -0500 [thread overview]
Message-ID: <CAGfcS_=t9miZ4jBNxVM0bR4LFxSB-HnzQhXao5XDMFxsEs1TOg@mail.gmail.com> (raw)
In-Reply-To: <3c3f0434-0497-b302-210e-64cb6e1a565b@gentoo.org>
On Fri, Feb 1, 2019 at 12:27 PM Kristian Fiskerstrand <k_f@gentoo.org> wrote:
>
> On 2/1/19 3:53 PM, Kristian Fiskerstrand wrote:
> > Notes
> > [N1] Infra is in a special role here, but so are a lot of other projects
> > like comrel just to name another.
>
> One alternative is of course to start gradually, and only require WoT
> for certain roles; offhand I can think of; Infra, Comrel, Security,
> Trustees and Council.
Do we really want to tell developers they're not allowed to vote for a
particular candidate for Council because that candidate didn't prove
their identity? IMO developers should be as free as possible to elect
whatever representatives they prefer.
Remember, Council members aren't just some kind of "privileged elite."
They are also the way ordinary developers can exercise control over
all the other people who would otherwise be the "privileged elite" in
the absence of some kind of democratic representation.
I could see more of an argument for some of the other roles on the list.
--
Rich
next prev parent reply other threads:[~2019-02-01 20:46 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 13:56 [gentoo-project] pre-GLEP: Gentoo OpenPGP web of trust Michał Górny
2019-01-31 14:21 ` Brian Evans
2019-01-31 15:33 ` Matthew Thode
2019-02-01 2:48 ` Sam Jorna (wraeth)
2019-02-01 6:57 ` Michał Górny
2019-02-01 14:43 ` Brian Evans
2019-02-02 6:00 ` desultory
2019-01-31 15:32 ` Matthew Thode
2019-02-01 12:47 ` Andreas K. Huettel
2019-02-01 14:17 ` Cynede
2019-02-01 14:32 ` Rich Freeman
2019-02-01 14:53 ` Kristian Fiskerstrand
2019-02-01 17:27 ` Kristian Fiskerstrand
2019-02-01 20:46 ` Rich Freeman [this message]
2019-02-02 6:02 ` desultory
2019-02-01 14:20 ` Michał Górny
2019-01-31 16:33 ` Kristian Fiskerstrand
2019-01-31 16:35 ` Alec Warner
2019-01-31 20:29 ` Kristian Fiskerstrand
2019-01-31 21:40 ` Alec Warner
2019-01-31 22:00 ` Kristian Fiskerstrand
2019-01-31 22:49 ` Michael Orlitzky
2019-02-01 0:09 ` Rich Freeman
2019-02-01 0:47 ` Kristian Fiskerstrand
2019-01-31 17:33 ` Rich Freeman
2019-02-01 12:51 ` Andreas K. Huettel
2019-02-01 13:25 ` Michał Górny
2019-02-02 5:55 ` desultory
2019-02-02 13:47 ` Rich Freeman
2019-01-31 19:25 ` Kristian Fiskerstrand
2019-02-01 0:41 ` Chris Reffett
2019-02-01 0:42 ` Kristian Fiskerstrand
2019-02-01 0:55 ` Chris Reffett
2019-02-01 1:56 ` Rich Freeman
2019-02-01 12:52 ` Andreas K. Huettel
2019-02-02 5:54 ` desultory
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='CAGfcS_=t9miZ4jBNxVM0bR4LFxSB-HnzQhXao5XDMFxsEs1TOg@mail.gmail.com' \
--to=rich0@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