You can use the table below to measure your own open source project community engagement health.
Please see HEALTHCHECKS for more information on all the measurements below.
Category | Measurement | Status | Advice | Notes |
---|---|---|---|---|
Project Maturity | Following the "Getting Started" guidelines | |||
Project Maturity | Following CII Best Practices | |||
Project Maturity | Regular release cadence | |||
Project Maturity | Roadmap quality | |||
Project Viability | Documentation thoroughness | |||
Project Viability | Low elephant factor (if applicable) | |||
Growth of Community | Role definitions | |||
Growth of Community | Path to maintainership | |||
Growth of Community | Continually onboarding new contributors | |||
Growth of Community | Distribution of work | |||
Growth of Community | Decision distribution - central vs distributed | |||
Growth of Community | Communication channels are in place and used effectively | |||
Diversity of Community | Number of contributors | |||
Diversity of Community | Contributing organizations - monthly | |||
Diversity of Community | Non-code contributions | |||
Diversity of Community | Contributor breadth | |||
Attentiveness of Maintainers | Recognition of contributors | |||
Attentiveness of Maintainers | Retrospectives | |||
Attentiveness of Maintainers | Release note completeness | |||
Attentiveness of Maintainers | Transparency | |||
User Community Engagement | User training material (visible, being updated) | |||
User Community Engagement | Communications channel for user questions are used actively by both users and maintainers | |||
User Community Engagement | Obvious process for user bug reports and feature requests | |||
User Community Engagement | Meetings for user engagement, bof, best practices |