2017 IEEE International Conference on Software Maintenance and Evolution (ICSME) (2017)
Sept. 17, 2017 to Sept. 22, 2017
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/ICSME.2017.81
Open Source Software (OSS) communities depend on continu-ally recruiting new contributors. Some communities promote initiatives such as Summers of Code to foster contribution, but little is known about how successful these initiatives are. As a case study, we chose Google Summer of Code (GSoC), which is a three-month internship promoting software development by students in several OSS projects. We quantitatively inves-tigated different aspects of students' contribution, including number of commits, code churn, and contribution date inter-vals. We found that 82% of the studied OSS projects merged at least one commit in codebase. When only newcomers are considered, ~54% of OSS projects merged at least one com-mit. We also found that ~23% of newcomers contributed to GSoC projects before knowing they would be accepted. Addi-tionally, we found that the amount of commits and code of students with experience in the GSoC projects are strongly correlated with how much code they produced and how long they remained during and after GSoC. OSS communities can take advantage of our results to balance the trade-offs in-volved in entering CCEs, to set the communities' expectations about how much contribution they can expect to achieve, and for how long students will probably engage.
public domain software, software engineering, source code (software)
"How Long and How Much: What to Expect from Summer of Code Participants?", 2017 IEEE International Conference on Software Maintenance and Evolution (ICSME), vol. 00, no. , pp. 69-79, 2017, doi:10.1109/ICSME.2017.81