From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: Rich Freeman <rich0@gentoo.org>
Subject: Re: [gentoo-project] pre-GLEP: Gentoo OpenPGP web of trust
Date: Fri, 01 Feb 2019 13:52:50 +0100 [thread overview]
Message-ID: <3632143.Zo7t0miSdB@porto> (raw)
In-Reply-To: <CAGfcS_=CR0=A9L0e4pdhgEf8ADp5e2VTFBaqHkskcp0YT0KUBA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1377 bytes --]
Am Freitag, 1. Februar 2019, 02:56:29 CET schrieb Rich Freeman:
> On Thu, Jan 31, 2019 at 7:55 PM Chris Reffett <creffett@gentoo.org> wrote:
> > On 1/31/2019 7:42 PM, Kristian Fiskerstrand wrote:
> > > On 2/1/19 1:41 AM, Chris Reffett wrote:
> > >> but let me pose a more philosophical
> > >> question: _why should proving my real name matter_?
> > >
> > > It matters in the context of copyright law.
> >
> > That said, though, I'm talking about the GPG key itself here, not my
> > commits, and I think that verification of real identity through WoT is
> > an unreasonably high bar for claiming copyright.
>
> ++
>
> I think there are a lot of good reasons to require real names.
> However, making that our policy and upholding it when we have cause to
> think a name is false doesn't require us to rigorously check IDs.
>
> Maybe for officers listed on filings for the Foundation it is more of a
> concern.
>
> IMO Gentoo developers should simply be asked to provide their real
> name, and to confirm that they are legally adults. I don't think
> we're doing anything that necessitates a higher level of due diligence
> than that unless somebody actually brings a potential specific concern
> to our attention.
++
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-02-01 12:53 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
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 [this message]
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=3632143.Zo7t0miSdB@porto \
--to=dilfridge@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
--cc=rich0@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