EDBT 2026 Demo / reviewers in the wild / expert
Metehan Saçakçi
dblp:378/3283
· DBLP profile ↗
1ranked-venue papers
0as first author
1since 2021 · last 2024
0000-0002-3836-4040ORCID · reported
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1 · 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 |
Empirical software engineering · 67% Software maintenance and evolution · 33% |
Topics — the 2 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Software maintenance and evolution
issue tracking |
0.8 | 1 | 2024 | An Empirical Analysis of Issue Templates Usage in Large-Scale Projects on GitHub · ACM Trans. Softw. Eng. Methodol. 2024 |
Empirical software engineering
mining software repositories |
0.8 | 1 | 2024 | An Empirical Analysis of Issue Templates Usage in Large-Scale Projects on GitHub · ACM Trans. Softw. Eng. Methodol. 2024 |
Methods — techniques the papers use, named apart from their topics
survey · 0.8empirical analysis · 0.8
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2024 | An Empirical Analysis of Issue Templates Usage in Large-Scale Projects on GitHubabstractGitHub Issues is a widely used issue tracking tool in open-source software projects. Originally designed with broad flexibility, its lack of standardization led to incomplete issue reports, impeding software development and maintenance efficiency. To counteract this, GitHub introduced issue templates in 2016, which rapidly became popular. Our study assesses the current use and evolution of these templates in large-scale open-source projects and their impact on issue tracking metrics, including resolution time, number of reopens, and number of issue comments. Employing a comprehensive analysis of 350 templates from 100 projects, we also evaluated over 1.9 million issues for template conformity and impact. Additionally, we solicited insights from open-source software maintainers through a survey. Our findings highlight issue templates’ extensive usage in 99 of the 100 surveyed projects, with a growing preference for YAML-based templates, a more structured template variant. Projects with a template exhibited markedly reduced resolution time (381.02 days to 103.18 days) and reduced issue comment count (4.95 to 4.32) compared to those without. The use of YAML-based templates further significantly decreased resolution time, the number of reopenings, and the discussion extent. Thus, our research underscores issue templates’ positive impact on large-scale open-source projects, offering recommendations for improved effectiveness. Emre Sülün, Metehan Saçakçi, Eray Tüzün |
ACM Trans. Softw. Eng. Methodol. | 2 |