Money. Identity. Technology.
Follow the money. Find the decision.
Repository-level decision-makers for changes and releases
ROOST project maintainers are the people responsible under published project rules for development, releases and merge approval. They work within repository protections and the project's technical-governance structure. The role identifies control over a software project rather than control over every service deploying it.
The repository host initially appoints maintainers and may replace them for inactivity, vacancy or misconduct; maintainers may appoint additional or replacement maintainers. ROOST's Technical Direction Committee sets overarching technical direction and resolves technical ties after consultation. Ordinary community membership carries no explicit permissions, and an employer is not automatically a contributor because an employee participates. The public rules explain the authority model, but the retained evidence does not audit each current permission or identify every approver of the Foundation's policy pack.
ROOST contributor / community role → ROOST project maintainers
Current policy gives ordinary community membership no explicit permissions. Employer organizations are not automatically contributors; partner GitHub teams administer access, not necessarily policy votes.
ROOST Technical Design Committee → ROOST project maintainers
Current TDC roadmap/technical role includes consultation and tie-breaking for maintainer teams. It does not require a deploying platform to adopt every update or classification policy.
ROOST — Robust Open Online Safety Tools Inc → ROOST project maintainers
Repository host may replace for inactivity, vacancy or misconduct. Maintainers may appoint additional/replacement maintainers; exact current permission exercise not audited.
ROOST project maintainers → ROOST Model Community (RMC)
General ROOST project roles assign releases, development and merge approval under branch protection. RMC is a hosted project; this does not identify each actual RMC approver or prove a specific policy merge decision.
ROOST Technical Design Committee → sets overarching technical direction and resolves technical ties → ROOST project maintainers
Current TDC roadmap/technical role includes consultation and tie-breaking for maintainer teams. It does not require a deploying platform to adopt every update or classification policy.
ROOST — Robust Open Online Safety Tools Inc → initially appoints and may replace maintainers → ROOST project maintainers
Repository host may replace for inactivity, vacancy or misconduct. Maintainers may appoint additional/replacement maintainers; exact current permission exercise not audited.
ROOST project maintainers → exercise project and merge authority under repository rules → ROOST Model Community (RMC)
Interpretation from the evidence
General ROOST project roles assign releases, development and merge approval under branch protection. RMC is a hosted project; this does not identify each actual RMC approver or prove a specific policy merge decision.
ROOST contributor / community role → may propose changes without membership-based permissions → ROOST project maintainers
Current policy gives ordinary community membership no explicit permissions. Employer organizations are not automatically contributors; partner GitHub teams administer access, not necessarily policy votes.