Skip to content
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

docs: update Contributing.md to clarify repo captain permissions #6357

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

bjohansebas
Copy link
Member

This came up in expressjs/discussions#326, to clarify a bit the permissions of captains.

@bjohansebas bjohansebas added docs semver-ignore This change does not have any impact in semver (docs, tooling, etc..) labels Feb 22, 2025
@bjohansebas bjohansebas requested a review from a team February 22, 2025 15:50
@bjohansebas
Copy link
Member Author

There is no section that specifies the inactivity period for a committer or captain, it's only mentioned for TC and triage. It might be a good idea to document it as well.

@@ -120,7 +120,7 @@ active member steps down.
The Express TC can designate captains for individual projects/repos in the
organizations. These captains are responsible for being the primary
day-to-day maintainers of the repo on a technical and community front.
Repo captains are empowered with repo ownership and package publication rights.
Repo captains are empowered with maintain access and package publication rights.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I understand that only the TCs can have admin rights, but when it comes to security reports, with maintainer rights, it is not possible to publish or review those reports on GitHub. There are quite a few limitations with those permissions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs semver-ignore This change does not have any impact in semver (docs, tooling, etc..)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant