Uh oh!
There was an error while loading. Please reload this page.
governance.md: add inactivity policy for any roles - #378
Conversation
Signed-off-by: Sebastian Beltran <bjohansebas@gmail.com>
Uh oh!
There was an error while loading. Please reload this page.
Co-authored-by: Ulises Gascón <ulisesgascongonzalez@gmail.com>
Uh oh!
There was an error while loading. Please reload this page.
Co-authored-by: Sebastian Beltran <bjohansebas@gmail.com>
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
wesleytodd
left a comment
There was a problem hiding this comment.
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".
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Co-authored-by: Wes Todd <wes@wesleytodd.com>
Uh oh!
There was an error while loading. Please reload this page.
Co-authored-by: Jon Church <me@jonchurch.com>
Signed-off-by: Sebastian Beltran <bjohansebas@gmail.com>
Signed-off-by: Sebastian Beltran <bjohansebas@gmail.com>
wesleytodd
left a comment
There was a problem hiding this comment.
One nit, but otherwise LGTM.
Uh oh!
There was an error while loading. Please reload this page.
Co-authored-by: Wes Todd <wes@wesleytodd.com>
Uh oh!
There was an error while loading. Please reload this page.
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