Revisiting the applicability of the pareto principle to core development teams in open source software projects

Kazuhiro Yamashita, Shane McIntosh, Yasutaka Kamei, Ahmed E. Hassan, Naoyasu Ubayashi

Research output: Chapter in Book/Report/Conference proceedingConference contribution

16 Citations (Scopus)

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 of the studied GitHub projects are susceptible to the bus factor, where the impact of a core developer leaving would be quite harmful.

Original languageEnglish
Title of host publication14th International Workshop on Principles of Software Evolution, IWPSE 2015 - Proceedings
PublisherInstitute of Electrical and Electronics Engineers Inc.
Pages46-55
Number of pages10
ISBN (Electronic)9781450338165
DOIs
Publication statusPublished - Aug 30 2015
Event14th International Workshop on Principles of Software Evolution, IWPSE 2015 - Bergamo, Italy
Duration: Aug 30 2015 → …

Publication series

NameInternational Workshop on Principles of Software Evolution (IWPSE)
Volume30-Aug-2015

Other

Other14th International Workshop on Principles of Software Evolution, IWPSE 2015
CountryItaly
CityBergamo
Period8/30/15 → …

Fingerprint

Pareto principle
Open Source Software
Pareto
Proportion
Vary
Heuristics
Subset
Open source software

All Science Journal Classification (ASJC) codes

  • Software
  • Theoretical Computer Science
  • Modelling and Simulation
  • Computational Theory and Mathematics

Cite this

Yamashita, K., McIntosh, S., Kamei, Y., Hassan, A. E., & Ubayashi, N. (2015). Revisiting the applicability of the pareto principle to core development teams in open source software projects. In 14th International Workshop on Principles of Software Evolution, IWPSE 2015 - Proceedings (pp. 46-55). (International Workshop on Principles of Software Evolution (IWPSE); Vol. 30-Aug-2015). Institute of Electrical and Electronics Engineers Inc.. https://doi.org/10.1145/2804360.2804366

Revisiting the applicability of the pareto principle to core development teams in open source software projects. / Yamashita, Kazuhiro; McIntosh, Shane; Kamei, Yasutaka; Hassan, Ahmed E.; Ubayashi, Naoyasu.

14th International Workshop on Principles of Software Evolution, IWPSE 2015 - Proceedings. Institute of Electrical and Electronics Engineers Inc., 2015. p. 46-55 (International Workshop on Principles of Software Evolution (IWPSE); Vol. 30-Aug-2015).

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Yamashita, K, McIntosh, S, Kamei, Y, Hassan, AE & Ubayashi, N 2015, Revisiting the applicability of the pareto principle to core development teams in open source software projects. in 14th International Workshop on Principles of Software Evolution, IWPSE 2015 - Proceedings. International Workshop on Principles of Software Evolution (IWPSE), vol. 30-Aug-2015, Institute of Electrical and Electronics Engineers Inc., pp. 46-55, 14th International Workshop on Principles of Software Evolution, IWPSE 2015, Bergamo, Italy, 8/30/15. https://doi.org/10.1145/2804360.2804366
Yamashita K, McIntosh S, Kamei Y, Hassan AE, Ubayashi N. Revisiting the applicability of the pareto principle to core development teams in open source software projects. In 14th International Workshop on Principles of Software Evolution, IWPSE 2015 - Proceedings. Institute of Electrical and Electronics Engineers Inc. 2015. p. 46-55. (International Workshop on Principles of Software Evolution (IWPSE)). https://doi.org/10.1145/2804360.2804366
Yamashita, Kazuhiro ; McIntosh, Shane ; Kamei, Yasutaka ; Hassan, Ahmed E. ; Ubayashi, Naoyasu. / Revisiting the applicability of the pareto principle to core development teams in open source software projects. 14th International Workshop on Principles of Software Evolution, IWPSE 2015 - Proceedings. Institute of Electrical and Electronics Engineers Inc., 2015. pp. 46-55 (International Workshop on Principles of Software Evolution (IWPSE)).
@inproceedings{4f642e271e864fed8c0529492f2ff1fd,
title = "Revisiting the applicability of the pareto principle to core development teams in open source software projects",
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 of the studied GitHub projects are susceptible to the bus factor, where the impact of a core developer leaving would be quite harmful.",
author = "Kazuhiro Yamashita and Shane McIntosh and Yasutaka Kamei and Hassan, {Ahmed E.} and Naoyasu Ubayashi",
year = "2015",
month = "8",
day = "30",
doi = "10.1145/2804360.2804366",
language = "English",
series = "International Workshop on Principles of Software Evolution (IWPSE)",
publisher = "Institute of Electrical and Electronics Engineers Inc.",
pages = "46--55",
booktitle = "14th International Workshop on Principles of Software Evolution, IWPSE 2015 - Proceedings",
address = "United States",

}

TY - GEN

T1 - Revisiting the applicability of the pareto principle to core development teams in open source software projects

AU - Yamashita, Kazuhiro

AU - McIntosh, Shane

AU - Kamei, Yasutaka

AU - Hassan, Ahmed E.

AU - Ubayashi, Naoyasu

PY - 2015/8/30

Y1 - 2015/8/30

N2 - 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 of the studied GitHub projects are susceptible to the bus factor, where the impact of a core developer leaving would be quite harmful.

AB - 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 of the studied GitHub projects are susceptible to the bus factor, where the impact of a core developer leaving would be quite harmful.

UR - http://www.scopus.com/inward/record.url?scp=84958664805&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=84958664805&partnerID=8YFLogxK

U2 - 10.1145/2804360.2804366

DO - 10.1145/2804360.2804366

M3 - Conference contribution

AN - SCOPUS:84958664805

T3 - International Workshop on Principles of Software Evolution (IWPSE)

SP - 46

EP - 55

BT - 14th International Workshop on Principles of Software Evolution, IWPSE 2015 - Proceedings

PB - Institute of Electrical and Electronics Engineers Inc.

ER -