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 - 1.0 reply
Date: Wed, 11 Jan 2017 10:06:40 -0500 [thread overview]
Message-ID: <assp.01844b6216.1630487.UI17VbWlKS@wlt> (raw)
In-Reply-To: <1d601c44-e136-382d-54f4-27d3437dfcc5@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1171 bytes --]
On Wednesday, January 11, 2017 4:59:49 AM EST Matthew Thode wrote:
>
> On second thought, I think that under the board there will still be a
> council for general technical matters that you would still be electable
> towards.
I think in any merge it would be best to keep existing structure, just unify
and have means for them to work together rather than in their own silo.
> In the next version of this (1.1) I think I'm leaning towards
> the 'board' being what is currently trustees + hr(comrel) + pr + infra.
> Under that would go what is currently being done by council.
>
> I think rich0 proposed the merged board having the functionality of both
> council and trustees, but I'm not sure that'd work with your concerns.
I think merging Trustees and Council is a mistake. It would reduce any checks
and balances, and combine focus of the two bodies, possibly getting less done.
I see the Council as more running the project, and Trustees overseeing such,
helping where they can, etc. Each can have their own roles duties, but the
Council still being the main/core entity leading the project technically.
--
William L. Thomson Jr.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2017-01-11 15:06 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 22:37 [gentoo-project] Merging Trustees and Council / Developers and Foundation - 1.0 reply Matthew Thode
2017-01-10 23:03 ` Rich Freeman
2017-01-10 23:34 ` William L. Thomson Jr.
2017-01-11 7:54 ` Ulrich Mueller
2017-01-11 7:50 ` Ulrich Mueller
2017-01-11 10:03 ` Matthew Thode
2017-01-11 10:19 ` Kristian Fiskerstrand
2017-01-11 10:59 ` Matthew Thode
2017-01-11 12:24 ` Matthias Maier
2017-01-11 12:59 ` Raymond Jennings
2017-01-11 14:07 ` Rich Freeman
2017-01-11 15:23 ` William L. Thomson Jr.
2017-01-11 15:49 ` Raymond Jennings
2017-01-11 15:18 ` William L. Thomson Jr.
2017-01-11 16:50 ` Matthias Maier
2017-01-11 16:54 ` Ciaran McCreesh
2017-01-11 17:16 ` Matthias Maier
2017-01-11 17:42 ` William L. Thomson Jr.
2017-01-11 16:56 ` Alec Warner
2017-01-11 17:06 ` Matthias Maier
2017-01-11 17:20 ` Alec Warner
2017-01-11 19:16 ` Matthias Maier
2017-01-11 17:39 ` William L. Thomson Jr.
2017-01-12 5:53 ` Daniel Campbell
2017-01-11 17:55 ` Michał Górny
2017-01-11 17:01 ` Matthias Maier
2017-01-11 17:41 ` William L. Thomson Jr.
2017-01-12 0:03 ` Matthias Maier
2017-01-11 17:33 ` William L. Thomson Jr.
2017-01-25 20:32 ` Matthew Thode
2017-01-25 20:40 ` Rich Freeman
2017-01-25 20:51 ` Matthew Thode
2017-01-26 16:02 ` William L. Thomson Jr.
2017-01-11 15:06 ` William L. Thomson Jr. [this message]
2017-01-11 15:11 ` Michał Górny
2017-01-11 15:29 ` William L. Thomson Jr.
2017-01-11 15:56 ` Raymond Jennings
2017-01-11 14:46 ` Michał Górny
2017-01-11 15:56 ` William L. Thomson Jr.
2017-01-11 16:50 ` Michał Górny
2017-01-11 17:04 ` Alec Warner
2017-01-11 18:04 ` Michał Górny
2017-01-11 17:28 ` William L. Thomson Jr.
2017-01-11 18:55 ` Michał Górny
2017-01-11 19:17 ` Raymond Jennings
2017-01-11 21:13 ` William L. Thomson Jr.
2017-01-11 16:06 ` Matthew Thode
2017-01-11 16:58 ` Michał Górny
2017-01-15 15:55 ` Roy Bamford
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.01844b6216.1630487.UI17VbWlKS@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