Here’s my ideas:
-
Automated reporting of code/docs contributions.
There’s a lot of non-code contributions we can’t automatically track, but we could do:- OSPRs opened/reviewed/merged
- Forum discussions created/answered/solved
- openedx issues raised/replied/closed
- Working group attendance/actions taken on – this one’s harder since it’s only in Confluence, but maybe?
We’ve had stalled efforts towards a Leaderboard for a while now (see BB-6823), but maybe now is the time to finish this?
- Having these stats automatically generated for each contributor is could replace/prepopulate individual CC sprint updates, and inform annual reviews.
- Having these stats across all contributors could help us measure impact of the CC program.
-
Organization-level reporting of github contributions.
This is a subset of my first suggestion, with slightly different motivations:
- Measure community progress against the “elephant factor” of Axim/2U
- Reward the big contributing organizations
- Highlight any CCs not currently employed by one of the CC orgs who may want jobs.