This talk seeks to introduce the CHAOSS -Community Health Analytics for Open Source Projects- to the InnerSource practitioners. Metrics and KPIs are of importance for the InnerSource Commons as seen in the several talks and discussions during the last summits.
CHAOSS was born in 2017 under the Linux Foundation umbrella and this is a hub of OSS projects and organizations participating in the definition of metrics of interest for Open Source projects.
As active members of CHAOSS, there are some lessons learnt when dealing with those metrics and KPIs, either at the theoretical definition and from a software implementation that might be worth exploring across the InnerSource ecosystem.
This talk will bring this discussion and how to potentially build bridges between both
6. OBJECTIVES
Establish a standard
implementation of
metrics ● Produce integrated open source
software for analyzing software
community development
● Build reproducible project
health reports
17. Short Term Business Goal: Increase the adoption of the InnerSource projects
within the organization.
Question #1: How many people are contributing month by month?
Question #2: Are our contributors base increasing?
Question #3: What are the data sources with lower barriers to contribute?
Question #4: How many months in a row have we had a growth in the number of
contributors?
Proposed panel: contributors growth.
18.
19. Short Term Business Goal: Reduce time to market of our products
Question #1: How long does it take to close an issue and a PR?
Question #2: Are we improving in our software development cycle once we have
InnerSource in place?
Question #3: What are the fastest data sources? (issues, PRs?)
Question #4: What are the most efficient BUs? What can we learn from them?
Proposed panel: efficiency panel.
20.
21. Short Term Business Goal: Increase InnerSource projects engagement within the
organization
Question #1: Which projects contributors/BUs interacts most with?
Question #2: What is the general trend my contributors follow across data
sources?
Question #3: What path are my contributors following when getting involved with
InnerSource projects?
Proposed panel: engagement panel
Proposed panel: lifecycle
29. OSS behaviours not happening in IS
(e.g., collaboration or communication)
What about exploring those at the ISC from a
CHAOSS perspective?
Benchmarking
30. What do you mean by
collaboration?
commit?
active contributor?
communication?
31. Metrics is a hot topic at ISC
No discussion beyond initial steps
Metric granularity is too low
What about Use Cases?
Benchmarking?
32. Present ISC at CHAOSSCon in Brussels
Start framing the metrics discussion
- Pattern? A new WG?
Build some bridges and check what we
can learn from each other
NEXT STEPS
33. The Metrics Journey
Metrics and KPIs for an InnerSource Office
Thoughts on Adopting InnerSource and/or
Agile
REFERENCES