Skip to content

Commit 402b6c4

Browse files
authored
Merge pull request #191 from Michadelic/patch-1
Fine-tuning for Repository Activity Score pattern
2 parents d9b7160 + c0e0d53 commit 402b6c4

File tree

1 file changed

+5
-7
lines changed

1 file changed

+5
-7
lines changed

patterns/2-structured/repository-activity-score.md

Lines changed: 5 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ When InnerSource is practiced for a long time or scales beyond a certain number
2121

2222
A list of InnerSource projects should not be considered a static resource, but an exciting place to discover and explore new and active projects, just like a news page listing the most interesting topics of the day first. Thus it is beneficial when the order of the projects is regularly updated and changes according to the project's popularity and activity.
2323

24-
These considerations let to a first prototype to calculate a repository activity score, which worked surprisingly well and determines an ever-changing order of projects according to their activity.
24+
These considerations led to a first prototype to calculate a repository activity score, which worked surprisingly well and determines an ever-changing order of projects according to their activity.
2525

2626
## Context
2727

@@ -44,7 +44,7 @@ A centralized approach for calculating an applying the repository activity score
4444
The repository activity score is a numeric value that represents the (GitHub) activity of an InnerSource project. It is derived automatically from repository statistics like GitHub stars, watches, and forks and may be enriched with KPIs from other tools or manual evaluations.
4545

4646
In addition, it considers activity parameters like last update and creation date of the repo to give young projects with a lot of traction a boost.
47-
Projects with contributing guidelines and issues (public backlog) receive a higher ranking as well.
47+
Projects with contributing guidelines, active participation stats, and issues (public backlog) receive a higher ranking as well.
4848

4949
All of this can be fetched and calculated automatically using the result set of the [GitHub search API](https://developer.github.com/v3/search/#search-repositories) and [GitHub statistics API](https://developer.github.com/v3/repos/statistics/). Other code versioning systems like BitBucket, Gitlab, Gerrit can be integrated as well if a similar API is available.
5050

@@ -96,7 +96,7 @@ Contributors are free to commit a part of their time to InnerSource project. The
9696

9797
Projects can be sorted and presented by repository activity score to give a meaningful order in a portal presenting projects to potential new contributors. The score can be calculated on the fly or in a background job that evaluates all projects on a regular basis and stores a list of results.
9898

99-
A crawler that regularly searches all InnerSource repositories (e.g. tagged with a certain topic in GitHub) can be a helpful addition as well. It provides a ranked list of projects that can be used as an input for tools like the [InnerSource Portal](innersource-portal.md), a search engine, or an interactive chat bot.
99+
A crawler that regularly searches all InnerSource repositories (e.g. tagged with a certain [topic](https://github.com/topics) in GitHub) can be a helpful addition as well. It provides a ranked list of projects that can be used as an input for tools like the [InnerSource Portal](innersource-portal.md), a search engine, or an interactive chat bot.
100100

101101
## Rationale
102102

@@ -108,11 +108,9 @@ Used in SAP's InnerSource project portal to define the default order of the Inne
108108

109109
When proposed to InnerSourceCommons in July 2020, this pattern emerged.
110110

111-
## Status (optional until merging)
111+
## Status
112112

113-
* First Draft: 30th July 2020
114-
* Second Draft: 5th August 2020
115-
* Third Draft: 6th August 2020
113+
Proven
116114

117115
## Author(s)
118116

0 commit comments

Comments
 (0)