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

By Audris Mockus, Roy T. Fielding, James D. Herbsleb. TSEM, 2002

1,952 citations recorded by the source corpus.

Subfields: Computer Science Applications, Information Systems

View Paper: https://www.semanticscholar.org/paper/b452c83fcdee0b9f3e02573144919487c1eae4d3

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Computer Science Applications

In Information Systems

Citations in the corpus

The promises and perils of mining git (2009, neutral): “A. E. Housman, A Shropshire Lad”
The influence of organizational structure on software quality (2008, background): “Also Mockus et al. [23] investigate how different individuals across geographical boundaries contribute towards open source projects (Apache and Mozilla).”
Hipikat: a project memory for software development (2005, methodology): “The prototype has been designed to adapt easily to any project that follows the common open-source development model [26] and that produces at least a subset of the artifact types contained in the project memory schema.”
Work Practices and Challenges in Pull-Based Development: The Contributor's Perspective (2014, background): “In distributed software development, the ﬁrst step towards integrating changes is evaluating the proposed contributions.”
How to Best Ensure Remuneration for Creators in the Market for Music? Copyright and its Alternatives (2006, methodology): “…software suggests that it closely resembles production in more traditional software markets C© 2006 The Authors Journal compilation C© 2006 Blackwell Publishing Ltd and if anything, the creation of open source software is actually more concentrated (Mockus et al., 2002, 2003; Asundi et al., 2006).”
An approach to detecting duplicate bug reports using natural language and execution information (2008, background): “First, the bug repository allows users all around the world to be " testers " * Corresponding authors of the software, so it can increase the possibility of revealing defects and thus increase the quality of the software [14].”
Wiki: A Technology for Conversational Knowledge Management and Group Collaboration (2004, background): “Similarly, open source software developers appear to be more productive than those working on proprietary projects [Mockus et al., 2002].”
Hipikat: recommending pertinent software development artifacts (2003, methodology): “Mockus, Fielding, and Herbsleb have described building logical work units from CVS revisions by looking at revisions that were checked in by a single author within a small time interval and that share the same comment [11].”
Impacts of License Choice and Organizational Sponsorship on User Interest and Development Activity in Open Source Software Projects (2006, background): “Furthermore, an active user base will generate defect reports and support requests (Mockus et al. 2002), providing greater opportunities for developers to hone their skills on a variety of tasks, and thereby stimulating more development work.”
The impact of code review coverage and code review participation on software quality: a case study of the qt, VTK, and ITK projects (2014, background): “find that the recorded priority in Apache and Mozilla projects was not related to the time taken to resolve an issue, largely because the reporters who file the defects had far less experience than the core developers who fix them [26].”
The Mirroring Hypothesis: Theory, Evidence and Exceptions (2016, background): “Thus a third pattern we observed was the formation of a “core-periphery” organizational structure (Koch and Schneider, 2002; von Krogh et al., 2003; Mockus et al., 2000; 2002).”
Latent social structure in open source projects (2008, background): “While this is the prescribed venue for engineering discussions (due to it’s broadcast nature) [7, 22, 34, 46], we miss other potential developer interactions, such as private emails, irc channels, or discussions in bug reports.”
Weblog success: Exploring the role of technology (2006, background): “…issues relating to electronic commerce (e.g., Liu and Arnett, 2000; Molla and Licker, 2002; Torkzadeh and Dhillon, 2002), open source movement (e.g., Markus et al., 2000; Mockus et al., 2002; Raymond, 1998), and online community (e.g., Hagel and Armstrong, 1997; Kozinets, 1999; Preece, 2001).”
An empirical study of the impact of modern code review practices on software quality (2015, background): “Indeed, Mockus et al. (2002) ﬁnd that the recorded priority in Apache and Mozilla projects was not related to the time taken to resolve an issue, largely because the reporters who ﬁle the defects had far less experience than the core developers who ﬁx them.”