Split Content Review Procudure and Doc Review Procedure. Add types of Maintainers to maintainer.md. Add Documaintainer. #590
Conversation
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
juliangiebel
requested changes
Jan 23, 2026
Member
Author
I swear I did fug |
Member
Author
|
Ok it's working now |
juliangiebel
approved these changes
Jan 24, 2026
RemFexxel
reviewed
Jan 24, 2026
Contributor
RemFexxel
left a comment
RemFexxel
left a comment
There was a problem hiding this comment.
Small grammar and text improvements.
Co-authored-by: Rem <Remfexxel@pm.me>
Co-authored-by: Rem <Remfexxel@pm.me>
keronshb
approved these changes
Jan 25, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Description
Did some organizing/cleanup of the docs repo to add descriptions for the different types of Maintainers and added Documaintainer as a new type of maintainer. Also moved doc review policy to it's own file rather than it being tacked on to the end of content review procedure.
Why?
Documents do not get the maintenance that they deserve, this has been a persistent problem for years. They're also something that we do not need a full content maintainer to maintain, and are of a specialization different from code review. This is a low hanging fruit for a task we can split off into a specialized new staff role.
In addition, the docs repo is extremely important. All staff changes, policy changes, and such MUST go through the docs repo. Therefore the more competent hands we can have maintaining the docs repo, the easier it will be to make important policy changes, add new types of specialized staff which allows us to lift a lot of the burden off of our currently small maintainer team.