TY - GEN
T1 - Early identification of future committers in open source software projects
AU - Ihara, Akinori
AU - Kamei, Yasutaka
AU - Ohira, Masao
AU - Hassan, Ahmed E.
AU - Ubayashi, Naoyasu
AU - Matsumoto, Ken Ichi
N1 - Publisher Copyright:
© 2014 IEEE.
PY - 2014/11/14
Y1 - 2014/11/14
N2 - There exists two types of developers in Open Source Software (OSS) projects: 1) Committers who have permission to commit edited source code to the Version Control System (VCS), 2) Developers who contribute source code but cannot commit to the VCS directly. In order to develop and evolve high quality OSS, projects are always in search of new committers. OSS projects often promote strong developers to become committers. When existing committers find strong developers, they propose their promotion to a committer role. Delaying the committer-promotion might lead to strong developers departing from an OSS project and the project losing them. However early committer-promotion comes with its own slew of risks as well (e.g., the promotion of inexperienced developers). Hence, committer-promotion decisions are critical for the quality and successful evolution of OSS projects. In this paper, we examine the committer-promotion phenomena for two OSS projects (Eclipse and Firefox). We find that the amount of activities by future committers was higher than the amount of activities by developers who did not become committers). We also find that some developers are promoted to a committer role very rapidly (within a few month) while some of developers take over one year to become a committer. Finally, we develop a committer-identification model to assist OSS projects identifying future committers.
AB - There exists two types of developers in Open Source Software (OSS) projects: 1) Committers who have permission to commit edited source code to the Version Control System (VCS), 2) Developers who contribute source code but cannot commit to the VCS directly. In order to develop and evolve high quality OSS, projects are always in search of new committers. OSS projects often promote strong developers to become committers. When existing committers find strong developers, they propose their promotion to a committer role. Delaying the committer-promotion might lead to strong developers departing from an OSS project and the project losing them. However early committer-promotion comes with its own slew of risks as well (e.g., the promotion of inexperienced developers). Hence, committer-promotion decisions are critical for the quality and successful evolution of OSS projects. In this paper, we examine the committer-promotion phenomena for two OSS projects (Eclipse and Firefox). We find that the amount of activities by future committers was higher than the amount of activities by developers who did not become committers). We also find that some developers are promoted to a committer role very rapidly (within a few month) while some of developers take over one year to become a committer. Finally, we develop a committer-identification model to assist OSS projects identifying future committers.
UR - http://www.scopus.com/inward/record.url?scp=84912076219&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=84912076219&partnerID=8YFLogxK
U2 - 10.1109/QSIC.2014.30
DO - 10.1109/QSIC.2014.30
M3 - Conference contribution
AN - SCOPUS:84912076219
T3 - Proceedings - International Conference on Quality Software
SP - 47
EP - 56
BT - Proceedings - International Conference on Quality Software
PB - IEEE Computer Society
T2 - 14th International Conference on Quality Software, QSIC 2014
Y2 - 2 October 2014 through 3 October 2014
ER -