Proceedings Article10.1109/HICSS.2007.426
Patch Review Processes in Open Source Software Development Communities: A Comparative Case Study
Jai Asundi,Rajiv Jayant +1 more
- 03 Jan 2007
- Vol. 1, pp 166
TL;DR: The results show that while the patch review processes are not exactly identical across various F/OSS projects, the core members across all projects play the vital role of gate-keepers to ensure a high level of review for submitted patches.
read more
Abstract: In spite of the overwhelming success of free/open source software (F/OSS) like Apache and GNU/Linux, there is a limited understanding of the processes and methodologies that specify this form of software development. In this paper, we examine the process of patch reviews as a proxy for the extent of code-review in F/OSS projects. While existing descriptions of patch review processes are mostly narrative and based on individual experiences, we systematically analyze the email archives of five F/OSS projects to characterize this process. While doing so, we make a distinction between contributions (patches or review comments) by core members and casual contributors to grasp the role of core members in this process. Our results show that while the patch review processes are not exactly identical across various F/OSS projects, the core members across all projects play the vital role of gate-keepers to ensure a high level of review for submitted patches
read more
Chat with Paper
AI Agents for this Paper
Find similar papers on Google Scholar, PubMed and Arxiv
Write a critical review of this paper
Analyze citations of this paper to find unaddressed research gaps
Citations
Convergent contemporary software peer review practices
Peter C. Rigby,Christian Bird +1 more
- 18 Aug 2013
TL;DR: A measure of the degree to which knowledge is shared during review shows that conducting peer review increases the number of distinct files a developer knows about by 66% to 150% depending on the project.
Open source software peer review practices: a case study of the apache server
Peter C. Rigby,Daniel M. German,Margaret-Anne Storey +2 more
- 10 May 2008
TL;DR: It is concluded that Apache reviews can be described as early, frequent reviews of small, independent, complete contributions conducted asynchronously by a potentially large, but actually small, group of self-selected experts leading to an efficient and effective peer review technique.
255
Understanding broadcast based peer review on open source software projects
Peter C. Rigby,Margaret-Anne Storey +1 more
- 21 May 2011
TL;DR: An empirical study is described to investigate the mechanisms and behaviours that developers use to find code changes they are competent to review and how stakeholders interact with one another during the review process.
Process Aspects and Social Dynamics of Contemporary Code Review: Insights from Open Source Development and Industrial Practice at Microsoft
TL;DR: The findings identify the following key areas that warrant focused research: exploring the non-technical benefits of code reviews, helping developers in articulating review comments, and assisting reviewers’ program comprehension during code reviews.
166
Key factors for adopting inner source
TL;DR: A framework derived from the literature on Inner Source is presented, which identifies nine important factors that need to be considered when implementing Inner Source, and can be used as a probing instrument to assess an organization on these nine factors so as to gain an understanding of whether or not Inner source is suitable.
References
Some Simple Economics of Open Source
Josh Lerner,Jean Tirole +1 more
TL;DR: In this article, the authors make a preliminary exploration of the economics of open source software and highlight the extent to which labor economics, especially the literature on "career concerns" and industrial organization theory can explain many of these projects' features.
The cathedral and the bazaar
TL;DR: A sustained argument from the Linux experience is made for the proposition that "Given enough eyeballs, all bugs are shallow," and productive analogies with other self-correcting systems of selfish agents are suggested.
2.2K
Two case studies of open source software development: Apache and Mozilla
TL;DR: This work examines data from two major open source projects, the Apache web server and the Mozilla browser, and quantifies aspects of developer participation, core team size, code ownership, productivity, defect density, and problem resolution intervals for these OSS projects.
1.9K
The Simple Economics of Open Source
TL;DR: The extent to which labor economics, especially the literature on career concerns,' can explain many of these projects' features is highlighted, and aspects of the future of open source development process remain somewhat difficult to predict with off-the-shelf economic models.
Design and code inspections to reduce errors in program development
TL;DR: It is shown that by using inspection results, a mechanism for initial error reduction followed by ever-improving error rates can be achieved.
1.4K