You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As projects adopt InnerSource, there are signs of such adoption on the corresponding source code repositories.
6
+
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`.
7
+
8
+
One challenge with this metric, is defining an InnerSource repository, as there is no clear cut definition.
9
+
Some companies may have strict requirements that define an InnerSource repository, while others may adopt a _self-declaration_.
10
+
11
+
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.
12
+
13
+
**Synopsis**: Number of source code repositories that adopt InnerSource
14
+
15
+
**Unit of Measurement**: Number of repositories
16
+
17
+
**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.
18
+
19
+
e.g. 10% of repositories are InnerSource
20
+
21
+
It's more interesting to observe this metric's trend over time.
22
+
23
+
**Measuring**
24
+
25
+
Examples:
26
+
- Measure the number of GitHub repositories tagged with the `innersource` topic.
27
+
- Measure the number of repositories that are above a given threshold using an automated maturity score calculation
28
+
29
+
## Related InnerSource Patterns
30
+
-[InnerSource Portal](https://patterns.innersourcecommons.org/p/innersource-portal) - typically shows the number of InnerSource projects
31
+
-[Repository Activity Score](https://patterns.innersourcecommons.org/p/repository-activity-score) - defines a score for ranking active projects, usable as a criteria to identify InnerSource repositories
32
+
-[Standard Base Documentation](https://patterns.innersourcecommons.org/p/base-documentation) - describe common files used to document different aspects of InnerSource projects
33
+
-[Maturity Model](https://patterns.innersourcecommons.org/p/maturity-model) - defines levels of maturity for InnerSource projects and can help classify a repository as InnerSource.
# **Question:** What is the InnerSource adoption trend?
4
+
5
+
This question is something an InnerSource program asks while fostering the adoption of InnerSource.
6
+
Lack of adoption, or stagnant adoption may reveal that it is necessary to rethink the program strategy or investigate impediments.
7
+
8
+
## Related Metrics
9
+
10
+
|**Metric**|**How it answers the question**|**Gotchas**|
11
+
| --- | --- | --- |
12
+
|[Number of InnerSource repositories](../metrics/number-of-innersource-repositories.md)| The number of (source code) repositories that are directly related to the adoption of the practice. | Depending on how you define _InnerSource repositories_, it can report incorrect results |
click adoption-trend.md "https://github.com/InnerSourceCommons/managing-inner-source-projects/blob/main/measuring/questions/adoption-trend.md" "What is the InnerSource adoption trend?"
56
62
click who-contributes.md "https://github.com/InnerSourceCommons/managing-inner-source-projects/blob/main/measuring/questions/who-contributes.md" "Who contributes to the InnerSource project?"
57
63
click who-uses.md "https://github.com/InnerSourceCommons/managing-inner-source-projects/blob/main/measuring/questions/who-uses.md" "Who uses the InnerSource project?"
0 commit comments