The Impact of Ideology on Effectiveness in Open Source Software Development Teams

MIS Quarterly ◽  
2006 ◽  
Vol 30 (2) ◽  
pp. 291 ◽  
Author(s):  
Stewart ◽  
Gosain
Keyword(s):  
Software Development ◽  
Open Source ◽  
Open Source Software ◽  
Open Source Software Development ◽  
Development Teams ◽  
Software Development Teams ◽  
The Impact

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

2009 ◽  
pp. 1079-1110 ◽  
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.

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

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.

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

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.

Sign in / Sign up

Export Citation Format

Share Document