# Maintainers

## Active

| Name              | GitHub                                              | Areas                             |
|-------------------|-----------------------------------------------------|-----------------------------------|
| Ezzy1630     | [@Ezzy1630](https://github.com/Ezzy1630)  | All. Architecture, releases.      |

## Response time

This is a personal project. Best-effort response times:

- **Security reports** (per [SECURITY.md](SECURITY.md)): within 7 days, often faster.
- **Bug reports** with reproductions: within 14 days for an initial response.
- **Pull requests** from external contributors: within 14 days for an initial review.
- **Feature requests and general questions**: when I can; no commitment.

If you don't hear back in those windows, a polite nudge is welcome.

## Release management

Releases are cut by the active maintainer. Pre-1.0, minor versions land roughly every 4–6 weeks; patches as needed. See [ROADMAP.md](ROADMAP.md) for what's in flight.

## Becoming a maintainer

There is no formal process yet. If you've made several sustained, high-quality contributions and want a larger role, open an issue or reach out. The bar is judgment and reliability, not output volume.

## Code of Conduct enforcement

Maintainers are responsible for enforcing the [Code of Conduct](CODE_OF_CONDUCT.md). Report concerns to the contact listed there.
