activity
20172022
most citedPredicting Defective Lines Using a Model-Agnostic Technique

138 citations · 184 across the 18 of their papers we have counts for

collaborators

27 papers

cs.SE2021

FixMe: A GitHub Bot for Detecting and Monitoring On-Hold Self-Admitted Technical Debt

Saranphon Phaithoon, Supakarn Wongnil, Patiphol Pussawong +6

Self-Admitted Technical Debt (SATD) is a special form of technical debt in which developers intentionally record their hacks in the code by adding comments for attention. Here, we…

cs.SE202112 cited

Science-Software Linkage: The Challenges of Traceability between Scientific Knowledge and Software Artifacts

Hideaki Hata, Jin L. C. Guo, Raula Gaikovina Kula +1

Although computer science papers are often accompanied by software artifacts, connecting research papers to their software artifacts and vice versa is not always trivial. First of…

cs.SE2021

Same File, Different Changes: The Potential of Meta-Maintenance on GitHub

Hideaki Hata, Raula Gaikovina Kula, Takashi Ishio +1

Online collaboration platforms such as GitHub have provided software developers with the ability to easily reuse and share code between repositories. With clone-and-own and forking…

cs.SE2021

Characterizing and Mitigating Self-Admitted Technical Debt in Build Systems

Tao Xiao, Dong Wang, Shane McIntosh +4

Technical Debt is a metaphor used to describe the situation in which long-term software artifact quality is traded for short-term goals in software projects. In recent years, the c…

cs.SE2021

GitHub Discussions: An Exploratory Study of Early Adoption

Hideaki Hata, Nicole Novielli, Sebastian Baltes +2

Discussions is a new feature of GitHub for asking questions or discussing topics outside of specific Issues or Pull Requests. Before being available to all projects in December 202…

cs.SE2020

Automated Identification of On-hold Self-admitted Technical Debt

Rungroj Maipradit, Bin Lin, Csaba Nagy +4

Modern software is developed under considerable time pressure, which implies that developers more often than not have to resort to compromises when it comes to code that is well wr…