Description
Overview
Following recent discussions about the OSPO Book, I'd like to propose adding a chapter on InnerSource. This would explore how InnerSource practices work alongside Open Source Program Offices and why this relationship matters for organizations developing their open source capabilities.
Context and Rationale
The connection between InnerSource and OSPOs might not be immediately obvious to everyone, so let me explain why this addition would be valuable. InnerSource uses open source principles within organizational boundaries, and in practice, most InnerSource Program Offices operate within or alongside OSPOs. This relationship exists because:
- Natural progression pathway: InnerSource serves as a stepping stone to open source participation, preparing developers and organizations for external contributions
- Shared methodologies: Both use similar collaboration models, code review processes, and community-building practices
- Talent development: InnerSource creates a safe environment for employees to learn open source skills before engaging with external communities
- Cultural alignment: The transparency, meritocracy, and collaborative mindset required for InnerSource directly supports OSPO objectives
- Risk mitigation: Organizations can experiment with open source practices internally before making external commitments
- Proven organizational structure: Most successful ISPOs are embedded within OSPOs, leveraging shared infrastructure and governance models
It's worth noting that the OSPO Alliance's Good Governance Initiative already dedicates Chapter 3 to InnerSource, recognizing it as an integral part of the open source ecosystem. According to the OSPO Alliance resource, many leading companies have successfully implemented InnerSource initiatives or InnerSource Program Offices (ISPOs):
Technology Companies:
- Microsoft
- IBM
- SAP
- Nokia
- Siemens
Financial Services:
- Banco de Santander
- Société Générale
- PayPal
Automotive:
- Mercedes
- Bosch
- Renault
Other Industries:
- BBC (Media)
- Nike (Retail)
- Comcast (Telecommunications)
- Ericsson (Telecommunications)
- SNCF Connect & Tech (Transportation)
- Philips (Healthcare/Electronics)
- Engie (Energy)
- Thales (Aerospace/Defense)
- VeePee (E-commerce)
This existing recognition in similar resources, along with the diverse range of industries adopting InnerSource, underscores the importance of covering InnerSource in our OSPO Book.
Instead of creating artificial boundaries between "open source" and "closed source" areas within a company, InnerSource helps transform the entire internal environment to be more compatible with open source practices. From an organizational perspective, InnerSource accelerates innovation cycles and helps break down silos using proven open source methods. The incentive programs and cultural changes required for successful InnerSource directly support broader OSPO objectives.
What This Chapter Could Cover
The chapter could explore the practical relationship between InnerSource and OSPOs, including governance models, implementation strategies, and real-world case studies from the InnerSource Commons community. We could also address common misconceptions, such as the myth that InnerSource detracts from open source contributions, when evidence shows it actually builds capability and often leads to more external contributions.
Success stories like Kubernetes, Docker, and React Native – all of which started as internal projects before becoming major open source initiatives – demonstrate the potential of this approach.
Starting the Conversation
I'm opening this issue to gauge interest and start a discussion about how InnerSource content might fit into the OSPO Book. I'd love to hear thoughts from the community about what aspects of InnerSource would be most valuable to cover, and how this aligns with the book's overall vision and timeline.
Let's use this space for brainstorming and gathering perspectives from both OSPO practitioners and those with InnerSource experience. Once we have a sense of interest and direction, we can determine next steps together.
References: