Problem
IPI still depends on a bootstrap owner account and cannot yet require an independent approving review on every repository without risking deadlock.
Outcome
Create a public, evidence-based path from bootstrap control to independent maintenance.
Acceptance criteria
- define eligibility, conflicts of interest, inactivity, removal, and recovery for maintainers and IPI editors
- nominate at least two active reviewers whose independence and responsibilities are public
- map code ownership for active repositories without granting unnecessary organization-wide access
- document how an outside contributor can earn review and maintenance responsibility
- enable at least one required approving review after the reviewer pool is demonstrably sufficient
- record the decision through the governance and IPI processes
No individual should be appointed only to satisfy a number. The team must be able to review and operate the relevant project from public information.
Problem
IPI still depends on a bootstrap owner account and cannot yet require an independent approving review on every repository without risking deadlock.
Outcome
Create a public, evidence-based path from bootstrap control to independent maintenance.
Acceptance criteria
No individual should be appointed only to satisfy a number. The team must be able to review and operate the relevant project from public information.