-
Notifications
You must be signed in to change notification settings - Fork 55
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
First stab at figuring out the number of very active mentors #206
Conversation
most_active_mentors.py
Outdated
|
||
Open questions: | ||
- should there be an option to limit this to certain users, e.g. core maintainers? | ||
- should there be a limit to how many comments per PR we consider to avoid having |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, a limit makes sense to me. It may make sense to say that after 1 comment someone was involved with a PR, and after 3 comments they were heavily involved, and to stop counting after that. Those numbers are my personal thresholds in my mind but could be set to configurable numbers with reasonable defaults.
most_active_mentors.py
Outdated
- should there be an option to limit this to certain users, e.g. core maintainers? | ||
- should there be a limit to how many comments per PR we consider to avoid having | ||
the statistic dominated by contested PRs? | ||
- should this metric count consecutive comments coming from the same user as only |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great question. In this case I would also consider the length of the comment. If somebody has a lot to say and they break that up into several meaningful comments, I would see that as several contributions worth counting.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see this as really valuable work! Thanks for working on it! ✨
For larger projects or organizations, it would be especially great to be able to see this data to be able to quickly find active projects that lack mentorship.
next step for this one looks like working on fixing the tests. |
8b788f0
to
ebb61da
Compare
I fixed the linter errors, ran the tests. Still on my TODO list:
|
Output added to markdown and call added - and fixed the issues with the original design. Still missing:
|
In the last commit I added mentor counting results to json output. In addition max number of comments per issue as well as the cutoff number for heavily involved mentors are now configurable. Tests seem to run through locally, including the ones I added.
With that I think this is ready for getting a closer look and feedback. Wish you Happy Easter (no, no Easter eggs hidden here ;) ) |
This adds the call to mentor counter and displays the results in markdown including first tests for this functionality.
This adds two configuration options: One to enable mentor counting and one for configuring how many comments a user needs to leave in discussions, PRs. and issues to be counted as an active mentor.
This adds mentor counting output to json format. In addition this change makes max number of comments to evaluate configurable as well as the cutoff for heavily involved mentors.
9133bca
to
1a01093
Compare
Fixed merging errors. There are two lint warnings still open that I can't figure out. |
I can dig into some of these linting errors. I'll set aside some time this coming week. |
Signed-off-by: Zack Koppert <[email protected]>
Signed-off-by: Zack Koppert <[email protected]>
@MaineC I was able to correct the linting errors and override some unreasonable linting rules. Ready to click the ready for review button? |
Clicked the button. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Just a couple asks. Thank you for your contribution.
Co-authored-by: Jason Meridth <[email protected]>
Co-authored-by: Jason Meridth <[email protected]>
Remove merge residual
Remove lib only needed for testing.
Co-authored-by: Jason Meridth <[email protected]>
Finally back from Easter vacation/ family birthdays/ cold caught after that: Thanks for the feedback. I hope I caught all of the suggestions. |
set type of `enable_mentor_count` to `bool`
change tests to handle boolean change of enable_mentor_count
Relates to #114
This is a work in progress pull request. The goal is to extract the number of very active mentors in a project based on number of comments they left in issues and pull requests.
In order to avoid including endless discussion threads that often go in circles the idea is to limit the number of issue comments and pr comments taken into consideration.
This is also where I need input:
As in many other issue-metrics stats I used https://github3.readthedocs.io/en/1.0.1/issues.html#github3.issues.issue.Issue.comments in order to iterate over comments. In the documentation it says the iterator can limit the number of comments considered. In my test case though it seems to ignore this parameter. Likely I mis-understood the use of the iterator?
Readiness Checklist
Author/Contributor
make lint
and fix any issues that you have introducedmake test
and ensure you have test coverage for the lines you are introducingReviewer
bug
,documentation
,enhancement
,infrastructure
, orbreaking