-
-
Notifications
You must be signed in to change notification settings - Fork 848
Promote helping with reviews more #194
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
Comments
One cannot edit headers right away, but one can evaluate issues and leave comments right away. 1. Is issue bug or enhancement? 2. If bug, present on current release or different OS or system?* 3. If enhancement, is it useful? Is function already present? That is how I started and would advise others to start.
|
@terryjreedy hopefully that's covered by https://cpython-devguide.readthedocs.io/tracker.html#helptriage (which should probably be merged with https://cpython-devguide.readthedocs.io/triaging.html with a clear separation of what anyone can do and what people with Contirbutor privileges can do). |
Maybe include the following shortcuts: Open PRs awaiting reviews: Open PRs awaiting core reviews: |
This might fall out as part of #189 , but as of right now all of the highly promoted activities for people to contribute by are (in order of the index):
There is no mention of helping to review PRs. And idea 6 for helping triage issues is at the end. Unfortunately triaging issues and helping to review PRs can be the most helpful as they help reduce the workload for core devs versus ideas 1 - 5 which make work for core devs.
Now it might not entirely make sense to have people start with triage and code review, but the point should be made somehow that activities that reduce workload is really important.
The text was updated successfully, but these errors were encountered: