Jonatan Matajonmatum.com
conceptsnotesexperimentsessays
© 2026 Jonatan Mata. All rights reserved.v2.1.1
Concepts

InnerSource

Application of open-source development practices within an organization, allowing teams to contribute to other teams' projects with transparent processes.

seed#innersource#collaboration#open-source#culture#contribution

What it is

InnerSource applies open-source practices within an organization. Any team can see, use, and contribute to other teams' code, following transparent contribution processes.

Principles

  • Transparency: code visible to the entire organization
  • Open contribution: anyone can submit PRs
  • Code review: maintainers review contributions
  • Documentation: README, CONTRIBUTING, AGENTS.md
  • Governance: clear roles (contributor, trusted committer, maintainer)

Benefits

  • Reduce code duplication across teams
  • Accelerate development by reusing existing solutions
  • Improve quality through more eyes on code
  • Develop cross-team talent

Connection with monorepos

Monorepos facilitate InnerSource by having all code in one place with shared tooling.

InnerSource maturity levels

LevelPracticesSignals
1. Visible codeInternal repos accessible to allTeams can read other teams' code
2. Ad-hoc contributionsCross-team PRs acceptedSome cross-team PRs per quarter
3. Formal processCONTRIBUTING.md, trusted committersDefined roles, review SLAs
4. Established cultureContributing outside the team is normal>20% of PRs are cross-team

Why it matters

Inner source applies open source practices within the organization. It allows any team to contribute to any repository, reducing silos and duplication. It is especially valuable in large organizations where teams solve similar problems independently.

References

  • InnerSource Commons — Community and patterns.
  • InnerSource Patterns — InnerSource Commons, 2024. InnerSource patterns catalog.
  • InnerSource Patterns — GitHub — InnerSource Commons, 2024. Patterns repository.

Related content

  • Monorepos

    Code organization strategy where multiple projects coexist in a single repository, sharing dependencies, configuration, and build tooling.

  • Developer Experience

    Discipline focused on optimizing developer productivity, satisfaction, and effectiveness through well-designed tools, processes, and environments.

  • GitHub

    Collaborative development platform built on Git. More than repository hosting — it's the central hub for code review, CI/CD, project management, and open source collaboration.

Concepts