-
Notifications
You must be signed in to change notification settings - Fork 23
docs: update GOVERNANCE.md to clarify repo captain permissions #363
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
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.
Pull Request Overview
This PR aims to clarify the permissions and roles of repo captains as discussed in the Express discussions.
- Clarifies the scope of repo captain permissions
- Updates wording to reflect the intended repository maintainership role
Co-authored-by: Copilot <[email protected]>
|
cc: @expressjs/express-tc |
Co-authored-by: Jon Church <[email protected]>
|
Blocked on (similar to #375): openjs-foundation/cross-project-council#1607 |
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.
LGTM
|
I agree with the spirit fo the PR that captains hsoudl have admin and publishh on their repos. Approved int hat spirit, idk if there is dissent here still, would love to see other @expressjs/express-tc opinions via approve/reqquest change |
|
Governance docs can have this detail in it, I don't think we are blocked on the CHarter vs Governance issue anymore cc @wesleytodd |
This came up in #326, to clarify a bit the permissions of captains.