mirrors/velero
1
0
Fork 0
mirror of https://github.com/vmware-tanzu/velero.git synced 2026-09-27 18:34:18 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Document maintainer contact info and shared responsibility (#10568)
Run the E2E test on kind / setup-test-matrix (push) Failing after 3s
Details
e2e-test-kind.yaml / extract (push) Failing after 8s
Details
Run the E2E test on kind / get-go-version (push) Failing after 8s
Details
Run the E2E test on kind / build (push) Skipped
Details
Run the E2E test on kind / run-e2e-test (push) Skipped
Details
push.yml / extract (push) Failing after 7s
Details
Scorecard supply-chain security / Scorecard analysis (push) Skipped
Details
Main CI / get-go-version (push) Failing after 7s
Details
Main CI / Build (push) Skipped
Details

Browse Source 
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>
This commit is contained in:
Shubham Pampattiwar
2026-09-23 09:59:40 -04:00
committed by GitHub
parent 00788053ae
commit 8f438e0b8e
1 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
MAINTAINERS.md
+9
View File
@@ -4,6 +4,8 @@
## 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) |
@@ -15,6 +17,13 @@
| 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))