Software inspections, in which developers subject their code to review by peers or other stakeholders to identify defects, was developed by Michael Fagan in 1976 [12]. Since then, it has been established as an effective quality improvement practice [6], [35]. Even with the benefits offered by software inspections, their relatively high cost and time requirements have reduced the prevalence with which software teams, in general, adopt them [19]. Conversely, many mature, successful OSS projects have recently adopted peer code reviews (informal software inspection) as an important quality assurance mechanism.