public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: Matthew Thode <prometheanfire@gentoo.org>
Cc: gentoo-project@lists.gentoo.org,
	gentoo-nfp <gentoo-nfp@lists.gentoo.org>
Subject: Re: [gentoo-project] Merging Trustees and Council / Developers and Foundation
Date: Thu, 5 Jan 2017 23:14:03 +0100	[thread overview]
Message-ID: <20170105231403.5c44eb6d.mgorny@gentoo.org> (raw)
In-Reply-To: <f671df99-af80-b726-99eb-c5973616c6a9@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]

On Thu, 5 Jan 2017 16:02:57 -0600
Matthew Thode <prometheanfire@gentoo.org> wrote:

> On 01/05/2017 03:56 PM, Michał Górny wrote:
> > 
> > As far as I understand, this would effectively require every developer
> > to be a member of the Foundation. I think that Foundation membership is
> > more legally binding than 'being a developer = having commit access'.
> > 
> > One thing I'm particular worried about is the potential of 'US
> > embargo'. What if a particular developer/recruit is/will not be legally
> > allowed to be a member of Gentoo Foundation?
> >   
> 
> I think that this brings us more in line with the legal realities of
> running a distro like this.  We may want to be separate but don't think
> that's actually the case.  So we should stop pretending we are separate.

The reality is as people/committees perceive it. I can imagine quite
a distinction between 'working on an international project' and 'being
enlisted member of US organization'.

-- 
Best regards,
Michał Górny
<http://dev.gentoo.org/~mgorny/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 963 bytes --]

  reply	other threads:[~2017-01-05 22:14 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-05 21:36 [gentoo-project] Merging Trustees and Council / Developers and Foundation Matthew Thode
2017-01-05 21:56 ` Michał Górny
2017-01-05 22:02   ` Matthew Thode
2017-01-05 22:14     ` Michał Górny [this message]
2017-01-05 22:17       ` William L. Thomson Jr.
2017-01-10  5:32         ` Daniel Campbell
2017-01-06 10:43     ` Andreas K. Huettel
2017-01-06 15:28       ` William L. Thomson Jr.
2017-01-10  5:35       ` Daniel Campbell
2017-01-05 22:03   ` M. J. Everitt
2017-01-05 22:14   ` William L. Thomson Jr.
2017-01-06 10:48     ` Andreas K. Huettel
2017-01-06 15:15       ` [gentoo-project] OT " William L. Thomson Jr.
     [not found]       ` <8835202.ILOODCAab9@wlt>
2017-01-06 15:31         ` William L. Thomson Jr.
2017-01-10  5:39       ` [gentoo-project] " Daniel Campbell
2017-01-10  6:21         ` Matthew Thode
2017-01-06  0:41   ` Alec Warner
2017-01-06  1:15     ` Rich Freeman
2017-01-06 10:40   ` Andreas K. Huettel
2017-01-06 15:37     ` William L. Thomson Jr.
2017-01-05 21:57 ` Kristian Fiskerstrand
2017-01-05 22:10   ` [gentoo-nfp] " Matthew Thode
2017-01-05 22:17     ` Kristian Fiskerstrand
2017-01-05 22:20   ` Raymond Jennings
2017-01-05 22:54     ` Rich Freeman
2017-01-05 23:03       ` Raymond Jennings
2017-01-05 23:20         ` David Abbott
2017-01-06 12:10 ` Andreas K. Huettel
2017-01-06 14:47   ` Rich Freeman
2017-01-06 16:22     ` William L. Thomson Jr.
2017-01-10  5:55     ` Daniel Campbell
2017-01-06 15:57   ` William L. Thomson Jr.
2017-01-06 16:24     ` Rich Freeman
2017-01-06 16:41       ` William L. Thomson Jr.
2017-01-06 16:51         ` Rich Freeman
2017-01-06 17:09           ` William L. Thomson Jr.
2017-01-06 17:13     ` Andreas K. Huettel
2017-01-06 17:19       ` Matthew Thode
2017-01-06 17:37         ` Raymond Jennings
2017-01-06 18:15           ` Rich Freeman
2017-01-06 18:31             ` Raymond Jennings
2017-01-06 17:26       ` Alec Warner
2017-01-06 17:37         ` William L. Thomson Jr.
2017-01-06 18:43           ` Alec Warner
2017-01-06 20:22             ` William L. Thomson Jr.
2017-01-10  6:19             ` Daniel Campbell

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=20170105231403.5c44eb6d.mgorny@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-nfp@lists.gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    --cc=prometheanfire@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