-
-
Notifications
You must be signed in to change notification settings - Fork 138
Election for the Voting Representative for the OpenJS Cross-Project-Council (TSC rep) #835
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
@nodejs/tsc please self-nominate in this issue if you are interested to run to be the Node.js TSC voting CPC representative. |
I'm happy to continue as the Voting Representative for Node.js. |
Nominations are now closed. With a single volunteer I think we can confirm @mcollina. Lets discussion in the TSC meeting tomorrow. @nodejs/tsc if there are any objections to confirming @mcollina please chime into this issue. If we don't hear any by the end of the week (March 20) and we agree in the TSC meeting we'll confirm @mcollina for another year and close the issue. |
It’s time to elect the Cross-Project-Council voting representatives for next term which starts on April 1st 2020. The current one is @mcollina.
See nodejs/admin#472 for more detail.
Timeline is:
Please note the expectations of the voting CPC representative:
https://github.com/openjs-foundation/cross-project-council/blob/master/CPC-CHARTER.md#voting-members
Also note: any member of the Node.js org can participate in the Cross Project Council as a regular member.
https://github.com/openjs-foundation/cross-project-council/blob/master/CPC-CHARTER.md#regular-members
Similar to the practices in Node.js, the CPC follows the consensus seeking model and there is little difference between a voting rep of a project and a regular member. Becoming a regular member could be a good way to get involved if one is unsure of running for a voting member.
The text was updated successfully, but these errors were encountered: