-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Establish a process/tools for awareness of contribution metrics #22
Comments
Open questions:
|
@Shreyanand and I are tracking some of these metrics in this doc and we are also working on creating an initial notebook which fetches GitHub metrics from Augur to evaluate/visualize some of the metrics. (Related issue: AICoE/data-driven-development#4) |
Initial notebook exploring/visualizing some of the metrics: https://github.com/operate-first/community/blob/main/metrics/community_metrics.ipynb |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with /lifecycle rotten |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
@MichaelClifford yes we can close this out for now and open newer issues to track other tasks |
Create a tracking process and metrics tooling to go forward from this baseline.
For inclusion tracking, be sure to breakdown the functional contribution areas. This helps ensure that clumps of e.g. only-Red-Hatters don’t get hidden in the tracking.
Document and track the ways the project is contributor-driven. This means, do contributors have access to all aspects of the project and the ability to have a seat at the decision making table for each aspect?
The text was updated successfully, but these errors were encountered: