From: Chris Reffett <creffett@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] pre-GLEP: Gentoo OpenPGP web of trust
Date: Thu, 31 Jan 2019 19:55:13 -0500 [thread overview]
Message-ID: <c8799c49-f1db-5046-bf6c-153e96362ab4@gentoo.org> (raw)
In-Reply-To: <f33043d9-d0b8-d1ff-5def-f38bdad28059@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 1026 bytes --]
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.
>
(IANAL, etc., etc.) At least in US copyright law, you may hold copyright
under a pseudonym, though it has different rules on the length of the
copyright and can cause issues with claiming ownership. Ref:
https://www.copyright.gov/fls/fl101.pdf
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. As an analogy, I can
write a novel, self-publish, and claim copyright (without registering
the copyright, mind you - again, working in US law here, where copyright
is automatic on publication), and I never had to show ID to anyone - the
name on the cover gets the copyright. Why should my commits be any
different?
-creffett
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 885 bytes --]
next prev parent reply other threads:[~2019-02-01 0:55 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 [this message]
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=c8799c49-f1db-5046-bf6c-153e96362ab4@gentoo.org \
--to=creffett@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