Learning Through Writing
summary
Shows that turning company problems into structured inner source patterns forces clarity by using a fixed template: problem, context, forces, solution, resulting context. The Inner Source Commons collects these into a published book and a Slack channel so authors—developers, product owners, architects—can compare cases and reuse fixes. Writing for an external audience removes jargon, sparks cross-team conversations and even surfaces a documented transparent cross-team decision making pattern.
AI-written summary · about
related talks
47mWhat Is InnerSource? How Do You Implement It ...
54mInnerSource 101 and the Apache Way
39mSolving (team) dependencies - the Open Source way
47mHow Should Your OSPO Work with InnerSource?
12mIs the Future Forked? Navigating an Uncertain Era via InnerSource
30mInnersource: open source collaboration patterns beyond public FOSS projects
25mLooking at the Future of InnerSource
16mHow SAP runs and documents its InnerSource program
