Convergent contemporary software peer review practices

By Peter C. Rigby, Christian Bird. ESEC/FSE 2013, 2013

364 citations recorded by the source corpus.

Subfields: Computer Science Applications, Information Systems

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

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 impact of code review coverage and code review participation on software quality: a case study of the qt, VTK, and ITK projects (2014, background): “, mailing lists or the Gerrit web application(1)) tend to converge on a lightweight variant of the formal code inspections of the past, where the focus has shifted from defect-hunting to group problemsolving [34].”
An empirical study of the impact of modern code review practices on software quality (2015, background): “Rigby and Bird (2013) ﬁnd that the modern code review processes that are adopted through a variety of reviewing mediums (e.g., mailing lists or the Gerrit web application 1 ) tend to converge on a lightweight variant of the formal code inspections of the past, where the focus has shifted from…”
An in-depth study of the promises and perils of mining GitHub (2015, result): “The numbers are comparable with other work on code review (Rigby et al. 2008; Rigby and Bird 2013; Bacchelli and Bird 2013) which suggests that the peer review process may have more fundamental underpinnings yet to be explored.”
Work Practices and Challenges in Pull-Based Development: The Contributor's Perspective (2014, methodology): “The pull-based model on GitHub lacks a specific patch acceptance process (as is the case with Gerrit [40] or CodeFlow [2]).”
The promises and perils of mining GitHub (2009, result): “The numbers are comparable with other work in code review [23, 22, 2], which suggests that the peer review process may have more fundamental underpinnings yet to be explored.”
A Security Perspective on Code Review: The Case of Chromium (2016, background): “Studies on the topic confirm that code review is an activity that is effective when a reasonably low number of people is involved [16], [35] Focusing on security, we have initial evidence suggesting that a number of reviewers higher than 2 is advisable to find the most security flaws.”