-
Notifications
You must be signed in to change notification settings - Fork 161
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: CPC Secondary Director #1142
Comments
Per Friday's board vote approving an additional director, we are extending the deadline on the nomination period one week, to August 25th. This vote will elect two board seats. |
Actually scratch that, we should not open up the additional seat until the by-laws are published AND the updated CPC charter is published. Will still move the nomination period out one week to give folks extra time to nominate (it's vacation season). |
@bensternthal - Do we need to update the voting period and announcement dates to reflect the extension? |
Good call, adjusted. I am hoping to do the vote in 1 week. |
2023 CPC Voting Bios: Secondary Director bios are attached below: |
Ballots have been sent out to voting members via Opavote. If anyone has not received an email from Opavote and believes this to be an error, please contact me. |
In my role as a Node.js representative on the CPC, should my vote represent my personal assessment or should it represent the view of the TSC of Node.js collectively? Or is that a question for me to take up with the TSC? |
@Trott this isn't addressed (as far as I can tell) in the CPC documentation. I would suggest working with the TSC to decide. |
That's an interesting question. There's nothing in the bylaws, the CPC charter, governance or member expectations documents that point in either direction. Given the vote is secret and that there are no distinction made between voting members in the charter, regardless of how they get elected, it feels reasonable to assume every voting member has been delegated decision-making power within the CPC. If not, CPC voting members elected by At Large projects and by other CPC members should be having conversations with At Large project maintainers and every CPC member respectively before casting a vote, and we'd be spending even more of our time doing election work rather than work that actually benefits the different constituencies we represent. Additionally, as a voting member, you have a lot more visibility in how the candidates actually operate in the CPC and Board than the folks that elected you have, and so you're better positioned to make the right call. However there might be circumstances where you'd like the opinion of the Node TSC, or someone else for that matter, and you should absolutely seek it, but it shouldn't be a requirement. |
Per #1161, closing this out. |
This Issue tracks the election of the CPC Secondary Director / At Large Community director. Details about the role can be found in the CPC charter.
Nomination Process
Please complete this form.
Eligibility
Nominees for this role must be an Active OpenJS Collaborator at the time of their selection, as defined in the CPC's Governance document.
Term
Term begins Sept. 1, 2023 and concludes Aug. 31, 2024.
Election Schedule
The text was updated successfully, but these errors were encountered: