How SAP runs and documents its InnerSource program
summary
A Cross Product Architecture workgroup runs InnerSource at SAP with a documented strategy, an open-source InnerSource portal, a public Jira backlog and a weekly recorded open forum; roles include coordinator, colleagues, contributors and registered interested observers. Documentation lives as documentation as code (Markdown, PRs) and links to a GitHub-based InnerSource Dojo that uses Pages, issues, actions and a belt system (white/red/black) to claim learning via PRs. They maintain 15 myths collected, project checklists, case studies, and report quarterly; a tiny typo PR led to an ongoing engaged contributor.
AI-written summary · about
chapters (9)
- 0:00Introduction to InnerSource
- 1:06InnerSource program structure
- 3:13Work group communication
- 5:19Documentation strategy
- 6:22Getting started guide
- 9:38General documentation
- 11:47Support and participation
- 13:13InnerSource Dojo
- 15:22Key takeaways
related talks
25mDriving the InnerSource Program at SAP
47mHow Should Your OSPO Work with InnerSource?
28mA Journey to Inner Source
47mWhat Is InnerSource? How Do You Implement It ...
30mInnersource: open source collaboration patterns beyond public FOSS projects
09mInnerSource 101
54mInnerSource 101 and the Apache Way
36mInnerSource at Scale: A Platform-centric Approach