SEMar 21, 2021

Escaping the Time Pit: Pitfalls and Guidelines for Using Time-Based Git Data

arXiv:2103.11339v115 citations
Originality Synthesis-oriented
AI Analysis

This addresses a data quality issue for software engineering researchers, but it is incremental as it provides guidelines rather than a new method.

The paper tackled the problem of dirty time-based data in software engineering research by surveying its usage in the MSR conference series and quantifying sources of dirty commit timestamps, finding that at least 35% of papers used such data.

Many software engineering research papers rely on time-based data (e.g., commit timestamps, issue report creation/update/close dates, release dates). Like most real-world data however, time-based data is often dirty. To date, there are no studies that quantify how frequently such data is used by the software engineering research community, or investigate sources of and quantify how often such data is dirty. Depending on the research task and method used, including such dirty data could affect the research results. This paper presents the first survey of papers that utilize time-based data, published in the Mining Software Repositories (MSR) conference series. Out of the 690 technical track and data papers published in MSR 2004--2020, we saw at least 35% of papers utilized time-based data. We then used the Boa and Software Heritage infrastructures to help identify and quantify several sources of dirty commit timestamp data. Finally we provide guidelines/best practices for researchers utilizing time-based data from Git repositories.

Foundations

The foundational work for this paper's niche, ranked by how specifically the neighbourhood builds on it — not by global fame.

Your Notes