ABSTRACT
Open Source has changed the landscape for software development organizations. There are numerous very successful open source projects involving hundreds of developers dispersed worldwide, and many organizations are interested in adopting the principles and practices to build "open" communities within their organizations. This has been termed "InnerSource" and this paradigm is attracting considerable attention from the software industry. The InnerSource Commons is an industry-driven community that is actively pursuing an agenda to share knowledge, experiences, and lessons learned on adopting InnerSource. One means of doing this is to encode "best practices" as patterns. In this paper, we present a number of patterns that the InnerSource Commons community has distilled, which other organizations that are interested in InnerSource can adopt and tailor to their respective organizational settings.
- S. Bonewald. 2017. Understanding the InnerSource Checklist. O'Reilly.Google Scholar
- M. Capraro and D. Riehle. 2017. Inner Source Definition, Benefits, and Challenges. Comput. Surveys 49, 4 (2017). Google ScholarDigital Library
- Chatham. 2002. Chatham House Rule. (2002). https://www.chathamhouse.org/about/chatham-house-rule.Google Scholar
- J. Dinkelacker, P. Garg, R. Miller, and D. Nelson. 2002. Progressive Open Source. In Proc. International Conference on Software Engineering. Google ScholarDigital Library
- B. Fitzgerald. 2011. Open Source Software: Lessons from and for Software Engineering. Computer 44, 10 (2011). Google ScholarDigital Library
- V.K. Gurbani, A. Garvert, and J.D. Herbsleb. 2006. A case study of a corporate open source development model. In Proceedings of the 28th International Conference on Software Engineering. Google ScholarDigital Library
- V.K. Gurbani, A. Garvert, and J.D. Herbsleb. 2010. Managing a Corporate Open Source Software Asset. Commun. ACM 53, 2 (2010). Google ScholarDigital Library
- A. Mockus and J.D. Herbsleb. 2002. Why not improve coordination in distributed software development by stealing good ideas from open source. In The 2nd Workshop on Open Source Software Engineering: Meeting Challenges and Surviving Success.Google Scholar
- A. Neus and P. Scherf. 2005. Opening minds: Cultural change with the introduction of open-source collaboration methods. IBM Systems Journal 44, 2 (2005). Google ScholarDigital Library
- A. Oram. 2015. Getting Started with InnerSource. O'Reilly.Google Scholar
- T. O'Reilly. 1999. Lessons from Open-Source Software Development. Commun. ACM 42, 4 (1999). Google ScholarDigital Library
- T. O'Reilly. 2000. In response to Matt Feinstein on "Open Source and OpenGL". (2000). http://archive.oreilly.com/pub/a/oreilly/ask_tim/2000/opengl_1200.html.Google Scholar
- D. Riehle, J. Ellenberger, T. Menahem, B. Mikhailovski, Y. Natchetoi, Barak Naveh, and T. Odenwald. 2009. Open Collaboration within Corporations Using Software Forges. IEEE Software 26, 2 (2009). Google ScholarDigital Library
- K.J. Stol, P. Avgeriou, M. Babar, Y. Lucas, and B. Fitzgerald. 2014. Key Factors for Adopting Inner Source. ACM Trans Software Engineering and Methodology 23, 2 (2014). Google ScholarDigital Library
- K.J. Stol, A. Babar, P. Avgeriou, and B. Fitzgerald. 2011. A comparative study of challenges in integrating Open Source Software and Inner Source Software. Information and Software Technology 53, 12 (2011). Google ScholarDigital Library
- K.J. Stol and B. Fitzgerald. 2015. Inner Source---Adopting Open Source Development Practices in Organizations: A Tutorial. IEEE Software 32, 4 (2015).Google Scholar
- Frank van der Linden. 2009. Applying open source software principles in product lines. UPGRADE X, 3 (2009), 32âĂŞ40.Google Scholar
- J. Wesselius. 2008. The Bazaar inside the Cathedral: Business Models for Internal Markets. IEEE Software 25, 3 (2008). Google ScholarDigital Library
- T. Yao and P. Sudarsan. 2016. InnerSource Patterns: Establishing a new inner source patterns community. (2016). presentation at the InnerSource Commons Fall Summit 2016, https://drive.google.com/file/d/0B7_9iQb93uBQbnlkdHNuUGhpTXc/view.Google Scholar
Index Terms
- Innersource patterns for collaboration
Recommendations
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 ...
Sharing Source Code with Clients: A Hybrid Business and Development Model
Open innovation and the recent emphasis on client involvement imply the emergence of hybrid software licensing models combining the limited openness of source code with traditional value appropriation logic. A practical hybrid licensing model responds ...
How are Open Source Practices Possible within a Medical Diagnostics Company?: Developing and Testing a Maturity Model of Inner Source Implementation
OpenSym '17: Proceedings of the 13th International Symposium on Open CollaborationOpen Source Software (OSS) development has seen a considerable increase in attention over the last few years. The success of various OSS projects, such as Linux and Apache, is now widely recognized. Many organizations have shown interest not only in ...
Comments