@article{mockus02, title = {Two case studies of open source software development: Apache and Mozilla}, address = {New York, NY, USA}, author = {Audris Mockus and Roy T. Fielding and James Herbsleb}, journal = {ACM Trans. Softw. Eng. Methodol.}, number = 3, pages = {309--346}, publisher = {ACM}, volume = 11, year = 2002, url = {http://portal.acm.org/citation.cfm?id=567795}, issn = {1049-331X}, doi = {http://doi.acm.org/10.1145/567793.567795}, description = {Two case studies of open source software development}, abstract = {According to its proponents, open source style software development has the capacity to compete successfully, and perhaps in many cases displace, traditional commercial development methods. In order to begin investigating such claims, we examine data from two major open source projects, the Apache web server and the Mozilla browser. By using email archives of source code change history and problem reports we quantify aspects of developer participation, core team size, code ownership, productivity, defect density, and problem resolution intervals for these OSS projects. We develop several hypotheses by comparing the Apache project with several commercial projects. We then test and refine several of these hypotheses, based on an analysis of Mozilla data. We conclude with thoughts about the prospects for high-performance commercial/open source process hybrids.}, biburl = {http://www.bibsonomy.org/bibtex/26abef027845ec3a3f9043d3fe3c46aa6/neilernst}, keywords = {open-source empirical software} } @article{iannacci05, title = {Coordination Processes in Open Source Software Development: The Linux Case Study}, author = {Federico Iannacci}, journal = {Emergence: Complexity and Organization}, number = 2, pages = {21--31}, volume = 7, year = 2005, url = {http://personal.lse.ac.uk/iannacci/Publications&Seminars.htm}, abstract = {Although open source projects have been subject to extensive study, their coordination processes are still poorly understood. Drawing on organization theory, this paper sets out to remedy this imbalance by showing that large-scale open source projects exhibit three main coordination mechanisms, namely standardization, loose coupling and partisan mutual adjustment. Implications in terms of electronically-mediated communications and networked interdependencies are discussed in the final sections where a new light is cast on the concept of structuring as a by-product of localized adjustments.}, biburl = {http://www.bibsonomy.org/bibtex/2894cbdbca47e32a14790e88392af41a3/neilernst}, keywords = {software open-source linux} } @inproceedings{godfrey00, title = {Evolution in Open Source Software: A Case Study}, address = {San Jose, California}, author = {Michael W. Godfrey and Qiang Tu}, booktitle = {International Conference on Software Maintenance}, month = {October}, pages = {131--142}, publisher = {IEEE Computer Society}, year = 2000, url = {http://portal.acm.org/citation.cfm?id=853411}, doi = {10.1109/ICSM.2000.883030}, abstract = {Most studies of software evolution have been performed on systems developed within a single company using traditional management techniques. With the widespread availability of several large software systems that have been developed using an “open source” development approach, we now have a chance to examine these systems in detail, and see if their evolutionary narratives are significantly different from commercially developed systems. The paper summarizes our preliminary investigations into the evolution of the best known open source system: the Linux operating system kernel. Because Linux is large (over two million lines of code in the most recent version) and because its development model is not as tightly planned and managed as most industrial software processes, we had expected to find that Linux was growing more slowly as it got bigger and more complex. Instead, we have found that Linux has been growing at a super-linear rate for several years. The authors explore the evolution of the Linux kernel both at the system level and within the major subsystems, and they discuss why they think Linux continues to exhibit such strong growth}, biburl = {http://www.bibsonomy.org/bibtex/2290390167f71426da0a1de4998f4e57c/neilernst}, keywords = {evolution litmap open-source} } @inproceedings{scacchi05b, title = {Multi-Modal Modeling, Analysis and Validation of Open Source Software Requirements Processes}, address = {Genoa, Italy}, author = {Walt Scacchi and Chris Jensen and John Noll and Margaret Elliott}, booktitle = {International conference on Open Source Systems}, journal = {International Journal of Information Technology and Web Engineering (IJITWE)}, number = 3, pages = {49-63}, volume = 1, year = 2005, url = {http://oss2005.case.unibz.it/Papers/53.pdf}, abstract = {Understanding the context, structure, activities, and content of software development processes found in practice has been and remains a challenging problem. In the world of free/open source software development (F/OSSD), discovering and understanding what processes are used in particular projects is important in determining how they are similar to or different from those advocated by the software engineering community. Prior studies however have revealed that the requirements processes in F/OSSD projects are different in a number of ways. In this article, we describe how a variety of modeling perspectives and techniques are used to elicit, analyze, and validate software requirements processes found in F/OSSD projects, with examples drawn from studies of the NetBeans.org project.}, biburl = {http://www.bibsonomy.org/bibtex/26f315bcbe57a4aa92429c4647361c4a5/neilernst}, keywords = {open-source requirements} } @article{riehle07, title = {The Economic Motivation of Open Source Software: Stakeholder Perspectives}, author = {Dirk Riehle}, journal = {IEEE Computer}, number = 4, pages = {25-32}, volume = 40, year = 2007, url = {http://www.riehle.org/computer-science/research/2007/computer-2007-article.html}, date = {(April 2007)}, description = {Provides some insight into why companies may adopt open-source software.}, biburl = {http://www.bibsonomy.org/bibtex/28f8492f4944637550c420a193dca20a3/neilernst}, keywords = {economics open-source} } @article{wilson99oss, title = {Is the Open-Source Community Setting a Bad Example?}, author = {Greg Wilson}, journal = {IEEE Software}, number = 1, pages = {23--25}, publisher = {IEEE Press}, volume = 16, year = 1999, url = {http://ieeexplore.ieee.org/search/srchabstract.jsp?arnumber=744561&isnumber=16092&punumber=52&k2dockey=744561@ieeejrns&query=%28+%28+wilson+%3Cin%3Eau+%29+%3Cand%3E+%28+open-source%3Cin%3Eti+%29+%29&pos=0}, ee = {http://dlib.computer.org/so/books/so1999/pdf/s1023.pdf}, abstract = {My, how the world has changed. IBM is now backing Apache, Netscape has put an extraordinary amount of useful software out into the open, and vendors such as Metrowerks, Sybase and Oracle have released versions of their tools to run on a give-away operating system. It seems that the open-source movement-Linux, Perl, Apache, and their many cousins-has finally hit the big time. But my, how the world has stayed the same. EGGS (a derivative of the Free Software Foundation's GNU C++) is one of the few compilers around that has kept pace with the ANSI standard, but CVS, the open-source version control system, is 1O years behind equivalent commercial offerings. Linux is now more robust than some commercial varieties of Unix, but it's impossible to compare the reliability of open-source project management tools to that of Microsoft Project because the former don't exist}, biburl = {http://www.bibsonomy.org/bibtex/2365ba959d641f73926ff3046a38f16ba/neilernst}, keywords = {open-source software} } @article{aberdour07, title = {Achieving Quality in Open Source Software}, author = {Mark Aberdour}, journal = {IEEE Software}, month = {January/February}, number = 1, pages = {58-64}, volume = 24, year = 2007, url = {http://doi.ieeecomputersociety.org/10.1109/MS.2007.2}, abstract = {The open source software community has published a substantial body of research on OSS quality. Focusing on this peer-reviewed body of work lets us draw conclusions from empirical data rather than rely on the large volume of evangelical opinion that has historically dominated this field. This body of published research has become much more critical and objective in its efforts to understand OSS development, and a consensus has emerged on the key components of high-quality OSS delivery. This article reviews this body of research and draws out lessons learned, investigating how the approaches used to deliver high-quality OSS differ from, and can be incorporated into, closed-source software development. }, biburl = {http://www.bibsonomy.org/bibtex/2c35f7ef2ff4fe21a7d411360eb91b5ae/neilernst}, keywords = {software open-source} } @inproceedings{koch06, title = {Conceptual Modelling as a New Entry in the Bazaar: The Open Model Approach}, address = {Como, Italy}, author = {Stefan Koch and Stefan Strecker and Ulrich Frank}, booktitle = {International Conference on Open Source Systems}, editor = {Ernesto Damiani and Brian Fitzgerald and Walt Scacchi and Marco Scotto and Giancarlo Succi}, month = {June}, publisher = {Springer}, year = 2006, day = {8--10}, url = {http://dx.doi.org/10.1007/0-387-34226-5_2}, abstract = {The present contribution proposes to transfer the main principles of open source software development to a new context: conceptual modelling; an activity closely related to software development. The goal of the proposed “open model” approach is to collaboratively develop reference models for everyone to copy, use and refine in a public process. We briefly introduce conceptual modelling and reference models, discuss the cornerstones of an open modelling process, and propose a procedure for initiating, growing and sustaining an open model project. The paper concludes with a discussion of potential benefits and pitfalls.}, biburl = {http://www.bibsonomy.org/bibtex/2d4dc78d9972f9c00febfdd9fa3679c45/neilernst}, keywords = {modeling open-source conceptual} } @inproceedings{paech06, title = {Open source requirements engineering}, address = {Minneapolis, Minnesota}, author = {Barbara Paech and Bernd Reuschenbach}, booktitle = {International Conference on Requirements Engineering}, month = {September}, pages = {257--262}, publisher = {IEEE}, year = 2006, day = {10--14}, url = {http://www-swe.informatik.uni-heidelberg.de/research/publications/index.htm}, biburl = {http://www.bibsonomy.org/bibtex/21ee4ab2add2037542fd1b2fe224c887e/neilernst}, keywords = {requirements open-source empirical} } @techreport{maccormack05, title = {Exploring the Structure of Complex Software Designs: An Empirical Study of Open Source and Proprietary Code}, author = {Alan MacCormack and John Rusnak and Carliss Y. Baldwin}, institution = {Harvard Business School}, number = {05-016}, publisher = {Harvard Business School}, type = {Working Paper}, year = 2005, url = {http://freesoftware.mit.edu/papers/maccormackrusnakbaldwin2.pdf}, abstract = {This paper reports data from a study that seeks to characterize the differences in design structure between complex software products. In particular, we use Design Structure Matrices (DSMs) to map the dependencies between the elements of a design and define metrics that allow us to compare the structures of different designs. We first use these metrics to compare the architectures of two software products – the Linux operating system and the Mozilla web browser – that were developed via contrasting modes of organization: specifically, open source versus proprietary development. We then track the evolution of Mozilla, paying particular attention to a purposeful “re-design” effort that was undertaken with the intention of making the product more “modular.” We find significant differences in structure between Linux and the first version of Mozilla, suggesting that Linux had a more modular architecture. We also find that the redesign of Mozilla resulted in an architecture that was significantly more modular than that of its predecessor, and indeed, than that of Linux. Our results, while exploratory, are consistent with a view that different modes of organization are associated with designs that possess different structures. However, we also illustrate that purposeful managerial actions can have a large impact on structure. This latter result is important given recent moves to release proprietary software into the public domain. These moves are likely to fail unless the product possesses an architecture that facilitates participation. Our paper provides evidence that a tightly-coupled design can be adapted to meet this objective.}, biburl = {http://www.bibsonomy.org/bibtex/2dd1595573c25988f6df6a4875df255fc/neilernst}, keywords = {empirical open-source could-read complexity design} } @inproceedings{gurbani06, title = {A case study of a corporate open source development model.}, author = {Vijay K. Gurbani and Anita Garvert and James D. Herbsleb}, booktitle = {ICSE}, crossref = {DBLP:conf/icse/2006}, editor = {Leon J. Osterweil and H. Dieter Rombach and Mary Lou Soffa}, pages = {472-481}, publisher = {ACM}, year = 2006, url = {http://doi.acm.org/10.1145/1134352}, ee = {}, bibsource = {DBLP, http://dblp.uni-trier.de}, isbn = {1-59593-375-1}, biburl = {http://www.bibsonomy.org/bibtex/27a5b1d3e4ddb5904f74d6df749b85ed2/neilernst}, keywords = {open-source should-read} } @misc{moen99, title = {Fear of Forking}, author = {Rick Moen}, howpublished = {http://linuxmafia.com/faq/Licensing_and_Law/forking.html}, month = {November}, year = 1999, url = {http://linuxmafia.com/faq/Licensing_and_Law/forking.html}, id = {401470}, priority = {0}, description = {sdasda}, abstract = {WHY LINUX WON'T FORK And why being able to fork is still A Good Thing.[2]}, biburl = {http://www.bibsonomy.org/bibtex/2d4ad400d07a3f8bc900b3dfd4bd2d4de/neilernst}, keywords = {forking open-source} } @article{goode05, title = {Something for nothing: management rejection of open source software in Australia's top firms}, author = {Sigi Goode}, journal = {Information \& Management}, month = {July}, number = 5, pages = {669--681}, volume = 42, year = 2005, url = {http://dx.doi.org/10.1016/j.im.2004.01.011}, id = {205598}, priority = {0}, doi = {10.1016/j.im.2004.01.011}, abstract = {Organisations have traditionally relied on commercial software products to support their operations. However, rising software costs and recent corporate failures have brought the provision and value of commercial software into question. Recently, open source software, as a relatively new development in the IS field, has risen in popularity as a possible panacea for these ills. If firms value low acquisition cost, ostensibly plentiful support, and source code access, why have not more firms adopted open source software? The lack of published empirical research in the area means this issue has been inadequately addressed.This paper examines why firms do not adopt open source software. This study surveyed 500 of Australia's top firms to see why managers rejected open source software. The study found that managers rejected open source software because they could not see that it had any relevance to their operations, perceived a lack of reliable ongoing technical support of it and also appeared to see substantial learning costs or had adopted other software that they believed to be incompatible with open source software.}, biburl = {http://www.bibsonomy.org/bibtex/227c5bd1547cb52bcb04884bd57ee3a92/neilernst}, keywords = {open-source} } @article{wilkinson02, title = {BioMOBY: an open source biological web services proposal.}, address = {BioMOBY Project, Plant Biotechnology Institute, National Research Council Canada, Saskatoon, Saskatchewan. mwilkinson@gene.pbi.nrc.ca}, author = {M. D. Wilkinson and M. Links}, journal = {Brief Bioinform}, month = {December}, number = 4, pages = {331--341}, volume = 3, year = 2002, url = {http://www.ncbi.nlm.nih.gov/entrez/query.fcgi?cmd=Retrieve\&db=pubmed\&dopt=Abstract\&list_uids=12511062}, id = {682116}, issn = {1467-5463}, priority = {2}, comment = {Canadian eh!}, description = {Not previously uploaded}, abstract = {BioMOBY is an Open Source research project which aims to generate an architecture for the discovery and distribution of biological data through web services; data and services are decentralised, but the availability of these resources, and the instructions for interacting with them, are registered in a central location called MOBY Central. BioMOBY adds to the web services paradigm, as exemplified by Universal Data Discovery and Integration (UDDI), by having an object-driven registry query system with object and service ontologies. This allows users to traverse expansive and disparate data sets where each possible next step is presented based on the data object currently in-hand. Moreover, a path from the current data object to a desired final data object could be automatically discovered using the registry. Native BioMOBY objects are lightweight XML, and make up both the query and the response of a simple object access protocol (SOAP) transaction.}, biburl = {http://www.bibsonomy.org/bibtex/20f4215246e03fc01e0b36eb65f8ff7b3/neilernst}, keywords = {semantic open-source bioinformatics} } @book{weber04, title = {The Success of Open Source}, author = {Steven Weber}, howpublished = {Hardcover}, month = {April}, publisher = {Harvard University Press}, year = 2004, url = {http://www.amazon.co.uk/exec/obidos/ASIN/0674012925/citeulike-21}, id = {106560}, priority = {0}, isbn = {0674012925}, description = {Not previously uploaded}, abstract = {

Much of the innovative programming that powers the Internet, creates operating systems, and produces software is the result of "open source" code, that is, code that is freely distributed--as opposed to being kept secret--by those who write it. Leaving source code open has generated some of the most sophisticated developments in computer technology, including, most notably, Linux and Apache, which pose a significant challenge to Microsoft in the marketplace. As Steven Weber discusses, open source's success in a highly competitive industry has subverted many assumptions about how businesses are run, and how intellectual products are created and protected.

Traditionally, intellectual property law has allowed companies to control knowledge and has guarded the rights of the innovator, at the expense of industry-wide cooperation. In turn, engineers of new software code are richly rewarded; but, as Weber shows, in spite of the conventional wisdom that innovation is driven by the promise of individual and corporate wealth, ensuring the free distribution of code among computer programmers can empower a more effective process for building intellectual products. In the case of Open Source, independent programmers--sometimes hundreds or thousands of them--make unpaid contributions to software that develops organically, through trial and error.

Weber argues that the success of open source is not a freakish exception to economic principles. The open source community is guided by standards, rules, decisionmaking procedures, and sanctioning mechanisms. Weber explains the political and economic dynamics of this mysterious but important market development.

}, biburl = {http://www.bibsonomy.org/bibtex/209dffb63daba25c66f9bb6483aeb8ea8/neilernst}, keywords = {open-source} } @inproceedings{georgas05, title = {Raging incrementalism: harnessing change with open-source software}, address = {New York, NY, USA}, author = {John C. Georgas and Michael M. Gorlick and Richard N. Taylor}, booktitle = {ICSE Workshop on Open source software engineering}, month = {July}, number = 4, pages = {1--6}, publisher = {ACM Press}, volume = 30, year = 2005, url = {http://dx.doi.org/10.1145/1083258.1083263}, id = {668865}, issn = {0163-5948}, priority = {0}, doi = {10.1145/1083258.1083263}, description = {Not previously uploaded}, biburl = {http://www.bibsonomy.org/bibtex/2fef6dc120123f2a1c6b36fe57676b526/neilernst}, keywords = {open-source evolution requirements} } @article{fitzgerald04, title = {A critical look at open source}, author = {B. Fitzgerald}, journal = {Computer}, number = 7, pages = {92--94}, volume = 37, year = 2004, url = {http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=1310249}, id = {668795}, priority = {0}, description = {Not previously uploaded}, abstract = {In recent years, open source software - more properly, free and open source software - has emerged as one popular solution to the so-called "software crisis". Advocates regard F/OSS as an agile, practice-led initiative that addresses three key issues namely cost, time scale and quality. F/OSS products are usually freely available for public download. The collaborative, parallel efforts of globally distributed developers allow many F/OSS products to be developed much more quickly than conventional software. Many F/OSS offerings are recognized for their high standards of reliability, efficiency, and robustness; products such as GNU/Linux, Apache, and Bind have become "category killers" stifling the incentive to develop any competing products.}, biburl = {http://www.bibsonomy.org/bibtex/28fd8b3a5a840e3a33573667bbdd76b0a/neilernst}, keywords = {open-source forking} } @inproceedings{bonaccorsi05, title = {Intrinsic Motivations and Profit-oriented Firms in Open Source Software: Do firms practise what they preach?}, address = {Genova, Italy}, author = {Andrea Bonaccorsi and Cristina Rossi}, booktitle = {Intern. Conf. Open Source Software}, month = {July}, pages = {241--245}, year = 2005, url = {http://oss2005.case.unibz.it/Resources/Proceedings/OSS2005Proceedings.pdf}, id = {669133}, priority = {0}, description = {Not previously uploaded}, abstract = {This paper contributes to the literature by providing empirical evidence on the incentives of firms that engage in Open Source activities. Data collected by a survey on 146 Italian companies supplying OS solutions (Open Source firms) show that (surprisingly) intrinsic, communitybased incentives do play a role but are not, in general, put into practise. The discrepancy between attitudes and behaviours is investigated and firms adopting more consistent behaviours are singled out. Our results are in line with the literature on business models of firms entering the Open Source field.}, biburl = {http://www.bibsonomy.org/bibtex/22f3302938c488ce9bd2b2f7a827ad051/neilernst}, keywords = {requirements empirical open-source} } @inproceedings{bauer03c, title = {The contribution of free software to software evolution}, author = {A. Bauer and M. Pizka}, booktitle = {International Workshop on Principles of Software Evolution}, journal = {Software Evolution, 2003. Proceedings. Sixth International Workshop on Principles of}, pages = {170--179}, year = 2003, url = {http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=1231224}, id = {272331}, priority = {3}, description = {Not previously uploaded}, abstract = {It is remarkable to think that even without any interest in finding suitable methods and concepts that would allow complex software systems to evolve and remain manageable, the ever growing open source movement has silently managed to establish highly successful evolution techniques over the last two decades. These concepts represent best practices that could be applied equally to a number of today's most crucial problems concerning the evolution of complex commercial software systems. The authors state and explain some of these principles from the perspective of experienced open source developers, and give the rationale as to why the highly dynamic "free software development process", as a whole, is entangled with constantly growing code bases and changing project sizes, and how it deals with these successfully.}, biburl = {http://www.bibsonomy.org/bibtex/21b3c03076fffe444725ba8dc5f548a05/neilernst}, keywords = {evolution software open-source} } @inproceedings{adams05, title = {Using Open Source Tools to Support Collaboration Within CALIBRE}, address = {Genova, Italy}, author = {Paul Adams and David Nutter and Stephen Rank and Cornelia Boldyreff}, booktitle = {Int. Conf. Open Source Software}, month = {July}, pages = {61--65}, year = 2005, id = {669131}, priority = {0}, description = {Not previously uploaded}, abstract = {This paper describes the deployment of Plone, an Open-Source content management system, to support the activities of CALIBRE, an EU-funded coordination action integrating research into Libre software. The criteria by which Plone was selected are described, and the goodness of fit to these criteria is analysed. As a coordination action, CALIBRE involves 12 partners with different requirements and characteristics. The CALIBRE Working Environment (CWE) must therefore support a variety of users with different levels of technical expertise and expectations. Implementation of the support infrastructure for CALIBRE is ongoing, and has provided some interesting insights into the benefits of the use of libre software. Although Plone has not been explicitly developed as a collaboration infrastructure, with its wealth of plugins, it has proven highly adaptable for this purpose.}, biburl = {http://www.bibsonomy.org/bibtex/2b79173ab46b2784562a8c7e0514690d3/neilernst}, keywords = {open-source tool} }