Add annual report templates for 2021

1 files changed, 143 insertions, 0 deletions

diff --git a/sig-network/annual-report-2021.md b/sig-network/annual-report-2021.md
new file mode 100644
index 00000000..447fd359
--- /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):
+
+<!--
+In future, this will be generated from kubernetes/enhancements kep.yaml files
+1. with SIG as owning-sig or in participating-sigs
+2. listing 1.x, 1.y, or 1.z in milestones or in latest-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
+   - 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: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
+- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
+
+Include any other ways you measure group membership
+
+## Subprojects
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+Manually visible via `git diff HEAD@{$YYYY-01-01} HEAD@{$YYYY-12-31} -- $sig-id/README.md`
+-->
+
+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
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+Manually visible via `git diff HEAD@{$YYYY-01-01} HEAD@{$YYYY-12-31} -- $sig-id/README.md`
+-->
+
+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
+