-
Notifications
You must be signed in to change notification settings - Fork 175
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
chore: update Node.js representative #783
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.
LGTM.
Thank you @mmarchini for the work you've done and thank you @Trott for stepping in.
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
What needs to happen for this to be merged? Is there anything I should be doing on my end? |
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.
Technically, we'll need to cover this in a CPC meeting:
Changes to CPC membership should be posted in the agenda, and may be suggested as any other agenda item.
@joesepi On a related note, have the impact project voting members been re-nominated and re-ratified this year? I think we may have missed that, and just elected the non-impact project voting members...
We covered in the last CPC meeting, landing. |
Mary Marchini (@mmarchini) has asked to take an indefinite hiatus from CPC. The Node.js TSC discussed the issue and decided that I would fill out the remainder of Mary's term or until she decides to re-join the CPC.
I'm not sure what the process is for making these changes, and like an absolutely terrible council member, I am forging ahead with a pull request because it's what I know how to do.