# Maintainers

Maintainers have commit access to this repository and decide what lands in it. If you need a review, an answer on a design question, or a decision unstuck, these are the people to reach. Tagging the whole list on a pull request is fine.

How maintainers are added, how they step down, and how decisions get made are covered in [GOVERNANCE.md](GOVERNANCE.md).

## Current maintainers

| Name | GitHub |
|---|---|
| Bolin Chen | [@bolichen97](https://github.com/bolichen97) |
| Joe Guo | [@iamwhatever](https://github.com/iamwhatever) |
| Zezhen Xu | [@CrysisDeu](https://github.com/CrysisDeu) |

Every path in this repository is owned by `@kirodotdev/kirocrew-team` in [CODEOWNERS](.github/CODEOWNERS), so reviewers are requested automatically and you do not need to pick one by hand.

## Emeritus

Maintainers who have stepped back. Their past work stands, and any of them can pick commit access back up by asking.

None yet.

## Reaching maintainers

For anything about the project itself, open a [GitHub issue](https://github.com/kirodotdev/KiroCrew/issues) rather than contacting a maintainer directly. Public questions get answered where the next person with the same question can find them.

Do not use this list to report a security vulnerability. Follow [SECURITY.md](SECURITY.md) instead, which routes reports privately so a fix can ship before the problem is public.

Conduct concerns are handled under the [Code of Conduct](CODE_OF_CONDUCT.md), which names where those reports go.