public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: desultory <desultory@gentoo.org>
To: gentoo-project@lists.gentoo.org, "Michał Górny" <mgorny@gentoo.org>
Subject: Re: [gentoo-project] pre-GLEP: Gentoo OpenPGP web of trust
Date: Sat, 2 Feb 2019 01:00:04 -0500	[thread overview]
Message-ID: <b23f9349-a82b-1606-81e2-e41cfaa6676d@gentoo.org> (raw)
In-Reply-To: <1549004234.3382.1.camel@gentoo.org>

On 02/01/19 01:57, Michał Górny wrote:
> On Thu, 2019-01-31 at 09:21 -0500, Brian Evans wrote:
>> On 1/31/2019 8:56 AM, Michał Górny wrote:
>>
>>>
>>> Signature requirements
>>> ----------------------
>>>
>>> As a final goal of this GLEP, each Gentoo developer will be required
>>> to have at least one signature from another Gentoo developer or from
>>> member of one of the partner communities present on their
>>> ``@gentoo.org`` UID.
>>
>> -1
>>
>> I won't be able to accomplish this as I do not travel and have no
>> opportunities to meet with others. Plus, it's just downright awkward.
>> I'm sure there are other devs in this same situation.
>>
> 
> The most commonly proposed alternative is identity verification via
> video chat.  Would that also be unachievable for you?
> 
> It would be really nice to get some measure on how many people *really*
> can't do it, rather than how many will oppose for the sake of opposing. 
> It is funny how many of the people complaining today would actually
> quickly get the needed signature if this was required from the start.
> 
I, for one, am a member of both sets: I neither reasonably could nor
would I if I reasonably could. In context [GLEP76], the proposed policy
is, by all appearances, pointless make work for the sake of buzzword bingo.

[GLEP76] https://www.gentoo.org/glep/glep-0076.html


  parent reply	other threads:[~2019-02-02  6:00 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 [this message]
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
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=b23f9349-a82b-1606-81e2-e41cfaa6676d@gentoo.org \
    --to=desultory@gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    --cc=mgorny@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