-
Notifications
You must be signed in to change notification settings - Fork 154
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
CHAOSS metrics and additional tooling #1320
Comments
I'm familiar with CHAOSS but not with "CHAOSS metrics" - can you tldr what they are? |
I was referring to the CHAOSS view in the report that is generated (Node example) |
CHAOSS has defined close to 90 metrics. The page with the four visualizations in Cauldron that are under "CHAOSS" was an attempt at creating a "CHAOSS Report" with some interesting metrics that go beyond the elementary metrics. We have not advanced this further but shifted focus to creating Metric Models and Practitioner Guides. |
Meeting notes:
|
This started as a Slack discussion
I created some reports using Cauldron (Bitergia tooling) that digest all the GitHub activity from any org/repo you want to track. These reports contain a lot of relevant information, including CHAOSS metrics, and a way to export this data into a Kibana instance.
Personally, I find this fascinating, and I think it could be very relevant as a tool for the CPC to better understand how projects are doing in terms of risks like bus factors, etc and when on boarding new projects to get a much better context. Additionally, it is a great tool to see the evolution once certain decisions are made. For example, it is very easy to see the impact in Express of the Express Forward plan six months later.
This tool is complementary to the one provided by the LFX that we are trying to adopt in the projects (additional context). I am very happy to do a small demo showcasing the Express case and metrics on both platforms. I can also invite the Bitergia team, as they can provide tons of context for us, especially regarding CHAOSS metrics.
For additional context:
The text was updated successfully, but these errors were encountered: