GitHub Projects. Quality Analysis of Open-Source Software

Jarczyk, Oskar; Gruszka, Blazej; Jaroszewicz, Szymon; Bukowski, Leszek; Wierzbicki, Adam

doi:10.1007/978-3-319-13734-6_6

Cited by 66 publications

(32 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…• Lowering the issues/bugs/enhancements resolution times [2,6,18,20,26,34]; • Increasing the number of issues/bugs/enhancements being resolved [20].…”

Section: Related Workmentioning

confidence: 99%

We don't need another hero?

Agrawal¹,

Rahman²,

Krishna³

et al. 2018

Proceedings of the 40th International Conference on Software Engineering: Software Engineering in Practice

View full text Add to dashboard Cite

A software project has "Hero Developers" when 80% of contributions are delivered by 20% of the developers. Are such heroes a good idea? Are too many heroes bad for software quality? Is it better to have more/less heroes for different kinds of projects? To answer these questions, we studied 661 open source projects from Public open source software (OSS) Github and 171 projects from an Enterprise Github.We find that hero projects are very common. In fact, as projects grow in size, nearly all projects become hero projects. These findings motivated us to look more closely at the effects of heroes on software development. Analysis shows that the frequency to close issues and bugs are not significantly affected by the presence of heroes or project type (Public or Enterprise). Similarly, the time needed to resolve an issue/bug/enhancement is not affected by heroes or project type. This is a surprising result since, before looking at the data, we expected that increasing heroes on a project will slow down how fast that project reacts to change. However, we do find a statistically significant association between heroes, project types, and enhancement resolution rates. Heroes do not affect enhancement resolution rates in Public projects. However, in Enterprise projects, heroes increase the rate at which projects complete enhancements.In summary, our empirical results call for a revision of a longheld truism in software engineering. Software heroes are far more common and valuable than suggested by the literature, particularly for medium to large Enterprise developments. Organizations should reflect on better ways to find and retain more of these heroes. CCS CONCEPTS• Software and its engineering → Agile software development;

show abstract

“…• Lowering the issues/bugs/enhancements resolution times [2,6,18,20,26,34]; • Increasing the number of issues/bugs/enhancements being resolved [20].…”

Section: Related Workmentioning

confidence: 99%

We don't need another hero?

Agrawal¹,

Rahman²,

Krishna³

et al. 2018

Proceedings of the 40th International Conference on Software Engineering: Software Engineering in Practice

View full text Add to dashboard Cite

show abstract

“…Another study was done by Jarczyk et al [15] which investigates the relation between the OSS project quality and the properties of the development team members. The study was done on a dataset representing OSS projects from GitHub.…”

Section: Related Workmentioning

confidence: 99%

“…Furthermore, most the studies have done their study on one OSS hosting platform such as GitHub [15], [17], [18]. However, in this research a thorough qualitative analysis of a set of OSS hosting platforms is performed to study the built-in collaboration features.…”

Section: Related Workmentioning

confidence: 99%

Open Source Software Hosting Platforms: A Collaborative Perspective’s Review

Alamer¹,

Alyahya²

2017

JSW

View full text Add to dashboard Cite

Abstract:Open source software (OSS) has been gaining large attention lately. In fact, several studies have shown that the collaboration is a remarkably major factor influencing the OSS quality. In addition, there are several existing platforms providing mediums for collaborative development of the OSS projects and involve advanced features that assist in boosting the collaboration process. Such platforms which can be called as open source software hosting platforms are rich of collaborative workflows. Therefore, in this research a comprehensive investigation of the current OSS hosting platforms is held for the sake of studying their collaboration capabilities as well as pointing out any limitations related to collaboration that might hinder OSS from meeting high quality. The review has shown that the current OSS hosting platforms have some potential limitations. The identified limitations have been shared through a survey with developers working on OSS platforms and the results have generally revealed that there is a necessity to overcome these limitations.

show abstract

“…The intuition is that popular repositories (i.e. repositories with many "stargazers") will contain actual software that people like and use (Jarczyk et al, 2014). The intuition has been the basis for several well-received studies.…”

Section: Utility Data Setmentioning

confidence: 99%

Curating GitHub for engineered software projects

Munaiah

Kroh

Cabrey

et al. 2016

Preprint

View full text Add to dashboard Cite

Software forges like GitHub host millions of repositories. Software engineering researchers have been able to take advantage of such a large corpora of potential study subjects with the help of tools like GHTorrent and Boa. However, the simplicity in querying comes with a caveat: there are limited means of separating the signal (e.g. repositories containing engineered software projects) from the noise (e.g. repositories containing home work assignments). The proportion of noise in a random sample of repositories could skew the study and may lead to researchers reaching unrealistic, potentially inaccurate, conclusions. We argue that it is imperative to have the ability to sieve out the noise in such large repository forges. We propose a framework, and present a reference implementation of the framework as a tool called reaper, to enable researchers to select GitHub repositories that contain evidence of an engineered software project. We identify software engineering practices (called dimensions) and propose means for validating their existence in a GitHub repository. We used reaper to measure the dimensions of 1,994,977 GitHub repositories. We then used the data set train classifiers capable of predicting if a given GitHub repository contains an engineered software project. The performance of the classifiers was evaluated using a set of 200 repositories with known ground truth classification. We also compared the performance of the classifiers to other approaches to classification (e.g. number of GitHub Stargazers) and found our classifiers to outperform existing approaches. We found stargazers-based classifier to exhibit high precision (96%) but an inversely proportional recall (27%). On the other hand, our best classifier exhibited a high precision (82%) and a high recall (83%). The stargazer-based criteria offers precision but fails to recall a significant potion of the population.

show abstract

GitHub Projects. Quality Analysis of Open-Source Software

Cited by 66 publications

References 16 publications

We don't need another hero?

We don't need another hero?

Open Source Software Hosting Platforms: A Collaborative Perspective’s Review

Curating GitHub for engineered software projects

Contact Info

Product

Resources

About