Managing InnerSource Projects
English
English
  • Summary
  • Introduction
    • Scenarios
    • Framework
    • Authors and Reviewers
  • Infrastructure
    • Basic Infrastructure
    • Comparing How Inner-Sourced Your Infra Is
    • Authors and Reviewers
  • What, When and How to Measure
    • Goals using Metrics
      • Use Goals, Questions, and Metrics
        • Goals
          • Find InnerSource Projects
          • Reduce Duplication
        • Questions
          • What is the InnerSource Adoption Trend?
          • Who contributes to the InnerSource project?
          • Who Uses
        • Metrics
          • Code Contributions
          • Contribution Distance
          • Number of InnerSource repositories
          • Usage Count
    • Areas of Analysis
    • Goal-Question-Metric Approach
    • Strategy
    • Examples of Interest
    • References
    • Authors and Reviewers
  • Governance
  • Tooling
    • GitHub Strategy
    • GitHub Configuration
    • GitLab Strategy
    • GitLab Configuration
    • Authors and Reviewers
Powered by GitBook
On this page
  • Metric: Number of InnerSource repositories
  • Related InnerSource Patterns
Edit on GitHub
Export as PDF
  1. What, When and How to Measure
  2. Goals using Metrics
  3. Use Goals, Questions, and Metrics
  4. Metrics

Number of InnerSource repositories

Last updated 1 month ago

Metric: Number of InnerSource repositories

As projects adopt InnerSource, there are signs of such adoption on the corresponding source code repositories. Examples are the presences of a CONTRIBUTING.md file, a "How to Contribute" section on the README.md file or repository topics in GitHub such as innersource.

One challenge with this metric, is defining an InnerSource repository, as there is no clear cut definition. Some companies may have strict requirements that define an InnerSource repository, while others may adopt a self-declaration.

Another challenge is that companies that use (entirely or partially) the concept of a monorepo may need to find a different unit of measure to observe, as a single repository may be used for many projects or software packages.

Synopsis: Number of source code repositories that adopt InnerSource

Unit of Measurement: Number of repositories

Interpretation: Comparing an absolute number to a range does not make sense in this context. Comparing percentages does make sense, but there's no strong base for comparison.

e.g. 10% of repositories are InnerSource

It's more interesting to observe this metric's trend over time.

Measuring

Examples:

  • Measure the number of GitHub repositories tagged with the innersource topic.

  • Measure the number of repositories that are above a given threshold using an automated maturity score calculation

Related InnerSource Patterns

  • - typically shows the number of InnerSource projects

  • - defines a score for ranking active projects, usable as a criteria to identify InnerSource repositories

  • - describe common files used to document different aspects of InnerSource projects

  • - defines levels of maturity for InnerSource projects and can help classify a repository as InnerSource.

⬑ back to the overall graph
InnerSource Portal
Repository Activity Score
Standard Base Documentation
Maturity Model