Internal Open Source
summary
Describes how Sberbank Online scaled its mobile app development by adopting an "internal open-source" process: opening feature development to many internal contributors while retaining architectural and quality control. Explains the problem—developer teams became a bottleneck as internal requesters multiplied—and the solution—cultural and process changes to let anyone implement features under centralized oversight.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:06Sberbank Online challenges
- 5:26Team structure issues
- 10:14Transformation approach
- 13:24Modular architecture
- 19:29Platform team
- 23:47Daily PRs and testing
- 28:14Unit tests and coverage
- 31:35Bottlenecks and overload
- 38:43Internal open source
- 43:24Results and plans
- 44:49Q&A
related talks
39mGetting started with internal open source
52mBottom-Up Open Source Culture
54mInnerSource 101 and the Apache Way
45mFostering an Open Environment for Developers in a Regulated Industry
45mInnerSource and OSPOs: Institutionalizing Open Source Culture Change
47mWhat Is InnerSource? How Do You Implement It ...
21mScaling Internal Collaboration with Open Source Operating Models
41mPanel Discussion: The Growth of InnerSource in Financial Services