From: Aaron Bauman <bman@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] call for agenda items -- council meeting 2019-04-14
Date: Tue, 9 Apr 2019 20:17:56 -0400 [thread overview]
Message-ID: <20190410001756.GH8129@monkey> (raw)
In-Reply-To: <9b6b02c8-bc96-6e5d-d99a-56e9290479b0@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1594 bytes --]
On Tue, Apr 09, 2019 at 06:49:11PM -0400, Chris Reffett wrote:
>
> On 4/9/2019 6:10 PM, Kristian Fiskerstrand wrote:
> > On 4/10/19 12:05 AM, Michael Everitt wrote:
> >> Not all cases are simply ones where a person does not wish to use their
> >> full given name, there are perfectly decent arguments for using a pseudonym
> >> when there could be mild or severe ramifications if their true identity was
> >> in the public domain. I'm thinking as obvious examples of those involved in
> >> security/penetration work, where it may be required, and not simply
> >> desirable to keep ones primary identity confidential. Are we really so
> >> draconian to eliminate these (often very well-skilled individuals) for
> >> making a specialist contribution to Gentoo Linux?!
> >
> > The ultimate goal is to ensure that contributions are actually by the
> > ones holding a valid copyright, or the contribution being of a license
> > that is allowed under a license from the copyright holder. As mentioned
> > in the link in prior post, GPL itself doesn't explicitly exclude the
> > warranty of non-infridgement under UCC which can have severe legal
> > consequences if a third party relies on the contribution, and as such
> > puts Gentoo in a legal liability if we can't reasonably explain such
> > contributions. As long as the copyright is valid and we can document it,
> > it is fine, but as soon as things gets murky...
> >
>
Michael, I would be very intrigued to read about such pseudonyms being
required by cybersecurity folks... references?
--
Cheers,
Aaron
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-04-10 0:18 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 3:20 [gentoo-project] call for agenda items -- council meeting 2019-04-14 William Hubbs
2019-04-02 13:47 ` Michał Górny
2019-04-03 11:31 ` NP-Hardass
2019-04-03 12:43 ` Alec Warner
2019-04-03 14:04 ` NP-Hardass
2019-04-03 14:43 ` Andrew Savchenko
2019-04-03 18:12 ` Andrew Savchenko
2019-04-03 21:39 ` Michael Everitt
2019-04-03 18:44 ` Michał Górny
2019-04-03 22:35 ` Alec Warner
2019-04-03 22:48 ` Michael Everitt
2019-04-04 5:20 ` Michał Górny
2019-04-09 20:18 ` Gokturk Yuksek
2019-04-09 20:45 ` Alec Warner
2019-04-09 20:56 ` Rich Freeman
2019-04-09 21:03 ` Raymond Jennings
2019-04-09 21:05 ` Raymond Jennings
2019-04-09 21:13 ` Gokturk Yuksek
2019-04-10 7:13 ` Michał Górny
2019-04-10 7:36 ` Alice Ferrazzi
2019-04-10 7:45 ` Michał Górny
2019-04-10 8:02 ` Michael Everitt
2019-04-10 7:42 ` Mikle Kolyada
2019-04-14 13:58 ` Andreas K. Huettel
2019-04-09 21:06 ` Ulrich Mueller
2019-04-09 21:30 ` Gokturk Yuksek
2019-04-09 21:46 ` Kristian Fiskerstrand
2019-04-09 21:50 ` Rich Freeman
2019-04-09 21:53 ` Kristian Fiskerstrand
2019-04-09 22:00 ` Kristian Fiskerstrand
2019-04-09 22:05 ` Michael Everitt
2019-04-09 22:10 ` Kristian Fiskerstrand
2019-04-09 22:49 ` Chris Reffett
2019-04-10 0:17 ` Aaron Bauman [this message]
2019-04-10 0:31 ` Michael Everitt
2019-04-10 1:12 ` Alice Ferrazzi
2019-04-14 14:09 ` Andreas K. Huettel
2019-04-10 1:58 ` Michael Orlitzky
2019-04-10 2:07 ` Aaron Bauman
2019-04-10 7:20 ` Michał Górny
2019-04-14 14:04 ` Andreas K. Huettel
2019-04-10 1:15 ` Alice Ferrazzi
2019-04-10 1:30 ` Aaron Bauman
2019-04-10 1:47 ` Alice Ferrazzi
2019-04-10 1:48 ` Aaron Bauman
2019-04-14 14:11 ` Andreas K. Huettel
2019-04-14 15:28 ` Andrew Savchenko
2019-04-14 15:48 ` Aaron Bauman
2019-04-14 16:13 ` Andrew Savchenko
2019-04-14 16:41 ` Michał Górny
2019-04-14 16:47 ` Andrew Savchenko
2019-04-10 5:42 ` Ulrich Mueller
2019-04-10 5:59 ` Ulrich Mueller
2019-04-10 6:27 ` Alice Ferrazzi
2019-04-10 6:29 ` Ulrich Mueller
2019-04-10 6:54 ` Alec Warner
2019-04-11 0:22 ` Gokturk Yuksek
2019-04-14 14:18 ` Andreas K. Huettel
2019-04-10 7:28 ` Michał Górny
2019-04-10 12:47 ` Alec Warner
2019-04-10 13:21 ` Rich Freeman
2019-04-10 22:36 ` Aaron Bauman
2019-04-14 14:23 ` Andreas K. Huettel
2019-04-03 14:56 ` Ulrich Mueller
2019-04-04 6:30 ` Mikle Kolyada
2019-04-04 7:47 ` Ulrich Mueller
2019-04-04 10:15 ` Mikle Kolyada
2019-04-03 23:05 ` Alec Warner
2019-04-04 0:20 ` Alec Warner
2019-04-09 20:46 ` Gokturk Yuksek
2019-04-09 21:01 ` Aaron Bauman
2019-04-09 21:34 ` Gokturk Yuksek
2019-04-19 6:50 ` [gentoo-project] GLEP76, legal liability around misrepresentation in copyright, real names, how it's handled at FSF, SFC & at the US copyright office! Robin H. Johnson
2019-04-20 23:41 ` Rich Freeman
2019-04-08 5:03 ` [gentoo-project] call for agenda items -- council meeting 2019-04-14 Michał Górny
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=20190410001756.GH8129@monkey \
--to=bman@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