The Value of InnerSource Culture
summary
IBM Z adapts InnerSource to a high‑assurance mainframe with 60 years of tooling, converting hundreds of legacy scripts into a searchable InnerSource portal and GitHub org, enforcing project templates and starter kits and standardized CI pipelines. Adoption starts slow but accelerates once security reviewers and execs see real wins: a retired maintainer’s bug fixed by five contributors, reuse that saves days, interns who pivot careers, a bounty program and promotion credit that make participation measurable. Security posture improves via approved stacks and automated reviews.
AI-written summary · about
chapters (8)
- 0:00Introduction to InnerSource
- 2:54InnerSource for developers
- 11:28Communicating to leadership
- 17:28Incentivizing participation
- 21:25Best practices for projects
- 25:36Upskilling through InnerSource
- 28:48Community and long-term benefits
- 31:16Success stories and security
related talks
28mA Journey to Inner Source
25mDriving the InnerSource Program at SAP
18m(Y)Our Journey to Inner Source
14mAdopting InnerSource to maximize Developer Experience
19mWhen there is no alternative to InnerSource
30mInnersource: open source collaboration patterns beyond public FOSS projects
17mEnhancing Developer Experience through InnerSource and Platform Engineering
01h 00mBuilding a testing- and quality-driven culture at IBM