From 34d0c59cd7260cf80ecb58ab9eabb644d9b46b86 Mon Sep 17 00:00:00 2001 From: Christoph Blecker Date: Tue, 25 Jan 2022 08:54:16 -0800 Subject: [PATCH] Add annual report templates for 2021 --- generator/annual-report/sig_report.tmpl | 34 ++--- generator/annual-report/wg_report.tmpl | 18 +-- sig-api-machinery/annual-report-2021.md | 143 ++++++++++++++++++ sig-apps/annual-report-2021.md | 143 ++++++++++++++++++ sig-architecture/annual-report-2021.md | 143 ++++++++++++++++++ sig-auth/annual-report-2021.md | 143 ++++++++++++++++++ sig-autoscaling/annual-report-2021.md | 143 ++++++++++++++++++ sig-cli/annual-report-2021.md | 143 ++++++++++++++++++ sig-cloud-provider/annual-report-2021.md | 143 ++++++++++++++++++ sig-cluster-lifecycle/annual-report-2021.md | 143 ++++++++++++++++++ .../annual-report-2021.md | 143 ++++++++++++++++++ sig-docs/annual-report-2021.md | 143 ++++++++++++++++++ sig-instrumentation/annual-report-2021.md | 143 ++++++++++++++++++ sig-k8s-infra/annual-report-2021.md | 143 ++++++++++++++++++ sig-multicluster/annual-report-2021.md | 143 ++++++++++++++++++ sig-network/annual-report-2021.md | 143 ++++++++++++++++++ sig-node/annual-report-2021.md | 143 ++++++++++++++++++ sig-release/annual-report-2021.md | 143 ++++++++++++++++++ sig-scalability/annual-report-2021.md | 143 ++++++++++++++++++ sig-scheduling/annual-report-2021.md | 143 ++++++++++++++++++ sig-security/annual-report-2021.md | 143 ++++++++++++++++++ sig-service-catalog/annual-report-2021.md | 143 ++++++++++++++++++ sig-storage/annual-report-2021.md | 143 ++++++++++++++++++ sig-testing/annual-report-2021.md | 143 ++++++++++++++++++ sig-ui/annual-report-2021.md | 143 ++++++++++++++++++ sig-usability/annual-report-2021.md | 143 ++++++++++++++++++ sig-windows/annual-report-2021.md | 143 ++++++++++++++++++ wg-api-expression/annual-report-2021.md | 62 ++++++++ wg-data-protection/annual-report-2021.md | 62 ++++++++ wg-iot-edge/annual-report-2021.md | 62 ++++++++ wg-multitenancy/annual-report-2021.md | 62 ++++++++ wg-policy/annual-report-2021.md | 62 ++++++++ wg-reliability/annual-report-2021.md | 62 ++++++++ wg-structured-logging/annual-report-2021.md | 62 ++++++++ 34 files changed, 4035 insertions(+), 26 deletions(-) create mode 100644 sig-api-machinery/annual-report-2021.md create mode 100644 sig-apps/annual-report-2021.md create mode 100644 sig-architecture/annual-report-2021.md create mode 100644 sig-auth/annual-report-2021.md create mode 100644 sig-autoscaling/annual-report-2021.md create mode 100644 sig-cli/annual-report-2021.md create mode 100644 sig-cloud-provider/annual-report-2021.md create mode 100644 sig-cluster-lifecycle/annual-report-2021.md create mode 100644 sig-contributor-experience/annual-report-2021.md create mode 100644 sig-docs/annual-report-2021.md create mode 100644 sig-instrumentation/annual-report-2021.md create mode 100644 sig-k8s-infra/annual-report-2021.md create mode 100644 sig-multicluster/annual-report-2021.md create mode 100644 sig-network/annual-report-2021.md create mode 100644 sig-node/annual-report-2021.md create mode 100644 sig-release/annual-report-2021.md create mode 100644 sig-scalability/annual-report-2021.md create mode 100644 sig-scheduling/annual-report-2021.md create mode 100644 sig-security/annual-report-2021.md create mode 100644 sig-service-catalog/annual-report-2021.md create mode 100644 sig-storage/annual-report-2021.md create mode 100644 sig-testing/annual-report-2021.md create mode 100644 sig-ui/annual-report-2021.md create mode 100644 sig-usability/annual-report-2021.md create mode 100644 sig-windows/annual-report-2021.md create mode 100644 wg-api-expression/annual-report-2021.md create mode 100644 wg-data-protection/annual-report-2021.md create mode 100644 wg-iot-edge/annual-report-2021.md create mode 100644 wg-multitenancy/annual-report-2021.md create mode 100644 wg-policy/annual-report-2021.md create mode 100644 wg-reliability/annual-report-2021.md create mode 100644 wg-structured-logging/annual-report-2021.md diff --git a/generator/annual-report/sig_report.tmpl b/generator/annual-report/sig_report.tmpl index fb5443f5d..d018622a3 100644 --- a/generator/annual-report/sig_report.tmpl +++ b/generator/annual-report/sig_report.tmpl @@ -23,16 +23,16 @@ In future, this will be generated from kubernetes/enhancements kep.yaml files --> - Stable - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable - Beta - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta - Alpha - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha - Pre-alpha - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) ## Project health @@ -122,16 +122,16 @@ Continuing: 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 {{lastYear}} are linked from [README.md] and updated/uploaded if needed -[ ] Did you have community-wide updates in {{lastYear}} (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: - - - - +- [ ] [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 {{lastYear}} are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in {{lastYear}} (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - [CONTRIBUTING.md]: https://git.k8s.io/community/{{.Dir}}/CONTRIBUTING.md [contributor ladder]: https://git.k8s.io/community/community-membership.md diff --git a/generator/annual-report/wg_report.tmpl b/generator/annual-report/wg_report.tmpl index 6e4e2d5b2..1fde241ca 100644 --- a/generator/annual-report/wg_report.tmpl +++ b/generator/annual-report/wg_report.tmpl @@ -46,15 +46,15 @@ Include any other ways you measure group membership Operational tasks in [wg-governance.md]: -[ ] [README.md] reviewed for accuracy and updated if needed -[ ] WG leaders in [sigs.yaml] are accurate and active, and updated if needed -[ ] Meeting notes and recordings for {{lastYear}} are linked from [README.md] and updated/uploaded if needed -[ ] Updates provided to sponsoring SIGs in {{lastYear}} - - [$sig-name](https://git.k8s.io/community/$sig-id/) - - links to email, meeting notes, slides, or recordings, etc - - [$sig-name](https://git.k8s.io/community/$sig-id/) - - links to email, meeting notes, slides, or recordings, etc - - +- [ ] [README.md] reviewed for accuracy and updated if needed +- [ ] WG leaders in [sigs.yaml] are accurate and active, and updated if needed +- [ ] Meeting notes and recordings for {{lastYear}} are linked from [README.md] and updated/uploaded if needed +- [ ] Updates provided to sponsoring SIGs in {{lastYear}} + - [$sig-name](https://git.k8s.io/community/$sig-id/) + - links to email, meeting notes, slides, or recordings, etc + - [$sig-name](https://git.k8s.io/community/$sig-id/) + - links to email, meeting notes, slides, or recordings, etc + - [wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md [README.md]: https://git.k8s.io/community/{{.Dir}}/README.md diff --git a/sig-api-machinery/annual-report-2021.md b/sig-api-machinery/annual-report-2021.md new file mode 100644 index 000000000..bfa398960 --- /dev/null +++ b/sig-api-machinery/annual-report-2021.md @@ -0,0 +1,143 @@ +# 2021 Annual Report: SIG API Machinery + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +3. KEP work in 2021 (1.x, 1.y, 1.z): + + + + - Stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - Beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - Alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - Pre-alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) + +## Project health + +1. What areas and/or subprojects does your group need the most help with? + Any areas with 2 or fewer OWNERs? (link to more details) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +3. 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? + + - + +4. 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]? + + - + +5. Does the group have contributors from multiple companies/affiliations? + + - + +6. 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? + + - + - + +## Membership + +- 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 + +## Subprojects + + + +New in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Retired in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Continuing: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +## Working groups + + + +New in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Retired in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Continuing: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +## Operational + +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 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-api-machinery/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-api-machinery/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md + diff --git a/sig-apps/annual-report-2021.md b/sig-apps/annual-report-2021.md new file mode 100644 index 000000000..318b6761d --- /dev/null +++ b/sig-apps/annual-report-2021.md @@ -0,0 +1,143 @@ +# 2021 Annual Report: SIG Apps + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +3. KEP work in 2021 (1.x, 1.y, 1.z): + + + + - Stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - Beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - Alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - Pre-alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) + +## Project health + +1. What areas and/or subprojects does your group need the most help with? + Any areas with 2 or fewer OWNERs? (link to more details) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +3. 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? + + - + +4. 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]? + + - + +5. Does the group have contributors from multiple companies/affiliations? + + - + +6. 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? + + - + - + +## Membership + +- 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 + +## Subprojects + + + +New in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Retired in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Continuing: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +## Working groups + + + +New in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Retired in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Continuing: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +## Operational + +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 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-apps/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-apps/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md + diff --git a/sig-architecture/annual-report-2021.md b/sig-architecture/annual-report-2021.md new file mode 100644 index 000000000..faa497302 --- /dev/null +++ b/sig-architecture/annual-report-2021.md @@ -0,0 +1,143 @@ +# 2021 Annual Report: SIG Architecture + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +3. KEP work in 2021 (1.x, 1.y, 1.z): + + + + - Stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - Beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - Alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - Pre-alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) + +## Project health + +1. What areas and/or subprojects does your group need the most help with? + Any areas with 2 or fewer OWNERs? (link to more details) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +3. 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? + + - + +4. 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]? + + - + +5. Does the group have contributors from multiple companies/affiliations? + + - + +6. 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? + + - + - + +## Membership + +- 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 + +## Subprojects + + + +New in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Retired in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Continuing: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +## Working groups + + + +New in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Retired in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Continuing: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +## Operational + +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 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-architecture/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-architecture/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md + diff --git a/sig-auth/annual-report-2021.md b/sig-auth/annual-report-2021.md new file mode 100644 index 000000000..c247be3b6 --- /dev/null +++ b/sig-auth/annual-report-2021.md @@ -0,0 +1,143 @@ +# 2021 Annual Report: SIG Auth + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +3. KEP work in 2021 (1.x, 1.y, 1.z): + + + + - Stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - Beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - Alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - Pre-alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) + +## Project health + +1. What areas and/or subprojects does your group need the most help with? + Any areas with 2 or fewer OWNERs? (link to more details) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +3. 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? + + - + +4. 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]? + + - + +5. Does the group have contributors from multiple companies/affiliations? + + - + +6. 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? + + - + - + +## Membership + +- 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 + +## Subprojects + + + +New in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Retired in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Continuing: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +## Working groups + + + +New in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Retired in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Continuing: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +## Operational + +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 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-auth/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-auth/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md + diff --git a/sig-autoscaling/annual-report-2021.md b/sig-autoscaling/annual-report-2021.md new file mode 100644 index 000000000..0ba26a1f3 --- /dev/null +++ b/sig-autoscaling/annual-report-2021.md @@ -0,0 +1,143 @@ +# 2021 Annual Report: SIG Autoscaling + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +3. KEP work in 2021 (1.x, 1.y, 1.z): + + + + - Stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - Beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - Alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - Pre-alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) + +## Project health + +1. What areas and/or subprojects does your group need the most help with? + Any areas with 2 or fewer OWNERs? (link to more details) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +3. 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? + + - + +4. 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]? + + - + +5. Does the group have contributors from multiple companies/affiliations? + + - + +6. 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? + + - + - + +## Membership + +- 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 + +## Subprojects + + + +New in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Retired in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Continuing: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +## Working groups + + + +New in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Retired in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Continuing: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +## Operational + +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 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-autoscaling/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-autoscaling/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md + diff --git a/sig-cli/annual-report-2021.md b/sig-cli/annual-report-2021.md new file mode 100644 index 000000000..316cbdba3 --- /dev/null +++ b/sig-cli/annual-report-2021.md @@ -0,0 +1,143 @@ +# 2021 Annual Report: SIG CLI + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +3. KEP work in 2021 (1.x, 1.y, 1.z): + + + + - Stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - Beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - Alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - Pre-alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) + +## Project health + +1. What areas and/or subprojects does your group need the most help with? + Any areas with 2 or fewer OWNERs? (link to more details) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +3. 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? + + - + +4. 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]? + + - + +5. Does the group have contributors from multiple companies/affiliations? + + - + +6. 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? + + - + - + +## Membership + +- 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 + +## Subprojects + + + +New in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Retired in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Continuing: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +## Working groups + + + +New in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Retired in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Continuing: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +## Operational + +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 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-cli/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-cli/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md + diff --git a/sig-cloud-provider/annual-report-2021.md b/sig-cloud-provider/annual-report-2021.md new file mode 100644 index 000000000..09864bd73 --- /dev/null +++ b/sig-cloud-provider/annual-report-2021.md @@ -0,0 +1,143 @@ +# 2021 Annual Report: SIG Cloud Provider + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +3. KEP work in 2021 (1.x, 1.y, 1.z): + + + + - Stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - Beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - Alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - Pre-alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) + +## Project health + +1. What areas and/or subprojects does your group need the most help with? + Any areas with 2 or fewer OWNERs? (link to more details) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +3. 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? + + - + +4. 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]? + + - + +5. Does the group have contributors from multiple companies/affiliations? + + - + +6. 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? + + - + - + +## Membership + +- 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 + +## Subprojects + + + +New in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Retired in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Continuing: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +## Working groups + + + +New in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Retired in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Continuing: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +## Operational + +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 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-cloud-provider/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-cloud-provider/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md + diff --git a/sig-cluster-lifecycle/annual-report-2021.md b/sig-cluster-lifecycle/annual-report-2021.md new file mode 100644 index 000000000..593152092 --- /dev/null +++ b/sig-cluster-lifecycle/annual-report-2021.md @@ -0,0 +1,143 @@ +# 2021 Annual Report: SIG Cluster Lifecycle + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +3. KEP work in 2021 (1.x, 1.y, 1.z): + + + + - Stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - Beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - Alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - Pre-alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) + +## Project health + +1. What areas and/or subprojects does your group need the most help with? + Any areas with 2 or fewer OWNERs? (link to more details) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +3. 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? + + - + +4. 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]? + + - + +5. Does the group have contributors from multiple companies/affiliations? + + - + +6. 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? + + - + - + +## Membership + +- 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 + +## Subprojects + + + +New in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Retired in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Continuing: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +## Working groups + + + +New in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Retired in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Continuing: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +## Operational + +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 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-cluster-lifecycle/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-cluster-lifecycle/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md + diff --git a/sig-contributor-experience/annual-report-2021.md b/sig-contributor-experience/annual-report-2021.md new file mode 100644 index 000000000..296ba7415 --- /dev/null +++ b/sig-contributor-experience/annual-report-2021.md @@ -0,0 +1,143 @@ +# 2021 Annual Report: SIG Contributor Experience + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +3. KEP work in 2021 (1.x, 1.y, 1.z): + + + + - Stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - Beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - Alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - Pre-alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) + +## Project health + +1. What areas and/or subprojects does your group need the most help with? + Any areas with 2 or fewer OWNERs? (link to more details) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +3. 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? + + - + +4. 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]? + + - + +5. Does the group have contributors from multiple companies/affiliations? + + - + +6. 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? + + - + - + +## Membership + +- 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 + +## Subprojects + + + +New in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Retired in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Continuing: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +## Working groups + + + +New in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Retired in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Continuing: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +## Operational + +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 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-contributor-experience/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-contributor-experience/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md + diff --git a/sig-docs/annual-report-2021.md b/sig-docs/annual-report-2021.md new file mode 100644 index 000000000..8f6e074a0 --- /dev/null +++ b/sig-docs/annual-report-2021.md @@ -0,0 +1,143 @@ +# 2021 Annual Report: SIG Docs + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +3. KEP work in 2021 (1.x, 1.y, 1.z): + + + + - Stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - Beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - Alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - Pre-alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) + +## Project health + +1. What areas and/or subprojects does your group need the most help with? + Any areas with 2 or fewer OWNERs? (link to more details) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +3. 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? + + - + +4. 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]? + + - + +5. Does the group have contributors from multiple companies/affiliations? + + - + +6. 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? + + - + - + +## Membership + +- 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 + +## Subprojects + + + +New in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Retired in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Continuing: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +## Working groups + + + +New in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Retired in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Continuing: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +## Operational + +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 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-docs/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-docs/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md + diff --git a/sig-instrumentation/annual-report-2021.md b/sig-instrumentation/annual-report-2021.md new file mode 100644 index 000000000..6f200a4e5 --- /dev/null +++ b/sig-instrumentation/annual-report-2021.md @@ -0,0 +1,143 @@ +# 2021 Annual Report: SIG Instrumentation + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +3. KEP work in 2021 (1.x, 1.y, 1.z): + + + + - Stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - Beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - Alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - Pre-alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) + +## Project health + +1. What areas and/or subprojects does your group need the most help with? + Any areas with 2 or fewer OWNERs? (link to more details) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +3. 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? + + - + +4. 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]? + + - + +5. Does the group have contributors from multiple companies/affiliations? + + - + +6. 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? + + - + - + +## Membership + +- 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 + +## Subprojects + + + +New in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Retired in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Continuing: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +## Working groups + + + +New in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Retired in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Continuing: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +## Operational + +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 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-instrumentation/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-instrumentation/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md + diff --git a/sig-k8s-infra/annual-report-2021.md b/sig-k8s-infra/annual-report-2021.md new file mode 100644 index 000000000..33a8ca6b3 --- /dev/null +++ b/sig-k8s-infra/annual-report-2021.md @@ -0,0 +1,143 @@ +# 2021 Annual Report: SIG K8s Infra + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +3. KEP work in 2021 (1.x, 1.y, 1.z): + + + + - Stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - Beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - Alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - Pre-alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) + +## Project health + +1. What areas and/or subprojects does your group need the most help with? + Any areas with 2 or fewer OWNERs? (link to more details) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +3. 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? + + - + +4. 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]? + + - + +5. Does the group have contributors from multiple companies/affiliations? + + - + +6. 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? + + - + - + +## Membership + +- 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 + +## Subprojects + + + +New in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Retired in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Continuing: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +## Working groups + + + +New in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Retired in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Continuing: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +## Operational + +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 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-k8s-infra/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-k8s-infra/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md + diff --git a/sig-multicluster/annual-report-2021.md b/sig-multicluster/annual-report-2021.md new file mode 100644 index 000000000..53d8488ef --- /dev/null +++ b/sig-multicluster/annual-report-2021.md @@ -0,0 +1,143 @@ +# 2021 Annual Report: SIG Multicluster + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +3. KEP work in 2021 (1.x, 1.y, 1.z): + + + + - Stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - Beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - Alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - Pre-alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) + +## Project health + +1. What areas and/or subprojects does your group need the most help with? + Any areas with 2 or fewer OWNERs? (link to more details) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +3. 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? + + - + +4. 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]? + + - + +5. Does the group have contributors from multiple companies/affiliations? + + - + +6. 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? + + - + - + +## Membership + +- 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 + +## Subprojects + + + +New in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Retired in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Continuing: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +## Working groups + + + +New in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Retired in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Continuing: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +## Operational + +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 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-multicluster/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-multicluster/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md + diff --git a/sig-network/annual-report-2021.md b/sig-network/annual-report-2021.md new file mode 100644 index 000000000..447fd359a --- /dev/null +++ b/sig-network/annual-report-2021.md @@ -0,0 +1,143 @@ +# 2021 Annual Report: SIG Network + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +3. KEP work in 2021 (1.x, 1.y, 1.z): + + + + - Stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - Beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - Alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - Pre-alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) + +## Project health + +1. What areas and/or subprojects does your group need the most help with? + Any areas with 2 or fewer OWNERs? (link to more details) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +3. 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? + + - + +4. 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]? + + - + +5. Does the group have contributors from multiple companies/affiliations? + + - + +6. 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? + + - + - + +## Membership + +- 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 + +## Subprojects + + + +New in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Retired in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Continuing: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +## Working groups + + + +New in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Retired in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Continuing: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +## Operational + +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 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-network/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-network/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md + diff --git a/sig-node/annual-report-2021.md b/sig-node/annual-report-2021.md new file mode 100644 index 000000000..18384773f --- /dev/null +++ b/sig-node/annual-report-2021.md @@ -0,0 +1,143 @@ +# 2021 Annual Report: SIG Node + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +3. KEP work in 2021 (1.x, 1.y, 1.z): + + + + - Stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - Beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - Alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - Pre-alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) + +## Project health + +1. What areas and/or subprojects does your group need the most help with? + Any areas with 2 or fewer OWNERs? (link to more details) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +3. 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? + + - + +4. 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]? + + - + +5. Does the group have contributors from multiple companies/affiliations? + + - + +6. 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? + + - + - + +## Membership + +- 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 + +## Subprojects + + + +New in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Retired in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Continuing: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +## Working groups + + + +New in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Retired in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Continuing: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +## Operational + +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 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-node/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-node/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md + diff --git a/sig-release/annual-report-2021.md b/sig-release/annual-report-2021.md new file mode 100644 index 000000000..21e848aef --- /dev/null +++ b/sig-release/annual-report-2021.md @@ -0,0 +1,143 @@ +# 2021 Annual Report: SIG Release + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +3. KEP work in 2021 (1.x, 1.y, 1.z): + + + + - Stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - Beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - Alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - Pre-alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) + +## Project health + +1. What areas and/or subprojects does your group need the most help with? + Any areas with 2 or fewer OWNERs? (link to more details) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +3. 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? + + - + +4. 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]? + + - + +5. Does the group have contributors from multiple companies/affiliations? + + - + +6. 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? + + - + - + +## Membership + +- 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 + +## Subprojects + + + +New in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Retired in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Continuing: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +## Working groups + + + +New in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Retired in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Continuing: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +## Operational + +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 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-release/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-release/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md + diff --git a/sig-scalability/annual-report-2021.md b/sig-scalability/annual-report-2021.md new file mode 100644 index 000000000..e75a66dcf --- /dev/null +++ b/sig-scalability/annual-report-2021.md @@ -0,0 +1,143 @@ +# 2021 Annual Report: SIG Scalability + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +3. KEP work in 2021 (1.x, 1.y, 1.z): + + + + - Stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - Beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - Alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - Pre-alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) + +## Project health + +1. What areas and/or subprojects does your group need the most help with? + Any areas with 2 or fewer OWNERs? (link to more details) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +3. 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? + + - + +4. 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]? + + - + +5. Does the group have contributors from multiple companies/affiliations? + + - + +6. 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? + + - + - + +## Membership + +- 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 + +## Subprojects + + + +New in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Retired in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Continuing: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +## Working groups + + + +New in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Retired in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Continuing: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +## Operational + +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 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-scalability/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-scalability/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md + diff --git a/sig-scheduling/annual-report-2021.md b/sig-scheduling/annual-report-2021.md new file mode 100644 index 000000000..0cf9e6c4b --- /dev/null +++ b/sig-scheduling/annual-report-2021.md @@ -0,0 +1,143 @@ +# 2021 Annual Report: SIG Scheduling + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +3. KEP work in 2021 (1.x, 1.y, 1.z): + + + + - Stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - Beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - Alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - Pre-alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) + +## Project health + +1. What areas and/or subprojects does your group need the most help with? + Any areas with 2 or fewer OWNERs? (link to more details) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +3. 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? + + - + +4. 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]? + + - + +5. Does the group have contributors from multiple companies/affiliations? + + - + +6. 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? + + - + - + +## Membership + +- 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 + +## Subprojects + + + +New in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Retired in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Continuing: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +## Working groups + + + +New in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Retired in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Continuing: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +## Operational + +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 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-scheduling/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-scheduling/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md + diff --git a/sig-security/annual-report-2021.md b/sig-security/annual-report-2021.md new file mode 100644 index 000000000..9684e8f59 --- /dev/null +++ b/sig-security/annual-report-2021.md @@ -0,0 +1,143 @@ +# 2021 Annual Report: SIG Security + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +3. KEP work in 2021 (1.x, 1.y, 1.z): + + + + - Stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - Beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - Alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - Pre-alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) + +## Project health + +1. What areas and/or subprojects does your group need the most help with? + Any areas with 2 or fewer OWNERs? (link to more details) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +3. 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? + + - + +4. 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]? + + - + +5. Does the group have contributors from multiple companies/affiliations? + + - + +6. 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? + + - + - + +## Membership + +- 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 + +## Subprojects + + + +New in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Retired in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Continuing: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +## Working groups + + + +New in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Retired in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Continuing: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +## Operational + +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 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-security/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-security/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md + diff --git a/sig-service-catalog/annual-report-2021.md b/sig-service-catalog/annual-report-2021.md new file mode 100644 index 000000000..3ed71f988 --- /dev/null +++ b/sig-service-catalog/annual-report-2021.md @@ -0,0 +1,143 @@ +# 2021 Annual Report: SIG Service Catalog + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +3. KEP work in 2021 (1.x, 1.y, 1.z): + + + + - Stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - Beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - Alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - Pre-alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) + +## Project health + +1. What areas and/or subprojects does your group need the most help with? + Any areas with 2 or fewer OWNERs? (link to more details) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +3. 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? + + - + +4. 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]? + + - + +5. Does the group have contributors from multiple companies/affiliations? + + - + +6. 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? + + - + - + +## Membership + +- 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 + +## Subprojects + + + +New in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Retired in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Continuing: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +## Working groups + + + +New in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Retired in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Continuing: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +## Operational + +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 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-service-catalog/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-service-catalog/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md + diff --git a/sig-storage/annual-report-2021.md b/sig-storage/annual-report-2021.md new file mode 100644 index 000000000..c3c8ce0e1 --- /dev/null +++ b/sig-storage/annual-report-2021.md @@ -0,0 +1,143 @@ +# 2021 Annual Report: SIG Storage + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +3. KEP work in 2021 (1.x, 1.y, 1.z): + + + + - Stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - Beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - Alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - Pre-alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) + +## Project health + +1. What areas and/or subprojects does your group need the most help with? + Any areas with 2 or fewer OWNERs? (link to more details) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +3. 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? + + - + +4. 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]? + + - + +5. Does the group have contributors from multiple companies/affiliations? + + - + +6. 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? + + - + - + +## Membership + +- 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 + +## Subprojects + + + +New in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Retired in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Continuing: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +## Working groups + + + +New in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Retired in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Continuing: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +## Operational + +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 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-storage/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-storage/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md + diff --git a/sig-testing/annual-report-2021.md b/sig-testing/annual-report-2021.md new file mode 100644 index 000000000..12ddfca74 --- /dev/null +++ b/sig-testing/annual-report-2021.md @@ -0,0 +1,143 @@ +# 2021 Annual Report: SIG Testing + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +3. KEP work in 2021 (1.x, 1.y, 1.z): + + + + - Stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - Beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - Alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - Pre-alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) + +## Project health + +1. What areas and/or subprojects does your group need the most help with? + Any areas with 2 or fewer OWNERs? (link to more details) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +3. 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? + + - + +4. 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]? + + - + +5. Does the group have contributors from multiple companies/affiliations? + + - + +6. 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? + + - + - + +## Membership + +- 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 + +## Subprojects + + + +New in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Retired in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Continuing: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +## Working groups + + + +New in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Retired in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Continuing: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +## Operational + +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 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-testing/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-testing/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md + diff --git a/sig-ui/annual-report-2021.md b/sig-ui/annual-report-2021.md new file mode 100644 index 000000000..c53834ba1 --- /dev/null +++ b/sig-ui/annual-report-2021.md @@ -0,0 +1,143 @@ +# 2021 Annual Report: SIG UI + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +3. KEP work in 2021 (1.x, 1.y, 1.z): + + + + - Stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - Beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - Alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - Pre-alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) + +## Project health + +1. What areas and/or subprojects does your group need the most help with? + Any areas with 2 or fewer OWNERs? (link to more details) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +3. 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? + + - + +4. 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]? + + - + +5. Does the group have contributors from multiple companies/affiliations? + + - + +6. 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? + + - + - + +## Membership + +- 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 + +## Subprojects + + + +New in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Retired in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Continuing: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +## Working groups + + + +New in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Retired in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Continuing: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +## Operational + +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 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-ui/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-ui/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md + diff --git a/sig-usability/annual-report-2021.md b/sig-usability/annual-report-2021.md new file mode 100644 index 000000000..6d2230d71 --- /dev/null +++ b/sig-usability/annual-report-2021.md @@ -0,0 +1,143 @@ +# 2021 Annual Report: SIG Usability + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +3. KEP work in 2021 (1.x, 1.y, 1.z): + + + + - Stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - Beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - Alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - Pre-alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) + +## Project health + +1. What areas and/or subprojects does your group need the most help with? + Any areas with 2 or fewer OWNERs? (link to more details) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +3. 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? + + - + +4. 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]? + + - + +5. Does the group have contributors from multiple companies/affiliations? + + - + +6. 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? + + - + - + +## Membership + +- 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 + +## Subprojects + + + +New in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Retired in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Continuing: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +## Working groups + + + +New in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Retired in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Continuing: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +## Operational + +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 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-usability/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-usability/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md + diff --git a/sig-windows/annual-report-2021.md b/sig-windows/annual-report-2021.md new file mode 100644 index 000000000..818f81503 --- /dev/null +++ b/sig-windows/annual-report-2021.md @@ -0,0 +1,143 @@ +# 2021 Annual Report: SIG Windows + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +3. KEP work in 2021 (1.x, 1.y, 1.z): + + + + - Stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - Beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - Alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - Pre-alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) + +## Project health + +1. What areas and/or subprojects does your group need the most help with? + Any areas with 2 or fewer OWNERs? (link to more details) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +3. 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? + + - + +4. 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]? + + - + +5. Does the group have contributors from multiple companies/affiliations? + + - + +6. 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? + + - + - + +## Membership + +- 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 + +## Subprojects + + + +New in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Retired in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Continuing: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +## Working groups + + + +New in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Retired in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Continuing: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +## Operational + +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 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-windows/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-windows/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md + diff --git a/wg-api-expression/annual-report-2021.md b/wg-api-expression/annual-report-2021.md new file mode 100644 index 000000000..2f60d4386 --- /dev/null +++ b/wg-api-expression/annual-report-2021.md @@ -0,0 +1,62 @@ +# 2021 Annual Report: WG API Expression + +## Current initiatives + +1. What work did the WG do this year that should be highlighted? + For example, artifacts, reports, white papers produced this year. + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +## Project health + +1. What's the current roadmap until completion of the working group? + + - + - + - + +2. Does the group have contributors from multiple companies/affiliations? + + - + +3. 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? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): + +Include any other ways you measure group membership + +## Operational + +Operational tasks in [wg-governance.md]: + +- [ ] [README.md] reviewed for accuracy and updated if needed +- [ ] WG leaders in [sigs.yaml] are accurate and active, and updated if needed +- [ ] Meeting notes and recordings for 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Updates provided to sponsoring SIGs in 2021 + - [$sig-name](https://git.k8s.io/community/$sig-id/) + - links to email, meeting notes, slides, or recordings, etc + - [$sig-name](https://git.k8s.io/community/$sig-id/) + - links to email, meeting notes, slides, or recordings, etc + - + +[wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md +[README.md]: https://git.k8s.io/community/wg-api-expression/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml + diff --git a/wg-data-protection/annual-report-2021.md b/wg-data-protection/annual-report-2021.md new file mode 100644 index 000000000..d3d281e56 --- /dev/null +++ b/wg-data-protection/annual-report-2021.md @@ -0,0 +1,62 @@ +# 2021 Annual Report: WG Data Protection + +## Current initiatives + +1. What work did the WG do this year that should be highlighted? + For example, artifacts, reports, white papers produced this year. + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +## Project health + +1. What's the current roadmap until completion of the working group? + + - + - + - + +2. Does the group have contributors from multiple companies/affiliations? + + - + +3. 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? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): + +Include any other ways you measure group membership + +## Operational + +Operational tasks in [wg-governance.md]: + +- [ ] [README.md] reviewed for accuracy and updated if needed +- [ ] WG leaders in [sigs.yaml] are accurate and active, and updated if needed +- [ ] Meeting notes and recordings for 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Updates provided to sponsoring SIGs in 2021 + - [$sig-name](https://git.k8s.io/community/$sig-id/) + - links to email, meeting notes, slides, or recordings, etc + - [$sig-name](https://git.k8s.io/community/$sig-id/) + - links to email, meeting notes, slides, or recordings, etc + - + +[wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md +[README.md]: https://git.k8s.io/community/wg-data-protection/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml + diff --git a/wg-iot-edge/annual-report-2021.md b/wg-iot-edge/annual-report-2021.md new file mode 100644 index 000000000..b6120e071 --- /dev/null +++ b/wg-iot-edge/annual-report-2021.md @@ -0,0 +1,62 @@ +# 2021 Annual Report: WG IoT Edge + +## Current initiatives + +1. What work did the WG do this year that should be highlighted? + For example, artifacts, reports, white papers produced this year. + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +## Project health + +1. What's the current roadmap until completion of the working group? + + - + - + - + +2. Does the group have contributors from multiple companies/affiliations? + + - + +3. 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? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): + +Include any other ways you measure group membership + +## Operational + +Operational tasks in [wg-governance.md]: + +- [ ] [README.md] reviewed for accuracy and updated if needed +- [ ] WG leaders in [sigs.yaml] are accurate and active, and updated if needed +- [ ] Meeting notes and recordings for 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Updates provided to sponsoring SIGs in 2021 + - [$sig-name](https://git.k8s.io/community/$sig-id/) + - links to email, meeting notes, slides, or recordings, etc + - [$sig-name](https://git.k8s.io/community/$sig-id/) + - links to email, meeting notes, slides, or recordings, etc + - + +[wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md +[README.md]: https://git.k8s.io/community/wg-iot-edge/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml + diff --git a/wg-multitenancy/annual-report-2021.md b/wg-multitenancy/annual-report-2021.md new file mode 100644 index 000000000..48822ea60 --- /dev/null +++ b/wg-multitenancy/annual-report-2021.md @@ -0,0 +1,62 @@ +# 2021 Annual Report: WG Multitenancy + +## Current initiatives + +1. What work did the WG do this year that should be highlighted? + For example, artifacts, reports, white papers produced this year. + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +## Project health + +1. What's the current roadmap until completion of the working group? + + - + - + - + +2. Does the group have contributors from multiple companies/affiliations? + + - + +3. 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? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): + +Include any other ways you measure group membership + +## Operational + +Operational tasks in [wg-governance.md]: + +- [ ] [README.md] reviewed for accuracy and updated if needed +- [ ] WG leaders in [sigs.yaml] are accurate and active, and updated if needed +- [ ] Meeting notes and recordings for 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Updates provided to sponsoring SIGs in 2021 + - [$sig-name](https://git.k8s.io/community/$sig-id/) + - links to email, meeting notes, slides, or recordings, etc + - [$sig-name](https://git.k8s.io/community/$sig-id/) + - links to email, meeting notes, slides, or recordings, etc + - + +[wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md +[README.md]: https://git.k8s.io/community/wg-multitenancy/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml + diff --git a/wg-policy/annual-report-2021.md b/wg-policy/annual-report-2021.md new file mode 100644 index 000000000..a2399a31d --- /dev/null +++ b/wg-policy/annual-report-2021.md @@ -0,0 +1,62 @@ +# 2021 Annual Report: WG Policy + +## Current initiatives + +1. What work did the WG do this year that should be highlighted? + For example, artifacts, reports, white papers produced this year. + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +## Project health + +1. What's the current roadmap until completion of the working group? + + - + - + - + +2. Does the group have contributors from multiple companies/affiliations? + + - + +3. 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? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): + +Include any other ways you measure group membership + +## Operational + +Operational tasks in [wg-governance.md]: + +- [ ] [README.md] reviewed for accuracy and updated if needed +- [ ] WG leaders in [sigs.yaml] are accurate and active, and updated if needed +- [ ] Meeting notes and recordings for 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Updates provided to sponsoring SIGs in 2021 + - [$sig-name](https://git.k8s.io/community/$sig-id/) + - links to email, meeting notes, slides, or recordings, etc + - [$sig-name](https://git.k8s.io/community/$sig-id/) + - links to email, meeting notes, slides, or recordings, etc + - + +[wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md +[README.md]: https://git.k8s.io/community/wg-policy/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml + diff --git a/wg-reliability/annual-report-2021.md b/wg-reliability/annual-report-2021.md new file mode 100644 index 000000000..923acd4e0 --- /dev/null +++ b/wg-reliability/annual-report-2021.md @@ -0,0 +1,62 @@ +# 2021 Annual Report: WG Reliability + +## Current initiatives + +1. What work did the WG do this year that should be highlighted? + For example, artifacts, reports, white papers produced this year. + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +## Project health + +1. What's the current roadmap until completion of the working group? + + - + - + - + +2. Does the group have contributors from multiple companies/affiliations? + + - + +3. 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? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): + +Include any other ways you measure group membership + +## Operational + +Operational tasks in [wg-governance.md]: + +- [ ] [README.md] reviewed for accuracy and updated if needed +- [ ] WG leaders in [sigs.yaml] are accurate and active, and updated if needed +- [ ] Meeting notes and recordings for 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Updates provided to sponsoring SIGs in 2021 + - [$sig-name](https://git.k8s.io/community/$sig-id/) + - links to email, meeting notes, slides, or recordings, etc + - [$sig-name](https://git.k8s.io/community/$sig-id/) + - links to email, meeting notes, slides, or recordings, etc + - + +[wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md +[README.md]: https://git.k8s.io/community/wg-reliability/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml + diff --git a/wg-structured-logging/annual-report-2021.md b/wg-structured-logging/annual-report-2021.md new file mode 100644 index 000000000..472825451 --- /dev/null +++ b/wg-structured-logging/annual-report-2021.md @@ -0,0 +1,62 @@ +# 2021 Annual Report: WG Structured Logging + +## Current initiatives + +1. What work did the WG do this year that should be highlighted? + For example, artifacts, reports, white papers produced this year. + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +## Project health + +1. What's the current roadmap until completion of the working group? + + - + - + - + +2. Does the group have contributors from multiple companies/affiliations? + + - + +3. 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? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): + +Include any other ways you measure group membership + +## Operational + +Operational tasks in [wg-governance.md]: + +- [ ] [README.md] reviewed for accuracy and updated if needed +- [ ] WG leaders in [sigs.yaml] are accurate and active, and updated if needed +- [ ] Meeting notes and recordings for 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Updates provided to sponsoring SIGs in 2021 + - [$sig-name](https://git.k8s.io/community/$sig-id/) + - links to email, meeting notes, slides, or recordings, etc + - [$sig-name](https://git.k8s.io/community/$sig-id/) + - links to email, meeting notes, slides, or recordings, etc + - + +[wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md +[README.md]: https://git.k8s.io/community/wg-structured-logging/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +