Community
Governance
How decisions are made. The OAS governance model balances rapid iteration with careful stewardship of a vendor-neutral standard.
RFC Process
1
Draft
1-2 weeksAuthor submits an RFC as a pull request to the specification repository. The proposal must include motivation, detailed design, and alternatives considered.
2
Review
2-4 weeksThe community reviews and discusses the proposal. Maintainers may request changes or additional justification. All feedback is public.
3
Vote
10 daysA 10-day final comment period begins. Concerns must be raised during this window. Core maintainers cast their votes.
YES0
NO0
Two-thirds required
4
Accept
3-5 daysRequires two-thirds majority for specification changes, simple majority for implementation details. The RFC is merged into the specification.
Seats in the Chamber
Core Maintainer
3-5- —Final approval on specification changes
- —Release management and versioning
- —Security vulnerability triage
- —RFC final comment period management
SDK Maintainer
1 per language- —Language-specific SDK quality and releases
- —Cross-language parity enforcement
- —Dependency management and security updates
Reviewer
10-20- —Code review on pull requests
- —RFC feedback and discussion
- —Community mentorship and issue triage
Contributor
Open- —Code contributions via pull requests
- —Bug reports, feature requests, and documentation
- —RFC proposals
Decision Making
| Scope | Threshold | Voters |
|---|---|---|
| Specification changes | Two-thirds majority | Core Maintainers |
| New entity kinds | Unanimous | Core Maintainers |
| SDK releases | SDK Maintainer + 1 Core | SDK + Core |
| New maintainers | Two-thirds majority | Core Maintainers |
| RFC acceptance | Simple majority | Core Maintainers |
| Breaking changes | Unanimous + FCP | Core Maintainers |