activity
20172023
most citedPandemic Programming: How COVID-19 affects software developers and how their organizations can help

238 citations · 682 across the 39 of their papers we have counts for

collaborators

40 papers

cs.SE2023★ 44 cited

DevGPT: Studying Developer-ChatGPT Conversations

Tao Xiao, Christoph Treude, Hideaki Hata +1

This paper introduces DevGPT, a dataset curated to explore how software developers interact with ChatGPT, a prominent large language model (LLM). The dataset encompasses 29,778 pro…

cs.SE2023★ 8 cited

18 Million Links in Commit Messages: Purpose, Evolution, and Decay

Tao Xiao, Sebastian Baltes, Hideaki Hata +4

Commit messages contain diverse and valuable types of knowledge in all aspects of software maintenance and evolution. Links are an example of such knowledge. Previous work on "9.6…

cs.SE2023

Meta-Maintanance for Dockerfiles: Are We There Yet?

Takeru Tanaka, Hideaki Hata, Bodin Chinthanet +2

Docker allows for the packaging of applications and dependencies, and its instructions are described in Dockerfiles. Nowadays, version pinning is recommended to avoid unexpected ch…

cs.SE2023

Understanding the Role of Images on Stack Overflow

Dong Wang, Tao Xiao, Christoph Treude +3

Images are increasingly being shared by software developers in diverse channels including question-and-answer forums like Stack Overflow. Although prior work has pointed out that t…

cs.SE2023★ 4 cited

She Elicits Requirements and He Tests: Software Engineering Gender Bias in Large Language Models

Christoph Treude, Hideaki Hata

Implicit gender bias in software development is a well-documented issue, such as the association of technical roles with men. To address this bias, it is important to understand it…

cs.SE2022

Release as a Contract: A Concept of Meta-Maintenance for the Entire FLOSS Ecosystem

Hideaki Hata

We advocate for a paradigm shift in supporting free/libre and open source software (FLOSS) ecosystem maintenance, from focusing on individual projects to monitoring a whole organic…

cs.SE2022★ 2 cited

Software Supply Chain Map: How Reuse Networks Expand

Hideaki Hata, Takashi Ishio

Clone-and-own is a typical code reuse approach because of its simplicity and efficiency. Cloned software components are maintained independently by a new owner. These clone-and-own…

cs.SE2022★ 11 cited

GitHub Sponsors: Exploring a New Way to Contribute to Open Source

Naomichi Shimada, Tao Xiao, Hideaki Hata +2

GitHub Sponsors, launched in 2019, enables donations to individual open source software (OSS) developers. Financial support for OSS maintainers and developers is a major issue in t…

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.SE2021★ 12 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★ 23 cited

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★ 12 cited

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★ 8 cited

A Framework for Conditional Statement Technical Debt Identification and Description

Abdulaziz Alhefdhi, Hoa Khanh Dam, Yusuf Sulistyo Nugroho +3

Technical Debt occurs when development teams favour short-term operability over long-term stability. Since this places software maintainability at risk, technical debt requires ear…

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…

cs.SE2020★ 138 cited

Predicting Defective Lines Using a Model-Agnostic Technique

Supatsara Wattanakriengkrai, Patanamon Thongtanunam, Chakkrit Tantithamthavorn +2

Defect prediction models are proposed to help a team prioritize source code areas files that need Software QualityAssurance (SQA) based on the likelihood of having defects. However…

cs.SE2020★ 2 cited

How are Project-Specific Forums Utilized? A Study of Participation, Content, and Sentiment in the Eclipse Ecosystem

Yusuf Sulistyo Nugroho, Syful Islam, Keitaro Nakasai +5

Although many software development projects have moved their developer discussion forums to generic platforms such as Stack Overflow, Eclipse has been steadfast in hosting their se…

cs.GT2020

Optimizing Affine Maximizer Auctions via Linear Programming: an Application to Revenue Maximizing Mechanism Design for Zero-Day Exploits Markets

Mingyu Guo, Hideaki Hata, Ali Babar

Optimizing within the affine maximizer auctions (AMA) is an effective approach for revenue maximizing mechanism design. The AMA mechanisms are strategy-proof and individually ratio…

cs.GT2020

Revenue Maximizing Markets for Zero-Day Exploits

Mingyu Guo, Hideaki Hata, Ali Babar

Markets for zero-day exploits (software vulnerabilities unknown to the vendor) have a long history and a growing popularity. We study these markets from a revenue-maximizing mechan…

cs.SE2020★ 238 cited

Pandemic Programming: How COVID-19 affects software developers and how their organizations can help

Paul Ralph, Sebastian Baltes, Gianisa Adisaputri +14

Context. As a novel coronavirus swept the world in early 2020, thousands of software developers began working from home. Many did so on short notice, under difficult and stressful…

cs.SE2020

GitHub Repositories with Links to Academic Papers: Public Access, Traceability, and Evolution

Supatsara Wattanakriengkrai, Bodin Chinthanet, Hideaki Hata +4

Traceability between published scientific breakthroughs and their implementation is essential, especially in the case of open-source scientific software which implements bleeding-e…

cs.SE2020★ 12 cited

Ammonia: An Approach for Deriving Project-specific Bug Patterns

Yoshiki Higo, Shinpei Hayashi, Hideaki Hata +1

Finding and fixing buggy code is an important and cost-intensive maintenance task, and static analysis (SA) is one of the methods developers use to perform it. SA tools warn develo…

cs.SE2019★ 5 cited

Challenges for Inclusion in Software Engineering: The Case of the Emerging Papua New Guinean Society

Raula Gaikovina Kula, Christoph Treude, Hideaki Hata +4

Software plays a central role in modern societies, with its high economic value and potential for advancing societal change. In this paper, we characterise challenges and opportuni…

cs.SE2019★ 6 cited

From Academia to Software Development: Publication Citations in Source Code Comments

Akira Inokuchi, Yusuf Sulistyo Nugroho, Supatsara Wattanakriengkrai +5

Academic publications have been evaluated in terms of their impact on research communities based on many metrics, such as the number of citations. On the other hand, the impact of…