You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
Sources of data to support the various aspects of projects health
github (contributors, code activities, PRs)
discord (engagement level, responsiveness)
information contributed by project maintainers and members (technology usage)
| Focus | Aspect | Detail | Supporting Data |
|---|
| Community | Growth | new interested individuals and conversion to contributor | - the number of contributors to the code base (github PRs)
- the number of contributors to design discussions (discord)
- the number of contributors to requirements (github issues)
|
| Diversity | no single organization keeps the project live | - the number of organizations contributing to the code base (github PRs)
|
| Retention | interesting/useful projects attract contributors, healthy projects retain them | - active contributor longevity (github PRs, discord)
|
| Maturity | reflects the lifecycle phase a project is in. This gives context to the others, what may be a red flag for a mature project may not be so for a young one | - when was the first commit
- frequency of releases (more mature projects have more regular cadence and have a higher success rate to achieve the cadence)
|
| Friendliness | to new contributors/ideas | - number of good-first-issues
- new contributors onboarded
- can new ideas be accommodated, even if that may lead to forking of the code base
|
| Responsiveness | how long until proposed changes (code, design, bug reports, etc.) are given attention? | - time to resolve PRs and issues (github)
- time to respond to questions (discord)
|
| Code | Usefulness | is the project being adopted by customers and tire kickers? | - usage information provided by customers and developers
- number of questions from clients trying to use the code
- docker pulls
- release binary downloads
- tagged online resources: case studies, presentations, mentorship programs
- amount of research publications it generates
|
| Production Readiness | is the current code base coherent enough to be usable in a real-world scenario? | - release number (latest is 1.0.0 or later?)
- test coverage
- performance and reliability testing data
- user documentation
|
| Fundamental Metrics |
| - commit rate: number of commits per month etc.
- maybe indicators that would allow us to catch when a project starts to "cool down" or "people are leaving it for other options"
|
| Docs |
| |
| Amount of Innovation | how cutting edge? | - ePrint, arxiv
- measures academic interests
|