Update GC based on election results

[beeme1mr]

Updated the GitHub groups based on the recent GC election.

Election guidelines: https://github.com/open-feature/community/blob/main/Elections/2026/Election-Guidelines.md
Voting results: https://vote.heliosvoting.org/helios/elections/c5b3e0eb-dfc8-4c60-b262-05849142619e/view

[gemini-code-assist]

Summary of Changes

Hello @beeme1mr, 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 updates the GitHub organization configuration to align with the outcomes of the recent Governance Board elections. It ensures that the open-feature/org.yaml file accurately reflects the current composition of the Governance Board and Technical Steering Committee, thereby synchronizing GitHub group memberships with the latest governance decisions.

Highlights

• Governance Board Membership Updated: The Governance Board membership has been updated to reflect recent election results. New members askpt, cupofcat, and thomaspoignant were added, while AloisReitbauer, jrydberg, and weyert were removed from both the admins and teams sections.
• Technical Steering Committee Membership Adjusted: The Technical Steering Committee membership was adjusted by removing thomaspoignant from both the admins and teams sections.

Changelog

• config/open-feature/org.yaml
  • Modified the admins list to reflect changes in the Governance Board membership, adding askpt, cupofcat, thomaspoignant and removing AloisReitbauer, jrydberg, weyert.
  • Modified the admins list to remove thomaspoignant from the Technical Steering Committee.
  • Updated the Governance Board team members to include askpt, cupofcat, thomaspoignant and remove AloisReitbauer, jrydberg, weyert.
  • Updated the Technical Steering Committee team members to remove thomaspoignant.

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

The pull request correctly updates the Governance Committee (GC) and Technical Steering Committee (TSC) memberships in config/open-feature/org.yaml based on the election results. The alphabetical ordering of the GC members is well-maintained. However, there is a minor formatting inconsistency with an extra newline in the admins section. Additionally, please note that askpt and cupofcat are now listed in both the admins and members sections; typically, admins are removed from the general members list to avoid duplication. Also, ensure that members removed from the board (like jrydberg) are added to the members list if they should remain part of the organization. Finally, there appears to be a potential duplication in the members list between cupofcat and DavidPHirsch which may need investigation.

[askpt]

The company name is incomplete. 😄