Open source

Open source refers to a production process that relies on the free exchange of knowledge and information among producers as a basis for the joint development or improvement of a product. It emerged in the software sector and is now expanding to other industries. Specific IP rights are important for the open source movement, notably those committing users to grant-backs of their modifications into the common knowledge pool. IP policy can in that way support this type of innovation production.
What is open source?
Open source refers to a production process that relies on free exchanges of knowledge and information among producers as a basis for jointly developing and improving a product. 
 
An innovation can be the product of open source production if the following holds: 
 
  • Actors in the innovation process voluntarily disclose the knowledge (technical or not) they produce. This knowledge is “open” in that it is available to all without discrimination. 
  • Actors in the innovation process interact in a bazaar mode, meaning that the open disclosure of knowledge initiates a long lasting chain of exchanges and collaborations in order to enrich the open knowledge base (i.e. knowledge disclosure is continuous and is not the work of one single individual at a single point in time). 
 
The most prominent example is open source software, which is released with its source code, made available and developed following a loose organization (Raymond, 1999). This differs from the traditional in-house conception of software, based on hierarchy, secrecy and control.
 
Open source and open innovation (see Open innovation) differ in two central dimensions: 
 
  • The degree of openness. Open source is more “open” in that producers abandon their right to control the use of the technologies they develop and give up any possibility of controlling knowledge flows, in the sense that anybody can use the knowledge once it has been disclosed. In contrast, participants in open innovation projects usually rely on exclusive appropriation strategies. 
  • The degree of interactivity. Open source is more interactive, since actors involved in open source projects continuously exchange knowledge over a significantly longer period of time. In contrast, open innovation can be about spot knowledge transaction. Furthermore, open source often involves many different actors in a community and peer production, while open innovation usually relies on bilateral exchanges (in and out-licensing, merges, spin-in and out, etc.).
How does IP relate to open source?
Open source software often uses licenses to forbid the closing of the source code, and stipulates that everyone can use, modify, copy and even distribute the software on the unique condition that any change is protected by the same system. Licensing contracts for open source projects can contain grant-back provisions that require users to commit to licensing any improvement back into the open pool: Users of open source technologies are granted a license only if they agree to share any alteration they might make to the technology with its creators and to keep it in the “free” regime. This helps avoid the case of free riders taking advantage of the open knowledge space and then protecting their improvements via intellectual property rights, thus introducing closure into the knowledge space. Anticipating such free riding behaviors, fewer participants may be willing to contribute, thus slowing down the pace of open source development. Therefore, IP rights are at the heart of the open source mode of functioning.
 
How well do these licenses perform in supporting open source? Gambardella and Hall (2006) studied this issue and stressed two opposite effects. On the one hand, such licenses may trigger greater participation in the development of open source initiatives because some contributors, who may have contributed under a private patent regime, are now constrained by the terms of the license to contribute in an open way. But on the other hand, since the license restricts contributors’ rights, it may also deter some of them from contributing at all. In the case of software, it seems that the more restrictive the open license, the lower the probability of achieving a stable mature software product (Comino et al., 2007).
How important is open source in practice?
In software, the open source movement is usually associated with the creation of the free software foundation (FSF) in 1984. The purpose of this foundation was to promote the elaboration and development of free software, an important feature of which is the release of the source code. In order to ensure the freedom of software, the FSF developed the General Public License (GPL). Also, the FSF launched the GNU project, which aimed at developing an open source operating system that would provide an alternative to UNIX. This project ended successfully in 1991 with the development of LINUX. While the open source movement emerged in software in the 80s, it is now growing in many other sectors. While LINUX is the most famous success story of the open source movement, it is not the only one: other prominent examples of successful free software include Sendmail, which underlies the routing of e-mails over the Internet, Apache, a free server programme that runs more than half of web servers, Mozilla firefox (the web browser) and Android, which is now the most used operating system in smartphones.
 
The success of open source can also be seen beyond software. For instance, the encyclopedia Wikipedia is an open source product that has been (and is still) developed thanks to interactions among millions of contributors, who voluntarily and freely share their information. This case exemplifies the role of the Internet in facilitating open source. The Internet facilitates rapid interactions among participants and reduces the costs of information flows. Other open source initiatives are now flourishing in a wide range of domains: in beverages, with the example of open source colas, which are similar to Coca Cola and whose recipes are open source; in life science and health, with initiatives such as the tropical disease initiative; in scientific research, with the science common initiative; and in robotics, with the open source robotics initiative. Even before the Internet, the open source process of production and collective invention had been observed in very traditional sectors (Allen, 1983; Nuvolari, 2004).
References
  • Bonaccorsi A., Rossi C. (2003), “Why open source software can succeed”, Research Policy, 32, pp. 1243-1258.
  • Burk D.L. (2002), “Open source genomics”, Journal of Science and Technology Law, 8, p. 254.
  • Chesbrough, H. (2003), Open Innovation: The New Imperative for Creating and Profiting from Technology, Harvard Business School Press, Boston, MA.
  • Comino, S., Manenti, F., and Parisi, M.-L. (2007), “From planning to mature : On the success of open source projects”, Research Policy, 36, pp. 1575-1586.
  • Gambardella, A., and Hall, B.H. (2006), “Proprietary versus public domain licensing of software and research products,” Research Policy, 35, pp. 875-892.
  • Heron, M. J., Hanson, V. L., and Ricketts, I. (2013), “Open source and accessibility: Advantages and limitations”, Journal of Interaction Science, 1(1), pp. 1-10.
  • Lakhani, K. R., von Hippel, E. (2003), “How open source software works : ‘Free’ user-touser assistance”, Research Policy, 32, pp. 923-943.
  • Lerner, J. and Tirole, J. (2005), “The economics of technology sharing: Open source and beyond”, The Journal of Economic Perspectives, Vol. 19, No. 2, pp. 99-120.
  • Osterloh, M. and Rota, S. (2007), “Open source software development – just another case of collective invention?”, Research Policy, 36 (2): pp. 157-171.
  • Weber S. (2004), The Success of Open Source, Harvard University Press.
Image description here.
Printer-friendly versionPDF version