-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Track the number of contributors from repos that use the json-schema topic, over time #3
Comments
hey @benjagm @Relequestual I can work on this issue. Could you assign this to me? |
@Kaku-g I think it's possible to work on this now, having reviewed an existing PR. Do you feel you understand the expectations related to "over time"? |
@Relequestual So for 'over time' contributions we need some database to store past and current data. Also the repos for which it should keep track include all the internal repos(within json-schema org) + external repos(throughout github that uses json-schema topic)? |
@Kaku-g No database here, just storing the data in files in the repo. Is this something you're still interested to try do, or was that only in relation to GSoC? |
Hi, I'd like to work on #1 and this as well, could you please assign these to me? |
Depends on: #1
We define contributors as users who have comitted to the git history.
It should be quite easy to get the current number of contributors using just a few lines.
Getting this historically shouldn't be super difficult, as you can checkout git repos without code (just the log) and do an analysis.
If we expanded the definition of contributions to include Issues and PR reviews, this would probably be different to what most people expect, and getting at historic data would be much more effort, although not impossible.
Would need to do something similar to https://github.com/api7/contributor-graph
There may be an easier approach, but I haven't been able to find one when looking for about half an hour.
(Look at the nice graphs it makes from the data it collects!)
The text was updated successfully, but these errors were encountered: