| 1 |
On Wed, September 7, 2005 06:57, Finn Thain wrote: |
| 2 |
> Yes, in an ideal world, a lead would not have to exercise powers that |
| 3 |
> no-one else in the team posessed. But in reality, one doesn't elect leads |
| 4 |
> by drawing straws to pick a random unfortunate who will merely carry the |
| 5 |
> burden of extra responsibilities. So why elect a lead? |
| 6 |
> |
| 7 |
> In my opinion, the most effective (and innovative) open source projects |
| 8 |
> are run by an (inspired) dictator, and the least effective are run by |
| 9 |
> committee or by a loose group of random volunteers, each one with a |
| 10 |
> different "itch to scratch". |
| 11 |
|
| 12 |
To stay close with our home, Apple wouldn't be whatever it is today, if it |
| 13 |
hadn't such a (almost notorious) key figure called Steve Jobs. Many, |
| 14 |
many, many people have declared that it is *impossible* to work with him, |
| 15 |
though the man has a vision, and makes that vision happen. So far, he has |
| 16 |
had luck and bad luck, where the luck outweights the last years. |
| 17 |
|
| 18 |
I completely agree that there wouldn't be a GNU (which is not Linux) if |
| 19 |
there wasn't an ultra arrogant Richard Stallman who even insults his own |
| 20 |
"user base", if they don't think like he wants to. |
| 21 |
|
| 22 |
Last FOSDEM, I met Gerv, the Bugzilla guy from Mozilla. He's a real |
| 23 |
*******, and I can say so, because he didn't hestitate to cut my question |
| 24 |
and put it in the corner as "useless". It simply didn't match his vision, |
| 25 |
and so it was crap. In the end, he *did* produce a fairly well bug |
| 26 |
tracking system, but don't you dare to suggest something he doesn't like, |
| 27 |
or your bug will disappear or get REJECT/WONTFIX etc. If you really want |
| 28 |
to change something in that thing, your one and only resort is the 'fork'. |
| 29 |
And I assume you all know what 'forks' have happened in the past an what |
| 30 |
it finally ends up with. |
| 31 |
|
| 32 |
I think there are plenty of (open source) projects to be identified that |
| 33 |
all got stuck after there was released some initial code (in the best |
| 34 |
case). Or just code that doesn't innovate and only gets bugfixed and in |
| 35 |
the end get overruled by a fork or redo. (See -dev on torsmo, which is |
| 36 |
such case.) |
| 37 |
|
| 38 |
-- |
| 39 |
gentoo-osx@g.o mailing list |
Archives