-
What work did the SIG do this year that should be highlighted?
-
What initiatives are you working on that aren't being tracked in KEPs?
-
KEP work in 2022 (v1.24, v1.25, v1.26):
- stable:
-
What areas and/or subprojects does your group need the most help with? Any areas with 2 or fewer OWNERs? (link to more details)
-
What metrics/community health stats does your group care about and/or measure?
-
Does your CONTRIBUTING.md help new contributors engage with your group specifically by pointing to activities or programs that provide useful context or allow easy participation?
-
If your group has special training, requirements for reviewers/approvers, or processes beyond the general contributor guide, does your CONTRIBUTING.md document those to help existing contributors grow throughout the contributor ladder?
-
Does the group have contributors from multiple companies/affiliations?
-
Are there ways end users/companies can contribute that they currently are not? If one of those ways is more full time support, what would they work on and why?
- Primary slack channel member count:
- Primary mailing list member count:
- Primary meeting attendee count (estimated, if needed):
- Primary meeting participant count (estimated, if needed):
- Unique reviewers for SIG-owned packages:
- Unique approvers for SIG-owned packages:
Include any other ways you measure group membership
Continuing:
- architecture-and-api-governance
- code-organization
- conformance-definition
- enhancements
- production-readiness
Continuing:
- API Expression
- Policy
- Reliability
- Structured Logging
Operational tasks in sig-governance.md:
- README.md reviewed for accuracy and updated if needed
- CONTRIBUTING.md reviewed for accuracy and updated if needed (or created if missing and your contributor steps and experience are different or more in-depth than the documentation listed in the general contributor guide and devel folder.)
- Subprojects list and linked OWNERS files in sigs.yaml reviewed for accuracy and updated if needed
- SIG leaders (chairs, tech leads, and subproject owners) in sigs.yaml are accurate and active, and updated if needed
- Meeting notes and recordings for 2022 are linked from README.md and updated/uploaded if needed
- Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: - -