Hi Gijs, Sorry for late reply (for some reason we've never received a notification of your post)!
Our much earlier study was about the lifecycle of Firefox patches: "The Secret Life of Patches: A Firefox Case Study" (https://cs.uwaterloo.ca/~obaysal/wcre2012-baysal.pdf) We then worked on Martin Best's Bugzilla Anthropology project (https://wiki.mozilla.org/Bugzilla_Anthropology) where we analyzed the interview data that he collected. The tech report is available online (http://www.cs.uwaterloo.ca/research/tr/2012/CS-2012-10.pdf). In this study, we developed a situational awareness tool organized around custom developer dashboards. Pre-prints of the published work are also publicly available: "No Issue Left Behind: Reducing Information Overload in Issue Tracking" (https://cs.uwaterloo.ca/~obaysal/fse14-baysal.pdf) and "DASHboards: Enhancing Developer Situational Awareness" (https://cs.uwaterloo.ca/~obaysal/icse14_kononenko_preprint.pdf) Currently we are looking into Mozilla's code review process and investigating the factors that affect its quality. Olga and Oleksii _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
