Governance and maintainers
CGP currently uses a lead-maintainer governance model appropriate for a pre-alpha project, with an explicit goal of moving toward multi-maintainer stewardship as independent implementations and contributors emerge.
Current leadership
Section titled “Current leadership”The lead maintainer is Matteo Pelosi (@MrQwenty).
Current responsibilities include:
- protocol direction;
- release integrity;
- repository administration;
- security coordination;
- maintainer appointments;
- compatibility decisions when consensus cannot be reached.
Decision model
Section titled “Decision model”Routine implementation and documentation changes use pull-request review.
Protocol changes require an RFC and are evaluated for:
- independent implementability;
- compatibility;
- privacy and security impact;
- deterministic conformance testing;
- operational complexity;
- migration cost;
- evidence supporting performance or governance claims.
Future structure
Section titled “Future structure”As the project matures, governance should add:
- additional component maintainers;
- independent implementation reviewers;
- a technical steering group;
- published voting and recusal rules;
- transparent conformance and certification governance.