138 citations · 247 across the 17 of their papers we have counts for
30 papers
What makes a good Node.js package? Investigating Users, Contributors, and Runnability
Bodin Chinthanet, Brittany Reid, Christoph Treude +4
The Node.js Package Manager (i.e., npm) archive repository serves as a critical part of the JavaScript community and helps support one of the largest developer ecosystems in the wo…
Automatic Patch Linkage Detection in Code Review Using TextualContent and File Location Features
Dong Wang, Raula Gaikovina Kula, Takashi Ishio +1
Context: Contemporary code review tools are a popular choice for software quality assurance. Using these tools, reviewers are able to post a linkage between two patches during a re…
Code Reviews with Divergent Review Scores: An Empirical Study of the OpenStack and Qt Communities
Toshiki Hirao, Shane McIntosh, Akinori Ihara +1
Code review is a broadly adopted software quality practice where developers critique each others' patches. In addition to providing constructive feedback, reviewers may provide a s…
FLOSS != GitHub: A Case Study of Linux/BSD Perceptions from Microsoft's Acquisition of GitHub
Raula Gaikovina Kula, Hideki Hata, Kenichi Matsumoto
In 2018, the software industry giants Microsoft made a move into the Open Source world by completing the acquisition of mega Open Source platform, GitHub. This acquisition was not…
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…
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…