research-article

Key factors for adopting inner source

Authors:
Klaas-Jan Stol

Lero, University of Limerick

Lero, University of Limerick
View Profile

,
Paris Avgeriou

University of Groningen

University of Groningen
View Profile

,
Muhammad Ali Babar

IT University of Adelaide

IT University of Adelaide
View Profile

,
Yan Lucas

Neopost Technologies

Neopost Technologies
View Profile

,
Brian Fitzgerald

Lero, University of Limerick

Lero, University of Limerick
View Profile

ACM Transactions on Software Engineering and Methodology Volume 23 Issue 2Article No.: 18pp 1–35https://doi.org/10.1145/2533685

Published:04 April 2014Publication History

ACM Transactions on Software Engineering and Methodology

Abstract

A number of organizations have adopted Open Source Software (OSS) development practices to support or augment their software development processes, a phenomenon frequently referred to as Inner Source. However the adoption of Inner Source is not a straightforward issue. Many organizations are struggling with the question of whether Inner Source is an appropriate approach to software development for them in the first place. This article presents a framework derived from the literature on Inner Source, which identifies nine important factors that need to be considered when implementing Inner Source. The framework can be used as a probing instrument to assess an organization on these nine factors so as to gain an understanding of whether or not Inner Source is suitable. We applied the framework in three case studies at Philips Healthcare, Neopost Technologies, and Rolls-Royce, which are all large organizations that have either adopted Inner Source or were planning to do so. Based on the results presented in this article, we outline directions for future research.

References

Pär J. Ågerfalk and Brian Fitzgerald. 2008. Outsourcing to an unknown workforce: Exploring opensourcing as a global sourcing strategy. MIS Quart. 32, 2, 385--409. Google ScholarDigital Library
Allan Alter. 2006. Can IT use open source methods to write internal code&quest; CIO Insight, http://www.cioinsight.com/c/a/Expert-Voices/Can-IT-Use-Open-Source-Methods-To-Write-Internal-Code/.Google Scholar
Maureen Jane Angen. 2000. Evaluating interpretive inquiry: Reviewing the validity debate and opening the dialogue. Qualitat. Health Res. 10, 3, 378--395.Google ScholarCross Ref
Matt Asay. 2007. Microsoft Office experiments with open source (development). O'Reilly ONLamp. http://www.oreillynet.com/onlamp/blog/2007/02/microsoft_office_experiments_w.html.Google Scholar
Jai Asundi. 2001. Software engineering lessons from open source projects. In Proceedings of the 1st Workshop on Open Source Software Engineering. Joseph Feller, Brian Fitzgerald, and André van der Hoek (Eds.).Google Scholar
Jai Asundi and Rajiv Jayvant. 2007. Patch review processes in open source software development communities: A comparative case study. In Proceedings of the 40th Annual Hawaii International Conference on Systems Sciences (HICSS). Google ScholarDigital Library
Larry Augustin, Dan Bressler, and Guy Smith. 2002. Accelerating software development through collaboration. In Proceedings of the 24th International Conference on Software Engineering. 559--563. Google ScholarDigital Library
Carliss Y. Baldwin and Kim B. Clark. 2006. The architecture of participation: Does code architecture mitigate free riding in the open source development model&quest; Manag. Sci. 52, 7, 1116--1127. Google ScholarDigital Library
Liz Barnett. 2004. Applying open source processes in corporate development organizations. Forrester Report.Google Scholar
Betanews. 2005. IBM turns to open source development. http://betanews.com/2005/06/13/ibm-turns-to-open-source-development/&percnt;.Google Scholar
Andrea Bonaccorsi and Cristina Rossi. 2003. Why open source software can succeed. Res. Policy 32, 7, 1243--1258.Google ScholarCross Ref
Frederick P. Brooks. 1995. The Mythical Man-Month. Addison Wesley Longman, Inc. Google ScholarDigital Library
Peter G. Capek, Steven P. Frank, Steve Gerdt, and David Shields. 2005. A history of IBM's open-source involvement and strategy. IBM Syst. J. 44, 2, 249--257. Google ScholarDigital Library
Andrea Capiluppi, Klaas-Jan Stol, and Cornelia Boldyreff. 2012. Exploring the role of commercial stakeholders in open source software evolution. In Open Source Systems: Long-Term Sustainability, Imed Hammouda, Björn Lundell, Tommi Mikkonen, and Walt Scacchi (Eds.), Springer, 178--200.Google Scholar
Mike Cohn. 2009. Succeeding with Agile: Software Development Using Scrum. Addison-Wesley. Google ScholarDigital Library
Kieran Conboy and Brian Fitzgerald. 2010. Method and developer characteristics for effective agile method tailoring: A study of XP expert opinion. ACM Trans. Softw. Eng. Methodol. 20, 1 (2010). Google ScholarDigital Library
John W. Creswell. 2007. Qualitative Inquiry & Research Design 2nd Ed. SAGE Publications.Google Scholar
John W. Creswell and Dana L. Miller. 2000. Determining validity in qualitative inquiry. Theory Pract. 39, 3, 124--130.Google ScholarCross Ref
Kevin Crowston, Qing Li, Kangning Wei, U. Yeliz Eseryel, and James Howison. 2007. Self-organization of teams for free/libre open source software development. Inf. Softw. Technol. 49, 6, 564--575. Google ScholarDigital Library
Daniela S. Cruzes and Tore Dybå. 2011. Recommended steps for thematic synthesis in software engineering. In Proceedings of the 5th International Symposium on Empirical Software Engineering and Measurement. 275--284. Google ScholarDigital Library
Jamie Dinkelacker and Pankaj K. Garg. 2001. Corporate source: Applying open source concepts to a corporate environment. In Proceedings of the 1st Workshop on Open Source Software Engineering. Joseph Feller, Brian Fitzgerald, and André van der Hoek (Eds.).Google Scholar
Jamie Dinkelacker, Pankaj K. Garg, Rob Miller, and Dean Nelson. 2002. Progressive open source. In Proceedings of the 24th International Conference on Software Engineering. 177--184. Google ScholarDigital Library
Hakan Erdogmus. 2009. A process that is not. IEEE Softw. 26, 6, 4--7. Google ScholarDigital Library
Justin R. Erenkrantz. 2003. Release management within open source projects. In Proceedings of the 3rd Workshop on Open Source Software Engineering. Joseph Feller, Brian Fitzgerald, Scott A. Hissam, and Karim R. Lakhani (Eds.).Google Scholar
Justin R. Erenkrantz and Richard N. Taylor. 2003. Supporting distributed and decentralized projects: Drawing lessons from the open source community. In Proceedings of the 1st Workshop on Open Source in an Industrial Context. Marc Sihling (Ed.).Google Scholar
FCW. 2009. DOD launches site to develop open-source software. Federal Computer Week. http://fcw.com/articles/2009/01/30/dod-launches-site-to-develop-open-source-software.aspx.Google Scholar
Joseph Feller and Brian Fitzgerald. 2002. Understanding Open Source Software Development. Pearson Education Ltd. Google ScholarDigital Library
Brian Fitzgerald. 2006. The transformation of open source software. MIS Quart. 30, 3, 587--598. Google ScholarDigital Library
Brian Fitzgerald. 2011. Open source software: Lessons from and for software engineering. IEEE Computer 44, 10, 25--30. Google ScholarDigital Library
Karl Fogel. 2005. Producing Open Source Software: How to Run a Successful Free Software Project. O'Reilly Media. Google ScholarDigital Library
Martin Fowler and Jim Highsmith. 2001. The agile manifesto. Softw. Develop. 9, 28--32.Google Scholar
Cristina Gacek and Budi Arief. 2004. The many meanings of open source. IEEE Softw. 21, 1, 34--40. Google ScholarDigital Library
Gary Gaughan, Brian Fitzgerald, Lorraine Morgan, and Maha Shaikh. 2007. An examination of the use of inner source in multinational corporations. In Proceedings of the 1st OPAALS Conference.Google Scholar
Gary Gaughan, Brian Fitzgerald, and Maha Shaikh. 2009. An examination of the use of open source software processes as a global software development solution for commercial software engineering. In Proceedings of the 35th Euromicro Conference on Software Engineering and Advanced Applications (SEAA). 20--27. Google ScholarDigital Library
Judith Goetz and Margeret D. LeCompte. 1984. Ethnography and Qualitative Design in Educational Research. Academic Press.Google Scholar
Ron Goldman and Richard P. Gabriel. 2005. Innovation Happens Elsewhere. Morgan Kaufmann, Chapter 3: What is Open Source&quest;Google Scholar
Egon G. Guba. 1981. Criteria for assessing the trustworthiness of naturalistic inquiries. Edu. Commun. Technol. 29, 2, 75--91.Google Scholar
Vijay K. Gurbani, Anita Garvert, and James D. Herbsleb. 2005. A case study of open source tools and practices in a commercial setting. In Proceedings of the 5th Workshop on Open Source Software Engineering, Joseph Feller, Brian Fitzgerald, Scott A. Hissam, Karim Lakhani, and Walt Scacchi (Eds.). Google ScholarDigital Library
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. 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, 155--159. Google ScholarDigital Library
T. J. Halloran and William L. Scherlis. 2002. High quality and open source software practices. In Proceedings of the 2nd Workshop on Open Source Software Engineering. Joseph Feller, Brian Fitzgerald, Frank Hecker, Scott A. Hissam, Karim Lakhani, and André van der Hoek (Eds.).Google Scholar
James D. Herbsleb and Rebecca E. Grinter. 1999. Architectures, coordination, and distance: Conway's Law and beyond. IEEE Softw. 16, 5, 63--70. Google ScholarDigital Library
Madeleine Leininger. 1994. Evaluation criteria and critique of qualitative research studies. In Critical Issues in Qualitative Research Methods, Janice M. Morse (Ed.), SAGE Publications.Google Scholar
Yvonne S. Lincoln and Egon G. Guba. 1985. Naturalistic Inquiry. SAGE Publications.Google Scholar
Juho Lindman, Mikko Riepula, Matti Rossi, and Pentti Marttiin. 2013. Open source technology in intra-organisational software development--private markets or local libraries. In Managing Open Innovation Technologies, Jenny Ericsson Lundstrom, Mikael Wiberg, Stefan Hrastinski, Mats Edenius, and Pär J. Ågerfalk (Eds.), Springer.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.), Springer, 381--387.Google Scholar
Juho Lindman, Matti Rossi, and Pentti Marttiin. 2009. OSS as a way to sell organizational transformation. In Proceedings of the Information Systems Research Seminar in Scandinavia.Google Scholar
Juho Lindman, Matti Rossi, and Pentti Marttiin. 2010. Open source technology changes intra-organizational systems development--A tale of two companies. In Proceedings of the 18th European Conference on Information Systems.Google Scholar
Alan MacCormack, John Rusnak, and Carliss Y. Baldwin. 2006. Exploring the structure of complex software designs: An empirical study of open source and proprietary code. Manage. Sci. 52, 7, 1015--1030. Google ScholarDigital Library
Guy Martin and Aaron Lippold. 2011. Forge.mil: A case study for utilizing open source methodologies inside of government. In Open Source Systems: Grounding Research, Scott Hissam, Barbara Russo, Manuel Gomes de Mendonça Neto, and Fabio Kon (Eds.), Springer, 334--337.Google Scholar
Ken Martin and Bill Hoffman. 2007. An open source approach to developing software in a small organization. IEEE Softw. 24, 1, 46--53. Google ScholarDigital Library
Steven C. McConnell. 1999. Open-source methodology: Ready for prime time&quest; IEEE Softw. 16, 4, 6--8.Google Scholar
Catharina Melian. 2007. Progressive open source. Ph.D. Dissertation. Stockholm School of Economics.Google Scholar
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.), Springer.Google Scholar
Janne Merilinna and Mari Matinlassi. 2006. State of the art and practice of open source component integration. In Proceedings of the 32nd Euromicro Conference on Software Engineering and Advanced Applications (SEAA). 170--177. Google ScholarDigital Library
Martin Michlmayr and Brian Fitzgerald. 2012. Time-based release management in free and open source (FOSS) projects. Int. J. Open Source Softw. Process. 4, 1, 1--19.Google ScholarCross Ref
Audris Mockus, Roy T. Fielding, and James D. Herbsleb. 2002. Two case studies of open source software development: Apache and Mozilla. ACM Trans. Softw. Eng. Methodol. 11, 3, 309--346. Google ScholarDigital Library
Audris Mockus and James D. Herbsleb. 2002. Why not improve coordination in distributed software development by stealing good ideas from open source&quest;. In Proceedings of the 2nd Workshop on Open Source Software Engineering. Joseph Feller, Brian Fitzgerald, Frank Hecker, Scott A. Hissam, Karim R. Lakhani, and André van der Hoek (Eds.), 19--25.Google Scholar
Lorraine Morgan, Joseph Feller, and Patrick Finnegan. 2011. Exploring inner source as a form of intraorganisational open innovation. In Proceedings of the 19th European Conference on Information Systems.Google Scholar
Andreas Neus and Philipp Scherf. 2005. Opening minds: cultural change with the introduction of open-source collaboration methods. IBM Syst. J. 44, 2, 215--225. Google ScholarDigital Library
Todd Ogasawara. 2008. Microsoft CodeBox: Lessons from the open source community. http://www. oreillynet.com/onlamp/blog/2008/05/microsoft_codebox_lessons_from.html.Google Scholar
Patrick Oor and René Krikhaar. 2008. Balancing technology, organization, and process in inner source: Bringing inner source to the TOP. In Dagstuhl Seminar Proceedings. http://drops.dagstuhl.de/opus/volltexte/2008/1548.Google Scholar
Tim O'Reilly. 1999. Lessons from open source software development. Commun. ACM 42, 4, 33--37. Google ScholarDigital Library
Tim O'Reilly. 2000. O'Reilly network: Ask Tim: Is licensing what makes open source succeed&quest; http://www.linuxtoday.com/infrastructure/2000121601306OPCYSW.Google Scholar
David L. Parnas. 1972. On the criteria to be used in decomposing systems into modules. Commun. ACM 15, 12, 1053--1058. Google ScholarDigital Library
Mirja Pulkkinen, Oleksiy Mazhelis, Pentti Marttiin, and Jouni Meriluoto. 2007. Support for knowledge and innovations in software development—Community within company: Inner source environment. In Proceedings of the 3rd International Conference on Web Information Systems and Technologies. 141--150.Google Scholar
Eric S. Raymond. 2001. The Cathedral & the Bazaar: Musings on Linux and Open Source by an Accidental Revolutionary. O'Reilly Media. Google ScholarDigital Library
Dirk Riehle, J. Ellenberger, T. Menahem, B. Mikhailovski, Y. Natchetoi, B. Naveh, and T. Odenwald. 2009. Open collaboration within corporations using software forges. IEEE Softw. 26, 2, 52--58. Google ScholarDigital Library
Bram Riemens and Kees van Zon. 2006. PFSPD short history. http://pfspd.sourceforge.net/history.html.Google Scholar
Peter C. Rigby, Brendan Cleary, Frederic Painchaud, Margaret-Anne Storey, and Daniel M. German. 2012. Contemporary peer review in action: Lessons from open source development. IEEE Softw. 29, 56--61. Issue 6. Google ScholarDigital Library
Peter C. Rigby, Daniel M. German, and Margaret-Anne Storey. 2008. Open source software peer review practices: A case study of the Apache Server. In Proceedings of the 30th International Conference on Software Engineering. ACM, 541--550. Google ScholarDigital Library
Jason Robbins. 2002. Adopting OSS methods by adopting OSS tools. In Proceedings of the 2nd Workshop on Open Source Software Engineering. Joseph Feller, Brian Fitzgerald, Frank Hecker, Scott A. Hissam, Karim R. Lakhani, and André van der Hoek (Eds.).Google Scholar
Jason Robbins. 2005. Adopting open source software engineering (OSSE) practices by adopting OSSE tools. In Perspectives on Free and Open Source Software, Joseph Feller, Brian Fitzgerald, Scott A. Hissam, and Karim R. Lakhani (Eds.), MIT Press, 245--264.Google Scholar
Colin Robson. 2002. Real World Research (2nd Ed.). Blackwell Publishers.Google Scholar
Winston W. Royce. 1987. Managing the development of large software systems. In Proceedings of the 9th International Conference on Software Engineering. Originally published in Proceedings of WESCON'70. 328--338. Google ScholarDigital Library
Per Runeson, Martin Höst, A. Rainer, and Björn Regnell. 2012. Case Study Research in Software Engineering: Guidelines and Examples. John Wiley & Sons, Inc., Hoboken, NJ. Google ScholarDigital Library
Walt Scacchi. 2004. Free and open source development practices in the game community. IEEE Softw. 21, 1, 59--66. Google ScholarDigital Library
Ken Schwaber and Mike Beedle. 2002. Agile Software Development with Scrum. Prentice Hall. Google ScholarDigital Library
Andrew Schwarz, Manjari Mehta, Norman Johnson, and Wynne W. Chin. 2007. Understanding frameworks and reviews: A commentary to assist us in moving our field forward by analyzing our past. SIGMIS Data B. Adv. Inf. Syst. 38, 3, 29--50. Google ScholarDigital Library
Carolyn B. Seaman. 1999. Qualitative methods in empirical studies of software engineering. IEEE Trans. Softw. Eng. 25, 4, 557--572. Google ScholarDigital Library
Anthony Senyard and Martin Michlmayr. 2004. How to have a successful free software project. In Proceedings of the 11th Asia-Pacific Software Engineering Conference (APSEC). Google ScholarDigital Library
Panagiotis Sfetsos, Lefteris Angelis, and Ioannis Stamelos. 2006. Investigating the extreme programming system--An empirical study. Empirical Softw. Eng. 11, 2, 269--301. Google ScholarDigital Library
Srinarayan Sharma, Vijayan Sugumaran, and Balaji Rajagopalan. 2002. A framework for creating hybrid-open source software communities. Inf. Syst. J. 12, 1, 7--25.Google ScholarCross Ref
Phillip Smith and Chris Garber-Brown. 2007. Traveling the open road: Using open source practices to transform our organization. In Proceedings of the Agile Conference (AGILE). IEEE. Google ScholarDigital Library
Andrea Stellman, Jennifer Greene, and Auke Jilderda. 2009. Inner source. In Beautiful Teams: Inspiring and cautionary Tales from Veteran Team Leaders, Andrew Stellman and Jennifer Greene (Eds.), O'Reilly Media, 103--111.Google Scholar
Klaas-Jan Stol. 2011. Supporting product development with software from the bazaar. Ph.D. Dissertation. University of Limerick.Google Scholar
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. Inf. Softw. Technol. 53, 12, 1319--1336. Google ScholarDigital Library
E. Burton Swanson. 1976. The dimensions of maintenance. In Proceedings of the 2nd International Conference on Software Engineering. 492--497. Google ScholarDigital Library
Janice M. Swanson and Linda Chapman. 1994. Inside the black box: Theoretical and methodological issues in conducting evaluation research using a qualitative approach. In Critical Issues in Qualitative Research Methods, Janice M. Morse (Ed.), SAGE Publications.Google Scholar
Darryl K. Taft. 2005. IBM adopts open development internally. http://www.eweek.com/c/a/Linux-and- Open-Source/IBM-Adopts-Open-Development-Internally/.Google Scholar
Darryl K. Taft. 2006. IBM to employ open-source development style for tools. http://www.eweek.com/c/a/Application-Development/IBM-to-Employ-OpenSource-Development-Style-for-Tools/.Google Scholar
Darryl K. Taft. 2009. Community-source development appeals in tough times. http://mobile.eweek.com/c/a/Application-Development/CommunitySource-Development-Appeals-in-Tough-Times/.Google Scholar
Richard Torkar, Pau Minoves, and Janina Garrigós. 2011. Adopting free/libre/open source software practices, techniques and methods for industrial use. J. Associ. Inf. Syst. 12, 1, 88--122.Google ScholarCross Ref
Linus Torvalds. 1999. The Linux edge. In Open Sources: Voices from the Open Source Revolution, Chris DiBona, Sam Ockman, and Mark Stone (Eds.), O'Reilly Media.Google Scholar
Linus Torvalds. 2000. Linux Kernel mailing list. https://lkml.org/lkml/2000/8/25/132.Google Scholar
Frank van der Linden. 2009. Applying open source software principles in product lines. UPGRADE X, 3, 32--40.Google Scholar
Frank van der Linden, Björn Lundell, and Pentti Marttiin. 2009. Commodification of industrial software: A case for open source. IEEE Softw. 26, 4, 77--83. Google ScholarDigital Library
Frank van der Linden, Klaus Schmid, and Eelco Rommes. 2007. Software Product Lines in Action: The Best Industrial Practice in Product Line Engineering. Springer. Google ScholarDigital Library
June M. Verner, J. Sampson, V. Tosic, N.A. Abu Bakar, and Barbara A. Kitchenham. 2009. Guidelines for industrially-based multiple case studies in software engineering. In Proceedings of the 3rd International Conference on Research Challenges in Information Science. IEEE, 313--324.Google Scholar
Padmal Vitharana, Julie King, and Helena Shih Chapman. 2010. Impact of internal open source development on reuse: Participatory reuse in action. J. Manage. Inf. Syst. 27, 2, 277--304. Google ScholarDigital Library
Xiaofeng Wang, Ilona Kuzmickaja, Klaas-Jan Stol, Pekka Abrahamsson, and Brian Fitzgerald. 2014. Microblogging in open source software development: The case of Drupal using Twitter. IEEE Softw. DOI:10.1109/MS.2013.98.Google Scholar
Jacco Wesselius. 2008. The bazaar inside the cathedral: Business models for internal markets. IEEE Softw. 25, 3, 60--66. Google ScholarDigital Library
Robert K. Yin. 2003. Case Study Research: Design and Methods (3rd. Ed.). SAGE Publications, Thousand Oaks, CA.Google Scholar

Index Terms

Key factors for adopting inner source
1. Social and professional topics
  1. Professional topics
    1. Management of computing and information systems
      1. Project and people management
      2. Software management
        Software maintenance
2. Software and its engineering
  1. Software creation and management

Recommendations

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 ...
Read More
An Investigation into Inner Source Software Development: Preliminary Findings from a Systematic Literature Review
OpenSym '18: Proceedings of the 14th International Symposium on Open Collaboration

Given the value and effectiveness of open source software development to date, practitioners are keen to replicate these practices inside their respective corporations. This application of open source practices inside the confines of a corporate entity ...
Read More
Examining the Impact of Adopting Inner Source Software Practices
OpenSym '18: Proceedings of the 14th International Symposium on Open Collaboration

Open Source software (OSS) has been highly prevalent in both practice and research. Given the value and effectiveness of OSS development to date, practitioners are keen to replicate these practices inside their respective corporations. This application ...
Read More

Comments

Login options

Check if you have access through your login credentials or your institution to get full access on this article.

Full Access

Get this Article

Published in
ACM Transactions on Software Engineering and Methodology Volume 23, Issue 2
March 2014
319 pages
ISSN:1049-331X
EISSN:1557-7392
DOI:10.1145/2600788
Editor:
David S. Rosenblum
Issue’s Table of Contents
Copyright © 2014 ACM
Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than the author(s) must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected].
Sponsors
In-Cooperation
Publisher
Association for Computing Machinery
New York, NY, United States
Publication History
- Published: 4 April 2014
- Accepted: 1 September 2013
- Revised: 1 April 2013
- Received: 1 July 2012
Published in tosem Volume 23, Issue 2

Permissions
Request permissions about this article.
Request Permissions

Check for updates
Author Tags
Case study
framework
inner source
open-source development practices
Qualifiers
- research-article
- Research
- Refereed
Conference
Funding Sources
Other Metrics
View Article Metrics

Article Metrics
- 46
  Total Citations
  View Citations
- 1,226
  Total Downloads
- Downloads (Last 12 months)107
- Downloads (Last 6 weeks)9
Other Metrics
View Author Metrics
Cited By
View all

PDF Format

View or Download as a PDF file.

PDF

eReader

View online with eReader.

eReader

Key factors for adopting inner source

ACM Transactions on Software Engineering and Methodology

Abstract

References

Cited By

Index Terms

Recommendations

Inner Source Definition, Benefits, and Challenges

An Investigation into Inner Source Software Development: Preliminary Findings from a Systematic Literature Review

Examining the Impact of Adopting Inner Source Software Practices