Governance Charter
Overview
This document describes the governance process under which the project operates. It describes the election process for the Governance Committee (GC) and how the committee operates.
Goals
The role of the Governance Committee is to be a live, responsive body that can refactor and reform as necessary to adapt to a changing project and community.
Governance Committee
The Governance Committee is responsible for representing the project, making a final decision if a consensus cannot be reached (see Decision Making), handling the Code of Conduct escalations, defining and approving with the project members the final governance model, and organizing elections for the elected governance board body.
Governance Committee Members
Decision making
Decisions are made by a consensus of Project Members and Interested Parties. If this consensus cannot be reached, the decision can be made by the plain majority vote of Governance Committee members.
Key discussions and decisions should happen asynchronously in communication channels like GitHub Issues, discussions or pull requests. Technical decisions are expected to be documented in the OpenFeature Specification. The community decisions should be documented in this Governance repository.
Meetings
The project conducts regular project meetings hosted by its maintainers and contributors. These meetings are used as additional discussion and consensus building but not for making decisions without prior discussion in async channels.
Governance Committee Members
Governance Committee members are responsible for representing the project in communications with organizations, including but not limited to contributor companies, adopters, vendors and foundations. Apart from the representative role, they can make a final decision when a consensus cannot be reached. Each company/organization should have less than 50% of the seats.
Elections
Members
People which are part of the GitHub Organization are considered as members and are eligible to vote.