mirror of
https://github.com/vmware-tanzu/velero.git
synced 2026-09-27 18:34:18 +00:00
Shubham PampattiwarandGitHub
8f438e0b8e
Run the E2E test on kind / setup-test-matrix (push) Failing after 3s
e2e-test-kind.yaml / extract (push) Failing after 8s
Run the E2E test on kind / get-go-version (push) Failing after 8s
Run the E2E test on kind / build (push) Skipped
Run the E2E test on kind / run-e2e-test (push) Skipped
push.yml / extract (push) Failing after 7s
Scorecard supply-chain security / Scorecard analysis (push) Skipped
Main CI / get-go-version (push) Failing after 7s
Main CI / Build (push) Skipped
Add the maintainer information required by the CNCF Incubation criteria: - State that all maintainers share collective responsibility for the entire project, consistent with CODEOWNERS assigning ownership to the maintainer group as a whole (no siloed per-area owners). - Add a Contacting the maintainers section listing GitHub, Slack, the mailing list, and the security disclosure process. This makes MAINTAINERS.md cover names, contact information, domain of responsibility, and affiliation as required for the Incubation application. Signed-off-by: Shubham Pampattiwar <spampatt@redhat.com>
3.3 KiB
3.3 KiB
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 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.