Coordinating Interdependencies in an Open Source Software Project: A Replication of Lindberg, et al.

The current study is a full replication (conceptual and empirical) of “Coordinating Interdependencies in Online Communities: A Study of an Open Source Software Project” Lindberg et al (2016), which addresses the question of how OSS communities address unresolved interdependencies. Following the original study, we analyze project development data, archived in the GitHub repository, for the OSS project Rubinius. The analysis explores relationships among development and developer interdependencies as well as activity and order variation. Further, we extend the original study by examining the core relationships in the original study and investigating the external generalizability of the results by replicating the analysis on three analogous OSS projects: JRuby, mruby, and RubyMotion. These offer an opportunity to evaluate the generalizability of the original study to projects of different sizes and amount of activity, yet similar otherwise to the project in the original study. Another extension is the use of an additional control variable, length of activity sequence, which proves to have substantial implications of the study’s focal relationships. We find that three out of the four projects we analyze support the findings of the original study as it pertains to four relationships in the original study: order variation and developer interdependencies, activity variation and developer interdependencies, order variation and development interdependencies, and development and developer interdependencies. We also discuss the implications of our findings, especially in cases where the replication results differ from those in the original study and offer suggestions for future research that can help advance this stream of research.

[1]  Nicholas Berente,et al.  Coordinating Interdependencies in Online Communities: A Study of an Open Source Software Project , 2016, Inf. Syst. Res..

[2]  Gang Yin,et al.  Reviewer recommendation for pull-requests in GitHub: What can we learn from code review and bug assignment? , 2016, Inf. Softw. Technol..

[3]  Adam Croom,et al.  Roads and Bridges: The Unseen Labor Behind Our Digital Infrastructure / Ford Foundation , 2016 .

[4]  Michael C. Frank,et al.  Estimating the reproducibility of psychological science , 2015, Science.

[5]  Brian A. Nosek,et al.  Promoting an open research culture , 2015, Science.

[6]  Premkumar T. Devanbu,et al.  Wait for It: Determinants of Pull Request Evaluation Latency on GitHub , 2015, 2015 IEEE/ACM 12th Working Conference on Mining Software Repositories.

[7]  Arie van Deursen,et al.  An exploratory study of the pull-based software development model , 2014, ICSE.

[8]  Kelly Blincoe,et al.  Do all task dependencies require coordination? the role of task properties in identifying critical coordination needs in software projects , 2013, ESEC/FSE 2013.

[9]  Natalia Juristo Juzgado,et al.  Replications types in experimental disciplines , 2010, ESEM '10.

[10]  Audris Mockus,et al.  Software Dependencies, Work Dependencies, and Their Impact on Failures , 2009, IEEE Transactions on Software Engineering.

[11]  James D. Herbsleb,et al.  Socio-technical congruence: a framework for assessing the impact of technical and work dependencies on software development productivity , 2008, ESEM '08.

[12]  Audris Mockus,et al.  Formulation and preliminary test of an empirical theory of coordination in software engineering , 2003, ESEC/FSE-11.

[13]  J. Herbsleb,et al.  Two case studies of open source software development: Apache and Mozilla , 2002, TSEM.

[14]  W. E. Bardsleya,et al.  A significance test for empty corners in scatter diagrams , 1999 .