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

Fix governance discoverability for CLOMonitor (MAINTAINERS.md link + README section) (#10466)
e2e-test-kind.yaml / extract (push) Failing after 8s
Details
Run the E2E test on kind / get-go-version (push) Failing after 9s
Details
Run the E2E test on kind / build (push) Skipped
Details
Run the E2E test on kind / setup-test-matrix (push) Failing after 4s
Details
Run the E2E test on kind / run-e2e-test (push) Skipped
Details
push.yml / extract (push) Failing after 7s
Details
Main CI / get-go-version (push) Failing after 8s
Details
Main CI / Build (push) Skipped
Details

Browse Source 
* Fix dead GOVERNANCE.md link in MAINTAINERS.md

The GOVERNANCE.md link pointed to the old vmware-tanzu/velero path,
which now returns a 404. Governance now lives at the org level under
velero-io/.github. Repoint the link so it resolves correctly.

Part of the CNCF incubation readiness work (#10383).

Signed-off-by: Shubham Pampattiwar <spampatt@redhat.com>

* Add Governance section to README for discoverability

CLOMonitor's governance check looks for a governance file or a
governance reference (header/link) in the README, not in MAINTAINERS.md.
Add a Governance section to the README linking the org-level
GOVERNANCE.md so the check passes and the info is discoverable.

Part of the CNCF incubation readiness work (#10383).

Signed-off-by: Shubham Pampattiwar <spampatt@redhat.com>

---------

Signed-off-by: Shubham Pampattiwar <spampatt@redhat.com>
This commit is contained in:
Shubham Pampattiwar
2026-09-04 13:31:20 +08:00
committed by GitHub
parent df180c039c
commit 0af5adf8d5
2 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
MAINTAINERS.md
+1 -1
View File
@@ -1,6 +1,6 @@
# Velero Maintainers
[GOVERNANCE.md](https://github.com/vmware-tanzu/velero/blob/main/GOVERNANCE.md) describes governance guidelines and maintainer responsibilities.
[GOVERNANCE.md](https://github.com/velero-io/.github/blob/main/GOVERNANCE.md) describes governance guidelines and maintainer responsibilities.
## Maintainers
README.md
+5
View File
@@ -45,6 +45,10 @@ See the [community page](https://velero.io/community/) for the full schedule and
If you are ready to jump in and test, add code, or help with documentation, follow the instructions on our [Start contributing][31] documentation for guidance on how to setup Velero for development.
## Governance
Velero's [governance][32] describes how the project is run, including the decision-making process, the roles and responsibilities of maintainers, and how to become a maintainer. Governance applies across the Velero org and is maintained at [velero-io/.github][32].
## Changelog
See [the list of releases][6] to find out about feature changes.
@@ -98,4 +102,5 @@ For website terms of use, trademark policy and other project policies please see
[29]: https://velero.io/docs/
[30]: https://velero.io/docs/troubleshooting
[31]: https://velero.io/docs/start-contributing
[32]: https://github.com/velero-io/.github/blob/main/GOVERNANCE.md
[100]: https://velero.io/docs/main/img/velero.png