Results 1 - 10
of
93
The perils and pitfalls of mining SourceForge
- In Proceedings of the International Workshop on Mining Software Repositories (MSR 2004
, 2004
"... SourceForge provides abundant accessible data from Open Source Software development projects, making it an attractive data source for software engineering research. However it is not without theoretical peril and practical pitfalls. In this paper, we outline practical lessons gained from our spideri ..."
Abstract
-
Cited by 77 (4 self)
- Add to MetaCart
(Show Context)
SourceForge provides abundant accessible data from Open Source Software development projects, making it an attractive data source for software engineering research. However it is not without theoretical peril and practical pitfalls. In this paper, we outline practical lessons gained from our spidering, parsing and analysis of SourceForge data.
Coordination of free/libre open source software development
, 2005
"... 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 ..."
Abstract
-
Cited by 75 (28 self)
- Add to MetaCart
(Show Context)
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.
The impact of ideology on effectiveness in open source software development teams
- MIS Quarterly
, 2006
"... 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 ..."
Abstract
-
Cited by 54 (2 self)
- Add to MetaCart
(Show Context)
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
Emergence of New Project Teams from Open Source Software Developer Networks: Impact of Prior Collaboration Ties
, 2006
"... Software development has traditionally been regarded as an activity that can only be effectively conducted and managed within a firm setting. However, contrary to such assertions, the open source software development (OSSD) approach, in which software developers in digital social networks coordinate ..."
Abstract
-
Cited by 42 (0 self)
- Add to MetaCart
Software development has traditionally been regarded as an activity that can only be effectively conducted and managed within a firm setting. However, contrary to such assertions, the open source software development (OSSD) approach, in which software developers in digital social networks coordinate to voluntarily contribute programming code, has recently emerged as a promising alternative. Although many high profile cases of successful OSSD projects exist, the harsh reality is that the vast majority of OSS projects fail to take off and become abandoned. A commonly cited reason for the failure of OSS projects is the inability of the software project to bring together a critical mass of developers. This paper empirically examines the role of prior collaborative ties on how OSSD project teams are formed. Using software project data from real world OSSD projects, we find that the existence and the amount of prior collaborative relations in the developer network do increase the probability that an OSS project will attract more developers and that a developer’s prior relationships with a project initiator do increase the likelihood that a developer will join a project initiated by a past collaborator. We also explore the performance implications of early team formation behaviors.
A topological analysis of the open source software development community
- In HICSS ’05: Proceedings of the Proceedings of the 38th Annual Hawaii International Conference on System Sciences (HICSS’05) - Track 7
, 2005
"... The fast growth of OSS has increased the interest in studying the composition of the OSS community and its collaboration mechanisms. Moreover, the success of a project may be related to the underlying social structure of the OSS development community. In this paper, we perform a quantitative analysi ..."
Abstract
-
Cited by 39 (3 self)
- Add to MetaCart
(Show Context)
The fast growth of OSS has increased the interest in studying the composition of the OSS community and its collaboration mechanisms. Moreover, the success of a project may be related to the underlying social structure of the OSS development community. In this paper, we perform a quantitative analysis of Open Source Software developers by studying the entire development community at SourceForge [26]. Statistics and social network properties are explored to find collaborations and the effects of different members in the OSS development community. Small world phenomenon and scale free behaviors are found in the SourceForge development network. These topological properties may potentially explain the success and efficiency of OSS development practices. We also infer from our analysis that weakly associated but contributing co-developers and active users may be an important factor in OSS development. 1.
Self-organization of teams for free/libre open source software development,” Inf
- in WWW ’10: Proceedings of the 19th international conference on World wide web
"... 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, ..."
Abstract
-
Cited by 35 (7 self)
- Add to MetaCart
(Show Context)
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.
Effective work practices for software engineering: Free/libre open source software development
- in Proc. of WISER
, 2004
"... 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 wor ..."
Abstract
-
Cited by 28 (3 self)
- Add to MetaCart
(Show Context)
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.
Effective work practices for FLOSS development: A model and propositions
- In the Hawai’i International Conference on System Science (HICSS), Big Island
, 2005
"... 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 ..."
Abstract
-
Cited by 19 (1 self)
- Add to MetaCart
(Show Context)
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.
From Planning to Mature: on the Determinants of Open Source Take Off
, 2005
"... In this paper we use data from SourceForge.net, the largest open source projects repository, to estimate the main determinants of the progress in the development of a stable and mature code of a software. We find that the less restrictive the licensing terms the larger the likelihood of reaching an ..."
Abstract
-
Cited by 18 (0 self)
- Add to MetaCart
In this paper we use data from SourceForge.net, the largest open source projects repository, to estimate the main determinants of the progress in the development of a stable and mature code of a software. We find that the less restrictive the licensing terms the larger the likelihood of reaching an advanced development status and that this effect is even stronger for newer projects. We also find that projects geared towards system administrators appear to be the more successful ones. The determinants of projects’ development stage change with the age of the project in many dimensions, i.e. licensing terms, software audience and contents, thus supporting the common perception of opens source as a very dynamic phenomenon. The data seem to suggest that open source is evolving towards more commercial applications.
