public inbox for gentoo-osx@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Grobian" <grobian@gentoo.org>
To: gentoo-osx@lists.gentoo.org
Subject: Re: [gentoo-osx] Arch Testing Policy and Procedures
Date: Wed, 7 Sep 2005 09:21:46 +0200 (CEST)	[thread overview]
Message-ID: <54521.192.16.196.142.1126077706.squirrel@webmail.orakel.ods.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0509071440210.22106@loopy.telegraphics.com.au>

On Wed, September 7, 2005 06:57, Finn Thain wrote:
> Yes, in an ideal world, a lead would not have to exercise powers that
> no-one else in the team posessed. But in reality, one doesn't elect leads
> by drawing straws to pick a random unfortunate who will merely carry the
> burden of extra responsibilities. So why elect a lead?
>
> In my opinion, the most effective (and innovative) open source projects
> are run by an (inspired) dictator, and the least effective are run by
> committee or by a loose group of random volunteers, each one with a
> different "itch to scratch".

To stay close with our home, Apple wouldn't be whatever it is today, if it
hadn't such a (almost notorious) key figure called Steve Jobs.  Many,
many, many people have declared that it is *impossible* to work with him,
though the man has a vision, and makes that vision happen.  So far, he has
had luck and bad luck, where the luck outweights the last years.

I completely agree that there wouldn't be a GNU (which is not Linux) if
there wasn't an ultra arrogant Richard Stallman who even insults his own
"user base", if they don't think like he wants to.

Last FOSDEM, I met Gerv, the Bugzilla guy from Mozilla.  He's a real
*******, and I can say so, because he didn't hestitate to cut my question
and put it in the corner as "useless".  It simply didn't match his vision,
and so it was crap.  In the end, he *did* produce a fairly well bug
tracking system, but don't you dare to suggest something he doesn't like,
or your bug will disappear or get REJECT/WONTFIX etc.  If you really want
to change something in that thing, your one and only resort is the 'fork'.
 And I assume you all know what 'forks' have happened in the past an what
it finally ends up with.

I think there are plenty of (open source) projects to be identified that
all got stuck after there was released some initial code (in the best
case).  Or just code that doesn't innovate and only gets bugfixed and in
the end get overruled by a fork or redo.  (See -dev on torsmo, which is
such case.)

-- 
gentoo-osx@gentoo.org mailing list



      reply	other threads:[~2005-09-07  7:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-04  2:29 [gentoo-osx] Arch Testing Policy and Procedures Lina Pezzella
2005-09-04 10:57 ` Grobian
2005-09-04 19:22   ` Lina Pezzella
2005-09-04 20:53     ` Grobian
2005-09-05  3:42     ` Kito
2005-09-05  6:28       ` Grobian
2005-09-06 17:35         ` Nathan
2005-09-06 19:13           ` Grobian
2005-09-07  4:39             ` Finn Thain
2005-09-07  7:27               ` Grobian
2005-09-07  4:57           ` Finn Thain
2005-09-07  7:21             ` Grobian [this message]

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=54521.192.16.196.142.1126077706.squirrel@webmail.orakel.ods.org \
    --to=grobian@gentoo.org \
    --cc=gentoo-osx@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