|
| 1 | +# OpenFeature 2025 Governance Committee election |
| 2 | + |
| 3 | +Please see **[the list of candidates running in the election here](https://github.com/open-feature/community/blob/main/Elections/2025/Candidates.md)**. |
| 4 | + |
| 5 | +This election should fill four seats: |
| 6 | + |
| 7 | +- four seats from the existing governance committee |
| 8 | + |
| 9 | +Election schedule: |
| 10 | + |
| 11 | +- Feb 3rd - Feb 17th 2025 - period to submit nominations |
| 12 | +- Feb 18th 2025 - official nominees list published |
| 13 | +- Feb 24th - Mar 10th 2025 - voting period |
| 14 | +- Mar 12th 2025 - results announced |
| 15 | + |
| 16 | +We highly encourage participation in this election cycle to ensure that the community is well-represented by the Governance Committee. |
| 17 | + |
| 18 | +# TL;DR |
| 19 | + |
| 20 | +- If you've been nominated or are willing to nominate yourself: express your interest in [this issue](https://github.com/open-feature/community/issues/417) |
| 21 | +- Vote between Feb 24th 2025 00:00 UTC and Mar 10th 2025 23:59 UTC via the [voting link](https://vote.heliosvoting.org/helios/elections/0d3dca66-dd88-11ef-b00f-56fa8818c2bb/view) |
| 22 | + |
| 23 | +# Vacancies |
| 24 | + |
| 25 | +This election will fill four seats from the existing governance committee. These positions can either be members re-elected from the current Governance committee, or new members can join the committee, replacing current members. |
| 26 | + |
| 27 | +To encourage diversity there will be a maximum of one-third representation on the Governance Committee from any one company at any time. |
| 28 | +If the outcomes of an election result in greater than 1/3 representation (or maximum of two, whichever is greater), the lowest vote getters from any particular company will be removed until representation on the committee is equal or less than one-third. |
| 29 | + |
| 30 | +# Voting process |
| 31 | + |
| 32 | +Anyone can track the 2025 election process via [this GitHub issue](https://github.com/open-feature/community/issues/417). |
| 33 | +We will ensure that all documents and assets related to the 2025 election process are public. |
| 34 | + |
| 35 | +For the 2025 elections, [Helios Voting](https://vote.heliosvoting.org/) was chosen as it's a hosted solution with cryptographic guarantees that no GC members can meddle with the results. |
| 36 | + |
| 37 | +Helios voting also allows us to add GitHub handles to the list of voters in addition to email addresses. |
| 38 | +We need this, as we count contributions based on GitHub contributions and do not always have the contributor's email address. |
| 39 | +The disadvantage of Helios is that it does not support ranked voting. |
| 40 | + |
| 41 | +# Nominations |
| 42 | + |
| 43 | +Anybody is eligible to run for the Governance Committee. During the "call for nomination" period, people can be nominated or nominate themselves by expressing their interest in [this issue](https://github.com/open-feature/community/issues/417) a Pull Request adding said candidate to the [candidates-2025.md](https://github.com/open-feature/community/blob/main/Elections/2025/Candidates.md) file in the OpenFeature community repository. |
| 44 | + |
| 45 | +The template in that file includes the following columns: |
| 46 | + |
| 47 | +- Full name |
| 48 | +- GitHub alias |
| 49 | +- Company affiliation (if applicable) |
| 50 | +- Short bio or reasoning to join the Governance Committee (no more than a short paragraph) |
| 51 | +- _Optional_: photo/picture of a nominee |
| 52 | + |
| 53 | +The Pull Request will not be merged until the candidate has confirmed their desire to be nominated (if not self-nominating) and ratified via PR comments. |
| 54 | + |
| 55 | +# Voter Eligibility |
| 56 | + |
| 57 | +All members of the OpenFeature Organization Members, Approvers, Maintainers will automatically be eligible to vote. |
| 58 | + |
| 59 | +# Vote |
| 60 | + |
| 61 | +Everyone with voting rights may log into [Helios Voting](https://vote.heliosvoting.org/helios/elections/0d3dca66-dd88-11ef-b00f-56fa8818c2bb/view) using their GitHub account. |
| 62 | +Voting will be approval voting, where each voter may select up to seven candidates, **four** from the current Governance Committee and three from the new nominees. |
| 63 | +The seven candidates (four from current GC and three from new nominees) with the most votes win the election. |
| 64 | +The winners should be from different organizations(at most 1/3 from the same organization), therefore only the 2 highest ranked nominees from each organization will be elected. |
| 65 | +If the outcomes of an election result in greater than 1/3 representation (or maximum of two, whichever is greater), the lowest vote getters from any particular company will be removed until representation on the committee is equal or less than one-third. |
| 66 | + |
| 67 | +If there is a draw between the lower ranked candidates, there will be a runoff election between the tied candidates. |
| 68 | +The runoff election will be held within 48 hours of the original election. |
| 69 | +The runoff election will be a simple majority vote, and the candidate with the most votes will be elected. |
| 70 | + |
| 71 | +Per Helios, voting is entirely private: nobody will know any individual's vote. |
| 72 | + |
| 73 | +# Results |
| 74 | + |
| 75 | +Voting will close on the March 10th 2025 23:59 UTC. Nominees will be stack ranked. |
| 76 | +If a nominee becomes ineligible, the election committee will skip those nominees and pick the nominee with the next-highest score. |
| 77 | +The exact scores for each candidate will be public. |
0 commit comments