Please enable JavaScript.
Coggle requires JavaScript to display documents.
InnerSource Patterns - Coggle Diagram
InnerSource Patterns
Adoption
Valuation Challenges
How to measure a project's business value
Cross team project valuation
How long does it take them to consume your project output?
How long would it otherwise take them to home-roll the value of your project output for themselves?
What percentage of your project output is actually useful for them?
How much time on an ongoing basis (ideally per-use) would they otherwise spend maintaining their home-rolled solution?
Cultural Challenges
Unrecognized effort
Praised participant
Trusted commiter
Technical Challenges
Not meeting everyone's needs
Common requirements
Fear of shared support responsibility
Service vs Library
Project is difficult to contribute and use
Core team
Organization Challenges
Discouragement of contributing resource
Contrated contributor
Rejection of accepting contribution
30 days warranty
Radical change of management
Review committee
Fear of shared responsibility
Service vs Library
Not enough maintainers to scale
Trusted commiters
Difficult cross-teams coordination
Transparent cross team decision making using RFCs
Project without an owner or maintainer
Core team
Cross Legal entities challenges
Concern on legal liabilities or cross-company accounting
InnerSource License
Begin
Program Setup
Management hesitates to invest in InnerSource
Start as a experiment
Sufficient geographical distribution of developers
Sufficient departmental mix of developers
Openness of communication within community
Career path based on merit within community
Democratic decision making within community
Metrics in InnerSource
Number of PRs from external contributors
Number of PRs from external contributors that are merged
Number of issues created from external contributors
Number of clone or forks from external guests
Amount of code reuse across projects
Mean-time-to-review
Number of automated test runs on PRs
Number of repositories using InnerSource components
Number of visits from external guests
Slow Community growth hinders InnerSource
Dedicated community leader
is experienced in the Open Source working model or similar community based working models,
has the required soft-skills to act as a natural leader,
leads by example and thus justifies his position in the community meritocracy,
is an excellent networker,
is an excellent networker
inspires community members
can communicate effectively to both executive management and developers
is able to handle the managerial aspects of community work.
Ideally, empower the community to nominate a community leader themselves.
Project Setup
Hard to assess a project quickly
Standard base documentation
Ad-hoc communication hinders project growth
Communication tooling
Instransparent roadmap and direction of the roadmap
Issue tracker use cases
Grow
Discovery Challenges
Can't find matching projects
Gig Marketplace
InnerSource Portal
Difficult to find active projects
Repository Activity Score
Scale
Self education Challenges
Not aware about InnerSource best practices
Maturity Model