The Success of Open Source

JoshuaDFranklin writes "When confronted with the reality of Open Source, academics often ask what processes allow it to happen. In his new book The Success of Open Source, Berkeley professor Steven Weber answers that question. He presents a clear, logical picture of how Open Source development works in a variety of projects, and comes to the intriguing conclusion that the process may be generalizable to other areas of production. The results, he argues, would 'make the consequences of the first-generation Internet seem quaint.'" Read on for the rest of Franklin's review. The Success of Open Source author Steven Weber pages 320 pages, 5 line illustrations publisher Harvard University Press rating 9 reviewer Joshua Daniel Franklin ISBN 0674012925 summary Weber argues that the success of Open Source is due to a production process than may be generalizable to other arenas.

Weber is an academic and makes no apologies for it. He is not presenting an exciting new business plan, advocating a particular method of software development, or calling hackers to revolution. He is simply describing his findings after extensive research of the Open Source development process and drawing conclusions from them. As such, this book may not appeal to everyone in the Open Source community. However, Weber's ideas are timely and informative for anyone who wants to explain or advocate Open Source. He likens his work to The Machine that Changed the World, the story of Toyota's production method (224):

That book made two simple and profound points: The Toyota "system" was not a car, and it was not uniquely Japanese. The parallels are obvious. Open source is not a piece of software, and it is not unique to a group of hackers.

The first part of The Success of Open Source is a historical case study that examines the origins and social development of the Open Source community. It begins with Unix and hacker culture. For those who have read Steven Levy's Hackers: Heroes of the Computer Revolution and Peter Salus' A Quarter Century of UNIX, there is little new material here, but Weber offers a new and interesting perspective on the events. For example, he offers the insight that "hacker culture" existed before widespread network connectivity, drawing into question whether cheap bandwidth is really essential.

From there, he covers the development of the BSDs, Apache, and Linux, focusing again on social structures. He describes diverse events such as the messy expulsion of Theo de Raadt from the NetBSD core, the creation of Apache by an informal group of interested developers, and the establishment of Alan Cox as de facto Linux networking lieutenant. Weber draws from an impressive array of firsthand accounts, including mailing lists, websites, conference speeches, and personal interviews.

I get some interesting trivia out of this, such as Larry McVoy's original Unix is dying troll (98). Unfortunately, since Weber's narrative is mainly topical, it is occasionally redundant in telling one story from multiple social angles. Other claims are close to flamebait, such as suggesting that Richard Stallman is an example of a "failed leader." (168)

For the second half of the book, Weber moves on to Explaining Open Source in the terms of his discipline, political economy. He sees two broad categories of principles to the Open Source process: Microfoundations, including individual motivations and the economic logic of the collective good; and Macro-Organization, solving the problems of coordination and complexity. (133) While I doubt each reader will catch every academic nuance in these chapters, Weber is thankfully sparing in his use of specialized vocabulary and writes his overall argument in clear, easy-to-follow logic.

This section also contains the most insightful observations in The Success of Open Source. While there are too many to list here, one is the concept of Open Source Software as antirival. As more copies are made and put into use, value increases as a result of a larger market and the small percentage of users that contribute bug reports and possibly patches. This turns the traditional "free rider" problem into an advantage.

Though Weber does not mention this in the text, one can see part of this principle in proprietary vendors' providing free downloads or turning their backs on rampant piracy. It also does not take a great leap of logic to see application of the antirival model to other fields such as music or academic research.

As is customary in social science literature, Weber uses his conclusion to both recap his argument and to raise questions for future direction of research. What is the best organization method for property distribution, as opposed to the current methods based on exclusion? How can the Open Source production process be used effectively to improve prospects for the developing world? What is the best way for closed, hierarchical systems to interact with open, network-based ones? While some of the issues involved are offtopic for this book, hopefully future work will examine these questions in depth.

Though Open Source has been mentioned in many recent works, The Success of Open Source is the first academic book that focuses on the Open Source community as its object of study. It gives a readable, thought-provoking, and occasionally funny account of what Open Source is and means, making it an extremely valuable resource for those who want to engage and discuss these issues on an intellectual level. As Weber states, his positive, constructive outlook "may not be fully satisfying, but it's not a bad place to start." (272)

Joshua Daniel Franklin is a graduate student at the University of Washington's Information School. This review may be redistributed under the Creative Commons Attribution License. You can read the table of contents, preface, and an excerpt of the first chapter of The Success of Open Source at the Harvard University Press website. The reviewer's website has an list of errata. You can purchase the The Success of Open Source from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, carefully read the book review guidelines, then visit the submission page.

Comments

Steven Weber?

[Anonymous Coward]

I wondered what he was doing after the untimely demise of "Wings" (or "Flying Cheers" as some called it.

*BSD product support specialist. Man !

[Anonymous Coward]

Speaking of *BSD, I once had to make a technical support call to them. Here's the guy they have answering the phone these days. He told me he had to go into the vault to find the answer to my question. He put me on hold, and then the line went dead.

Excellent use of /. mods.

[Chris Burke]

"...interesting perspective on the events."
"...Larry McVoy's original Unix is dying troll"
"...it is occasionally redundant in telling one story from multiple social angles."
"This section also contains the most insightful observations..."
"Other claims are close to flamebait..."
"However, Weber's ideas are timely and informative..."
"and occasionally funny account of what Open Source is and means,"
"While some of the issues involved are offtopic for this book, ..."

Now the only question remaining after this review is whether any portions of the book may be over or underrated. Also, knowing if the author has a karma bonus would help in what is otherwise a tie of positive and negative mods.

Re:Come together, right now....

[Jane_Dozey]

Actually, no.
Many closed source developers don't work for large corporations. In fact, a good many work by themselves. They only want to pay the rent, and software is a good way for them to do so.
Also, just look at the amount of closed source "free-ware" that you can download. There's a huge amount, and none of the writers get paid for it. It's just not open source. Many of the motivations are they same (such as bragging rights and the possiblity of a jump start to a career).
You're looking at it with a very narrow view of the two models and don't seem to get it.
Lots of people write software, not all of it is closed source and not all of it is open source, but as long as it's quality software it shouldn't matter what license it falls under (unless, of course, the license impacts the end user to a higher degree (MS anyone?)). Use the best tool for the job, and if you insist on being so religious about your distinctions I suggest you start writing better tools that the closed source competition.