public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "William L. Thomson Jr." <wlt-ml@o-sinc.com>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Merging Trustees and Council / Developers and Foundation
Date: Thu, 05 Jan 2017 17:14:51 -0500	[thread overview]
Message-ID: <assp.0178ac1452.2183054.kgu1j0o2HE@wlt> (raw)
In-Reply-To: <20170105225649.17fc8f79.mgorny@gentoo.org>

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

On Thursday, January 5, 2017 10:56:49 PM EST Michał Górny wrote:
> 
> Well, this kind of superficial description does not raise any immediate
> concerns. However, the devil's in the detail, and if you really want
> comments, you should start providing some.

For such major changes it may not be practical to lay out all the details. Do 
politicians every lay out ever detail of their agenda? To an extent you need 
to trust the judgement of those elected. If they do not represent your 
interest and point of view, elect another or run yourself.

> 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'.

An indemnity clause or something to that effect should be suffice to transfer 
any and all liability from the individual to the Foundation. Which the 
Foundation is already liable for actions of developers, foundation member or 
not.

> 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?

Interesting point, but I do not see that as being so much of an issue, even if 
from a "terrorist or hostile" state, or other bad actor. Given Gentoo is a 
FOSS project, and most if not all will be made public or could be upon 
request. I could see more legal liability to developers who can commit vs 
foundation member who can do what?

Unless Gentoo is allowing someone to do something nefarious and not 
transparently. I do not see this as being an issue. If you can create a 
Facebook, Twitter, and other accounts from other countries. Then membership in 
Gentoo should not be much of a deal. It is not like you get anything being a 
member at this time. If there was a majority in a hostile state, maybe.

Keep in mind the US is founded on freedom of speech. An open source project 
could be argued along the same lines as freedom of speech and expression. Not 
to mention an argument could be made for technical benefit of all, etc.

Unless you live in say Iran, or North Korea, I am not sure it is an issue for 
most. Quite many projects have members in other countries.

For example
https://www.firebirdsql.org/en/members/

Several are in Russia, and some in the US are not to happy with Russia :)

-- 
William L. Thomson Jr.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  parent 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
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. [this message]
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=assp.0178ac1452.2183054.kgu1j0o2HE@wlt \
    --to=wlt-ml@o-sinc.com \
    --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