SIG governance: Remove yearly SIG mailing list status update requirement

This commit is contained in:
Bob Killen 2023-03-22 18:48:52 -05:00
parent bd5c10e8b5
commit 2f4aafcf68
1 changed files with 1 additions and 3 deletions

View File

@ -13,9 +13,7 @@ route contributors to the appropriate SIG; SIGs should follow these guidelines:
repo.
- Record meetings and make them publicly available on the
[Kubernetes Community YouTube playlist].
- Report activity with the community via the dev@kubernetes.io mailing list at
least once a year.
- This is separate from the [annual report].
- Record activity and complete the [annual report].
- Participate in release planning meetings, retrospectives, and burndown
meetings, as needed.
- Ensure related work happens in a project-owned GitHub org and repository,