2026 elections

[dabeeeenster]

This PR

• Get the 2026 election content into the repo

Related Issues

#512

Notes

Follow-up Tasks

How to test

[gemini-code-assist]

Summary of Changes

Hello @dabeeeenster, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request lays the groundwork for the 2026 OpenFeature Governance Committee elections by introducing essential documentation. It provides clear guidelines for the entire election process, from nominations and voter eligibility to the voting mechanism and diversity considerations, alongside a dedicated file for listing candidates. The changes aim to foster a transparent, well-organized, and inclusive election cycle, encouraging broad community participation and ensuring diverse representation within the committee.

Highlights

• New Election Documentation: Dedicated files have been introduced to manage the 2026 OpenFeature Governance Committee elections, providing a structured approach to the process.
• Candidate Listing Established: A new Candidates.md file has been added to list current and prospective candidates for the 2026 Governance Committee election, detailing members up for re-election and those stepping down, along with a template for new candidate information.
• Comprehensive Election Guidelines: A detailed Election-Guidelines.md file has been added, outlining the full election process, including the schedule, nomination procedures, voter eligibility, the voting mechanism (utilizing Helios Voting), and specific rules to ensure diversity in representation.
• Diversity Rules Implemented: Specific rules have been established to promote diversity within the Governance Committee, limiting representation from any single company to a maximum of one-third of the total seats.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds the necessary files for the 2026 Governance Committee elections. The changes are mostly based on previous years' election files. My review focuses on ensuring the correctness and clarity of the election guidelines. I've found a few critical inconsistencies in the voting process description, likely due to copy-pasting from previous years, which need to be addressed. I've also included some suggestions to improve clarity and consistency.

[gemini-code-assist]

There appears to be a copy-paste error from a previous election's guidelines. This election is for 4 seats, but the text says voters may select up to 7 candidates and that 7 candidates will win. This should be corrected to reflect that 4 seats are open.

Suggested change

	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.
	The seven candidates (four from current GC and three from new nominees) with the most votes win the election.
	Voting will be approval voting, where each voter may select up to four candidates.
	The four candidates with the most votes win the election.