CHAOSS Evolution Working Group
Formerly known as the Growth Maturity and Decline Working Group. This repository is where new metrics are actively developed and prepared for release. Released metrics are available on the CHAOSS Website: https://chaoss.community/metrics/
Table of Contents
Evolution is a working group focused on the lifecycle of open source projects. We do not valence the stages, but seek to build awareness of those stages among consumers of these metrics. Decline can be ok when a project's utility is waning; or terrible if 20% of the entire internet relies on that project. Context matters, and we are not the arbiters of your context. The "valence" of "good/bad" emerges from use cases and YOUR context.
For each area of interest, we're following the goal-question-metric methodology defining questions and metrics that help to answer them.
The evolution metrics dealt with in this working group are organized in focus areas:
|Code Development Activity||Learn about the types and frequency of activities involved in developing code.|
|Code Development Efficiency||Learn how efficiently activities around code development get resolved.|
|Code Development Process Quality||Learn about the processes to improve/review quality that are used (for example: testing, code review, tagging issues, tagging a release, time to response, CII Badging).|
|Issue Resolution||Identify how effective the community is at addressing issues identified by community participants.|
|Community Growth||Identify the size of the project community and whether it is growing, shrinking, or staying the same.|
Please note that the work in the focus areas is still in progress.
A few steps as good starting points for contributing to the Evolution Working group:
- Introduce yourself on the CHAOSS mailing list explaining your interest.
- Then, you can have a look at the archives of the mailing lists, at the minutes of past meetings, and at the
- By proposing new goals for a focus area, or new questions for learning about those goals, or new metrics for answering those questions. Or by helping to refine goals, and questions.
See more details in the contributing file.
- Sean P. Goggins
- Jesus M. Gonzales-Barahona
- Georg Link
- Matt Germonprez
- Kevin Lumbard
- Armstrong Foundjem
The criteria for becoming a core contributor is to participate at least once per month over a period of 3 months. Participation could include providing feedback in the Evolution working group meetings, providing feedback on docs, or making other contributions on GitHub (commits / issues). People not participating over a 3 month period may be removed as core contributors.
If you'd like to be on our squad, an easy way to start is by going through the issue list and fixing some or adding to the conversation.
The documents in this repositories are released under the MIT License. See LICENSE for details.
Copyright © 2018-2020 CHAOSS Project