Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Daniel Armanios

dblp:228/1092 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 2020
0000-0001-7100-2861ORCID · reported

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 1

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 · 62% Software maintenance and evolution · 38%

Topics — the 3 heaviest of 3, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Empirical software engineering
mining software repositories
0.412020
Heard it through the Gitvine: an empirical study of tool diffusion across the npm ecosystem · ESEC/SIGSOFT FSE 2020
Software maintenance and evolution › software ecosystems
npm ecosystem
0.112020
Heard it through the Gitvine: an empirical study of tool diffusion across the npm ecosystem · ESEC/SIGSOFT FSE 2020
Software maintenance and evolution
software ecosystems
0.112020
Heard it through the Gitvine: an empirical study of tool diffusion across the npm ecosystem · ESEC/SIGSOFT FSE 2020

Methods — techniques the papers use, named apart from their topics

survival analysis · 0.4network science · 0.4
YearPublicationVenuePosition
2020 Heard it through the Gitvine: an empirical study of tool diffusion across the npm ecosystem
abstract
Automation tools like continuous integration services, code coverage reporters, style checkers, dependency managers, etc. are all known to provide significant improvements in developer productivity and software quality. Some of these tools are widespread, others are not. How do these automation "best practices" spread? And how might we facilitate the diffusion process for those that have seen slower adoption? In this paper, we rely on a recent innovation in transparency on code hosting platforms like GitHub---the use of repository badges---to track how automation tools spread in open-source ecosystems through different social and technical mechanisms over time. Using a large longitudinal data set, multivariate network science techniques, and survival analysis, we study which socio-technical factors can best explain the observed diffusion process of a number of popular automation tools. Our results show that factors such as social exposure, competition, and observability affect the adoption of tools significantly, and they provide a roadmap for software engineers and researchers seeking to propagate best practices and tools.
Hemank Lamba, Asher Trockman, Daniel Armanios, Christian Kästner, Heather Miller, Bogdan Vasilescu
ESEC/SIGSOFT FSE3