Maximilian Capraro
Michael Dorner
Dirk Riehle
ABSTRACT
Inner source (IS) is the use of open source software development (SD) practices and the establishment of an open source-like culture within an organization. IS enables and requires developers to collaborate more than traditional SD methods such as plan-driven or agile development. To better understand IS, researchers and practitioners need to measure IS collaboration. However, there is no method yet for doing so. In this paper, we present a method for measuring IS collaboration by measuring the patch-flow within an organization. Patch-flow is the flow of code contributions across organizational boundaries such as project, organizational unit, or profit center boundaries. We evaluate our patch-flow measurement method using case study research with a software developing multi-industry company. By applying the method in the case organization, we evaluate its relevance and viability and discuss its usefulness. We found that about half (47.9%) of all code contributions constitute patch-flow between organizational units, almost all (42.2%) being between organizational units working on different products. Such significant patch-flow indicates high relevance of the patch-flow phenomenon and hence the method presented in this paper. Our patch-flow measurement method is the first of its kind to measure and quantify IS collaboration. It can serve as a base for further quantitative analyses of IS collaboration.
- Andrew Begel, Yit Phang Khoo, and Thomas Zimmermann. 2010. Codebook: discovering and exploiting relationships in software repositories. In Software Engineering, 2010 ACM/IEEE 32nd International Conference on, Vol. 1. IEEE, 125--134. Google Scholar
Digital Library
- Maximilian Capraro and Dirk Riehle. 2017. Inner source definition, benefits, and challenges. ACM Computing Surveys (CSUR) 49, 4 (2017), 67. Google ScholarDigital Library
- Gabriella CB Costa, Francisco Santana, Andréa M Magdaleno, and Cláudia ML Werner. 2014. Monitoring Collaboration in Software Processes Using Social Networks. In CYTED-RITOS International Workshop on Groupware. Springer, 89--96.Google Scholar
- Kevin Crowston and James Howison. 2005. The social structure of free and open source software development. First Monday 10, 2 (2005).Google Scholar
- Kevin Crowston, Kangning Wei, James Howison, and Andrea Wiggins. 2008. Free/Libre Open-source Software Development: What We Know and What We Do Not Know. ACM Comput. Surv. 44, 2, Article 7 (March 2008), 35 pages. Google ScholarDigital Library
- Daniela S Cruzes and Tore Dyba. 2011. Recommended steps for thematic synthesis in software engineering. In Empirical Software Engineering and Measurement (ESEM), 2011 International Symposium on. IEEE, 275--284. Google ScholarDigital Library
- Jamie Dinkelacker, Pankaj K Garg, Rob Miller, and Dean Nelson. 2002. Progressive open source. In Proceedings of the 24th International Conference on Software Engineering. ACM, 177--184. Google ScholarDigital Library
- Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides. 1994. Design patterns: elements of reusable object-oriented software. (1994). Google ScholarDigital Library
- Georgios Gousios, Eirini Kalliamvakou, and Diomidis Spinellis. 2008. Measuring developer contribution from software repository data. In Proceedings of the 2008 international working conference on Mining software repositories. ACM, 129--132. Google ScholarDigital Library
- Hillside Group. 2010. How to Hold a Writers Workshop. (2010). Last retrieved in January 2018, http://hillside.net/conferences/plop/235-how-to-hold-a-writers-workshop. Publication year estimated using http://web.archive.org.Google Scholar
- Egon G Guba. 1981. Criteria for assessing the trustworthiness of naturalistic inquiries. Educational Technology Research and Development 29, 2 (1981), 75--91.Google Scholar
- Vijay K. Gurbani, Anita Garvert, and James D. Herbsleb. 2006. A Case Study of a Corporate Open Source Development Model. In Proceedings of the 28th International Conference on Software Engineering (ICSE '06). ACM, New York, NY, USA, 472--481. Google ScholarDigital Library
- Vijay K. Gurbani, Anita Garvert, and James D. Herbsleb. 2010. Managing a Corporate Open Source Software Asset. Commun. ACM 53, 2 (Feb. 2010), 155--159. Google ScholarDigital Library
- Anja Guzzi, Andrew Begel, Jessica K Miller, and Krishna Nareddy. 2012. Facilitating enterprise software developer communication with CARES. In Software Maintenance (ICSM), 2012 28th IEEE International Conference on. IEEE, 527--536. Google ScholarDigital Library
- Mitchell Joblin, Wolfgang Mauerer, Sven Apel, Janet Siegmund, and Dirk Riehle. 2015. From developer networks to verified communities: a fine-grained approach. In Proceedings of the 37th International Conference on Software Engineering-Volume 1. IEEE Press, 563--573. Google ScholarDigital Library
- Eirini Kalliamvakou, Georgios Gousios, Diomidis Spinellis, and Nancy Pouloudi. 2009. Measuring Developer Contribution From Software Repository Data. MCIS 2009 (2009), 4th.Google Scholar
- Juho Lindman, Matti Rossi, and Pentti Marttiin. 2008. Applying Open Source Development Practices Inside a Company. In Open Source Development, Communities and Quality, Barbara Russo, Ernesto Damiani, Scott Hissam, Björn Lundell, and Giancarlo Succi (Eds.). IFIP - The International Federation for Information Processing, Vol. 275. Springer US, 381--387.Google Scholar
- Gregory Madey, Vincent Freeh, and Renee Tynan. 2002. The open source software development phenomenon: An analysis based on social network theory. AMCIS 2002 Proceedings (2002), 247.Google Scholar
- Ken Martin and Bill Hoffman. 2007. An Open Source Approach to Developing Software in a Small Organization. Software, IEEE 24, 1 (Jan 2007), 46--53. Google ScholarDigital Library
- Catharina Melian and Magnus Mähring. 2008. Lost and Gained in Translation: Adoption of Open Source Software Development at Hewlett-Packard. In Open Source Development, Communities and Quality, Barbara Russo, Ernesto Damiani, Scott Hissam, Björn Lundell, and Giancarlo Succi (Eds.). IFIP - The International Federation for Information Processing, Vol. 275. Springer US, 93--104.Google Scholar
- Andrew Meneely and Laurie Williams. 2011. Socio-technical developer networks: Should we trust our measurements?. In Proceedings of the 33rd International Conference on Software Engineering. ACM, 281--290. Google ScholarDigital Library
- Andreas Neus and Philipp Scherf. 2005. Opening minds: Cultural change with the introduction of open-source collaboration methods. IBM Systems Journal 44, 2 (2005), 215--225. Google ScholarDigital Library
- Andy Oram. 2015. Getting started with inner source. O'Reilly Media, Inc.Google Scholar
- Tim O'Reilly. 2000. Archived email discussion on Open Source and OpenGL. (2000). Last retrieved in January 2018, http://archive.oreilly.com/pub/a/oreilly/ask_tim/2000/opengl_1200.html.Google Scholar
- Martin Pinzger, Nachiappan Nagappan, and Brendan Murphy. 2008. Can developer-module networks predict failures?. In Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of software engineering. ACM, 2--12. Google ScholarDigital Library
- Dirk Riehle. 2015. The five stages of open source volunteering. In Crowdsourcing. Springer, 25--38.Google Scholar
- Dirk Riehle, John Ellenberger, Tamir Menahem, Boris Mikhailovski, Yuri Natchetoi, Barak Naveh, and Thomas Odenwald. 2009. Open collaboration within corporations using software forges. Software, IEEE 26, 2 (2009), 52--58. Google ScholarDigital Library
- Michael Schwind and Christian Wegmann. 2008. SVNNAT: Measuring collaboration in software development networks. In E-Commerce Technology and the Fifth IEEE Conference on Enterprise Computing, E-Commerce and E-Services, 2008 10th IEEE Conference on. IEEE, 97--104. Google ScholarDigital Library
- Phillip Smith and Chris Garber-Brown. 2007. Traveling the Open Road: Using Open Source Practices to Transform Our Organization. In Agile Conference (AGILE), 2007. 156--161. Google ScholarDigital Library
- Klaas-Jan Stol, Paris Avgeriou, Muhammad Ali Babar, Yan Lucas, and Brian Fitzgerald. 2014. Key Factors for Adopting Inner Source. ACM Trans. Softw. Eng. Methodol. 23, 2, Article 18 (April 2014), 35 pages. Google ScholarDigital Library
- Klaas-Jan Stol, Muhammad Ali Babar, Paris Avgeriou, and Brian Fitzgerald. 2011. A comparative study of challenges in integrating Open Source Software and Inner Source Software. Information and Software Technology 53, 12 (2011), 1319--1336. Google ScholarDigital Library
- Richard Torkar, Pau Minoves, and Janina Garrigós. 2011. Adopting free/libre/open source software practices, techniques and methods for industrial use. Journal of the Association for Information Systems 12, 1 (2011), 88--122.Google ScholarCross Ref
- Yuriy Tymchuk, Andrea Mocci, and Michele Lanza. 2014. Collaboration in open-source projects: Myth or reality?. In Proceedings of the 11th working conference on mining software repositories. ACM, 304--307. Google ScholarDigital Library
- Frank van der Linden. 2013. Open Source Practices in Software Product Line Engineering. In Software Engineering, Andrea De Lucia and Filomena Ferrucci (Eds.). Lecture Notes in Computer Science, Vol. 7171. Springer Berlin Heidelberg, 216--235.Google Scholar
- Frank van der Linden, Björn Lundell, and Pentti Marttiin. 2009. Commodification of Industrial Software: A Case for Open Source. Software, IEEE 26, 4 (July 2009), 77--83. Google ScholarDigital Library
- Padmal Vitharana, Julie King, and Helena Shih Chapman. 2010. Impact of internal open source development on reuse: Participatory reuse in action. Journal of Management Information Systems 27, 2 (2010), 277--304. Google ScholarDigital Library
- Robert K Yin. 2013. Case study research: Design and methods. Sage publications.Google Scholar
Index Terms
- The patch-flow method for measuring inner source collaboration
Recommendations
The Business Impact of Inner Source and How to Quantify It
Inner source software development is the practice of using open source practices for firm-internal software development. Practitioner reports have shown that inner source can increase flexibility and reduce costs. Despite the potential benefits of inner ...
What motivates software practitioners to contribute to inner source?
ESEC/FSE 2022: Proceedings of the 30th ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software EngineeringSoftware development organizations have adopted open source development practices to support or augment their software development processes, a phenomenon referred to as inner source. Given the rapid adoption of inner source, we wonder what motivates ...
Inner Source Definition, Benefits, and Challenges
Inner Source (IS) is the use of open source software development practices and the establishment of an open source-like culture within organizations. The organization may still develop proprietary software but internally opens up its development. A ...
Comments