# Maintainers

This file lists the maintainers of the RSR-Certified project.

## Current Maintainers

| Name | GitHub | Role | Perimeter |
|------|--------|------|-----------|
| *Your Name* | @Hyperpolymath | Lead Maintainer | Core (P1) |

## Emeritus Maintainers

Maintainers who have stepped back but retain honorary status:

*None yet*

## Becoming a Maintainer

To become a maintainer:

1. **Demonstrate Commitment**
   - Consistent contributions over 6+ months
   - Quality code reviews
   - Community engagement

2. **Show Expertise**
   - Deep understanding of the codebase
   - Security-conscious development
   - RSR/CCCP principles alignment

3. **Nomination Process**
   - Nominated by existing maintainer
   - 2/3 maintainer approval
   - 30-day provisional period

## Responsibilities

### All Maintainers
- Review pull requests within 72 hours
- Respond to security issues within 24 hours
- Participate in governance decisions
- Uphold Code of Conduct

### Lead Maintainer
- Release coordination
- External communications
- Conflict resolution (final)
- Onboarding new maintainers

## Contact

- **Security Issues**: See [SECURITY.md](SECURITY.md)
- **General**: Open an issue
- **Private**: maintainers@rsr-certified.dev

## Maintainer Emeritus Process

Maintainers may step back at any time:
1. Notify other maintainers
2. Transfer any critical responsibilities
3. Retain repository access for 90 days
4. Move to Emeritus status

---

*Updated: 2024-01-01*
