Skip to content

Conversation

bjohansebas
Copy link
Member

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

@bjohansebas bjohansebas requested a review from a team May 15, 2025 03:16
Co-authored-by: Ulises Gascón <[email protected]>
@bjohansebas bjohansebas added top priority Issues which the TC deem our current highest priorities for the project tc agenda labels May 15, 2025
Co-authored-by: Sebastian Beltran <[email protected]>
Copy link
Member

@wesleytodd wesleytodd left a 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: Jon Church <[email protected]>
Copy link
Member

@wesleytodd wesleytodd left a 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.

Copy link
Member

@sheplu sheplu left a comment

Choose a reason for hiding this comment

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

LGTM

@wesleytodd wesleytodd merged commit b604ca7 into expressjs:master Sep 29, 2025
1 check passed
@bjohansebas bjohansebas deleted the innactividad branch September 30, 2025 01:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

tc agenda top priority Issues which the TC deem our current highest priorities for the project

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants