Demo Data from EDBT 2026 / reviewers in the wild / expert
Prahar Pandya
dblp:332/5640
· DBLP profile ↗
1ranked-venue papers
1as first author
1since 2021 · last 2022
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1 · 1 first-author · 1 since 2021
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Software engineering, system software, and programming languages
1 paper |
Software maintenance and evolution · 87% Empirical software engineering · 13% |
Topics — the 3 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Software maintenance and evolution
code review |
0.6 | 1 | 2022 | CORMS: a GitHub and Gerrit based hybrid code reviewer recommendation approach for modern code review · ESEC/SIGSOFT FSE 2022 |
Software maintenance and evolution › code review
reviewer recommendation |
0.6 | 1 | 2022 | CORMS: a GitHub and Gerrit based hybrid code reviewer recommendation approach for modern code review · ESEC/SIGSOFT FSE 2022 |
Empirical software engineering
mining software repositories |
0.2 | 1 | 2022 | CORMS: a GitHub and Gerrit based hybrid code reviewer recommendation approach for modern code review · ESEC/SIGSOFT FSE 2022 |
Methods — techniques the papers use, named apart from their topics
similarity analysis · 0.6prediction model · 0.6
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2022 | CORMS: a GitHub and Gerrit based hybrid code reviewer recommendation approach for modern code reviewabstractModern Code review (MCR) techniques are widely adopted in both open-source software platforms and organizations to ensure the quality of their software products. However, the selection of reviewers for code review is cumbersome with the increasing size of development teams. The recommendation of inappropriate reviewers for code review can take more time and effort to complete the task effectively. In this paper, we extended the baseline of reviewers' recommendation framework - RevFinder - to handle issues with newly created files, retired reviewers, the external validity of results, and the accuracies of the state-of-the-art RevFinder. Our proposed hybrid approach, CORMS, works on similarity analysis to compute similarities among file paths, projects/sub-projects, author information, and prediction models to recommend reviewers based on the subject of the change. We conducted a detailed analysis on the widely used 20 projects of both Gerrit and GitHub to compare our results with RevFinder. Our results reveal that on average, CORMS, can achieve top-1, top-3, top-5, and top-10 accuracies, and Mean Reciprocal Rank (MRR) of 45.1%, 67.5%, 74.6%, 79.9% and 0.58 for the 20 projects, consequently improves the RevFinder approach by 44.9%, 34.4%, 20.8%, 12.3% and 18.4%, respectively. Prahar Pandya, Saurabh Tiwari 0001 |
ESEC/SIGSOFT FSE | 1 |