-
Notifications
You must be signed in to change notification settings - Fork 133
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
Node.js CPC reps #1627
Comments
I'm happy to continue and feel like I could improve in my representation of Node.js at the foundation and forge a better connection back to the project. Something I think about and am working on. Better attendance at the TSC meetings is one way (it's been crazy busy lately) but also being more tuned into the projects needs. All that is to say: I'm happy to continue and interested in improving. 🙌 |
Happy to continue but my time for meetings at around that time is getting lower by the time passes. I read minutes and engage in issues/decisions when they came through. |
Confirmed with @mcollina that while he is happy to continue if somebody else would like to volunteer he'd also be happy with that. I'll leave this open for another week to see if there are any other volunteers otherwise we'll assume that Matteo and Joe will continue. |
Looks like we are settled on Matteo and Joe continuing. Closing. |
It's the yearly elections/nominations on the CPC side.
We currently have @mcollina and @joesepi as our reps.
openjs-foundation/cross-project-council#1370
creating as an FYI to @nodejs/tsc members. @mcollina, @joesepi just confirming that you two are still happy to continue as the reps?
The text was updated successfully, but these errors were encountered: