-
Notifications
You must be signed in to change notification settings - Fork 32
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
RFC: Checklists #89
base: main
Are you sure you want to change the base?
RFC: Checklists #89
Conversation
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.
Solid work, feel like most of these suggestions could be discarded, but might give you an idea or two for improvement.
- [ ] Check `status` is set to 'Withdrawn' | ||
|
||
## Stagnant Checklist | ||
- [ ] Ensure that RPIP editors are in general agreement that the RPIP has been inactive for too long. |
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.
Worth adding time guidance here? I think it will be situational (some RPIPs might be drafted toward timely items), but having something like Identify RPIPs that have no commits for the last month
might be a good starting point for identifying stagnant ones
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 think this is more a checklist for after a stagnant RPIP has been identified? I could make a general 'RPIP weekly update checklist' to contain stuff like: 'check for stagnant RPIPs' Would this be useful to the editors?
Was useful, thanks Prose. |
Not fully happy with these as they are. Would appreciate input from editors to highlight any potential additions, etc.