Success of Open Source by Steven Weber: A book review


Using Linux as its primary example, The Success of Open Source by Steven Weber details the history, process, motivations, and possible long-term effects of open source software (OSS). This scholarly yet easy-to-read, well-written, and provocative book is worth the time of anybody who wants to understand how open source software is effecting information technology. It describes how the process of open source software may effect business & economics, methods of governance, and concepts of intellectual property. It is also a great read for those of us librarians who desire to play a role in the building of "next generation" library catalogs and other library-related information systems.

My acquisition of the book was rather embarrassing, and at the same time typical. As the leader of an open source software project called MyLibrary, I asked some of my fellow hackers and open source software affectionatos for advice on how to promote MyLibrary and build a larger community around it. One of the suggestions was to read Weber's book. Like most people, I searched Google for the title, and Google returned it as the first hit where I was able to read the entire text online, if I desired. I didn't. The librarian in me then went to WorldCat where I learned the book was located down the street in an another academic library. I could borrow the book for free. All I had to do was visit the library and check it out. I didn't. Instead, I looked the book up on and found a "new" copy from an Associate. Twelve dollars and four days later my book arrived. Easy. Convenient. Cheap. Food for thought.

The book can be divided into four overarching topics: 1) the history of open source, 2) the process of open source software development and the motivations of people who participate in it, 3) business models and open source software's relationship to the idea of a "commons", and finally, 4) a summary as well as a look to the future describing how the process of open source software might effect other human endeavors.

History of OSS

The chapter covering the history of open source software traces its roots from the development of AT&T Unix through the Berkeley Software Distribution (BSD) to the present day Linux operating systems. Weaved throughout is the development of networking technologies, specifically the Internet. The history brings to light two very influential computing philosophies. The first is the "Unix Way", an outline of three engineering principles for making good software: 1) write programs that do one thing and do it well, 2) write programs that work well together, and 3) write programs that handle text streams because that is a universal interface. Software that adheres to these principles is typically considered more useful than software trying to be all things to all people. Such software is modular, portable, easy to create and maintain, and can be applied in any number of settings.

The second philosophy revolves around ideas of intellectual property. Suppose I spend time and creative energy writing a piece of software. Through this expenditure I have the right to sell the software to other people in order to gain compensation for my efforts. Software, like other goods, can be exchanged for other things of value, namely money. Moreover, if people copy my software and give it other others, then such a process is just like stealing from me since I am not being compensated for my efforts. This was the attitude of Bill Gates as he stated it in his "open letter to hobbyists" as they distributed his implementation of the BASIC programming language in order to run programs they had written against it. This perspective regarding software as something to be bought and sold ultimately lead to the creation of Microsoft. At the time of his writing of the "letter" computers were bought and sold. Software sort of just came along for the ride.

While it is important to note that I, the author of this review, am certainly an advocate for open source software, the book takes no sides one way or another. Instead, throughout the book, Steven Weber tows a middle ground by simply asking questions and then does his best to answer them as objectively as possible. The book neither advocates nor condemns open source software. It simply observes the environment and makes generalizations accordingly.

OSS as a process not a thing

I found the chapters describing what the open source software process is, how it works, and what motivates people who participate in it to be the most interesting. If there was one thing I learned from the book, then that thing would be open source software is more about a particular process and less about a thing. Consider two statements a priori: 1) software can be copied an infinite number of times and not denigrate the original version, and 2) globally networked computers allow the tiniest numbers of like-minded individuals to find each other easily. Given such an environment the open source software process flourishes, and that process is outlined here:

  1. Someone has a computing problem they want to solve -- an itch to scratch.
  2. The person builds on the good work of others and writes a computer program.
  3. The person "freely" shares their software with others under a some sort of license agreement.
  4. A community forms along with norms of behavior and guidelines (governance) for contributing back to the solution.
  5. The software grows and matures, hopefully.
  6. Go to Step #1 until the software is "done" or until someone else wants to take on the leadership role.

The resulting open source software application, the book points out, is not necessarily better (or worse) from "closed source" software. Instead, it is simply different. It is more easily modified. It is vetted through the eyes of end-users -- a set of self-described pragmatists wanting to scratch their own itch. Furthermore, since the process easily accommodates the philosophy of letting a thousand flowers bloom, the resulting software is not necessarily designed for the mass market; the software is not aimed at a lowest common denominator.

What motivates open source software participants? Weber shys away from the altruistic motives espoused in Eric Raymond's The Cathedral and the Bazaar. Instead, he sees the motivations stemming from a desire for artistry & craftsmanship, the desire to create better software, and recognition from peers ("ego-boosting"). Many of the people who participate in open source software seem to enjoy puzzle solving. Some of them like reading and writing beautiful code -- software as poetry. They are engineers looking to build better solutions to known problems, similar to building a better mouse trap. Like scholars and researchers in academia, peer-review is an important aspect of the work, and if you write something that is used (cited) by many people, then in the eyes of others your value is increased.

OSS and business

The sections and chapters regarding open source software and business are probably the most significant aspects of the book. They cover issues that are the least understood by the wider community including the definition of "free", the concept of property and the "commons", the differences between the BSD and GPL licenses, how these differences effect business opportunities, and business models in an environment where the primary thing to be exchanged for value is bound by rights of distribution as opposed to exclusion.

In our increasingly commercial society, the concept of "free" software is something most people find confusing. Weber compares and contrasts "free" from the point of view of the Free Software Foundation lead by Richard Stallman and the point of view of many dot-com companies such as Red Hat. In both cases the concept of "free" should be equated with the word "liberty" as opposed to "gratis". On the other hand, the FSF seems to have a bit of moral slant to their approach whereas the more recent approach puts an emphasis on practicality and the ability to easily improve software solutions.

The concept of property plays a big role in business models. How can you sell something that is "free"? How can you earn money on a thing that is a part of the community commons? Who owns this intellectual property? These questions can be answered, according to Weber, by interpreting the BSD and GNU (or General) Public License. In both cased the software is give away gratis. The differences lie in redistribution. Under the GPL license new software created with GPL licensed software needs to be re-distributed under the GPL or a less restrictive license. The BSD license does not have this stipulation; new software created from BSD licensed software does not have to be redistributed for "free". This is, in fact, what Apple Computer has done with Mac OSX. They started with BSD Unix, enhanced it, and are redistributed it for a fee. Given such an environment, Weber outlines a number of possible business models: 1) support sellers, 2) loss leaders, 3) "sell it, free it", 4) accessorizing, 5) service enablers, and 6) branding. For each of these models Weber points to a number of examples.

The last two pages of the book summarize much of Weber's observations, and listing them here feels a bit like spoiling the ending of a mystery novel. On the other hand, if you read the book, then the summary makes more sense. The effective open source software process/project needs to take into account and support:

Weber also outlines the characteristics of effective agents (open source software participants). They:

OSS and libraries

Naturally, I read the book through my rose colored glasses of librarianship. After reading it and combining it with more recent personal experiences, I am now less of a "believer" in open source software. I am going away with a more realistic perspective on the definition of open source, its process, and what motivates participants in it. This does not in any way diminish my belief that the open source software process can not benefit the library community and therefore library users.

Throughout the book I kept comparing the kernel of the Linux operating system to the integrated library system (ILS) of libraries. In both cases they, the kernel and the ILS, provide fundamental interface functions between one entity and another. In the case of an operating system kernel, the interface is between hardware and people. In the case of an ILS the interface is between a library and patrons.

Some open source projects already exist, the extent they meet with continued success and wider adoption, I predict will be measured by the extent that they can accomplish the following things. First, an easy-to-understand vision statement needs to be outlined by one or more people who posses leadership qualities. Second, those leaders need to amass the resources required to make their vision a reality. Third, they need to put their vision into practice allowing as many people to participate as possible. Fourth, start small and work up. Encourage the building and re-use of existing core applications. Databases. Indexers. Editors. Server platforms. Make sure the applications are modular and standards-compliant. Practice the Unix Way. Make it work first, then improve things. Don't even attempt to create the perfect system the first time. The process won't be quick. The process won't be easy. The process won't be "free". On the other hand, the process will empower and enable the profession. It will give it increased choice and opportunity. Weber's book, the Success of Open Source, can be used as a set of guidelines -- a description of a framework -- for building software solutions for the computing problems facing libraries.

Creator: Eric Lease Morgan <>
Source: The is a pre-edited version of an article with the same title appearing in the first issue of Code4Lib Journal at
Date created: 2007-10-31
Date updated: 2008-04-11
Subject(s): book review; articles; open source software; librarianship;