From: Geralt <usr.gentoo@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] app-admin/eselect needs YOUR help
Date: Mon, 8 Dec 2008 20:00:08 +0100 [thread overview]
Message-ID: <fbdd0e50812081100jc75c85di1ee406e0271d131c@mail.gmail.com> (raw)
In-Reply-To: <20081208174434.7a91f976@snowcone>
On Mon, Dec 8, 2008 at 6:44 PM, Ciaran McCreesh
<ciaran.mccreesh@googlemail.com> wrote:
> On Mon, 8 Dec 2008 08:37:42 -0800
> Donnie Berkholz <dberkholz@gentoo.org> wrote:
>> Open and public debate about the right way to do things does take
>> longer, and it's something you certainly participate in quite
>> frequently so I'm surprised to hear you badmouth it when it comes to
>> your own ideas.
>
> Open and public debate requires two or more well informed parties who
> are seeking to reach the best solution regardless of who proposed it,
> and a deciding body who are prepared to go for the best solution even
> if it isn't universally popular. This sometimes happens with Gentoo,
> but unfortunately all too often it's one of these instead:
>
> * A good proposal gets a few incorrect objections from people who
> don't understand it and aren't prepared to put in the effort to
> become well informed. The Council then uses these objections as an
> excuse to sit on the proposal and do nothing for months, because
> making a decision is harder than maintaining the status quo.
>
> * A good proposal gets a whole load of silly, trivial and nonsensical
> objections from sockpuppeting trolls who don't like the people who
> came up with the proposal (or sometimes from sockpuppeting trolls who
> suspect that the person who came up with the proposal once spoke to
> the cousin of a cleaner who once worked for the nephew of someone who
> said that the proposal looked sensible...). The Council do not
> dismiss these objections because they don't want to risk upsetting
> anyone.
>
> * A good proposal comes along. Its proof of concept implementation is
> done using a project that is considered by some to risk upsetting the
> status quo. A bunch of people who are involved in the proposal get
> fired.
>
> * A proposal gets implemented without the debate. It's either a lousy
> proposal that we're then stuck with, or a decent proposal that has a
> few flaws that could have been addressed.
>
> This is the kind of 'open and public debate' one would expect from a
> failing government trying to cling to power for a few more years or a
> middle-management-heavy corporation on its last legs. It's fine if you
> want to repaint the bikeshed a slightly nicer shade of magenta, but
> it's a real nuisance for anything serious.
>
> None of the people involved in the decision to fork eselect rather than
> work on it for Gentoo are anything except entirely in favour of open and
> public debate. It's just that they don't exactly have a positive
> experience of that happening within Gentoo...
>
> --
> Ciaran McCreesh
>
Reminds me so much of
http://tieguy.org/blog/2008/12/05/the-linux-desktops-change-problem/
next prev parent reply other threads:[~2008-12-08 19:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 20:08 [gentoo-dev] app-admin/eselect needs YOUR help Doug Goldstein
2008-12-06 15:44 ` Ciaran McCreesh
2008-12-07 7:44 ` Donnie Berkholz
2008-12-07 14:46 ` Ciaran McCreesh
2008-12-08 16:37 ` Donnie Berkholz
2008-12-08 17:44 ` Ciaran McCreesh
2008-12-08 18:19 ` Santiago M. Mola
2008-12-08 18:28 ` nikos roussos
2008-12-08 18:33 ` Ciaran McCreesh
2008-12-08 19:00 ` Geralt [this message]
2008-12-08 17:49 ` Wulf C. Krueger
2008-12-08 20:56 ` Alec Warner
2008-12-08 21:30 ` Ferris McCormick
2008-12-09 13:54 ` [gentoo-dev] " Steve Long
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=fbdd0e50812081100jc75c85di1ee406e0271d131c@mail.gmail.com \
--to=usr.gentoo@googlemail.com \
--cc=gentoo-dev@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