Explore the InnerSource Patterns
Welcome to the comprehensive library
of InnerSource patterns.
This collection includes validated best practices published in our book, as well as initial drafts
and “donut” patterns currently being refined by the community.
Pattern Types
Maturity Level 2: Structured (The InnerSource Patterns Book)
These patterns are the most mature. Each has been reviewed by the community and has at least one known instance of successful use in a real-world organization. Below we have compiled five examples of mature patterns:
-
30 Day Warranty:
The contributing team provides bug fixes for a set period to build trust with the receiving team.
-
Trusted Committer:
Recognizing and rewarding frequent contributors by giving them maintainer-like influence.
-
Common Requirements:
Aligning needs across different teams to build shared code in a single repository.
-
Standard Base Documentation:
Using README.md and CONTRIBUTING.md to enable self-service onboarding.
-
Transparent Cross-Team Decision Making using RFCs:
Using “Requests for Comments” to build commitment before making design changes.
Pattern Types
Maturity Level 1: Initial (Work in Progress)
These patterns are currently in the incubation phase. They represent promising solutions that are still being documented or awaiting further validation from the community. An example of 5 such patterns are included below:
-
Modular Code:
Helping teams understand that decoupled architectures are essential for code reuse.
-
InnerSource Ambassadors:
Local volunteers who bridge the gap between their departments and the central InnerSource office.
-
Overcoming the Not-Invented-Here Mindset:
Shifting culture toward “Proudly Found Elsewhere” to reduce redundant work.
-
AI Code Generation Context:
Guiding AI tools to produce code that aligns with project-specific standards.
-
InnerSource as a Career Booster:
Highlighting how InnerSource participation grows skills and internal visibility.
Pattern Types
Donut Patterns (Seeking Solutions)
Donuts are patterns where the problem and forces are well-defined, but a proven solution is still needed. We invite you to contribute your experiences to help fill these gaps.
- How to Defeat the Hierarchical Constraints
- Organizational Mindset Change
- Bad Weather For Liftoff
- Incentive mechanisms to foster voluntary contribution
- Duplicated Projects