"Who are we helping" metric
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by reviewing the repository’s existing issue, pull request, and metric-aggregation entry points; the issue names no files or tests. Trace how reporters and team information are currently obtained, then define the expected aggregate output for solved issues and self-service pull requests and add coverage for that behavior.
Written by the indexing model from the issue text.
Description
Some InnerSource projects essentially provide platform capabilities for the organisation, meaning that they "only" have internal teams as customers. Understanding and talking about the customer value and business value of these platforms sometimes can be tricky.
With a bit of a workaround though it becomes easier: Look at issues and PRs created and check which team (filtered down to e.g. product teams with external customers) the reporter is assigned to. Then provide aggregate information on how many times each of these teams was unblocked by solved issues and how many times such teams were able to unblock themselves with PRs.
- Dominant language
- Python
- Stars
- 542
- Forks
- 94
- Avg merge
- 10h 3m
- Merged PRs (30d)
- 9
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github-community-projects/issue-metrics
-
enhancement keep
Difficulty 4/5 3-5 days Newbie friendliness 35/100
github-community-projects/issue-metrics#535 · 2 comments · 5 reactions ·
-
enhancement keep
Difficulty 3/5 1-2 days Newbie friendliness 35/100
github-community-projects/issue-metrics#312 · 6 comments ·
-
enhancement keep
Difficulty 5/5 Over a week Newbie friendliness 30/100
github-community-projects/issue-metrics#190 · 5 comments ·
-
enhancement keep
Difficulty 4/5 3-5 days Newbie friendliness 25/100
github-community-projects/issue-metrics#156 · 5 comments ·
-
enhancement good first issue keep
Difficulty 4/5 3-5 days Newbie friendliness 48/100
github-community-projects/issue-metrics#114 · 6 comments ·
All issues in github-community-projects/issue-metrics
Similar issues
-
A new VOLTTRON_HOME starts with agent isolation mode on (string comparison of a boolean default)Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
llm translation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
FAIRmat-NFDI/sand#239 ·
Maintainers usually reply within 1 day
-
bug P2
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
coco-research/coco#539 ·
Maintainers usually reply within 1 day
-
dependencies
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
JustBeanie/hass-volcano-hybrid#34 ·
Maintainers usually reply within 1 day