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.

1 Self-organization of teams for free/libre open source software development This paper provides empirical evidence about how free/libre open source software development teams self-organize their work, specifically, how tasks are assigned to project team members. Following a case study methodology, we examined developer interaction data from three active and successful FLOSS projects using qualitative research methods, specifically inductive content analysis, to identify the task-assignment mechanisms used by the participants. We found that „self-assignment ‟ was the most common mechanism across three FLOSS projects. This mechanism is consistent with expectations for distributed and largely volunteer teams. We conclude by discussing whether these emergent practices can be usefully transferred to mainstream practice and indicating directions for future research. (105 words) Keywords: Free/libre open source software development, task assignment, self-organizing teams, distributed teams, qualitative research methods Running head: Self-organization of teams in FLOSS development 2 Self-organization of teams for free/libre open source software development 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 [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.

This paper describes the evolution of the Linux operating system, and studies dynamics of socio-technical change using Linux as a case example. Theoretical models of community-based practice and learning are combined with actor-network theory, and the characteristics open source development model are described using the introduced theoretical concepts. The paper analyses the growth and development of Linux and its development community, and shows how the development community evolves into an ecology of community-centered practices. During the last couple of years, the Open Source development model has been on front pages of newspapers, and focus of much attention (e.g., DiBona, Ockman, & Stone, 1999

Abstract not found

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.

Organizational and managerial theories of modularity applied to the design and production of complex artifacts are used to interpret the rise and success of Free/Open Source Software methodologies and practices in software engineering. Strengths and risks of the adoption of a modular approach in software project management are introduced and are related to the achievements of the GNU/Linux project as a whole, as well as to the outcomes of some of its sub--projects. It is suggested that mindful implementation of the principles of modularity may improve the rate of success of many Free/Open Source software projects. Specific case studies here depicted, as well as indirect observation of common programming practices employed by Free/Open Source developers and users, suggest a possible revision towards an improved theory of modularity that may be extended also to settings di#erent from software production.

In this paper we report possibilities and experiences from employing Counter-Strike, a popular multi-player Internet computer game and its resulting online community in research on cooperative behaviour. Advantages from using this game include easy availability of rich data, the emphasis on team-playing, as well as numerous possibilities to change the experiment settings. We use descriptive game theory and statistical methods to explore cooperation within the game as well as the way the player community deals with disruptive behaviour. After a quick introduction to the basic rules of Counter-Strike, we describe the setup of the Internet game server used. We then present empirical results from the game server logs where cooperation within the game is analyzed from a game theoretic perspective. Finally we discuss the applications of our results to other online communities, including cooperation and self-regulation in open source teams.

Internet Entrepreneurship: Linux and the Dynamics of Open Source Software Maureen McKelvey This paper examines the development of the Linux operating system, in order to examine from where the initial investment of ideas which resulted in the software structure emerged. Linux is taken as one example of open source software, and the analysis focuses on the reasons for software development, particularly in terms of the underlying dynamics of incentives, skills and entrepreneurship for open source software.

this paper, we introduce accepted notions of software architectures (Section 2), discuss some of the known issues in OSS (Section 3), resulting in a set of aspects we consider to be relevant for future research (Section 4)