chore: introduce more active maintainers #1957
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
orta
approved these changes
Oct 27, 2021
I've done this in the reverse and made an "executive decision" to add these co-maintainers. Usually the process would be to propose in a PR as such, and then once approved, add them, but I wanted folks to be able to hit the ground running here. Moving forward, I would suggest giving new maintainer applicants "triage" privilege to start, and then promoting them to "write" once they've gained enough experience helping community members, assisting with building the roadmap, and helping to review or introduce PRs.
acao
force-pushed
the
chore/more-maintainers
branch
from
61531b1
to
49010cd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've done this in the reverse and made an "executive decision" to add these co-maintainers.
Usually the process would be to propose in a PR as such, and then once approved, add them, but I wanted folks to be able to hit the ground running here.
Moving forward, I would suggest giving new maintainer applicants "triage" privilege to start, and then promoting them to "write" once they've gained enough experience helping community members, assisting with building the roadmap, and helping to review or introduce PRs.