| Name | GitHub | Affiliation | Role |
|---|---|---|---|
| Imran Siddique | @imran-siddique | OPAQUE Systems | Project Lead |
| Rishabh Poddar | @podcastinator | OPAQUE Systems | Maintainer |
| Aaron Fulkerson | @AaronRoeF | OPAQUE Systems | Maintainer |
The Project Lead has final decision authority on architecture, conformance requirements, and Maintainer appointments.
Reviewer: triages issues, reviews pull requests, and approves changes within their area of expertise.
Maintainer: holds merge rights, participates in roadmap decisions, and is responsible for the health of the project.
To be considered for reviewer status you must:
- Have 3 or more pull requests merged into the repository
- Demonstrate working familiarity with TEE (Trusted Execution Environment) concepts and security primitives relevant to the project
- Be nominated by an existing maintainer
To be considered for maintainer status you must:
- Have held reviewer status for at least 60 days
- Have reviewed 10 or more pull requests
- Be nominated by an existing maintainer
- Be approved by a 2/3 vote of the current maintainers
Maintainers who are no longer active may move to emeritus status. Emeritus maintainers are listed here for recognition but do not hold merge rights or voting privileges.
Changes to MAINTAINERS.md must be approved by at least one existing maintainer.
| Name | GitHub | Appointment |
|---|---|---|
| Carlos Hernandez | @carloshvp | Project Lead announcement |
| Zoheb | @zohebk8s | Project Lead announcement |
| Dipika Ranabhat | @qubeena07 | Project Lead announcement |
| Rajnish Tiwari | @rajnisht7 | Project Lead announcement |
These appointments cover this repository. CODEOWNERS determines which paths each reviewer can approve for protected merges.