Dependencies, Networks, and Priorities in an Open Source Project

Author(s):  
Juha Järvensivu

Dependencies between modern software projects are common. Jointly, such dependencies form a project network, where changes in one project cause changes to the others belonging to the same project network. This chapter discusses the issues of dependencies, distances, and priorities in open source project networks, from the standpoint of both technological and social networks. Thus, a multidisciplinary approach to the phenomenon of open source software (OSS) development is offered. There is a strong empirical focus maintained, since the aim of the chapter is to analyze OSS network characteristics through an in-depth, qualitative case study of one specifi c open source community: the Open Source Eclipse plug-in project Laika. In our analysis, we will introduce both internal and external networks associated with Laika, together with a discussion of how tightly they are intertwined. We will analyze both the internal and the external networks through the elements of mutuality, interdependence, distance, priorities, different power relations, and investments made in the relationships—elements chosen on the basis of analysis of the network studies literature.

Author(s):  
E.G. Coleman ◽  
Benjamin Hill

This chapter examines the way that participation in Free software projects increases commitments to information freedom among participants. With the Debian project as its core case study, it argues that in Free and Open Source software communities, ethics are reinforced through the sustained collaborative development of code and discussions and decisions around Free software licenses and project policy. In the final section, the chapter draws on the ethnographic analysis of ethical cultivation in Debian to describe a model of ethical volunteerism based on institutional independence, volunteer labor, and networks of trust that is applicable to a range of vocations.


Author(s):  
Donald Wynn Jr.

This study examines the concept of an ecosystem as originated in the field of ecology and applied to open source software projects. Additionally, a framework for assessing the three dimensions of ecosystem health is defined and explained using examples from a specific open source ecosystem. The conceptual framework is explained in the context of a case study for a sponsored open source ecosystem. The framework and case study highlight a number of characteristics and aspects of these ecosystems which can be evaluated by existing and potential members to gauge the health and sustainability of open source projects and the products and services they produce.


Author(s):  
Martin Michlmayr ◽  
Gregorio Robles ◽  
Jesus M. Gonzalez-Barahona

Most libre (free, open source) software projects rely on the work of volunteers. Therefore, attracting people who contribute their time and technical skills is of paramount importance, both in technical and economic terms. This reliance on volunteers leads to some fundamental management challenges: Volunteer contributions are inherently difficult to predict, plan, and manage, especially in the case of large projects. In this chapter we present an analysis of the evolution over time of the human resources in large libre software projects, using the Debian project, one of the largest and most complex libre software projects based mainly in voluntary work, as a case study. We have performed a quantitative investigation of data corresponding to roughly seven years, studying how volunteer involvement has affected the software released by the project, and the developer community itself.


2007 ◽  
Vol 6 (2) ◽  
Author(s):  
Alex Gaudeul

This paper traces the history of TEX, the open source typesetting program. TEX was an early and very successful open source project that imposed its standards in a particularly competitive environment and inspired many advances in the typesetting industry. Developed over three decades, TEX came into competition with a variety of open source and proprietary alternatives. I argue from this case study that open source developers derive direct and indirect network externalities from the use of their software by others and must therefore consider non-developers' needs to make their software more attractive to a broader audience and more competitive with proprietary alternatives.


Author(s):  
Graham Morrison

The majority of open source projects fail. This chapter presents one such project as a case study, written from the perspective of the sole developer. It charts the various stages of development, from initial motivation and enthusiasm through the later stages of apathy and decline. It deals with many of the problems encountered by a sole developer, and the various approaches undertaken to maintain development momentum. This chapter provides anecdotal evidence as opposed to statistical analysis, giving an individual’s perspective on the development life cycle of an open source project, illustrating real world barriers to development and the typical issues that can stall a project.


Author(s):  
Neophytos Demetriou

OpenACS is a high-level community framework designed for developing collaborative Internet sites. It started from a university project at MIT, got momentum from the ArsDigita Foundation, and split up into a commercial and an open source version. OpenACS has proven its durability and utility by surviving the death of its parent company (ArsDigita) to grow into a vibrant grassroots collection of independent consultants and small companies implementing diverse and complex Web solutions around the globe for NPOs, philanthropy, and profit. A heritage from this history is a still dominant position of contributors with commercial interests that, in its intensity, is above the norm found in open source projects. In this paper, OpenACS, with its community is presented as a case study documenting the forces between commercial interests, securing investments, and technical development in a large open source project with a large proportion of commercial involvement.


2016 ◽  
Vol 42 (3) ◽  
pp. 220-260 ◽  
Author(s):  
Rick Kazman ◽  
Dennis Goldenson ◽  
Ira Monarch ◽  
William Nichols ◽  
Giuseppe Valetto

2015 ◽  
Vol 4 (2) ◽  
pp. 18 ◽  
Author(s):  
Georg Von Krogh ◽  
Nina Geilinger

Valve is a very interesting case study! The company shares many features with open source software projects. In Valve, as in the open source world, the focus is on creating advanced technologies and letting developers self-select projects and tasks. Self-selection seems to work particularly well in an environment where technology development itself has a coordinating function. In software development, people have a strong bond of common knowledge based on design philosophies and approaches, language and terminology, and engineering tasks. In most cases, they also share a similar educational background and/or development experience that helps them implement creative ideas in physical machines and graphic environments. Developers rarely rely on detailed instructions from higher-level managers because they already have the implicit knowledge of what needs to be done. When inconsistent views about development come to the forefront, they are best reconciled where the knowledge resides: with the experts. Moreover, it appears that Valve has uncovered how developers’ self-selection of projects and tasks can be a powerful motivator to unleash their creativity.


Sign in / Sign up

Export Citation Format

Share Document