Bug-Patching for Mozilla's Firefox
12 Pages Posted: 25 Mar 2008 Last revised: 6 Apr 2008
Date Written: February 1, 2008
Abstract
The case study of the Mozilla project is focused on the organization of quality control and quality assurance in a distributed innovation environment, and focuses on the coordination of the detection and correction of operating defects ('bugs') in Mozilla's Firefox web-browser. Analyzing two samples of bugs drawn from the 40,000 or so that have resulted in a change to the Firefox code base, the case study finds among others that bug treatment behavior in the project was not temporal stable, that bug reports from 'outsiders' took longer to find a successful resolution and were more likely to remain 'un-fixed' and that factors such as the objective technical complexity of the bug-patching problem, and the level of effort devoted to the contextualisation the reported defect played significant roles determining the speed with which a bug was typically fixed.
Suggested Citation: Suggested Citation
Do you have negative results from your research you’d like to share?
Recommended Papers
-
The Wisdom of Collaborative Network Organizations: Capturing the Value of Networked Individuals
-
Seriosity: Addressing the Challenges of Limited Attention Spans
By David A. Bray, Karen Croxson, ...
-
Information Markets: Feasibility and Performance
By David A. Bray, Karen Croxson, ...
-
The Performance of Distributed News Aggregators
By Wolf Richter, Tobias Escher, ...
-
The Atlas Collaboration: A Distributed Problem-Solving Network in Big Science
-
Reconfiguring Government - Public Engagements: Enhancing the Communicative Power of Citizens
By William H. Dutton and Malcolm Peltu
-
Sermo: A Community-Based, Knowledge Ecosystem
By David A. Bray, Karen Croxson, ...
-
By Irene Cassarino and Aldo Geuna