From proprietary to open source—Growing an open source ecosystem

In today's business and software arena, Free/Libre/Open Source Software has emerged as a promising platform for software ecosystems. Following this trend, more and more companies are releasing their proprietary software as open source, forming a software ecosystem of related development projects complemented with a social ecosystem of community members. Since the trend is relatively recent, there are few guidelines on how to create and maintain a sustainable open source ecosystem for a proprietary software. This paper studies the problem of building open source communities for industrial software that was originally developed as closed source. Supporting processes, guidelines and best practices are discussed and illustrated through an industrial case study. The research is paving the road for new directions in growing a thriving open source ecosystem.     

Impact of user skills and network effects on the competition between open source and proprietary software

Despite the availability of source code, deploying open source software in an enterprise environment requires skills. Recent surveys and case studies show that the skills of IT staff in an organization are one of the key factors in open source software adoption decisions. Another important factor organizations consider when choosing a platform is network effects. This paper studies how users’ skills and network effects may influence the market where proprietary software competes with open source software. In the model, users make adoption decisions considering their own skills and the network effects of the software, and the proprietary software vendor prices its product strategically. It is found that in the presence of network effects, the proprietary software dominates the market when the open source software does not provide higher benefits to users. This implies that open source software, as a low-cost substitute to proprietary software, may not survive in a market exhibiting network effects. To gain market share, open source software has to outperform proprietary software by a large margin, which can be achieved when a significant portion of users are highly skilled and thus can customize the open source software to better satisfy their needs.     

A framework for creating hybrid-open source software communities

Abstract The open source software (OSS) model is a fundamentally new and revolutionary way to develop software. The success of the OSS model is also setting the stage for a structural change in the software industry; it is beginning to transform software industry from manufacturing to a service industry. Despite the success of the OSS model, for‐profit organizations are having difficulty building a business model around the open source paradigm. Whereas there are some isolated empirical studies, little rigorous research has been done on how traditional organizations can implement and benefit from OSS practices. This research explores how organizations can foster an environment similar to OSS to manage their software development efforts to reap its numerous advantages. Drawing on organizational theory, we develop a framework that guides the creation and management of a hybrid‐OSS community within an organization. We discuss the implications of this framework and suggest areas for future research.     

Comparing the relative importance of evaluation criteria in proprietary and open‐source enterprise application software selection – a conjoint study of ERP and Office systems

Until recently, organizations willing to acquire application systems have had no choice but to adopt proprietary software. With the advent of open‐source software (OSS), a new model for developing and distributing software has entered the stage. OSS has evolved from a generally horizontal infrastructure towards more highly visible applications in vertical domains, giving information systems (IS) managers more degrees of freedom in their selection of enterprise application software (EAS). Although a large body of research exists on the relative importance of evaluation criteria for proprietary EAS, the role of OSS in the EAS evaluation process has received little attention so far. To address this research gap, this study represents the first empirical investigation to compare the relative importance of evaluation criteria in proprietary and open‐source EAS selection. Through an online survey, we evaluated the responses of IS managers of 358 organizations to a conjoint study spawning 8592 trade‐off pair comparisons and 3580 purchase evaluations on proprietary and open‐source enterprise resource planning (ERP) and Office software packages. The results show that the relative importance of evaluation criteria significantly varies between proprietary and open‐source ERP systems. Implementation factors such as ease of implementation and support are much more crucial in the evaluation of open‐source than of proprietary ERP systems, which is generally due to IS managers' risk mitigation behaviour. Interestingly, there are no major differences in the ranking of evaluation criteria between proprietary and open‐source Office systems. We conclude our paper with a detailed discussion of our findings and their implications for researchers, companies, EAS vendors and open‐source communities.     

Open source movements as a model for organising

Open source software such as the operating system Linux has in a few years created much attention as an alternative way to develop and distribute software. Open source is to let anyone have access to the source code, so that they can modify it. Open source can be seen as a movement, where communities of highly skilled programmers collectively develop software, often of a quality that outperforms commercial proprietary software. These movements are based on virtual networking on the Internet and the web. They are loosely coupled communities kept together by strong common values related to hacker culture. Work seems to be totally distributed, delegated and loosely coupled. The highly skilled members contribute to the collective effort of free software development. In this paper the open source phenomenon is investigated from different perspectives. It is claimed that the open source movement is one key to the understanding of future forms of organizations, information work and business.     

The Changing Face of Open Source

The inability of vendors to make money using pure open source approaches caused many to change their business models. They also now view open source as just one efficient way to develop software, not as a social movement.     

The Third Design Space: A postcolonial perspective on corporate engagement with open source software communities

Corporations increasingly engage with open source software communities in the co‐creation of software. This collaboration between corporate professionals and open source software community members is strikingly different from the early days of software development where for‐profit firms attempted to dominate and control the industry while attempting to throttle the success of independent developers offering an alternative, open source option. While many metaphors like trading zones, common pool resources and ecosystems have helped understand the phenomenon, the metaphors do not portray what the industry was like before and after the transition. We adopt a postcolonial metaphor as an analytical lens to examine such collaboration based on qualitative data gathered over three years from executives, managers and developers within corporations that engage in open source software development. Drawing on these insights, we then theorize a “Third Design Space,” based on the concept of the third space proposed by Bhabha. This metaphor encourages the cultivation of a new design environment, creation of new design associations and circulation of shared design resources. Together these practices and behaviours make it possible to nurture innovative methods and new rituals for designing software with results and methods that represent a distinct departure from the competitive and proprietary past, even creating innovative artefacts that could not have been created without the Third Design Space.     

An Empirical Study on the Relationship Between Software Design Quality, Development Effort and Governance in Open Source Projects

The relationship among software design quality, development effort, and governance practices is a traditional research problem. However, the extent to which consolidated results on this relationship remain valid for open source (OS) projects is an open research problem. An emerging body of literature contrasts the view of open source as an alternative to proprietary software and explains that there exists a continuum between closed and open source projects. This paper hypothesizes that as projects approach the OS end of the continuum, governance becomes less formal. In turn a less formal governance is hypothesized to require a higher-quality code as a means to facilitate coordination among developers by making the structure of code explicit and facilitate quality by removing the pressure of deadlines from contributors. However, a less formal governance is also hypothesized to increase development effort due to a more cumbersome coordination overhead. The verification of research hypotheses is based on empirical data from a sample of 75 major OS projects. Empirical evidence supports our hypotheses and suggests that software quality, mainly measured as coupling and inheritance, does not increase development effort, but represents an important managerial variable to implement the more open governance approach that characterizes OS projects which, in turn, increases development effort.     

Network Externalities,Incumbent’s Competitive Advantage and the Degree of Openness of Software Start-Ups

This paper proposes a formal model that analyzes the degree of openness chosen by start-ups when entering the software industry. In line with the literature, we label as degree of openness the extent to which software start-ups mix open source (OS) and proprietary solutions in the portfolio of software products they offer. We relate the choice of the degree of openness to two key characteristics of the market segments in which software start-ups operate: the strength of the network externalities and the competitive advantage of the incumbent. Specifically, by modelling (price) competition between an incumbent and an entrant in two ways, i.e., the entrant is price-setter or price-taker, we derive the necessary condition(s) in terms of the strength of network externalities for observing the adoption of a business model that comprises the offering of both proprietary and OS solutions by the entrant (i.e., hybrid business model). Then, we highlight that, if a hybrid business model is the choice, the degree of openness chosen in equilibrium increases along with both the strength of the network externalities and the competitive advantage of the incumbent. This result holds indifferently whether the software start-up is modelled as a price-setter or a price-taker. An empirical test run on a sample of European start-ups in the software industry supports these theoretical predictions.     

Comparing practices for reuse in integration‐oriented software product lines and large open source software projects

This article compares the organization and practices for software reuse in integration‐oriented software product lines (SPLs) and open source software projects. The main observation is that both approaches are successful regarding large variability and reuse, but differ widely in their practices and organization. To capture practices in large open source projects, we describe an open compositional model, which reflects their more decentralized organization of software development. We capture key practices and organizational forms for this and validate these by comparing four case studies of this model. Two of these studies are based on published SPL case studies, for the other two we analyze the practices in two large and successful open source projects based on their published developer documentation. Our analysis highlights key differences between the practices in the two open source organizations and the more integrational practices used in the other two cases. Finally, we discuss which practices are successful in which environment and how the current practices can move towards more open, widely scoped and distributed software development. Copyright © 2010 John Wiley & Sons, Ltd.     

考虑排错过程引进故障的开源软件可靠性模型研究

近年来,开源软件在软件行业很受欢迎。但是,开源软件的可靠性却受到人们的广泛质疑。如何评估开源软件的可靠性是一个重要的问题。与传统的闭源软件相比,在建立开源软件可靠性模型时,必须考虑故障引入和故障检测与排错之间的延迟时间这两个因素。本文考虑了排错过程和不完美调试现象,提出了相应的开源软件可靠性模型。并且我们用两个开源软件故障数据集实来验证提出模型的拟合性能与预测性能。实验结果表明,提出的模型在开源软件可靠性评估中具有良好的拟合和预测性能。提出的模型可以用于开源软件在实际的开发过程中的可靠性评估。     

开源软件生产的网络化创新系统研究*

从系统工程、经济学和生态学的角度分析了开源软件社区的内在创新机理。首先,基于系统学理论定义了开源软件生产系统的概念;然后通过分析开源软件与私有软件生产系统的差异,归纳了开源生产行为的经济学特征;最后基于耗散结构理论和复杂科学理论提出了创新熵来度量开源社区的创新效能,并进一步揭示了开源社区网络创新的内在演化机理。     

Fault prediction considering threshold effects of object‐oriented metrics

Software product quality can be enhanced significantly if we have a good knowledge and understanding of the potential faults therein. This paper describes a study to build predictive models to identify parts of the software that have high probability of occurrence of fault. We have considered the effect of thresholds of object‐oriented metrics on fault proneness and built predictive models based on the threshold values of the metrics used. Prediction of fault prone classes in earlier phases of software development life cycle will help software developers in allocating the resources efficiently. In this paper, we have used a statistical model derived from logistic regression to calculate the threshold values of object oriented, Chidamber and Kemerer metrics. Thresholds help developers to alarm the classes that fall outside a specified risk level. In this way, using the threshold values, we can divide the classes into two levels of risk – low risk and high risk. We have shown threshold effects at various risk levels and validated the use of these thresholds on a public domain, proprietary dataset, KC1 obtained from NASA and two open source, Promise datasets, IVY and JEdit using various machine learning methods and data mining classifiers. Interproject validation has also been carried out on three different open source datasets, Ant and Tomcat and Sakura. This will provide practitioners and researchers with well formed theories and generalised results. The results concluded that the proposed threshold methodology works well for the projects of similar nature or having similar characteristics.     

Free/libre open source software implementation in schools: Evidence from the field and implications for the future

This empirical paper shows how free/libre open source software (FLOSS) contributes to mutual and collaborative learning in an educational environment. Unlike proprietary software, FLOSS allows extensive customisation of software to support the needs of local users better. This also allows users to participate more proactively in the development and implementation process of a FLOSS-based system. In this paper, we observes how implementing FLOSS in an Italian high school challenges the conventional relationship between end users themselves (e.g. teachers and students) and that between users and developers. The findings will shed some light on the social aspects of FLOSS-based computerization – including the role of FLOSS in social and organizational change in educational environments and the ways that the social organization of FLOSS are influenced by social forces and social practices.     

On the security of open source software

Abstract With the rising popularity of so‐called ‘open source’ software there has been increasing interest in both its various benefits and disadvantages. In particular, despite its prominent use in providing many aspects of the Internet's basic infrastructure, many still question the suitability of such software for the commerce‐oriented Internet of the future. This paper evaluates the suitability of open source software with respect to one of the key attributes that tomorrow's Internet will require, namely security. It seeks to present a variety of arguments that have been made, both for and against open source security and analyses in relation to empirical evidence of system security from a previous study. The results represent preliminary quantitative evidence concerning the security issues surrounding the use and development of open source software, in particular relative to traditional proprietary software.     

Open source vs closed

“There's a human difference between open source and proprietary software”, says Dr. Joseph Feller, Lecturer in Business Information Systems at University College Cork, and an expert in the subject of open source software. “Gina Neff and Prof. David Stark of Columbia University advocate the idea of the ‘permanently beta’ organization - customer-driven and highly flexible. In this situation users would be encouraged to contribute in some way when they discover bugs or shortcomings. To become ‘permanently beta’, they say organizations need to build responsiveness into their products, services and organizational structures. But, socially and psychologically, users of open source tools have more of a motivation to contribute their time to the software producer than users of proprietary tools, who are ‘paying for the privilege’, says Dr. Feller.     

On the challenges of open-sourcing proprietary software projects

The open source software (OSS) movement has become widely recognized as an effective way to deliver software. Even big software companies, well-known for being restrictive when it comes to publishing their source code artifacts, have recently adopted open source initiatives and released for general use the source code of some of their most notable products. We conducted an exploratory study on merits of the widespread belief that open-sourcing a proprietary software project will attract external developers, like casual contributors, and therefore improve software quality (e.g., “given enough eyeballs, all bugs are shallow”). By examining the pre- and post-migration software history of eight active, popular, non-trivial proprietary projects that became open source, we characterize the phenomenon and identify some challenges. Contrary to what many believe, we found that only a few projects experienced a growth in newcomers, contributions, and popularity; furthermore, this growth does not last long. The results from the study can be useful for helping software companies to better understand the hidden challenges of open-sourcing their software projects to attract external developers.     

A platform independent distributed IPC mechanism in support of programming heterogeneous distributed systems

Interprocess communication (IPC) is a well-known technique commonly used by programs running on homogeneous distributed systems. However, it cannot be used readily and efficiently by programs running on heterogeneous distributed systems. This is because it must be given a uniform interface either by a set of middleware or more efficiently properly ported to the kernel of all varieties of open source and closed source proprietary operating systems running on heterogeneous nodes of distributed systems. This is particularly problematic to achieve when the kernel code of closed source operating systems are inaccessible to third parties. We propose an alternative nonproprietary approach to enable the use of IPC in heterogeneous distributed systems by wrapping IPC calls from the kernel of closed source operating systems, and converting them into equivalent IPC calls that are efficiently implemented inside the kernel code of open source operating systems. To show the superiority of our approach, we developed a wrapper for converting MS-Windows IPC calls into equivalent Linux IPC calls and benched our approach on a hybrid computer cluster running both types of operating systems.     

Setting up shop: The business of open-source software

Hecker, a developer at Netscape, discusses the business of commercial open-source software, including why a company might adopt an open-source model, how open-source licensing works, what business models might be usable and how various objections relating to open source might be answered