From: Aaron Bauman <bman@gentoo.org>
To: gentoo-nfp@lists.gentoo.org
Subject: Re: [gentoo-nfp] Questions For Gentoo Foundation Trustee Candidates
Date: Sun, 14 Jul 2019 11:21:03 -0400 [thread overview]
Message-ID: <20190714152103.GH22850@bubba.lan> (raw)
In-Reply-To: <13dad59c44f143059b7bf0e8e5216d5540285bef.camel@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1325 bytes --]
On Sat, Jul 13, 2019 at 03:39:51PM +0200, Michał Górny wrote:
> On Sat, 2019-07-13 at 06:17 -0700, Raymond Jennings wrote:
> > What are your plans regarding future relations between the trustees and the
> > council? I noted that the council isn't even mentioned in the bylaws
>
> I've answered this in detail in my Manifesto [1].
>
> Long story short, I believe the distribution should be self-governing,
> and Foundation should support it without interfering unnecessarily.
> This means that Council makes the majority of the decisions regarding
> Gentoo, and Trustees should work with the Council and respect
> the decisions made by it.
>
> [1] https://dev.gentoo.org/~mgorny/trustee-manifesto-2019.txt
>
> --
> Best regards,
> Michał Górny
>
Nothing is "self-governing" and always requires a legal entity of some kind.
This has implications beyond what the council can be held responsible for.
On the premise of your statement though and through IRC chats, I agree with your
statement.
I am for by-laws delineating the roles of the council to lead the distribution.
As stated above, some things cannot be delegated. That is, things which have
legal implications, COMREL, etc.
This drives my first comment that nothing is "self-governing" in general.
--
Cheers,
Aaron
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-07-14 15:21 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-13 12:12 [gentoo-nfp] Questions For Gentoo Foundation Trustee Candidates Roy Bamford
2019-07-13 12:18 ` Roy Bamford
2019-07-13 13:37 ` Michał Górny
2019-07-14 14:53 ` Aaron Bauman
2019-07-14 15:29 ` Robin H. Johnson
2019-07-14 15:54 ` Aaron Bauman
2019-07-14 16:01 ` Robin H. Johnson
2019-07-14 16:12 ` Aaron Bauman
2019-07-14 15:58 ` Aaron Bauman
2019-07-14 16:54 ` Robin H. Johnson
2019-07-14 17:46 ` Aaron Bauman
2019-07-14 19:25 ` Rich Freeman
2019-07-13 14:52 ` Alec Warner
2019-07-14 14:40 ` Aaron Bauman
2019-07-14 16:24 ` Roy Bamford
2019-07-14 16:32 ` Aaron Bauman
2019-07-14 17:24 ` Michał Górny
2019-07-14 17:35 ` Aaron Bauman
2019-07-14 17:04 ` Alec Warner
2019-07-14 17:51 ` Aaron Bauman
2019-07-14 17:56 ` Alec Warner
2019-07-14 18:15 ` Aaron Bauman
2019-07-14 0:29 ` Robin H. Johnson
2019-07-14 14:32 ` Aaron Bauman
2019-07-14 19:25 ` Robin H. Johnson
2019-07-14 19:43 ` Rich Freeman
2019-07-14 19:55 ` Michael Everitt
2019-07-14 19:53 ` Michael Everitt
2019-07-14 21:00 ` Aaron Bauman
2019-07-14 20:20 ` Aaron Bauman
2019-07-15 2:09 ` Robin H. Johnson
2019-07-15 16:00 ` Aaron Bauman
2019-07-15 19:29 ` Robin H. Johnson
2019-07-15 16:46 ` alicef
2019-07-13 13:17 ` Raymond Jennings
2019-07-13 13:39 ` Michał Górny
2019-07-13 13:51 ` Michael Everitt
2019-07-13 15:50 ` Roy Bamford
2019-07-13 19:03 ` Michał Górny
2019-07-13 19:59 ` Roy Bamford
2019-07-13 20:49 ` Michał Górny
2019-07-13 20:50 ` Rich Freeman
2019-07-14 15:23 ` Aaron Bauman
2019-07-14 15:21 ` Aaron Bauman [this message]
2019-07-14 15:51 ` Aaron Bauman
2019-07-13 20:15 ` Roy Bamford
2019-07-13 20:56 ` Alec Warner
2019-07-13 21:15 ` Roy Bamford
2019-07-13 21:25 ` Michał Górny
2019-07-14 14:59 ` Aaron Bauman
2019-07-14 17:15 ` Michał Górny
2019-07-14 17:21 ` Aaron Bauman
2019-07-15 10:44 ` Jorge Manuel B. S. Vicetto
2019-07-15 11:45 ` Michał Górny
2019-07-15 12:13 ` Alec Warner
2019-07-15 12:42 ` Jorge Manuel B. S. Vicetto
2019-07-13 20:57 ` Michał Górny
2019-07-14 15:17 ` Aaron Bauman
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=20190714152103.GH22850@bubba.lan \
--to=bman@gentoo.org \
--cc=gentoo-nfp@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