-
Notifications
You must be signed in to change notification settings - Fork 210
Simplify & Adjust CPC Voting Member Tiers and Process #1698
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
base: main
Are you sure you want to change the base?
Changes from all commits
dd84c5d
296ab5b
15383c8
6d9e05b
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||
|---|---|---|---|---|---|---|---|---|
|
|
@@ -49,19 +49,27 @@ In addition, a Regular CPC member can be removed by voluntary resignation, or by | |||||||
|
|
||||||||
| ### Voting members | ||||||||
|
|
||||||||
| ### Current Structure (Through Fall 2026) | ||||||||
|
|
||||||||
| Voting members are selected as follows: | ||||||||
|
|
||||||||
| * Each Impact project may nominate up to two members through a process of their choosing. Once nominated the member must be ratified by the CPC Voting members before becoming a Voting member. | ||||||||
| * Up to two Voting members may be nominated by the non-Impact projects based on a process set by the CPC. | ||||||||
| * Up to two Voting members may be nominated by the Regular members. Once nominated these members must be ratified by the CPC Voting members before becoming a Voting member. | ||||||||
|
|
||||||||
| ### New Structure (Effective Fall 2026 Election Cycle) | ||||||||
|
|
||||||||
| Beginning with the Fall 2026 election cycle, the CPC will transition from separate non-Impact project and Regular Member voting representatives to a unified class of Community Voting Members. Under this structure, voting members will be selected as follows: | ||||||||
|
|
||||||||
| * up to two Voting members may be nominated by the non Impact projects based on a process set by the CPC. | ||||||||
| * Each Impact project may nominate up to two Voting members through a process of their choosing. Once appointed, ratification occurs by opening an issue in the CPC repository announcing the appointment and following the [guidelines for merging PRs](./governance/GOVERNANCE.md#merging-prs-into-this-repository). Impact project voting members serve until they voluntarily step down, until their project appoints a replacement, or if they are removed by a CPC motion. | ||||||||
| * Up to five Community Voting Members may be elected through a process defined in [Section 7. Elections](#section-7-elections). Community Voting Members must be Regular members of the CPC and must not currently be serving as a voting representative for an Impact project. | ||||||||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The core collaboration space line is dependent on the outcome of the overall discussion on collab spaces and if they should have voting representation. |
||||||||
|
|
||||||||
| * up to two Voting members may be nominated by the Regular members. Once nominated these members must be ratified by the CPC Voting members before becoming a Voting member. | ||||||||
| ### General Requirements and Expectations | ||||||||
|
|
||||||||
| Voting members are expected to make a time commitment which allows them to be responsive to CPC business, participate regularly in meetings and to participate in all voting matters (either by voting or specifically abstaining). | ||||||||
| They are also expected to help to enable work of the regular CPC members by providing leadership, help with interactions with the board and Foundation staff and to generally help keep things moving. | ||||||||
|
|
||||||||
| Voting members serve for a term of 1 year and must be re-nominated and ratified by the Voting CPC members each year. | ||||||||
| In addition, a Voting CPC member can be removed by voluntary resignation, by a standard CPC motion, or in accordance to the participation rules described for Regular members. | ||||||||
| Non Impact Voting members serve for a term of 1 year and must be re-nominated and ratified by the Voting CPC members each year. In addition, a Voting CPC member can be removed by voluntary resignation, by a standard CPC motion, or in accordance to the participation rules described for Regular members. | ||||||||
|
|
||||||||
| Changes to CPC membership should be posted in the agenda, and may be suggested as any other agenda item. | ||||||||
|
|
||||||||
|
|
@@ -137,16 +145,13 @@ Not withstanding the above, the Projects and the entire technical community will | |||||||
|
|
||||||||
| ## Section 7. Elections | ||||||||
|
|
||||||||
| Leadership roles in OpenJS Foundation will be peer elected representatives of the community. | ||||||||
|
|
||||||||
| For election of persons (such as the CPC Chair), a multiple-candidate method should be used, such as: | ||||||||
|
|
||||||||
| * [Condorcet][] or | ||||||||
| * [Single Transferable Vote][] | ||||||||
|
|
||||||||
| Multiple-candidate methods may be reduced to simple election by plurality when there are only two candidates for one position to be filled. | ||||||||
| No election is required if there is only one candidate and no objections to the candidates election. | ||||||||
| Elections shall be done within the Projects by the Collaborators active in the Project. | ||||||||
|
|
||||||||
| The CPC will elect from amongst Regular and Voting members of the CPC: | ||||||||
|
|
||||||||
|
|
@@ -162,6 +167,10 @@ There are no limits on the number of terms a CPC Chair, Vice Chair, or Director | |||||||
|
|
||||||||
| The CPC Chair and Vice Chair may be (but are not required to be) CPC Directors. | ||||||||
|
|
||||||||
| ### Who Votes | ||||||||
|
|
||||||||
| CPC Voting members at the time of the election may vote. | ||||||||
|
|
||||||||
| ## Section 8. Board Representation | ||||||||
|
|
||||||||
| There are Board seats allocated for CPC members to represent the Foundation's projects and related communities to the Board. | ||||||||
|
|
||||||||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -7,9 +7,8 @@ This document captures important dates and reminders. | |
| Position | Term Length | Nomination Period | Voting Period | Term Start/End | ||
| -- | -- | -- | -- | -- | ||
| CPC Directors (3) | 1 Year | April: 1st & 2nd Week | April: 3rd week | May 1 | ||
| CPC Impact representative selection (2 per project) | 1 Year | Oct: 1st & 2nd Week | Oct: 3rd week | Nov 1 | ||
| CPC At Large voting members (2) | 1 Year | Oct: 1st & 2nd Week | Oct: 3rd week | Nov 1 | ||
| CPC Regular voting members (2) | 1 Year | Oct: 1st & 2nd Week | Oct: 3rd week | Nov 1 | ||
| CPC Impact Representative Selection (2 per project) | By Appointment | N/A | N/A | N/A | ||
| CPC Community Voting Members (5) | 1 Year | Oct: 1st & 2nd Week | Oct: 3rd week | Nov 1 | ||
|
Comment on lines
+10
to
+11
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. is this list missing collab space voting members? |
||
|
|
||
| Position | Term Length | Nomination Period | Voting Period | Term Start/End | ||
| -- | -- | -- | -- | -- | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We haven't ever used the collab space progression mechanism. I think we should decide what we want to do with it, before adding a dependency on it elsewhere.