-
Notifications
You must be signed in to change notification settings - Fork 23
governance.md: add inactivity policy for any roles #378
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
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Sebastian Beltran <[email protected]>
Co-authored-by: Ulises Gascón <[email protected]>
Co-authored-by: Sebastian Beltran <[email protected]>
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.
Just small changes, but I think we need to figure out the 6mo vs 12mo thing before we merge, hence the "request changes" and not just "approve".
Co-authored-by: Wes Todd <[email protected]>
Co-authored-by: Jon Church <[email protected]>
Signed-off-by: Sebastian Beltran <[email protected]>
Signed-off-by: Sebastian Beltran <[email protected]>
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.
One nit, but otherwise LGTM.
Co-authored-by: Wes Todd <[email protected]>
The goal of this is to have something written for when a member is considered inactive and to establish a certain process. Any suggestions on the wording are welcome.
This is important because of roles like captains who have access to package publishing—having someone with access who is no longer active in the project can be risky, so only active people should have access