# Maintainers

| Name | GitHub | Role | Areas |
| --- | --- | --- | --- |
| Osman Aslan | [@oaslananka](https://github.com/oaslananka) | Maintainer / Owner | All areas — see [.github/CODEOWNERS](.github/CODEOWNERS) |

This list is intentionally short: ssh-mcp-pro currently has one maintainer.
See [GOVERNANCE.md](GOVERNANCE.md) for how decisions are made and what it
would take to add a second maintainer.

## Becoming a maintainer

There is no application process today because there is no committee to review
one. In practice, a path to maintainership runs through sustained, trusted
contribution — see "Path to adding maintainers" in
[GOVERNANCE.md](GOVERNANCE.md#path-to-adding-maintainers). If you are
interested, the most useful thing to do is contribute: open well-scoped pull
requests, help triage issues, and engage with review feedback.

## Maintainer responsibilities

- Triage issues and pull requests (see [SUPPORT.md](SUPPORT.md) for response
  targets).
- Review and merge contributions, enforcing the quality gate in
  [CONTRIBUTING.md](CONTRIBUTING.md).
- Own security response per [SECURITY.md](SECURITY.md).
- Cut releases per [docs/development/release-process.md](docs/development/release-process.md).