Open Source Licensing in Mixed Markets, or Why Open Source Software Does Not Succeed

Open Questions in Open Source: Exploring Incentives, Licensing and Competition

In its first year, the minitrack on Open Source Software (OSS) Development will provide a forum for the presentation and discussion of a fascinating and increasingly important mode of software development. OSS is a broad term used to embrace software that is developed and released under some sort of “open source” license. There are thousands of OSS projects, spanning a range of applications, operating system (e.g, Linux, BSD), Internet infrastructure (e.g., the Apache Web Server, sendmail, bind), user applications (e.g., the GIMP, OpenOffice), programming languages (e.g., Perl, Python, gcc) and games (e.g., Paradise). A key feature of OSS development is the participation of a community of developers and active users primarily via the Internet. This mode of interaction creates new challenges to software development, as team members work in a distributed environment and often as volunteers rather than employees. The empirical literature on software engineering, programmers and the social and technical aspects of software development suggests that such teams would face insurmountable difficulties in developing code, yet in fact some of these teams have been remarkably successful. Researchers from a variety of disciplines have turned their attention to the phenomenon of OSS as an intriguing and successful form of Internetsupported work. Understanding how these teams work is important because a digital society entails an increased use of Internet-supported distributed teams for a wide range of knowledge work. This minitrack brings together nine papers addressing various aspects of the OSS phenomenon. The minitrack starts with the paper “The Mysteries of Open Source Software: Black and White and Red All Over” by Brian Fitzgerald and Par Agerfalk. This paper offers a general discussion of the OSS concept, noting a number of “contradictions, paradoxes and tensions throughout”. The session continues with two papers discussing community issues in OSS project teams in more detail. The first, “Collaboration, Leadership, Control, and Conflict Negotiation in the Netbeans.org Open Source Software Development Community” by Chris Jensen and Walt Scacchi, examines leadership and control sharing across organizations and individuals, in and between communities, using the Netbeans.org community as an example. The second paper, “Contrasting Community Building in Sponsored and Community Founded Open Source Projects” by Joel West and Siobhan O'Mahony, contrasts the lifecycles of two kinds of OSS projects, community-founded vs. spinouts from an organization, and discusses in particular the problems of building a community in the later case. The second session includes three papers that focus on the internal workings of OSS projects. The first, “Effective work practices for FLOSS development: A model and propositions” by Kevin Crowston, Hala Annabi, James Howison and Chengetai Masango, develops a set of propositions about the performance of FLOSS teams based on Hackman’s model of effectiveness of work teams. The second paper, “Discussion of a Large-Scale Open Source Data Collection Methodology” by Michael Hahsler and Stefan Koch, presents a set of research areas that could be studied by collecting data on a large number of open source software projects from a single project repository. The final paper in the session, “A Preliminary Analysis of the Influences of Licensing and Organizational Sponsorship on Success in Open Source Projects” by Katherine J. Stewart, Anthony P. Ammeter and Likoebe M. Maruping, develops a model of the impact of licensing restrictiveness and organizational sponsorship on the popularity and vitality of open source software (OSS) development projects and tests it using data from Freshmeat.net and OSS project home pages. The final session includes two papers that consider relations between projects. The first of these, “A Topological Analysis of the Open Source Software Development Community” by Jin Xu, Yongqin Gao, Scott Christley and Gregory Madey, uses social network data about SourceForge developers to examine the topology and evolution of the OSS development community. The second, “Shifting the Creative Effort: Knowledge Reuse in Open Source Software Development” by Stefan Haefliger and Sebastian Spaeth, examines the forms and extent of knowledge reuse from a sample of six open source software projects. The final paper in the minitrack, “Exploring Usability Discussions in Open Source Development” by Michael B. Twidale and David M. Nichols, examines bug reports from several projects to characterize how developers address and resolve issues concerning user interface and interaction design. These nine papers provide a cross-section of the current state of the research on Open Source Software development. We thank all authors who submitted papers and the reviewers for their contributions to the mini-track.

Open source software is becoming increasingly prominent, and the economic structure of open-source development is changing. In recent years, firms motivated by revenues from software services markets have become the primary contributors to open-source development. In this paper we study the role of services in open source software development and explore the choice between open source and proprietary software. Specifically, our economic model jointly analyzes the investment and pricing decisions of the originators of software and of subsequent open-source contributors. We find that if a contributor is efficient in software development, the originator should adopt an open-source strategy, allowing the contributor to offer higher total quality and capture the higher end of the market while the originator focuses on providing software services to lower end consumers. Conversely, if the contributor is not efficient in development, the originator should adopt a proprietary software development strategy, gaining revenue from software sales and squeezing the contributor out of the services market. In certain cases an increase in originator development efficiency can result in increased contributor profits. Finally, we find that, somewhat counterintuitively, an increase in contributor development efficiency can reduce overall social welfare.

Open Source Software Development: Structural Tension in the American Experiment

Open Source and Proprietary Software: The Search for a Profitable Middle-Ground

Full Papers.- A Framework for Evaluating Managerial Styles in Open Source Projects.- Forging A Community - Not: Experiences On Establishing An Open Source Project.- Mapping Linux Security Targets to Existing Test Suites.- Overview on Trust in Large FLOSS Communities.- PMLite: An Open Source Solution for Process Monitoring.- Requirements Acquisition in Open Source Development: Firefox 2.0.- Analysis of Coordination Between Developers and Users in the Apache Community.- Lost and Gained in Translation: Adoption of Open Source Software Development at Hewlett-Packard.- Mining for Practices in Community Collections: Finds From Simple Wikipedia.- Open to Grok. How do Hackers' Practices Produce Hackers?.- Social Dynamics of FLOSS Team Communication Across Channels.- Towards a Global Research Infrastructure for Multidisciplinary Study of Free/Open Source Software Development.- Update Propagation Practices in Highly Reusable Open Source Components.- Using Social Network Analysis Techniques to Study Collaboration between a FLOSS Community and a Company.- Empirical Analysis of the Bug Fixing Process in Open Source Projects.- The Total Growth of Open Source.- Adoption of Open Source in the Software Industry.- Migration Discourse Structures: Escaping Microsoft's Desktop Path.- The SQO-OSS Quality Model: Measurement Based Open Source Software Evaluation.- Short Papers.- An Open Integrated Environment for Transparent Fuzzy Agents Design.- Archetypal Internet-Scale Source Code Searching.- Channeling Firefox Developers: Mom and Dad Aren't Happy Yet.- Continuous Integration in Open Source Software Development.- Extracting Generally Applicable Patterns from Object-Oriented Programs for the Purpose of Test Case Creation.- Social Networking Technologies for Free-Open Source E-Learning Systems.- The Networked Forge: New Environments for Libre Software Development.- To What Extent Does It Pay to Approach Open Source Software for a Big Telco Player?.- A Framework to Abstract The Design Practices of e-Learning System Projects.- Assessing Innovation in the Software Sector: Proprietary vs. FOSS Production Mode. Preliminary Evidence from the Italian Case.- Detecting Agility of Open Source Projects Through Developer Engagement.- Facilitating Social Network Studies of FLOSS using the OSSNetwork Environment.- Reflection on Knowledge Sharing in F/OSS Projects.- Usability in Company Open Source Software Context - Initial Findings from an Empirical Case Study.- Willingness to Cooperate Within the Open Source Software Domain.- Open Source Project Categorization Based on Growth Rate Analysis and Portfolio Planning Methods.- Applying Open Source Development Practices Inside a Company.- Towards The Evaluation of OSS Trustworthiness: Lessons Learned From The Observation of Relevant OSS Projects.- Open Source Reference Systems for Biometric Verification of Identity.- eResearch Workflows for Studying Free and Open Source Software Development.- Panels.- Panel: Opportunities and Risks for Open Source Software in Industry.- Posters and Demonstrations.- Open Source Environments for Collaborative Experiments in e-Science.

This chapter evaluates the hypothesis that open source software can potentially help promote technological innovation. It analyzes the potential to open source software solve the tension between the need to provide firms and individuals with the incentive to innovate and the desirability of encouraging widespread use of cutting-edge technologies and examines the development and marketing of software. The analysis indicates that most firms extensively blend the development of open source and proprietary software, rather than specializing in one or the other and that they diversify between open source and proprietary software in other dimensions as well.

This paper investigates competition between open source and proprietary software. Open source software is divided into two types: free open source and commercial open source. Free open source software can be available from the not-for-profit community, and Commercial open source software is software product based on free open source software. The usability of both free and commercial open source software is assumed to be inferior to proprietary software. It finds that: (i) when commercial open source vendor faces competition from proprietary software and free open source software, it may still be able to obtain profits; (ii) commercial open source vendor's pricing (resp. share or profit) may still be much lower (resp. less) than that of proprietary vendor even if its software functionality is not inferior to proprietary software; (iii) commercial open source vendor's pricing and profit may not increase as its software usability increases; (iv) proprietary software's price decreases with the usability of commercial open source software. Index Terms—proprietary software, open source software, price competition, software features, software usability

Open Source Software (OSS) is software products available to the public, with its source code to study, change, and improves its design. Open Source Software Development (OSSD) is the process by which open source software is developed within the confines of software engineering life-cycle methods. However when open source used for commercial purpose, then an open source license is required. Open source software is very often developed in a public and collaborative manner. The quality assurance principle under open source software development is an approach to improve software product quality against traditional methods and techniques. Despite the fact that the open source developments have seen remarkable successful in recent years, there are a number of product quality issues and challenges facing the open source development model. Many industries and business sectors are following or using OSSD, since they realize the benefits, but they do have some reservations concerning quality assurance in the form of program code quality, maintenance of the code and its quality, over the life-cycle of the product and third party usage. This paper reviews the literature of the process of the latest quality assurance, under open source software development methods and techniques. The result from this review is to show the process of quality assurance of open source software and that how it can affect the overall quality assurance principal.

Guest Editorial Open source software: investigating the software engineering, psychosocial and economic issues

The community-based open source software (OSS) development model has emerged as a viable alternative to firm-based traditional software development. The naturally evolving structure of collaborative relationships among software developers is a major distinction between the OSS development model and the traditional development model. Conventional statistical methods that focus on individual cases and their attributes cannot properly inform the management of the naturally evolving collaborative relationships in open source project. We emphasize social network analysis as a method especially suitable for management of open source development projects, because it focuses on relations among individuals rather than attributes of individual cases. We show how open source development can be represented as a collaboration network graph and how the network can be characterized by various network structure metrics. We present four metrics as a starting point -- size, centralization, density and clusterness, that are most useful in revealing collaborative relationships in OSS development process. We discuss how to generate collaboration network for OSS projects and how to calculate the metrics. We further describe how these metrics can assist in effective management of open source software development process. We conclude by presenting preliminary empirical evidence in support of the metrics.

In open source software (OSS) development domain (a largely volunteer driven, geographically distributed, web based form of software development), it is mainly the OSS developers who are responsible for overseeing and managing the develop-mental activities. Existing OSS literature, based on qualitative analysis of web-based artifacts (e.g. data on discussion forums, issue databases) of a few OSS projects, report that requirements generation in OSS development is largely informal and ad hoc. But there is lack of an empirical study involving the practitioners themselves i.e. the OSS developers. We conducted a web-based survey among OSS developers in order to gain insights in to how they actually practice requirements engineering activities and what are their perceptions about it. For 57 requirements engineering practices obtained from closed source software development (CSSD) literature, the respondents indicated whether they currently used those practices in their OSS projects and whether those practices were useful for OSS development. The analysis of survey responses revealed that OSS developers used requirements engineering practices (from CSSD) significantly less in their developmental activities than what they believed they should have, indicated through usefulness ratings. We also asked participating OSS developers to indicate their perceptions about the usage of five informal requirements generation activities re-ported in OSS literature (e.g. developers simply asserting the requirements instead of eliciting). Subsequent analysis revealed that OSS developers used informal requirements generation activities significantly more than requirements elicitation practices (from CSSD) in their developmental activities. We use the survey findings to discuss implications for practice and research.

Open Source, Anarchy, and the Utopian Impulse

Abstract. Open source software could emerge thanks to the development of the Internet, development tools, and computer literacy in general. The most attractive parameter of open source GIS software is a free license. The rapid pace of development, attracting developers from all over the world and high modularity stimulate the innovative nature of open source software. Here, the introduction of new technologies does not meet with opposition, but rather welcomes. These circumstances, as well as elucidation of the functional capabilities of such GIS, become very important in the search for means of providing the educational process with modern GIS software, which is traditionally an expensive proprietary software. Goal: Analysis of up-to-date GIS software protection and visual accessibility of the QGIS system in the first place with studying geoinformation systems.Quantum GIS (QGIS) is an open source software (GIS) geographic information system (GIS). Open software is one of the most interesting technological phenomena of the present, owing to its rapid growth in the development of the Internet, development tools and computer literacy in general. The key role in the creation, development and support of open source software is played, as a rule, by the community of developers forming around individual software products: commercial companies, groups of enthusiasts or research organizations. The term open source was proposed by Bruce Perens, one of the key leaders in the Open Source and Free Software movement, cofounder with Eric Raymind in 1998 of the Open Source Initiative (OSI), an open source software development organization that promotes and provides technical open source support. This open source term is used by OSI to determine whether a software license complies with open source standards. The main features of open source software as defined include free distribution, accessible source code, permission to modify this source code. At the same time, even successful open source software products require companies on the market ready to provide technical support and advice on issues related to the selected products. However, the number of companies providing support services for open source GIS software is still relatively small.

Methodology for Public Administrators for selecting between open source and proprietary software