-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GQM: Adoption trend and related metric #78
GQM: Adoption trend and related metric #78
Conversation
This commit is based on the a value that is observed at SAP, where we periodically check the number of projects that have self-registered to our InnerSource Projects portal, by assigning a topic to their repositories. Related issues: - InnerSourceCommons/ispo-working-group#109
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
very well written, thank you. I just added two comments
Fixed typo. Co-authored-by: Michael Graf <mi.graf@sap.com>
Related review comment: - InnerSourceCommons#78 (comment)
…g-inner-source-projects into gqm__sap-2024-03
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this work, @dellagustin-sap!
@jeffabailey I tried out the GQM script on this branch, but I don't see these new files getting picked up on the auto-created graph. Is it because they are not attached to a goal?
I'm thinking about triggering the generation of the graph and attaching it to the PR when it's created to clarify the behind-the-scenes work that happens after merging. Right now, though, I'll make sure the commit occurs upon merge. |
Co-authored-by: Jeff Bailey <776901+jeffabailey@users.noreply.github.com>
Co-authored-by: Jeff Bailey <776901+jeffabailey@users.noreply.github.com>
Co-authored-by: Jeff Bailey <776901+jeffabailey@users.noreply.github.com>
Co-authored-by: Jeff Bailey <776901+jeffabailey@users.noreply.github.com>
Co-authored-by: Jeff Bailey <776901+jeffabailey@users.noreply.github.com>
Co-authored-by: Jeff Bailey <776901+jeffabailey@users.noreply.github.com>
Co-authored-by: Jeff Bailey <776901+jeffabailey@users.noreply.github.com>
I manually generated the mermaid graph using the script from @jeffabailey , here is the result. graph LR;
subgraph GQM[Goals, Questions, Metrics]
%% begin nodes
find-projects.md[Find InnerSource Projects]
reduce-duplication.md[Reduce duplication]
adoption-trend.md[What is the InnerSource adoption trend?]
who-contributes.md[Who contributes to the InnerSource project?]
who-uses.md[Who uses the InnerSource project?]
code-contributions.md[Code contributions]
contribution-distance.md[Contribution Distance]
number-of-innersource-repositories.md[Number of InnerSource repositories]
usage-count.md[Usage count]
%% end nodes
%% begin edges
find-projects.md-->who-uses.md
find-projects.md-->who-contributes.md
reduce-duplication.md-->who-uses.md
adoption-trend.md-->number-of-innersource-repositories.md
who-contributes.md-->code-contributions.md
who-contributes.md-->contribution-distance.md
who-uses.md-->usage-count.md
%% end edges
%% begin clicks
click find-projects.md "https://github.com/InnerSourceCommons/managing-inner-source-projects/blob/main/measuring/goals/find-projects.md" "Find InnerSource Projects"
click reduce-duplication.md "https://github.com/InnerSourceCommons/managing-inner-source-projects/blob/main/measuring/goals/reduce-duplication.md" "Reduce duplication"
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?"
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?"
click who-uses.md "https://github.com/InnerSourceCommons/managing-inner-source-projects/blob/main/measuring/questions/who-uses.md" "Who uses the InnerSource project?"
click code-contributions.md "https://github.com/InnerSourceCommons/managing-inner-source-projects/blob/main/measuring/metrics/code-contributions.md" "Code contributions"
click contribution-distance.md "https://github.com/InnerSourceCommons/managing-inner-source-projects/blob/main/measuring/metrics/contribution-distance.md" "Contribution Distance"
click number-of-innersource-repositories.md "https://github.com/InnerSourceCommons/managing-inner-source-projects/blob/main/measuring/metrics/number-of-innersource-repositories.md" "Number of InnerSource repositories"
click usage-count.md "https://github.com/InnerSourceCommons/managing-inner-source-projects/blob/main/measuring/metrics/usage-count.md" "Usage count"
%% end clicks
end
subgraph Legend
direction TB
goal[Goal]
question[Question]
metric[Metric]
classDef goals stroke:green,stroke-width:2px;
class goal,find-projects.md,reduce-duplication.md goals
classDef questions stroke:orange,stroke-width:2px;
class question,adoption-trend.md,who-contributes.md,who-uses.md questions
classDef metrics stroke:purple,stroke-width:2px;
class metric,code-contributions.md,contribution-distance.md,number-of-innersource-repositories.md,usage-count.md metrics
end
|
Nice work @dellagustin-sap! 🎉 🙌 |
This commit is based on the a value that is observed at SAP, where we periodically check the number of projects that have self-registered to our InnerSource Projects portal, by assigning a topic to their repositories.
I tried to generalize it a bit, so it goes a little bit beyond on how we use it.
Related issues: