Solving (team) dependencies - the Open Source way
summary
Adopting InnerSource practices via the InnerSource Commons playbook, Slack channel and a documented learning path turns blocking waits into actionable patches: teams check out internal repos, open issues in an archived searchable communication hub, submit draft patches, and trusted reviewers give continuous code review instead of end-of-feature gates. Role definitions like trusted committers and short contribution docs lower onboarding friction, reduce handoffs, and measurably speed deliveries while increasing upstream open source contributions.
AI-written summary · about
chapters (10)
- 0:00Start
- 1:00Solving Team Dependencies the Open Source Way
- 10:52Technical Dependencies
- 17:13What Is Your Prerequisite in Open Source
- 18:58What Would I Expect from a Trusted Committer
- 20:31Contributors
- 22:17Open Communication
- 26:48Three Challenges That You Would Like To Address within Your Organization by Bringing Open Source Collaboration Practices in Your Own Team
- 30:39Communication Hub
- 31:19Integrate into Existing Processes
related talks
52mBottom-Up Open Source Culture
30mInnersource: open source collaboration patterns beyond public FOSS projects
09mInnerSource 101
24mInnerSource Patterns for Success
24mBuilding a Foundation for Open Collaboration
15mAdopting Open Source Practices To Build More Inclusive Products and Services
54mInnerSource 101 and the Apache Way
44mBringing Open-Source Brilliance to Scrum Teams: A Guide to Enhanced Collaboration