Measuring Community Health
summary
Shows concrete metrics and tools: counting labeled community merge requests in GitLab, tracking first-time contributor mugs and follow-up via vendor-collected addresses, using merge-request labels plus issue thumbs up as priority to judge impact, and publishing a transparent CHAOS dashboard with opt-out re‑anonymization. Reports a rising monthly community-contribution count, uses GrimoireLab/OpenHub-style contributor histories, and warns that attribution to broader programs and privacy consent remain unresolved but measurable through proxies and program-level reports.
AI-written summary · about
chapters (5)
related talks
34mCommunity Data: What to Measure and Why?
43mBuilding and Supporting Open Source Communities Through Metrics
39mCollaboration as a Key Health Indicator for OSS Communities
30mCommunity Metrics What to Measure and Why?
26mBuilding & Supporting Open Source Communities Through Metrics
30mMeasuring the Impact of Community Events
44mWhy Is My Community In Danger?
23mIncentivizing Good Community Citizenship with Contributor Leaderboards