Abstract - It is often observed that the majority of the development work of an Open Source Software (OSS) project is contributed by a core team, i.e., a small subset of the pool of active developers. In fact, recent work has found that core development teams follow the Pareto principle --- roughly 80% of the code contributions are produced by 20% of the active developers. However, those findings are based on samples of between one and nine studied systems. In this paper, we revisit prior studies about core developers using 2,496 projects hosted on GitHub. We find that even when we vary the heuristic for detecting core developers, and when we control for system size, team size, and project age: (1) the Pareto principle does not seem to apply for 40%-87% of GitHub projects; and (2) more than 88% of GitHub projects have fewer than 16 core developers. Moreover, we find that when we control for the quantity of contributions, bug fixing accounts for a similar proportion of the contributions of both core (18%-20%) and non-core developers (21%-22%). Our findings suggest that the Pareto principle is not compatible with the core teams of many GitHub projects. In fact, several projects are more susceptible to the so-called 'bus factor,' where the impact of a core developer leaving a project would be quite harmful.
Preprint - PDF
Bibtex
@inproceedings{yamashita2015iwpse,
Author = {Kazuhiro Yamashita and Shane McIntosh and Yasutaka Kamei and Ahmed E. Hassan and Naoyasu Ubayashi},
Title = {{Revisiting the Applicability of the Pareto Principle to Core Development Teams in Open Source Software Projects}},
Year = {2015},
Booktitle = {Proc. of the 14th International Workshop on the Principles of Software Evolution (IWPSE) (IWPSE)},
Pages = {46-55}
}