Are we being inclusive with our community recognitions?
summary
Open source recognition currently skews to GitHub/GitLab repo metrics, which hides chat, forum and meetup work on Discord/Slack/Matrix and by non-developers; the talk argues for measure contributions beyond repos, using nomination forms, community voting and short coffee chats to surface unseen helpers, and for offer private recognition when public spotlight harms participation. It recommends avoiding volume-based rankings, treating “heroes” as an advisory cohort, sending immediate DMs or swag for timely thanks, and tracking outcomes of these changes.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:54Why are recognitions important
- 5:04Common mistakes
- 8:03The problem
- 12:42Public recognitions
- 17:58Looking beyond the code
- 18:52Coffee chats
- 20:23Other things
- 22:22Ranking like contributors
- 22:59Conclusion
related talks
35mBeyond Code: The Importance of Elevating Non-Code Contributions
49mPanel Discussion: Contributor Leaderboards to Incentivize Good Community Citizenship
42mEnhancing Open Source Collaboration: From Incentive Programs to Data-Driven Contribu...
23mIncentivizing Good Community Citizenship with Contributor Leaderboards
23mKeeping Your Open Source Project Accessible to All
21mThe Hidden Heroes: How Non-Technical Contributors Find Their Place in Open Source Communities
34mRecognizing the driving forces of impactful OS projects
30mTokenism in Open Source: Diversity or Decoration?
