Cited by 1,685Open Source Software InnovationsSoftware Engineering Techniques and PracticesSoftware Engineering Research

Two case studies of open source software development: Apache and Mozilla

Mockus, Audris, Fielding, Roy T., Herbsleb, James D.·2002·ACM Transactions on Software Engineering and Methodology

Abstract

According to its proponents, open source style software development has the capacity to compete successfully, and perhaps in many cases displace, traditional commercial development methods. In order to begin investigating such claims, we examine data from two major open source projects, the Apache web server and the Mozilla browser. By using email archives of source code change history and problem reports we quantify aspects of developer participation, core team size, code ownership, productivity, defect density, and problem resolution intervals for these OSS projects. We develop several hypotheses by comparing the Apache project with several commercial projects. We then test and refine several of these hypotheses, based on an analysis of Mozilla data. We conclude with thoughts about the prospects for high-performance commercial/open source process hybrids.

Integrity signals

Registry

Crossref · 10.1145/567793.567795

Cites

1 of 1 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

  • 87% of the Apache members who reported bugs submitted just one report.

    “Mockus et al. (2002) estimate that 87% of the Apache members who reported bugs submitted just one report.”

    From Open Source Software: The New Intellectual Property Paradigm (2006) · cites this paper as Mockus et al. (2002)

  • 15 core developers provide 83% of all Apache contributions.

    “Similarly, Mockus et al. (2002) tell us that 15 core developers provide 83% of all Apache contributions while Von Krogh et al . (2003) report that about one percent of Freenet's members account for fifty percent of all developer e-mails.”

    From Open Source Software: The New Intellectual Property Paradigm (2006) · cites this paper as Mockus et al. (2002)

  • Participation models such as the onion model and the core-periphery model become less hierarchical and more situational, as members can be peripheral in times of stability but become central agents during times of instability.

    “Accordingly, participation models such as the onion model (Nakakoji et al. 2002;Crowston and Howison 2005) and the core-periphery model (Mockus et al. 2002;Crowston et al. 2006) become less hierarchical and more situational, as members can be in peripheral positions in times of stability but become central agents during times of instability.”

Cites

Flagged first, then by citations

Cited by

Sorted by citations

Authors
Mockus, A., Fielding, R. T., & Herbsleb, J. D.
Affiliations
  • Avaya (United States) (US)
  • Day Software, Newport Beach, CA
  • Carnegie Mellon University (US)
Venue
ACM Transactions on Software Engineering and Methodology
Published
2002-07
Volume
11
Issue
3
Pages
309-346
ISSN
  • 1049-331X (ISSN-L)
  • 1557-7392
OpenAlex
W2107294940
Cited by
1,685
References
1
Citations by year
2026: 34 · 2025: 41 · 2024: 39 · 2023: 35 · 2022: 27 · 2021: 36 · 2020: 49 · 2019: 48 · 2018: 61 · 2017: 64 · 2016: 66 · 2015: 76 · 2014: 109 · 2013: 107 · 2012: 112
FWCI
108.28
Type
journal article
Language
en
Open access
closed
Locations
ACM Transactions on Software Engineering and Methodology (publishedVersion)
Topics
  • Physical Sciences › Computer Science › Computer Science Applications › Open Source Software Innovations
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
Keywords
open source software development, Apache web server, developer engagement, code ownership, developer productivity, defect density, commercial software development

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review