An InnerSource Transformation Story
summary
IBM Z runs a continuous InnerSource program that adapts open collaboration to a 60-year mainframe stack, guaranteeing 99.99999% uptime while reducing duplicated tooling across 100+ components and thousands of developers. A dedicated Z InnerSource team (two full‑time tools engineers) moves proprietary PLX/assembler tools into GitHub, adds templates, CI security scans, Dependabot, and documentation in a portal described as the “Google of internal tools”. Projects like Pyrackf and PIPCS and Ambitus progress from inner source to open source or product use, with hackathons, bounties and executive buy‑in driving adoption.
AI-written summary · about
chapters (9)
- 0:00Introduction to InnerSource
- 1:54Mainframe and Z Overview
- 3:58InnerSource Benefits and Challenges
- 6:23Tooling and Documentation Efforts
- 9:12Z InnerSource Team Initiatives
- 10:58Standards and Community Growth
- 14:07Security in InnerSource
- 17:59Success Patterns and Events
- 20:47Executive Support and Incentives
related talks
41mHow InnerSource Is Beginning to Change Software Development at IBM. Lessons Learned...
25mLooking at the Future of InnerSource
19mFrom InnerSource To Open Source: Building a Dual-Focused OSPO in a Tradition...
25mDriving the InnerSource Program at SAP
47mHow Should Your OSPO Work with InnerSource?
09mInnerSource 101
36mInnerSource at Scale: A Platform-centric Approach
47mWhat Is InnerSource? How Do You Implement It ...