doc: add Zach to active members & move inactive members to emeriti#388
Merged
Conversation
Member
|
I would like to stay in the team. I have not been to many of the meetings as the timing is not great for me, but I would still like to see what's going on and to engage when I can. 🙂 |
ovflowd
approved these changes
Jun 17, 2026
Member
Same over here 🙇 |
Member
Author
|
You could review #387 🙂 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Move the following inactive (nothing in next-10 in the past year) members to emeriti:
@ovflowd@QardIf any of these people wish to remain in the
@nodejs/next-10team for the tag notifications, please comment here. Otherwise, I'll tidy up the GH team next week.Add the following new active members: