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

@article{Mockus2002TwoCS,
  title={Two case studies of open source software development: Apache and Mozilla},
  author={Audris Mockus and Roy T. Fielding and James D. Herbsleb},
  journal={ACM Trans. Softw. Eng. Methodol.},
  year={2002},
  volume={11},
  pages={309-346}
}
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… 
Open source software development: a case study of FreeBSD
TLDR
A case study of the FreeBSD project provides further understanding of open source development, which uses a smaller set of core developers that implement a smaller portion of the system, and uses a more well-defined testing process.
Open source software development: a case study of FreeBSD
  • T. Dinh-Trong, J. Bieman
  • Computer Science
    10th International Symposium on Software Metrics, 2004. Proceedings.
  • 2004
TLDR
A case study of the FreeBSD project provides further understanding of open source development, which uses a smaller set of core developers that implement a smaller portion of the system, and uses a more well-defined testing process.
The FreeBSD project: a replication case study of open source development
TLDR
This case study of the FreeBSD project provides further understanding of open source development and details a method for mining repositories and querying project participants to retrieve key process information.
Automating the Measurement of Open Source Projects
TLDR
Based on experience analyzing numerous open source and commercial projects, a set of tools to support extraction and validation of software project data is proposed, which would streamline empirical investigation of open source projects and make it possible to test existing and new theories about the nature ofopen source projects.
Why modern open source projects fail
TLDR
It is shown that some maintenance practices---specifically the adoption of contributing guidelines and continuous integration---have an important association with a project failure or success and the principal strategies developers have tried to overcome the failure of the studied projects.
Understanding the Open-Source Software Development Process : a Case Study with CVSChecker
The open-source process model is emerging as a new lightweight paradigm for software development and has already produced several successful products. This process is fundamentally different from
Requirements elicitation in open source software development: a case study
TLDR
The results show that the majority of features are asserted by developers, based on either their personal experience, or knowledge of users' needs, suggesting that there is a common open source requirements approach that is independent of project size.
Calliope: supporting high-level documentation of open-source projects
TLDR
It is proposed that the explicit modeling of multivalence could improve the acceptance of more advanced documentation tools into the environment of open-source development and in order to test this claim, a prototype is built that implements explicit modeled ofMultivalence.
Estimating development effort in Free/Open source software projects by mining software repositories: a case study of OpenStack
TLDR
A novel approach to estimate effort by considering data from source code management repositories is presented, and it is shown that the model offers a simple, but sound way of obtaining software development estimations with bounded margins of error.
Bug Fixing Practices within Free/Libre Open Source Software Development Teams
TLDR
This article investigates 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.
...
1
2
3
4
5
...

References

SHOWING 1-10 OF 69 REFERENCES
Shared leadership in the Apache project
TLDR
According to the Netcraft survey of November 1998, the Apache server and its derivatives are used by over 57% of publicly accessible Web sites, more than double its nearest competitor.
Splitting the organization and integrating the code: Conway's law revisited
  • J. Herbsleb, Rebecca E. Grinter
  • Computer Science
    Proceedings of the 1999 International Conference on Software Engineering (IEEE Cat. No.99CB37002)
  • 1999
TLDR
A case study of what indeed turned out to be the most difficult part of a geographically distributed software project, i.e., integration, and shed light on the problems and mechanisms underlying the coordination needs of development projects generally, be they co-located or distributed.
Software configuration management for the 21st century
  • Anil K. Midha
  • Engineering, Computer Science
    Bell Labs Technical Journal
  • 1997
TLDR
The characteristics ofSCM systems, the SCM challenges for Lucent Technologies, the principal SCM systems being used within the company, and the issues of choosing and successfully implementing the best SCM system are focused on.
A FIELD STUDY OF THE SOFTWARE DESIGN PROCESS FOR 1ARGE
THE NEED FOR ECOLOGICAL DATA IN TECHNOLOGY RESEARCH MCC, The Microelectronics and Computer Technology Corporation, is a research consortium whose Software Technology Program was tasked by its member
The Open Source Definition
This chapter discusses the open source definition. Open source doesn't just mean access to the source code. The distribution terms of open-source software must comply with the following criteria:
The cathedral and the bazaar
I anatomize a successful open-source project, fetchmail, that was run as a deliberate test of some theories about software engineering suggested by the history of Linux. I discuss these theories in
A field study of the software design process for large systems
TLDR
A layered behavioral model is used to analyze how three of these problems—the thin spread of application domain knowledge, fluctuating and conflicting requirements, and communication bottlenecks and breakdowns—affected software productivity and quality through their impact on cognitive, social, and organizational processes.
The source code control system
  • M. Rochkind
  • Computer Science
    IEEE Transactions on Software Engineering
  • 1975
TLDR
The SCCS approach to source code control is discussed, how it is used and explained is shown and how the system is implemented is explained.
Software Measurement: A Necessary Scientific Basis
  • N. Fenton
  • Computer Science
    IEEE Trans. Software Eng.
  • 1994
TLDR
It is shown that the search for general software complexity measures is doomed to failure and the theory does help to define and validate measures of specific complexity attributes, and is able to view software measurement in a very wide perspective.
Software Measurement for DoD Systems: Recommendations for Initial Core Measures.
Abstract : This report presents our recommendations for a basic set of software measures that Department of Defense (DoD) organizations can use to help plan and manage the acquisition, development,
...
1
2
3
4
5
...