Closed
Conversation
Added a short beginner-friendly explanation to help new contributors understand the responsibilities of open source maintainers.
Contributor
|
Thanks for the contribution, but this doesn't materially improve the document and will cause drift with the non-English translations. so I am going to close the PR. |
This file contains hidden or 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
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.
This PR improves the "Best Practices for Maintainers" guide by adding
a short, beginner-friendly explanation of what a maintainer does.
The goal is to help new contributors better understand that maintainership
includes communication, decision-making, and community management —
not just writing code.