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.

community is growing across and within multiple disciplines. This community faces a new and unusual situation. The traditional difficulties of gathering enough empirical data have been replaced by issues of dealing with enormous amounts of freely available public data from many disparate sources (online discussion forums, source code directories, bug reports, OSS Web portals, etc.). Consequently, these data are being discovered, gathered, analyzed, and used to support multidisciplinary research. However at present, no means exist for assembling these data under common access points and frameworks for comparative, longitudinal, and collaborative research across disciplines. Gathering and maintaining large F/OSS data collections reliably and making them usable present several research challenges. For example, current projects usually rely on direct access to, and mining of raw data from groups that generate it, and both of these methods require unique effort for each new corpus, or even for updating existing corpora. In this paper, we identify several needs and critical factors in F/OSS empirical research across disciplines, and suggest recommendations for design of a global research infrastructure for multi-disciplinary research into F/OSS development. 1.

Climate scientists build large, complex simulations with little or no software engineering training, and do not readily adopt the latest software engineering tools and techniques. In this paper, we describe an ethnographic study of the culture and practices of climate scientists at the Met Office Hadley Centre. The study examined how the scientists think about software correctness, how they prioritize requirements, and how they develop a shared understanding of their models. The findings show that climate scientists have developed customized techniques for verification and validation that are tightly integrated into their approach to scientific research. Their software practices share many features of both agile and open source projects, in that they rely on self-organisation of the teams, extensive use of informal communication channels, and developers who are also users and domain experts. These comparisons offer insights into why such practices work. 1.

This study presents findings from an empirical study directed at understanding the roles, forms, and consequences arising in requirements for open source software (OSS) development efforts. Five open source software development communities are described, examined, and compared to help discover what differences may be observed. At least two dozen kinds of software informalisms are found to play a critical role in the elicitation, analysis, specification, validation, and management of requirements for developing OSS systems. Subsequently, understanding the roles these software informalisms take in a new formulation of the requirements development process for OSS is the focus of this study. This focus enables considering a reformulation of the requirements engineering process and its associated artifacts or (in)formalisms to better account for the requirements when developing OSS systems. Other findings identify how OSS requirements are decentralized across multiple informalisms, and to the need for advances in how to specify the capabilities of existing OSS systems.

www.isr.uci.edu

This paper discusses the meaning of open source in an industrial context. Building a grounded theory from an industry-driven R&D project, our analysis shows that open source in an industrial context is multifaceted. We find that the meaning of open source must be established in the context of the individual organization.

Open source software (OSS) development is a communityoriented, networkcentric approach to building complex software systems. OSS projects are typically organized as edge organizations lacking an explicit management regime to control and coordinate decentralized project work. However, a growing number of OSS projects are developing, delivering, and supporting largescale software systems, displacing proprietary software alternatives. Recent empirical studies of OSS projects reveal that OSS developers often selforganize into organizational forms we characterize as evolving sociotechnical interaction networks (STINs). STINs emerge in ways that effectively control semiautonomous OSS developers and coordinate project activities, producing reliable and adaptive software systems. In this paper, we examine how practices and processes enable and govern OSS projects when coalesced and configured as contingent, sociotechnical interaction networks. We draw on data sources and results from two ongoing case studies of governance activities and elements in a large OSS project.

In the past five or so years, it has become clear that the U.S. Air Force, Army, and Navy have all committed to a strategy of acquiring software-intensive systems that require or utilize an “open architecture ” (OA) and “open technology ” (OT) which may incorporate OSS technology or OSS development processes. There are many perceived benefits and anticipated cost savings associated with an OA strategy. However, the challenge for acquisition program managers is how to realize the savings and benefits through requirements that can be brought into system development practice. As such, the central problem we examine in this paper is to identify principles of software architecture and OSS copyright licenses that facilitate or inhibit the success of an OA strategy when OSS and open APIs are required or otherwise employed. By examining and analyzing this problem we can begin to identify what additional requirements may be needed to fulfill an OA strategy during program acquisition.

We seek to establish and sustain an agenda for a national program for research on free/open source software (FOSS, or sometimes FLOSS) by academic and industrial researchers in different disciplines. This proposal describes our vision for such a research agenda, along with the international workshop and supporting meetings we propose to conduct in order to develop the agenda to guide future research. The activities build from recent research meetings on FOSS support multidisciplinary studies of FOSS development. We also identify our goals, assessment method, activities, outcomes, and results from recent meetings giving rise to this proposal. Following this is a specification of proposed meetings and workshop, budget, budget rationale, and brief biographical description of the proposal organizers. Why we need a national research program in Free/Open Source Software Even though Free/Open Source Software (FOSS) is widely used, we believe the much of the Computer Science research community has yet to fully recognize its potential to change the world of research and development of software-intensive systems across disciplines. Tens of thousands of FOSS projects are up and running world-wide, and millions of end-users of computing increasingly rely on FOSS-based systems. Growing numbers of research projects in physical, social, and human sciences, as well as the cultural arts are now routinely expecting to develop or use FOSS-based systems to best meet their needs. Similarly, growing numbers of businesses and government organizations are now looking to develop and use mission-critical software applications that are built with FOSS components. We believe reasons for such attention and

We seek to establish and sustain an agenda for a national program for research on free/open source software (FOSS, or sometimes FLOSS) by academic and industrial researchers in different disciplines. This proposal describes our vision for such a research agenda, along with the international workshop and supporting meetings we propose to conduct in order to develop the agenda to guide future research. The activities build from recent research meetings on FOSS support multi-disciplinary studies of FOSS development. We also identify our goals, assessment method, activities, outcomes, and results from recent meetings giving rise to this proposal. Why we need a national research program in Free/Open Source Software Even though Free/Open Source Software (FOSS) is widely used, we believe the much of the Computer Science research community has yet to fully recognize its potential to change the world of research and development of software-intensive systems across disciplines. Tens of thousands of FOSS projects are up and running world-wide, and millions of end-users of computing increasingly rely on FOSS-based systems. Growing numbers of research projects in physical, social, and human sciences, as well as the