Skip to content
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

Election for the Voting Representative for the OpenJS Cross-Project-Council #472

Closed
mcollina opened this issue Mar 3, 2020 · 9 comments
Closed

Comments

@mcollina
Copy link
Member

mcollina commented Mar 3, 2020

Hi fellow @nodejs/tsc and @nodejs/community-committee ,

It’s time we elect our new Cross-Project-Council voting representatives for next term which starts on April 1st 2020. The current ones are @joesepi and me.

I propose we follow the same pattern we did last year with the TSC electing a representative and the CommComm electing one (see #316).

We need to have elected our new representatives by the 31st of March, therefore I propose the following timeline:

March 9th Call for nominations for both CPC representatives
March 16th Close nominations and open balloting for CPC representative
March 23rd Close balloting and announce CPC representative
March 23rd- Handover
April 1st Transition complete

As chairs of each committee, I kindly ask @mhdawson and @bnb to coordinate the nominations and balloting for the TSC and CommComm.

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.

@joesepi
Copy link
Member

joesepi commented Mar 3, 2020

If anyone has any questions about what it's like to participate as a member of the CPC, please don't hesitate to reach out to any of us. My DMs are open and you can find me on Slacks.

@mhdawson
Copy link
Member

mhdawson commented Mar 3, 2020

+1

@bnb
Copy link
Contributor

bnb commented Mar 4, 2020

+1. Also happy to facilitate the CommComm vote.

@mhdawson
Copy link
Member

mhdawson commented Mar 6, 2020

Unless I hear objections before then I'll open the call for nominations on the TSC side on Monday.

@joesepi
Copy link
Member

joesepi commented Mar 9, 2020

I think it should also be made clear that if anyone is considering running for the role but the timing of the weekly meetings is an issue -- there is talk of reconsidering the meeting times as new people come on board. Don't let that be a blocker.

@mhdawson
Copy link
Member

Issue opened in the TSC repo.

@mcollina
Copy link
Member Author

As per nodejs/TSC#835 (comment), I'll keep serving as Voting Representative for the @nodejs project for the next term.

@joesepi
Copy link
Member

joesepi commented Apr 16, 2020

As per nodejs/community-committee#586, I'll keep serving as the Voting Representative for the @nodejs project for the next term.

@joesepi
Copy link
Member

joesepi commented Apr 16, 2020

Closing this issue as elections have concluded. Thanks all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants