From: "Michał Górny" <mgorny@gentoo.org>
To: Matthew Thode <prometheanfire@gentoo.org>
Cc: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Merging Trustees and Council / Developers and Foundation - 1.0 reply
Date: Wed, 11 Jan 2017 17:58:28 +0100 [thread overview]
Message-ID: <20170111175828.5b798265.mgorny@gentoo.org> (raw)
In-Reply-To: <58b7d17f-0228-81b9-c90e-9bb1af815385@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2271 bytes --]
On Wed, 11 Jan 2017 10:06:24 -0600
Matthew Thode <prometheanfire@gentoo.org> wrote:
> On 01/11/2017 08:46 AM, Michał Górny wrote:
> > Hi, all.
> >
> > Since this is getting quite exhaustive, here's my point on the proposal
> > as it is hinted now, and a counter-proposal.
> >
> > TL;DR:
> >
> > 1. I do not mind encouraging more developers to join the Foundation, or
> > even making it opt-out. However, I do oppose discriminating developers
> > who decide not to join the Foundation.
> >
>
> How is it discriminating? As you said below, another option is to have
> the unified voting pool but vote for two bodies. However, in order to
> avoid repeating splitting the vote I think that opting out of voting for
> one should opt you out of voting for all.
That was just a general remark in case voting was tied to Foundation
membership.
> > 3. I don't think merging the Council and Trustees is a good idea.
> > The two projects have divergent goals and different qualities expected
> > from members.
>
> I mostly agree, but more in the way that Trustees should oversee the
> distro as a whole, but delegate technical matters to the Council, who
> are better equipped to deal with them. Non-technical matters would boil
> up to the Trustees.
That sounds like turning things upside down. Usually matters go from
down below to top. I see it like this:
dev [< project] < Council < Trustees
In which case it is only reasonable that if devs/projects can't handle
an issue by themselves they refer it to the Council. In this case,
the Council is a body elected by developers to handle disputes between
them.
I don't really see a reason to put Trustees in between that. I'd rather
keep them as final step overseeing the Council, i.e. things to go
Trustees if there is a problem with Council. However, to avoid
the 'two-headed beast' problem, I'd say that the Trustees should only
intervene if legally required to do so, i.e. if the Council is really
doing their job badly and put Gentoo at risk of legal issues.
As for the other issues, I think I'll continue arguing once I see
the updated proposal. Thanks for all the explanations.
--
Best regards,
Michał Górny
<http://dev.gentoo.org/~mgorny/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
next prev parent reply other threads:[~2017-01-11 16:58 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.
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 [this message]
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=20170111175828.5b798265.mgorny@gentoo.org \
--to=mgorny@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