How many open source developers does it take to change a light bulb?
The answer is 17!
17 to argue about the license; 17 to argue about the brain-deadness of the light bulb architecture; 17 to argue about a new model that encompasses all models of illumination and makes it simple to replace candles, campfires, pilot lights, and skylights with the same easy-to-extend mechanism; 17 to speculate about the secretive industrial conspiracy that ensures that light bulbs will burn out frequently; 1 to finally change the light bulb, and 16 who decide that this solution is good enough for the time being.
From Peter Wayner, cited by Steven Weber's book, The Success of Open Source, p. 81.
17 to argue about the license; 17 to argue about the brain-deadness of the light bulb architecture; 17 to argue about a new model that encompasses all models of illumination and makes it simple to replace candles, campfires, pilot lights, and skylights with the same easy-to-extend mechanism; 17 to speculate about the secretive industrial conspiracy that ensures that light bulbs will burn out frequently; 1 to finally change the light bulb, and 16 who decide that this solution is good enough for the time being.
From Peter Wayner, cited by Steven Weber's book, The Success of Open Source, p. 81.
Labels: Geek Talk, Huh?, Open Source
posted by Ricardo at
10:26 AM
2 Comments:
Actually, it takes 1. One person to start the development which is the hardest part.
People who are arguing are not really part of the effort. They are just spinning the wheels. There are two ways to start an open source project. The passive one is to go out to the community and say:
"There is a light bulb that needs to be changed. Let's discuss it"
Chances are nothing is going to get done, and empty discussions will ensue. The open source model is much more responsive to the "do it yourself" model - ie:
"I'm changing this light bulb, someone please get me a ladder - if not, I'm just gonna use this chair"
People can discuss the validity of methodology, or rag on the code but as long as they don't contribute actual concrete code or content they are nothing more than cheerleaders on the sidelines. :)
Luke, if you are starting a new open source project, chances are you will probably discuss your ideas first, more like "I think I have better method to change the light bulb, what do you think?"
If the community is active, discussion will follow until you get some confidence of what you're doing and start doing it.
If you simply start a project, you will have a great chance of being reinventing the wheel somehow.
And I don't think these people helping in the discussion are mere cheerleaders. They can be very helpful in designing, planning, choosing the right platform, etc. for your idea. Cheerleaders would be the marketing people promoting the software. :)
Post a Comment
Subscribe to Post Comments [Atom]
<< Home