Add emeritus policy for Maintainers and Admins#33
Draft
hydrosquall wants to merge 1 commit into
Draft
Conversation
- Add project-docs/EMERITUS.md defining the emeritus process: 12-month inactivity window, outreach requirements (30-day wait, 60-day deadline), PR documentation expectations, and a table for recording transitions. - Update GOVERNANCE.md to reference EMERITUS.md from the inactivity removal clauses for both Maintainers and Admins. - Add a pointer to EMERITUS.md in MAINTAINERS.md and ADMINS.md so the offboarding destination is visible from the role lists themselves.
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
1 participant
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.
Adds a lightweight emeritus process for the Maintainer and Admin roles.
The existing governance already allows removing inactive members by vote, but there was no shared definition of what happens to them afterward, no outreach expectations, and no record of past transitions.
Changes:
The automation for identifying candidates will follow in a separate PR.