Decision-making Processes in Community-based Free/Libre Open Source Software-development Teams with Internal Governance: An Extension to Decision-making Theory

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.

Download Full-text

Bug Fixing Practices within Free/Libre Open Source Software Development Teams

Database Technologies ◽

10.4018/978-1-60566-058-5.ch046 ◽

2009 ◽

pp. 797-828

Author(s):

Kevin Crowston ◽

Barbara Scozzi

Keyword(s):

Software Development ◽

Open Source ◽

Open Source Software ◽

Tracking System ◽

Distributed Teams ◽

Distributed Software ◽

Bug Fixing ◽

Development Teams ◽

Bulletin Boards ◽

Software Development Teams

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.

Download Full-text

Bug Fixing Practices within Free/Libre Open Source Software Development Teams

Advances in Database Research - Principle Advancements in Database Management Technologies ◽

10.4018/978-1-60566-904-5.ch003 ◽

2011 ◽

pp. 51-81

Author(s):

Kevin Crowston ◽

Barbara Scozzi

Keyword(s):

Software Development ◽

Open Source ◽

Open Source Software ◽

Tracking System ◽

Distributed Teams ◽

Distributed Software ◽

Bug Fixing ◽

Development Teams ◽

Bulletin Boards ◽

Software Development Teams

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.

Download Full-text