Can I Solve It? Identifying APIs Required to Complete OSS Tasks

Santos, Fabio; Wiese, Igor; Trinkenreich, Bianca; Steinmacher, Igor; Sarma, Anita; Gerosa, Marco Aurélio

doi:10.1109/msr52588.2021.00047

Cited by 13 publications

(17 citation statements)

References 51 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…4) API categorization: We use the API domain categories defined by Santos et al [8]. These 31 categories were defined by experts to encompass APIs from several projects (e.g., UI, IO, Cloud, DB, etc.-see our replication package 3 .…”

Section: A Model Trainingmentioning

confidence: 99%

“…However, since projects include thousands of different APIs, adding each API as a label would harm the user experience. To keep the number of labels manageable, we classified the APIs into domains for labeling [2,8] In our study, API domains represent categories of APIs such as "UI," "DB," "Test," etc. In our previous work, we used 31 distinct API domains [8].…”

Section: Introduction Contributors Struggle To Find Issues To Work On...mentioning

confidence: 99%

“…To keep the number of labels manageable, we classified the APIs into domains for labeling [2,8] In our study, API domains represent categories of APIs such as "UI," "DB," "Test," etc. In our previous work, we used 31 distinct API domains [8]. However, we acknowledge that the set of possible API-domain labels varies by project, as each project requires different skills and expertise.…”

Section: Introduction Contributors Struggle To Find Issues To Work On...mentioning

confidence: 99%

“…However, we acknowledge that the set of possible API-domain labels varies by project, as each project requires different skills and expertise. In another work, Santos et al [9] have evaluated the API domain labels in an empirical experiment with developers. The study showed that the labels enabled contributors to find OSS tasks that matched their expertise more efficiently.…”

Section: Introduction Contributors Struggle To Find Issues To Work On...mentioning

confidence: 99%

See 3 more Smart Citations

GiveMeLabeledIssues: An Open Source Issue Recommendation System

Vargovich

Santos

Penney

et al. 2023

View full text Add to dashboard Cite

Developers often struggle to navigate an Open Source Software (OSS) project's issue-tracking system and find a suitable task. Proper issue labeling can aid task selection, but current tools are limited to classifying the issues according to their type (e.g., bug, question, good first issue, feature, etc.). In contrast, this paper presents a tool (GiveMeLabeledIssues) that mines project repositories and labels issues based on the skills required to solve them. We leverage the domain of the APIs involved in the solution (e.g., User Interface (UI), Test, Databases (DB), etc.) as a proxy for the required skills. GiveMeLabeledIssues facilitates matching developers' skills to tasks, reducing the burden on project maintainers. The tool obtained a precision of 83.9% when predicting the API domains involved in the issues. The replication package contains instructions on executing the tool and including new projects. A demo video is available at https://www.youtube.com/watch?v=ic2quUue7i8

show abstract

Section: A Model Trainingmentioning

confidence: 99%

Section: Introduction Contributors Struggle To Find Issues To Work On...mentioning

confidence: 99%

Section: Introduction Contributors Struggle To Find Issues To Work On...mentioning

confidence: 99%

Section: Introduction Contributors Struggle To Find Issues To Work On...mentioning

confidence: 99%

See 2 more Smart Citations

GiveMeLabeledIssues: An Open Source Issue Recommendation System

Vargovich

Santos

Penney

et al. 2023

View full text Add to dashboard Cite

show abstract

“…For example, newcomer-friendly issue labels that explicitly highlight starter tasks can help newcomers make their first contribution [3,11,24]. Santos et al [20] provided an approach to automatically identify the skills needed for an OSS tasks, which could then be used to label issues. On the other hand, Huang et al [13] have shown that certain project topics, especially those that relate to social good help in attracting a diverse set of contributors.…”

Section: Introductionmentioning

confidence: 99%

Attracting and Retaining OSS Contributors with a Maintainer Dashboard

Guizani¹,

Zimmermann²,

Sarma³

et al. 2022

Preprint

Self Cite

View full text Add to dashboard Cite

Tools and artifacts produced by open source software (OSS) have been woven into the foundation of the technology industry. To keep this foundation intact, the open source community needs to actively invest in sustainable approaches to bring in new contributors and nurture existing ones. We take a first step at this by collaboratively designing a maintainer dashboard that provides recommendations on how to attract and retain open source contributors. For example, by highlighting project goals (e.g., a social good cause) to attract diverse contributors and mechanisms to acknowledge (e.g., a "rising contributor" badge) existing contributors. Next, we conduct a project-specific evaluation with maintainers to better understand use cases in which this tool will be most helpful at supporting their plans for growth. From analyzing feedback, we find recommendations to be useful at signaling projects as welcoming and providing gentle nudges for maintainers to proactively recognize emerging contributors. However, there are complexities to consider when designing recommendations such as the project current development state (e.g., deadlines, milestones, refactoring) and governance model. Finally, we distill our findings to share what the future of recommendations in open source looks like and how to make these recommendations most meaningful over time.

show abstract