Incentivizing Good Community Citizenship with Contributor Leaderboards
summary
Leaderboards rank contributors by metrics drawn from trace data (git, mailing lists, issue trackers) and work best when scoring is transparent and revisable, automated with tools like grimolap and auger and presented in domain-specific lists (translations, triage, UX). Implement identity unification carefully for privacy, use sliding windows or reset leaderboards every 3 months to let new contributors rise, and show immediate neighbors so people see achievable targets rather than unreachable top ranks.
AI-written summary · about
chapters (8)
- 0:00Introduction to leaderboards
- 2:49How leaderboards work
- 7:05Metrics and trace data
- 14:26Open source metrics tools
- 15:52Goal Question Metric approach
- 17:59Start small with metrics
- 18:20Best practices for leaderboards
- 22:53Recap and contact info
related talks
49mPanel Discussion: Contributor Leaderboards to Incentivize Good Community Citizenship
46mMeasuring Community Health
35mBeyond Code: The Importance of Elevating Non-Code Contributions
34mCommunity Data: What to Measure and Why?
42mEnhancing Open Source Collaboration: From Incentive Programs to Data-Driven Contribu...
26mAre we being inclusive with our community recognitions?
40mContributor Growth Strategies for OSS Projects
36mCommunity Data: What to Measure and Why?