Applying InnerSource for DATEV's Shared Frontend Library
summary
A front-end library built with GitLab-backed InnerSource reaches 99 teams, 314 contributors and grows its maintainer pool from 3 → 12, using Apache-style governance and documented 26 repeatable practices. Measured outcomes: median issue-to-merge is 30 days for maintainers, ~14 days for InnerSource contributors and 11 days when the issue author fixes it; about 15% of merge requests come from InnerSource contributors. Evidence of knowledge transfer includes 23 good‑Samaritan comments per month and long‑lived issue references; data is anonymized and coordinated with the works council.
AI-written summary · about
chapters (18)
- 0:00Introduction to talk
- 0:51About DATEV and its context
- 2:14Author's inner source journey
- 3:41Frontend library history
- 5:28Introducing Duckle library
- 6:10Inner source practices documented
- 7:55Infrastructure and maintainers
- 9:00Contributions and growth metrics
- 10:47Was inner source worth it?
- 11:30Data analysis overview
- 12:13Development speed improvements
- 14:18Volunteer contributor types
- 15:41Knowledge transfer insights
- 16:46Synchronous communication role
- 17:52Challenges faced
- 20:26Maintainer role demands
- 21:07Success and key takeaways
- 21:49Future of inner source at DATEV
related talks
25mDriving the InnerSource Program at SAP
14mAdopting InnerSource to maximize Developer Experience
30mInnersource: open source collaboration patterns beyond public FOSS projects
28mA Frictionless Inner Source Journey
18m(Y)Our Journey to Inner Source
28mA Journey to Inner Source
16mAnalysis of development velocity in an InnerSource context
19mWhen there is no alternative to InnerSource