# Velero Maintainers

[GOVERNANCE.md](https://github.com/velero-io/.github/blob/main/GOVERNANCE.md) describes governance guidelines and maintainer responsibilities.

## Maintainers

All maintainers share collective responsibility for the entire Velero project. There are no siloed, per-area owners: every maintainer is a final reviewer of pull requests across the codebase, and code ownership is assigned to the maintainer group as a whole (see [CODEOWNERS](https://github.com/velero-io/velero/blob/main/CODEOWNERS)). Maintainers review PRs, ensure code quality, triage issues, fix bugs, and perform release and maintenance tasks across all components.

| Maintainer          | GitHub ID                                                     | Affiliation                                      |
|---------------------|---------------------------------------------------------------|--------------------------------------------------|
| Scott Seago         | [sseago](https://github.com/sseago)                           | [OpenShift](https://github.com/openshift)        |
| Daniel Jiang        | [reasonerjt](https://github.com/reasonerjt)                   | Broadcom                                         |
| Wenkai Yin          | [ywk253100](https://github.com/ywk253100)                     | Broadcom                                         |
| Xun Jiang           | [blackpiglet](https://github.com/blackpiglet)                 | Broadcom                                         |
| Shubham Pampattiwar | [shubham-pampattiwar](https://github.com/shubham-pampattiwar) | [OpenShift](https://github.com/openshift)        |
| Yonghui Li          | [Lyndon-Li](https://github.com/Lyndon-Li)                     | Broadcom                                         |
| Anshul Ahuja        | [anshulahuja98](https://github.com/anshulahuja98)             | [Microsoft Azure](https://www.github.com/azure/) |
| Tiger Kaovilai      | [kaovilai](https://github.com/kaovilai)                       | [OpenShift](https://github.com/openshift)        |

## Contacting the maintainers

* **GitHub:** open an issue or pull request in the relevant [velero-io](https://github.com/velero-io) repository, or @mention a maintainer by their GitHub ID.
* **Slack:** [#velero](https://kubernetes.slack.com/messages/velero) on the Kubernetes Slack.
* **Mailing list:** [Velero Google Group](https://groups.google.com/forum/#!forum/projectvelero).
* **Security issues:** follow the private disclosure process in [SECURITY.md](https://github.com/velero-io/.github/blob/main/SECURITY.md) (cncf-velero-security@lists.cncf.io). Do not report vulnerabilities through public channels.

## Emeritus Maintainers
* Adnan Abdulhussein ([prydonius](https://github.com/prydonius))
* Andy Goldstein ([ncdc](https://github.com/ncdc))
* Steve Kriss ([skriss](https://github.com/skriss))
* Carlos Panato ([cpanato](https://github.com/cpanato))
* Nolan Brubaker ([nrb](https://github.com/nrb))
* Ashish Amarnath ([ashish-amarnath](https://github.com/ashish-amarnath))
* Carlisia Thompson ([carlisia](https://github.com/carlisia))
* Bridget McErlean ([zubron](https://github.com/zubron))
* JenTing Hsiao ([jenting](https://github.com/jenting))
* Dave Smith-Uchida ([dsu-igeek](https://github.com/dsu-igeek))
* Ming Qiu ([qiuming-best](https://github.com/qiuming-best))