Unusual Open Source
Dumitru Erhan writes "The Economist has a special report on open-source. It analyzes the way open-source projects succeed and finds that a rigid, business-like organizational structure is of vital importance to the quality of the final product. It cites Firefox, MySQL and (more recently) Wikipedia as examples of projects that do not simply allow anarchy to rein in, but which have 'real checks and balances, and real leadership taking place'. There is also a discussion of open-source methods being applied to non-software projects." From the article: "Constant self-policing is required to ensure its quality. This lesson was brought home to Wikipedia last December, after a former American newspaper editor lambasted it for an entry about himself that had been written by a prankster. His denunciations spoke for many, who question how something built by the wisdom of crowds can become anything other than mob rule."
Isn't that how people get elected?
Oh, I see what he means now.
Wikipedia is what it is today because of the large amount of people who care about it enough to fix vandalism. Not necessarily because of a centralized leadership.
Open source is successful because of the large number of people who have an interst in its success. Centralizing leadership might be helpful in some way, but I don't see it as the most important thing.
Many people still don't take the GNU project seriously. People often find it easier to keep their eyes shut than to have to change their beliefs in light of what they see.
I've shown people incredible stuff on my (Linux) PC, but often when they find out it doesn't run on Windows they continue to pretend it doesn't exist.
Good advertisement for your mag mates.
... pulled ... in that there is a need for them... Traditional software is ... pushed ... in that there's a need for profit.
You see, one thing economists (and many, many others) get wrong time and time again, is self organisation... They just don't get it for some reason. The "bazaar" encourages, promotes lots of projects, lots of errors, lots of iterations, lots of dead projects and we get emergent behaviour out of that environment. These are projects which are strong, robust and evolutionary in that they will fill all of the niches in which they are needed. These projects are
Deleted
So, if you define sucess as having a big reachable community, the sucessfull projects will have someone able to tell you the name of every developer. If you define sucess as being used by corporations, the sucessfull projects look like corporation projects.
Now, we could get the first page with some more truisms, or we could forget about generalising this idea of "sucess" to an area where there is simply no metric to be used.
Rethinking email
It's obvious that an entry created and commented on by many disinterested people is less biased than an entry created and commented on by few. Traditional encylopedias fall in the latter category, Wikipedia falls in the former. But people are not always disinterested, and that's where the problems lie. So the real problem is: are all the participants disinterested? With traditional encylopedias, the chances are that most writers are semi-disinterested observers, as they are ordered to write about subjects, they don't select them themselves. With Wikipedia, people self-select themselves, which means they cannot be disinterested, by definition. And that's the reason that some kind of community control is required for projects like this.
'real checks and balances, and real leadership taking place'
"Constant self-policing is required to ensure its quality.
Any task envisioning an end product could be said to require the characteristics mentioned above. What may be of more importance is that the venerable 'Economist'(although I believe its always been seen as left leaning) is making an effort to wrap its mind around Open Source and in doing so allowing its readers to follow suit.
Over the last year plus I've noticed more articles that tend to view Open Source projects as akin to 'hardnosed' business methods. I think they represent the establishment coming to a positive consensus about Open Source methods and projects.
I noticed a turn in the way the general business community reported and interacted with Open Source from about the time IBM ran the ads picturing Linux as a small, blonde haired, blue eyed wonderkid.
The old boy network isn't about to let Open Source join the club but they're certainly ready to let it in the service entrance.
"Academicians are more likely to share each other's toothbrush than each other's nomenclature."
Cohen
Any Project whether it's open source or commercial needs this to succeed. Open source is more than a development model. It's a software licensing model. As a result it's also a software as service model. The main difference between commercial and open source is the openness of the code and tendency to the service side rather than shrinkwrapped.
If you see spelling or grammatical errors don't blame me. I tried to preview but IE here at work borked the CSS
That's because language and therefore definitions reflect usage. Dictionaries are hardly "irrelevant" just because they contain common definitions you have some anal disagreement with society over.
"Sufferin' succotash."
Sure, I love bsd as much as the next guy, but seriously - the bsds have more rigid professionalism? more emphasis on correctness over features? Given the amount of improvement in the linux kernel over the past 10 years, compared to that of the bsds, that seems a curious statement.
I guess by improvement in the Linux kernel, you mean broken 2.6 development or bleeding edge hacks that break things. Yes, the BSDs have a much more professional approach. They actually try to retain stability instead of hacking in the latest gee-whiz device driver or VM scheme that breaks things.
"Sufferin' succotash."