%0 Journal Article %J Journal of Database Management %D 2008 %T Bug Fixing Practices within Free/Libre Open Source Software Development Teams %A Kevin Crowston %A Barbara Scozzi %K activity %K bug tracker %K bug tracking system %K coordination %K downloads %K dynapi %K effectiveness %K FLOSS %K gaim %K kicq %K phpmyadmin %K project success %K size %K status %X Free/libre open source software (FLOSS, e.g., Linux or Apache) is primarily developed by distributed teams. Developers contribute from around the world and coordinate their activity almost exclusively by means of email and bulletin boards, yet some how profit from the advantages and evade the challenges of distributed software development. In this article we investigate the structure and the coordination practices adopted by development teams during the bug-fixing process, which is considered one of main areas of FLOSS project success. In particular, based on a codification of the messages recorded in the bug tracking system of four projects, we identify the accomplished tasks, the adopted coordination mechanisms, and the role undertaken by both the FLOSS development team and the FLOSS community. We conclude with suggestions for further research. %B Journal of Database Management %V 19 %P 1–30 %> https://flosshub.org/sites/flosshub.org/files/CrowstonScozziJDBM2008.pdf %0 Conference Paper %B Proceedings of the 2005 international workshop on Mining software repositories %D 2005 %T Mining version histories to verify the learning process of Legitimate Peripheral Participants %A Huang, Shih-Kun %A Liu, Kang-min %K awstats %K bzflag %K cvs %K filezilla %K gallery %K Legitimate Peripheral Participants (LPP) %K moodle %K open boundary %K open source software development process %K phpmyadmin %K social networks %K sourceforge %X Since code revisions reflect the extent of human involvement in the software development process, revision histories reveal the interactions and interfaces between developers and modules.We therefore divide developers and modules into groups according to the revision histories of the open source software repository, for example, sourceforge.net. To describe the interactions in the open source development process, we use a representative model, Legitimate Peripheral Participation (LPP) [6], to divide developers into groups such as core and peripheral teams, based on the evolutionary process of learning behavior.With the conventional module relationship, we divide modules into kernel and non-kernel types (such as UI). In the past, groups of developers and modules have been partitioned naturally with informal criteria. In this work, however, we propose a developer-module relationship model to analyze the grouping structures between developers and modules. Our results show some process cases of relative importance on the constructed graph of project development. The graph reveals certain subtle relationships in the interactions between core and non-core team developers, and the interfaces between kernel and non-kernel modules. %B Proceedings of the 2005 international workshop on Mining software repositories %S MSR '05 %I ACM %C New York, NY, USA %P 84-88 %@ 1-59593-123-6 %U http://doi.acm.org/10.1145/1082983.1083158 %R http://doi.acm.org/10.1145/1082983.1083158 %> https://flosshub.org/sites/flosshub.org/files/84MiningVersion.pdf %0 Conference Paper %B 1st International Workshop on Computer Supported Activity Coordination, 6th International Conference on Enterprise Information Systems %D 2004 %T Coordination practices for bug fixing within FLOSS development teams %A Kevin Crowston %A Barbara Scozzi %K activity %K bug fixing %K bug reports %K bug tracker %K coordination %K downloads %K dynapi %K FLOSS %K gaim %K kicq %K phpmyadmin %K status %X Free/Libre Open Source Software (FLOSS) is primarily developed by distributed teams. Developers contribute from around the world and coordinate their activity almost exclusively by means of email and bulletin boards. FLOSS development teams some how profit from the advantages and evade the challenges of distributed software development. Despite the relevance of the FLOSS both for research and practice, few studies have investigated the work practices adopted by these development teams. In this paper we investigate the structure and the coordination practices adopted by development teams during the bug-fixing process, which is considered one of main areas of FLOSS project success. In particular, based on a codification of the messages recorded in the bug tracking system of four projects, we identify the accomplished tasks, the adopted coordination mechanisms, and the role undertaken by both the FLOSS development team and the FLOSS community. We conclude with suggestions for further research. %B 1st International Workshop on Computer Supported Activity Coordination, 6th International Conference on Enterprise Information Systems %C Porto, Portugal %> https://flosshub.org/sites/flosshub.org/files/CrowstonScozzi04coordination.pdf