The governance of free/open source software projects: monolithic, multidimensional, or configurational?
This paper presents the results of a qualitative review and synthesis of the literature on open source governance, addressing four key questions: (1) How has open source software (OSS) governance been defined? (2) Has the phenomenon of OSS governance been conceptualized as a monolithic or multidimensional phenomenon? (3) What purposes is OSS governance hypothesized to serve? and (4) What are the dimensions of OSS governance, and how are these dimensions related to each other? The results of the review suggest a framework for future comparative and case study research on OSS governance, and they provide a basis for comparison with research on the governance of other distributed, community-based forms of content and creation. Copyright Springer Science+Business Media, LLC 2007
If you experience problems downloading a file, check if you have the proper application to view it first. In case of further problems read the IDEAS help page. Note that these files are not on the IDEAS site. Please be patient as the files may be large.
As the access to this document is restricted, you may want to look for a different version under "Related research" (further below) or search for a different version of it.
References listed on IDEAS
Please report citation or reference errors to , or , if you are the registered author of the cited work, log in to your RePEc Author Service profile, click on "citations" and make appropriate adjustments.:
- O'Mahony, Siobhan, 2003. "Guarding the commons: how community managed software projects protect their work," Research Policy, Elsevier, vol. 32(7), pages 1179-1198, July.
- Hertel, Guido & Niedner, Sven & Herrmann, Stefanie, 2003. "Motivation of software developers in Open Source projects: an Internet-based survey of contributors to the Linux kernel," Research Policy, Elsevier, vol. 32(7), pages 1159-1177, July.
- B. Demil & X. Lecocq, 2006. "Neither Market nor Hierarchy nor Network: The Emergence of Bazaar Governance," Post-Print hal-00185026, HAL.
- Dahlander, Linus & Magnusson, Mats G., 2005. "Relationships between open source software companies and communities: Observations from Nordic firms," Research Policy, Elsevier, vol. 34(4), pages 481-493, May.
- Carliss Y. Baldwin & Kim B. Clark, 2006. "The Architecture of Participation: Does Code Architecture Mitigate Free Riding in the Open Source Development Model?," Management Science, INFORMS, vol. 52(7), pages 1116-1127, July.
- Franke, Nikolaus & Hippel, Eric von, 2003. "Satisfying heterogeneous user needs via innovation toolkits: the case of Apache security software," Research Policy, Elsevier, vol. 32(7), pages 1199-1215, July.
- Egon Franck & Carola Jungwirth, 2002. "Reconciling investors and donators - The governance structure of open source," Working Papers 0008, University of Zurich, Institute for Strategy and Business Economics (ISU).
When requesting a correction, please mention this item's handle: RePEc:kap:jmgtgv:v:11:y:2007:i:2:p:151-163. See general information about how to correct material in RePEc.
For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: (Sonal Shukla)or (Rebekah McClure)
If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.
If references are entirely missing, you can add them using this form.
If the full references list an item that is present in RePEc, but the system did not link to it, you can help with this form.
If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your profile, as there may be some citations waiting for confirmation.
Please note that corrections may take a couple of weeks to filter through the various RePEc services.