From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project <gentoo-project@lists.gentoo.org>
Cc: bman@gentoo.org
Subject: Re: [gentoo-project] Council meeting Sunday 10/June/2018 18:00 UTC
Date: Sun, 10 Jun 2018 13:19:32 -0400 [thread overview]
Message-ID: <CAGfcS_kH1pgG7zz8zPTpr=c+x37xBYi5uH6YWCkGiwpvrYAF6A@mail.gmail.com> (raw)
In-Reply-To: <2619723.dyicR4dehs@pinacolada>
On Sun, Jun 10, 2018 at 12:34 PM Andreas K. Huettel
<dilfridge@gentoo.org> wrote:
>
> I'm more worried that at the moment we're all checks and balances (or more
> precisely, unclear areas of responsibility and unclear procedures), so that in
> the end nothing gets done.
>
++
This whole situation is in part the result of having two
decision-making bodies with different constituencies, and perhaps even
slightly different missions. Adding yet another decision-making body
(literally a single body in this case) with yet another constituency
and also somewhat independent is going to make the problem worse, not
better.
Checks and balances makes sense for governments, because a government
can literally raid your house, seize your property, or lock you in
prison. They also have endless funding available to pay as many
levels of bureaucracy you might want to employ, and an entire army of
people and businesses looking to profit from the checks and balances
which help "make it work."
You almost never see this kind of arrangement in any kind of private
organization, whether for-profit or non-profit. You just have one
ultimate decision-making body, and anything else serves at their
convenience. It works because of competition - if your
employer/vendor/whatever does something you don't like, you can just
freely choose to leave and work for another. IMO this is part of why
Gentoo is struggling here - other distros are less niche and can
afford to fork when they disagree over issues.
IMO one of the bigger challenges will be working with the umbrella
group to make it clear who gets to appoint the liaison and so on.
They probably could make suggestions in this area.
--
Rich
next prev parent reply other threads:[~2018-06-10 17:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-08 17:44 [gentoo-project] Council meeting Sunday 10/June/2018 18:00 UTC Andreas K. Huettel
2018-06-08 17:57 ` Michał Górny
2018-06-08 18:05 ` Andreas K. Huettel
2018-06-08 18:02 ` Andreas K. Huettel
2018-06-10 15:24 ` Aaron Bauman
2018-06-10 16:34 ` Andreas K. Huettel
2018-06-10 16:43 ` Andreas K. Huettel
2018-06-10 16:52 ` Aaron Bauman
2018-06-10 17:19 ` Rich Freeman [this message]
2018-06-10 17:25 ` Andreas K. Huettel
2018-06-10 19:51 ` [gentoo-project] Re: SPI as an alternate foundation Matthew Thode
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='CAGfcS_kH1pgG7zz8zPTpr=c+x37xBYi5uH6YWCkGiwpvrYAF6A@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=bman@gentoo.org \
--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