Maintainers¶
This page lists who reviews and decides changes to TRACE, and how a regular contributor can take on one of those roles.
Project Lead¶
| Name | Affiliation | GitHub | Contact |
|---|---|---|---|
| Imran Siddique | AgenTrust-io | @imran-siddique | GitHub profile |
The Project Lead has final decision authority on specification changes, submission of TRACE deliverables to other organizations, conformance requirements, and Maintainer appointments.
Spec Editors¶
| Name | Affiliation | Area |
|---|---|---|
| Rishabh Poddar | OPAQUE Systems | Specification, TEE profiles |
| Aaron Fulkerson | OPAQUE Systems | Specification, governance |
Repository Maintainers¶
| Name | GitHub | Scope |
|---|---|---|
| Louie Lu | @lywinged | TRACE specification and conformance requirements |
| Rajnish Tiwari | @rajnisht7 | Adapters, provenance verification, and conformance vectors |
Louie's appointment was announced by the Project Lead. Rajnish's was announced here.
How to become a maintainer¶
Reviewer: 3+ merged PRs with substantive contributions. Nominated by a Maintainer, confirmed by Project Lead.
Maintainer: Active Reviewer for 60+ days, 5+ merged PRs, demonstrated judgment on spec design questions. Nominated by any Maintainer, confirmed by Project Lead.
We are actively recruiting Maintainers across independent organizations, particularly from silicon vendors, cloud providers, and regulated-industry deployers. If you are contributing to TRACE and want to take on a formal role, open an issue tagged maintainer-interest.
Affiliations identify each maintainer's professional context. They do not give an affiliated organization ownership or additional governance rights. See GOVERNANCE.md and SPONSORS.md.
Emeritus¶
Maintainers who step back from active review are listed here with thanks.
(none yet)