velero/MAINTAINERS.md

Velero Maintainers

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). 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	OpenShift
Daniel Jiang	reasonerjt	Broadcom
Wenkai Yin	ywk253100	Broadcom
Xun Jiang	blackpiglet	Broadcom
Shubham Pampattiwar	shubham-pampattiwar	OpenShift
Yonghui Li	Lyndon-Li	Broadcom
Anshul Ahuja	anshulahuja98	Microsoft Azure
Tiger Kaovilai	kaovilai	OpenShift

Contacting the maintainers

• GitHub: open an issue or pull request in the relevant velero-io repository, or @mention a maintainer by their GitHub ID.
• Slack: #velero-dev on the Kubernetes Slack.
• Mailing list: Velero Google Group.
• Security issues: follow the private disclosure process in SECURITY.md (cncf-velero-security@lists.cncf.io). Do not report vulnerabilities through public channels.

Emeritus Maintainers

• Adnan Abdulhussein (prydonius)
• Andy Goldstein (ncdc)
• Steve Kriss (skriss)
• Carlos Panato (cpanato)
• Nolan Brubaker (nrb)
• Ashish Amarnath (ashish-amarnath)
• Carlisia Thompson (carlisia)
• Bridget McErlean (zubron)
• JenTing Hsiao (jenting)
• Dave Smith-Uchida (dsu-igeek)
• Ming Qiu (qiuming-best)