add API Machinery annual report

Signed-off-by: Madhav Jivrajani <[email protected]>

Author: MadhavJivrajani

sig-api-machinery/annual-report-2022.md

@@ -4,13 +4,13 @@
 
 1. What work did the SIG do this year that should be highlighted?
 
-   -
+   - Storage layer test unification (https://github.com/kubernetes/kubernetes/issues/109831)
    -
    -
 
 2. What initiatives are you working on that aren't being tracked in KEPs?
 
-   -
+   - Storage layer test unification (https://github.com/kubernetes/kubernetes/issues/109831)
    -
    -
 
@@ -32,7 +32,7 @@
 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)
 
-   -
+   - 
    -
    -
 
@@ -45,16 +45,19 @@
 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?
 
-   -
+   - No, it can be improved. The README points contributors to SIG meetings and triage meetings that happens twice a week.
 
 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]?
 
-   -
+   - No, it can be improved.
 
 5. Does the group have contributors from multiple companies/affiliations?
 
-   -
+   - Yes, there are contributors from [multiple companies](https://k8s.devstats.cncf.io/d/74/contributions-chart?var-period=m&var-metric=contributions&var-repogroup_name=SIG%20API%20Machinery&var-repo_name=kubernetes%2Fkubernetes&var-country_name=All&var-company_name=All&var-company=all).
+   We see all sorts of contributions, varying from issues, to comments, to PRs, to designs, to sig meeting participation,
+   and user-survey data.
+   
 
 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?
@@ -64,12 +67,12 @@
 
 ## 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 -->
+- Primary slack channel member count: 3912
+- Primary mailing list member count: 771
+- Primary meeting attendee count (estimated, if needed): 30 <!-- carried over from last year -->
+- Primary meeting participant count (estimated, if needed): 10 <!-- carried over from last year -->
+- Unique reviewers for SIG-owned packages: 111 <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
+- Unique approvers for SIG-owned packages: 94 <!-- 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
 
@@ -106,16 +109,16 @@ Include any other ways you measure group membership
 
 Operational tasks in [sig-governance.md]:
 
-- [ ] [README.md] reviewed for accuracy and updated if needed
+- [x] [README.md] reviewed for accuracy and updated if needed
 - [ ] [CONTRIBUTING.md] reviewed for accuracy and updated if needed
       (or created if missing and your contributor steps and experience are different or more
       in-depth than the documentation listed in the general [contributor guide] and [devel] folder.)
 - [ ] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed
-- [ ] SIG leaders (chairs, tech leads, and subproject owners) in [sigs.yaml] are accurate and active, and updated if needed
-- [ ] Meeting notes and recordings for 2022 are linked from [README.md] and updated/uploaded if needed
-- [ ] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings:
-      -
-      -
+- [x] SIG leaders (chairs, tech leads, and subproject owners) in [sigs.yaml] are accurate and active, and updated if needed
+- [x] Meeting notes and recordings for 2022 are linked from [README.md] and updated/uploaded if needed
+- [x] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings:
+      - KubeCon NA and EU 22 maintainer track
+      - 
 
 [CONTRIBUTING.md]: https://git.k8s.io/community/sig-api-machinery/CONTRIBUTING.md
 [contributor ladder]: https://git.k8s.io/community/community-membership.md