rseng-community-metrics

# Community health metrics A community's health can be measured, and the CHAOSS project has standardized how: metrics for growth, responsiveness, retention and risk that turn "the community feels quiet lately" into checkable numbers. The same discipline as rseng-software-metrics applies unchanged: metrics LOCATE community problems, humans judge them; trends beat snapshots; and every metric can be gamed, so keep them plural and tie them to actions. ## The metrics that matter, and their sources Nearly everything comes from data the forge already has - git history, issues, PRs, reviews - all computable by an agent: - Growth and activity: new contributors per period, active contributors (authored, reviewed, triaged or commented - count ALL contribution kinds, the rseng-citation-metadata lesson), contribution volume by type. - Responsiveness: time to first response on issues and PRs (the promise rseng-community-governance made checkable), review latency, time to merge or close. First-response time is the single best predictor of whether a first-time contributor returns. - Retention and the funnel: how many first-time contributors make a second contribution (the conversion rate), casual-to-regular progression, time since last activity for previously regular contributors (quiet departures are findable before they are final). - Risk: bus factor (what fraction of recent work concentrates in how few people - the elephant-factor framing), single-maintainer ...