Is the Growth of Open Source Sustainable?

by Lisa Hoover - Mar. 18, 2008Comments (3)

Fellow OStatic blogger Joe Brockmeier took an insightful look yesterday at why open source is growing at an amazing pace. He posits that "the open source model allows agile development by disperse groups of people that can build on the already massive foundation of open source libraries and applications." While I agree that open source projects are springing up in record numbers, I hope it also remains a community that can sustain itself and ultimately deliver what it promises.

For every successful open source project like Mozilla's Firefox or Red Hat's Fedora, there are hundreds that stumble along for a long time or die a slow death before ever getting off the ground. Since many -- if not most -- open source developers volunteer their time while also trying to manage work, family, and other obligations, it's no surprise that some projects can take seemingly forever to reach 1.0.

As the recent reorganization at The Chandler Project has demonstrated, throwing money at something isn't always a panacea. Despite a room full of paid developers and the rather deep pockets of willing backer Mitch Kapor, the application hasn't reached 1.0 yet after seven (seven?!) years.

There are differing accounts of what happened, who's to blame, and even where The Chandler Project is going from here, but that isn't really the point. The point is, while it's wonderful to see the recent flurry of activity in the open source community, is it something that can be sustained over time?

In his post, Brockmeier explored how Tasque, a simple task manager, went from a drawing board concept to released code in a matter of weeks. That's a commendable pace, to be sure. Currently, there are over 50 free text editors being worked on by developers across the globe. Ten years from now, some will be abandoned, some will move slowly but surely along, and still more will be see faster and more stable releases than all the rest. Which projects will end up like Chandler, and which -- like Tasque -- will rocket ahead practically overnight?

Well, that depends on several things intrinsic to each project. Some open source projects need money to stay on track, some need more of a developer's time. Some need less politics, while others need more politics. Each environment has its unique challenges and joys, but they all share one thing in common: a dedicated community.

On one hand, the beauty of open source is that it offers a level playing field where anyone with a dream and a concept can develop whatever they want. Unfortunately, that may also be one of the biggest drawbacks. The fact that anyone can jump into the open source pool, means a lot of people will. One thing I've heard from every developer I've ever talked to is that developing an application is a lot of very hard work. If open source continues to grow at its current "amazing pace," I hope the community has the endurance to run the marathon, not just the sprint race.



Dawn Giorgio uses OStatic to support Open Source, ask and answer questions and stay informed. What about you?



3 Comments
 

As K3b and Wine both go to show, a 1.0 release doesn't mean a lot in the FLOSS world. "1.0" is just a number, and doesn't mean a project is stable (or not), nor feature-complete (is any software?).


0 Votes

yes, but isn't this true for pretty much any enterprise or venture? It comes down to how well a product is deemed useful by a critical mass of users and developers. A lot of the productsi would posit, come from scratching an itch. If others have that itch, they will consider helping, or developing their own offering. Given that most projects do not envision being zimbra or chandler, the core keeps working on it until they move on to bigger and better hints and if others have not found use, the product languishes.


Open Source also goes with the grain of "don't compain about the dark. Light a candle". I also agree with the previous poster that versions are not really very symbolic and while a 1.0 is a big indication of developer confidence, it should not be the only measure. Several Google products are forever in beta.


0 Votes

"Several Google products are forever in beta."


Heh, so true! I didn't mean to imply that reaching 1.0 should be the yardstick by which we measure a project's potential for success or failure. I meant it more in the metaphorical sense. :-)


0 Votes
Share Your Comments

If you are a member, to have your comment attributed to you. If you are not yet a member, Join OStatic and help the Open Source community by sharing your thoughts, answering user questions and providing reviews and alternatives for projects.