meta: move one or more collaborators to emeritus #56580
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nodejs-github-bot
added
meta
lpinca
approved these changes
Jan 13, 2025
|
Anatoli is still a TSC regular member, hence the linter error. |
aduh95
approved these changes
Jan 13, 2025
|
/cc @apapirovski FYI |
|
@targos I think when a collaborator drops out due to inactivity they move from regular to emeritus for the TSC, right? If so I'm happy to open a PR which will do that move. |
anonrig
approved these changes
Jan 13, 2025
benjamingr
approved these changes
Jan 13, 2025
|
Just going to see if I can give Anatoli a heads up through email and then will open the PR to move him to emeritus, that should resolve the linter issue. |
|
PR to move Anatoli to emeritus - #56592 |
targos
approved these changes
Jan 14, 2025
UlisesGascon
approved these changes
Jan 14, 2025
BridgeAR
approved these changes
Jan 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was generated by the
find-inactive-collaborators.ymlworkflow.@nodejs/tsc Please follow up with the offboarding tasks.