-
Notifications
You must be signed in to change notification settings - Fork 168
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
Opening nominations for the next year's voting CPC members #472
Comments
Am I right that we're going to need to shed some voting members? |
@boneskull I think the answer is yes. Last year we agreed to add all who applied but the governance states that there are only 2 voting CPC members from the non-impact projects: https://github.com/openjs-foundation/cross-project-council/blob/master/GOVERNANCE.md#election-process-for-non-impact-voting-cpc-members We of course can propose changes, but I'm thinking we might cut down on which roles need to be filled by voting members (ex Chair and Board representative) instead so that there is a lower impact on having regular members versus voting members in terms of candidates. The other option we have which we have not exercised is having the voting members elect 2 of the regular members to be voting members. |
Opened #488 per our discussion here, in the meetings & on the slack channel |
Closing as resolved. :) |
As mentioned in our governance document, the term for all voting members of the CPC is ending on 31 March 2020, and new members need to be selected before then.
For impact projects, next year's members need to be nominated (or re-nominated) by each project, and then ratified by the CPC.
For non-impact projects, this means that we need to elect the two representatives. This election process specifies that a two-week nomination period precedes this election, which means that this ought to start Real Soon Now.
To clarify, this issue is not the issue officially announcing the opening of the nomination period.
The text was updated successfully, but these errors were encountered: