The focus of this paper is to review what is known about free and open source software development (FOSSD) work practices, development processes, project and community dynamics, and other socio-technical relationships. It focuses on exploring how FOSS is developed and evolved based on an extensive review of a set of empirical studies of FOSSD projects that articulate different levels of analysis. These characterize what has been analyzed in FOSSD studies across levels that examine (i) why individuals participate; (ii) resources and capabilities supporting development activities; (iii) how cooperation, coordination, and control are realized in projects; (iv) alliance formation and inter-project social networking; (v) FOSS as a multi-project software ecosystem, and (vi) FOSS as a social movement. Next, there is a discussion of limitations and constraints in the FOSSD studies so far. Last, attention shifts to identifying emerging opportunities for future FOSSD studies that can give rise to the development of new software engineering tools or techniques, as well as to new empirical studies of software development.

the state of the literature. We develop a framework for organizing the literature based on the input-mediatoroutput-input (IMOI) model from the small groups literature. We present a quantitative summary of articles selected for the review and then discuss findings of this literature categorized into issues pertaining to inputs (e.g., member characteristics, technology use and project characteristics), processes (software development and social processes), emergent states (e.g., trust and task related states) and outputs (e.g. team performance, FLOSS implementation and project evolution). Based on this review, we suggest topics for future research, as well as identifying methodological and theoretical issues for future inquiry in this area, including issues relating to sampling and the need for more longitudinal studies.

This paper discusses in detail a possible methodology for collecting repository data on a large number of open source software projects from a single project hosting and community site. The process of data retrieval is described along with the possible metrics that can be computed and which can be used for further analyses. Example research areas to be addressed with the available data and first results are given. Then, both advantages and disadvantages of the proposed methodology are discussed together with implications for future approaches. 1.

ACKNOWLEDGEMENTS: We thank the senior editor on the manuscript, V. Sambamurthy, and the anonymous associate editor and reviewers for their many insightful suggestions on earlier

We review the literature on Free/Libre Open Source Software (FLOSS) development and on software development, distributed work and teams more generally to develop a theoretical model to explain the performance of FLOSS teams. The proposed model is based on Hackman’s [1] model of effectiveness of work teams, with coordination theory [2] and collective mind [3] to extend Hackman’s model by elaborating team practices relevant to effectiveness in software development. We propose a set of propositions to guide further research. 1.

Abstract. The quest for designing secure and trusted software has led to refined Software Engineering methodologies that rely on tools to support the design process. Automated reasoning mechanisms for requirements and software verification are by now a well-accepted part of the design process, and model driven architectures support the automation of the refinement process. We claim that we can further push the envelope towards the automatic exploration and selection among design alternatives and show that this is concretely possible for Secure Tropos, a requirements engineering methodology that addresses security and trust concerns. In Secure Tropos, a design consists of a network of actors (agents, positions or roles) with delegation/permission dependencies among them. Accordingly, the generation of design alternatives can be accomplished by a planner which is given as input a set of actors and goals and generates alternative multiagent plans to fulfill all given goals. We validate our claim with a case study using a state-of-the-art planner. 1

We review the literature on Free/Libre Open Source Software (FLOSS) development and on software development, distributed work and teams more generally to develop a theoretical model to explain the performance of FLOSS teams. The proposed model is based on Hackman’s [34] model of effectiveness of work teams, with coordination theory [52] and collective mind [79] to extend Hackman’s model by elaborating team practices relevant to effectiveness in software development. We propose a set of propositions to guide further research.

The emerging work on understanding open source software has strongly argued for the importance of understanding what leads to effectiveness in OSS development, has frequently pointed to ideology and communication as probable factors in effectiveness, and has presented conflicting opinions about the role of trust in effectiveness. For all the discussion of these issues, there has been no comprehensive elaboration of what constitutes OSS ideology, and very little empirical data has been brought to bear on examining antecedents of OSS team effectiveness. This paper develops a framework of the OSS ideology (including specific norms, beliefs, and values) and a theoretical model to show how components of the ideology, combined with trust and communication, impact effectiveness in OSS teams. The research model proposes distinct roles for affective trust, cognitive trust, social communication, and task communication as determinants of OSS team effectiveness. Qualitative and quantitative data are analyzed to evaluate the model. The results suggest that in order for OSS projects to grow into the kind of large successes that prior work has studied, the teams that work on them should foster the norms and values of the larger community and maintain consistent task communication to develop cognitive trust among members. Keywords: Open Source Software, Trust, Ideology, Communication, Virtual Teams ISRL categories: DA01, DA06, DD02 EFFECTIVENESS IN OPEN SOURCE SOFTWARE DEVELOPMENT TEAMS While the practices associated with Open Source Software (OSS) development have been in use for decades, recent years have seen a surge of interest in OSS across developers, businesses, governments, and academic researchers. Since its inception, more than 67,000 projects have been registered on Sourcefo...

This study seeks to identify and characterize the array of social and technical resources needed to support the development of open source software supporting E-Commerce (EC) or E-Business (EB) capabilities. This entails a case study within a virtual organization that has undertaken an organizational initiative to develop, deploy, and support free/open source software systems for EC or EB services, like those supporting Enterprise Resource Planning. The objective this study is to identify and characterize the resource-based software product development capabilities that lie at the center of the initiative, rather than the software itself, or the effectiveness of its operation in a business enterprise. By learning what these resources are, and how they are arrayed into product development capabilities, we can provide the knowledge needed to understand what resources are required to realize the potential of Free EC and EB software applications. In addition, the resource-based view draws attentions to those resources and capabilities that provide potential competitive advantages and disadvantages of the organization in focus. Introduction and Background

Building on transaction cost economics, this work describes the four different forms of communities and introduces transaction benefits as a means of explaining their existence. A research project to investigate governance, leadership, and management in two of the four forms of communities, adaptive and inventive, is described. It is argued that these digital communities are a way of engaging graduate students in wealth creation and thus ‘waste ’ in graduate education can be reduced. 1