Governance and Delivery
Reviewer roles
- Mission/content reviewers: clarity, accessibility, educational intent
- Code reviewers: behavior, safety, tests, maintainability
- Release steward: monthly changelog, roadmap updates, and merge readiness
Decision process
- Open proposal (issue or PR)
- Gather async feedback
- Resolve concerns in public thread
- Merge on maintainer approval and passing checks
If maintainers disagree, choose the option with:
1) clearer learner value, 2) lower maintenance cost, 3) better interoperability.
Response-time expectations
- First maintainer response: within 7 days
- Review follow-up after author update: within 7 days
- Monthly status update: within first 7 days of each month
Merge baseline
- Unit tests pass
- Mission validation passes
- PR template checklist completed
Roadmap
Now
- Reliable onboarding and contribution flow
- Mission-writing support for non-coders
- Accessibility baseline and review checklist
Next
- Pilot cohorts and feedback integration
- Mission packs (journalism, governance, genealogy)
- Better public metrics automation
Later
- Classroom dashboards
- Localization and translation infrastructure
- Multi-client ecosystem growth