Skip to main content
zenodoopen

Dataset of the study "Exploring the Notion of Risk in Reviewer Recommendation"

<p><strong>Note: Please find the dockerized version of this replication package in the following link:</strong></p> <p><a href="https://figshare.com/articles/dataset/Replication_Package_of_the_study_Exploring_the_Notion_of_Risk_in_Reviewer_Recommendation_/20673255">https://figshare.com/articles/dataset/Replication_Package_of_the_study_Exploring_the_Notion_of_Risk_in_Reviewer_Recommendation_/20673255</a></p> <p>&nbsp;</p> <p>This repository contains the necessary data for replicating the necessary information to replicate the study of &quot;Exploring the Notion of Risk in Reviewer Recommendation.&quot; This code extends the RelationalGit package (https://github.com/CESEL/RelationalGit) from the study of E. Mirsaeedi and P. C. Rigby &nbsp;[1] and adds some functionality that is needed to incorporate the concept of the fix-inducing likelihood of a project.</p> <p>In addition to our dataset, this repository also have the supporting materials for our study. The supporting materials are in the &quot;ICSME_online_materials_ICSME.pdf&quot; and contains the following items:</p> <ul> <li>Table 1 contains the detail of the dataset and some related statistics for each of the studied projects.&nbsp;</li> <li>Table 2 have risk measures that were used in our defect prediction model. We use Commit Guru Tool to extracts the data from the GitHub repositories and then use this data to train our defect prediction model.</li> <li>Figure 1 illustrates the distribution of predicted defect probability of different projects. This distribution shows how defect probability of different periods are similar to the adjacent periods.&nbsp;</li> </ul> <p><strong>References:</strong></p> <p>[1]&nbsp;E. Mirsaeedi and P. C. Rigby, &lsquo;Mitigating turnover with code review recommendation: Balancing expertise, workload, and knowledge distribution&rsquo;, &sigma;&tau;&omicron;&nbsp;<em>Proceedings of the ACM/IEEE 42nd International Conference on Software Engineering</em>, 2020.</p> <p>&nbsp;</p>

ShareScore

40/100

Overall dataset sharing score

Score breakdown

These five areas show where the dataset supports — or may limit — practical reuse.

Stewardship
8
Harmonization
4
Access
20
Reuse readiness
8
Engagement
0

Topics