-
Notifications
You must be signed in to change notification settings - Fork 70
CPC Representative Nominations #470
Comments
As a related task, we also need a PR to update our governance to reflect the election of a CPC member instead of a Board representative, but like the TSC, I believe we can do that in parallel. |
Discussion in last CommComm meeting is that for this time to be consistent with the process for Director representative, nominees are limited to members of the CommComm. |
Good morning and happy Tuesday everyone! Polls have closed and I’m happy to announce that @joesepi has been elected as our new CPC Voting Representative 🎉 We will close this issue when our README has been updated to reflect the results of the election. Please remember, the CPC is open for all member project collaborators to participate it, so everyone please keep engaging with the Foundation at https://github.com/openjs-foundation 🙂 https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_009ceb7f8a393a46 |
Hey @nodejs/community-committee!
We've agreed on the approach for electing the CPC representatives for Node.js in nodejs/admin#316 – in CommComm we will use a process similar to our existing director nomination process to elect 1 CPC voting representative. Our "target" date for rep announcement is May 1 as per openjs-foundation/cross-project-council#115.
I'll be conducting the election process on the following timeline:
April 17: Call for nominations for CPC Representative
April 22: Nominations closed and Candidate Statements / Q&A open in issues on GitHub
April 26: Close Q/A, open balloting.
April 30: Announce CPC Representative
Please fill out the following form to nominate a candidate: https://forms.gle/4jcR19wgY5AXJ1aB7
Notes on nominations:
Please review the expectations for voting CPC representatives before submitting a nomination.
And please remember: participation in the CPC is not limited to voting members! Other Node.js org collaborators can freely participate as regular members in the CPC.
Here we go 🎉
The text was updated successfully, but these errors were encountered: