Innersource: Bringing Open Source Principles to your Organization

Transcript

1. Innersource: Bringing Open Source Principles to your Organization Adebayo, Ilerioluwa Software Engineer
2. Agenda 1. What is Innersource? 1. Key Benefits 1. Implementation 4. Best Practices 5. Tools and Technologies 6. Challenges and Solutions
3. It is the use of open source methods and strategies within an organization’s proprietary software. What is Innersource?
4. What it means ? • Not all software can be open-sourced but they can benefit from process pioneered by the open source community • Establishing an open-source culture in the organisation
5. Growing Adoption According to Stackoverflow 2023 Developer Survey, Around 14% of teams have an innersource initiative in their organisation
6. Key Benefits of Innersource • Discoverability and Code Reuse • Innovation & Transparency • Talent Retention and Attraction
7. Discoverability and Code Reuse Most common metric when talking about Innersource is Code Reuse. But, what are actual measurable metrics that code reuse brings? • Saves Time and Cost • Improve Code quality • Increased Collaboration
8. Save time and Cost Accelerated Development Cycles Reusing code means less time developing it, Innersource can result in a more efficient and effective development by reducing time to market, development cost, and generally increasing development efficiency regardless of company size.
9. Improve Code quality and Collaboration - Reducing silos and simplifying collaboration throughout the entire organisation. - Innersource can facilitate collaboration with external contributors, such as partner organizations or the wider open source community. - More collaborators create more opportunities to catch bugs, get better feedback and investigate issues with maintainer/project owner involved. - More contribution to bug fixes and this way code review is a part of the process throughout development.
10. Innovation - Sharing and spreading ideas - Integrating new cultures, perspectives and ideas to your code - Benefit from a diverse team and improve creativity
11. Talent Retention and Attraction - Opportunity to work the same way internally by reading high quality code and fixing bugs in others code - Increased Employee engagement e.g Less working in isolation - Internal Community: Building a community around your software can lead to more innovation and new ideas. Sharing and talk about your knowledge. All these are green flags for developers. Developers love open source
13. Define Goals - Save cost: Shipping meaningful innersource projects or experiments and getting feedback. - Code quality: Improve the ratio of time spent fixing bugs. - Innovation: Number of new ideas coming from innersource projects.
14. Assess Readiness Evaluate the organization's readiness for Innersource adoption. Assess factors like the existing development culture, infrastructure, and processes. Identify any potential challenges or areas that need improvement to effectively implement Innersource.
15. Train and Educate - Train your middle management - Provide training and education to developers and teams on the principles and practices of Innersource. E.g Organise workshops, talks, write about it on your organisation blog e.t.c - Communicate in their language. - Ensure they understand the benefits, processes, and tools involved. Offer workshops, documentation, and resources to support their transition to Innersource workflows.
16. Challenges Solutions 1. Cultural Resistance 1. Ineffective Governance and Coordination 1. Intellectual property concerns 1. Quality Control 1. Scalability and Project Visibility • Foster a culture of transparency and collaboration • Establish a Governance model with clear roles and responsibilities • Implement proper licensing practices and policies • Define coding standards and best practices that everyone should follow • Implement project management tools to provide visibility and oversight
18. Tools and Technologies • Version Control Systems GitHub, GitLab, Bitbucket • Documentation Platforms Confluence, BackStage, Read the Docs, Notion • Analytics and Metric Tools GitHub Insights • License & Compliance Tools FOSSA, WhiteSource • CI/CD Tools CircleCI, Jenkins
19. CONCLUSION… Remember It’s okay if it’s not called Innersource Innersource can look different from company to company, but always shares the same goals: adopting open source tools, practices, and culture to build proprietary software.
20. Links https://bit.ly/osca-innersource
21. THANK YOU! • Site: https://adebayo.dev • Twitter: @adeileri