You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[2527 - Clarify meaning of status](https://github.com/kubernetes/enhancements/blob/master/keps/sig-architecture/2527-clarify-status-observations-vs-rbac/README.md) - 1.22
24
+
-[1693 - Warning API mechanism](https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/1693-warnings/README.md) - 1.22
-[2572 - Defining the Kubernetes release cadence](https://github.com/kubernetes/enhancements/blob/master/keps/sig-release/2572-release-cadence/) - 1.23
36
27
37
28
## Project health
38
29
39
30
1. What areas and/or subprojects does your group need the most help with?
40
31
Any areas with 2 or fewer OWNERs? (link to more details)
41
32
42
-
-
43
-
-
44
-
-
33
+
- PRR we need to grow more reviewers and approvers
34
+
- API reviews has a pipeline set up with Jordan leading. Need more SIGs to identify additional folks to start learning
35
+
- Conformance, all the easy stuff is done. So we have harder stuff to review, so need additional folks with context to help make progress
45
36
46
37
2. What metrics/community health stats does your group care about and/or measure?
47
38
48
-
-
49
-
-
39
+
- We care about regressions, backports, dependencies across release boundaries
40
+
- We care about the number of enhancements per release along with their timely graduation
50
41
-
51
42
52
43
3. Does your [CONTRIBUTING.md] help **new** contributors engage with your group specifically by pointing
53
44
to activities or programs that provide useful context or allow easy participation?
54
45
55
-
-
46
+
- Yes. it is [here](https://github.com/kubernetes/community/blob/master/sig-architecture/CONTRIBUTING.md)
56
47
57
48
4. If your group has special training, requirements for reviewers/approvers, or processes beyond the general [contributor guide],
58
49
does your [CONTRIBUTING.md] document those to help **existing** contributors grow throughout the [contributor ladder]?
59
50
60
-
-
51
+
- PRR and API review has dedicated docs that can help folks get start. What we need is for SIG leads to send people our way
52
+
- API review: each SIG can identify 2-3 people to be involved in API reviews - https://github.com/kubernetes/kubernetes/blob/v1.23.0/OWNERS_ALIASES#L451-L452
61
53
62
54
5. Does the group have contributors from multiple companies/affiliations?
63
55
64
-
-
56
+
- yes
65
57
66
58
6. Are there ways end users/companies can contribute that they currently are not?
67
59
If one of those ways is more full time support, what would they work on and why?
68
60
69
-
-
61
+
- We need help across all the subprojects that have well defined, ongoing work with an onboarding guide/doc
70
62
-
71
63
72
64
## Membership
73
65
74
-
- Primary slack channel member count:
75
-
- Primary mailing list member count:
76
-
- Primary meeting attendee count (estimated, if needed):
77
-
- Primary meeting participant count (estimated, if needed):
78
-
- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
79
-
- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
- Unique reviewers for SIG-owned packages: 20 <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
71
+
- Unique approvers for SIG-owned packages: 13
72
+
<!--
73
+
Used this from the owners [alias file](https://github.com/kubernetes/kubernetes/blob/master/OWNERS_ALIASES)
74
+
Counted Unique approvers and reviewers.
75
+
Did not count approvers again as reviewers. - Riaan
In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
106
-
Manually visible via `git diff HEAD@{$YYYY-01-01} HEAD@{$YYYY-12-31} -- $sig-id/README.md`
107
-
-->
152
+
-[Architecture and API Governance](https://github.com/kubernetes/community/tree/master/sig-architecture#architecture-and-api-governance-1)
153
+
- API guidance updates
154
+
- [Object references](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#object-references), including cross-namespace references from namespaced objects
155
+
- [Spec and Status](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status) ([#5842](https://github.com/kubernetes/community/pull/5842))
156
+
- 114 [API reviews completed](https://github.com/orgs/kubernetes/projects/13) in 2021 (30 for v1.21, 45 for v1.22, 39 for v1.23)
157
+
- Each SIG can identify 2-3 people to be involved in API reviews - https://github.com/kubernetes/kubernetes/blob/v1.23.0/OWNERS_ALIASES#L451-L452
- We started 2021 with 128 endpoints remaining without conformance test.(69.13% conformance tested)
160
+
- The current count is [51 endpoints](https://apisnoop.cncf.io/conformance-progress/endpoints/1.24.0/?filter=untested)
161
+
remaining without conformance tests putting us at [87.25%](https://apisnoop.cncf.io/?conformance-only=true) conformance tested.
162
+
- In the last 12 months
163
+
- Tests for 75 endpoints was promoted to conformance
164
+
- 34 Endpoints was promoted to GA with conformance tests
165
+
- No new technical debt was incurred
166
+
- We moved the Conformance Office Hours Meeting from Bi-weekly to monthly in Aug 2021 to reduce the strain on attendee's calendars and increase engagement.
167
+
- At the start of 2021 the tracking of ineligible endpoints for conformance was moved to
- In 2021, the subproject was mainly focused on improving the contributor experience via automation and thoughtful ui/ux changes making visible changes to the KEP process.
181
+
- Major efforts were put into improving tooling on the enhancements repo throughout the year allowing us to automate more validation lessening the burden on individual approvers and resulting in more accurate information reflected in the document. All KEPs were migrated to the new template which now includes a key.yaml file.
182
+
- The team had major contributions authoring and negotiating [KEP 2572 - Defining the Kubernetes release cadence](https://github.com/kubernetes/enhancements/blob/master/keps/sig-release/2572-release-cadence/).
183
+
- We made progress on the receipts process, but ultimately decided that it was too disruptive for the community as a new UI/UX.
184
+
- The team updated the repository documentation and work was started on a KEP website for easier navigation.
185
+
- New members joined the team: 1 new approver and 2 reviewers were added to the Enhancements Subproject. A new kep tools team with initially 4 reviewers and approvers was created and more recently had an addition of 1 new approver/reviewer. We also had 2 owners transition to become our first Emeritus approvers.
186
+
- We hope to keep improving the KEP process in 2022 and will be conducting a community survey to collect feedback, working on a Process KEP template and other improvements.
187
+
- In 2021, the subproject also started a [_KEP Reading Club_](https://docs.google.com/document/d/17kQZ__AfMv2D4O5PHJIKXyr9lNwYNAZjYUhvt3gRXCU/edit?usp=sharing) with the intent of creating more awareness around the features being worked on, more familiarity with the KEP process, and potentially connecting aspiring contributors with KEP authors looking for help.
188
+
- In 2021, we've conducted [8 sessions](https://www.youtube.com/playlist?list=PL69nYSiGNLP3hHfpaik9WzlbxB43BUPJ6) of the reading club which involved discussing important KEPs such as [KEP-2221: Removing dockershim from kubelet](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2221-remove-dockershim) and [KEP-3136: Beta APIs Are Off by Default](https://github.com/kubernetes/enhancements/tree/master/keps/sig-architecture/3136-beta-apis-off-by-default).
189
+
- These discussions have led to feedback that was taken by stakeholder SIGs and used to drive deeper discussions around the design of that feature, examples of such cases are [KEP-1440: kubectl events](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cli/1440-kubectl-events) and [KEP-2258: Node service log viewer](https://github.com/kubernetes/enhancements/blob/master/keps/sig-windows/2258-node-service-log-viewer/README.md).
TODO: dims to send email to WG asking them to talk to us sync of async
120
214
121
215
## Operational
122
216
123
217
Operational tasks in [sig-governance.md]:
124
218
125
-
-[][README.md] reviewed for accuracy and updated if needed
126
-
-[][CONTRIBUTING.md] reviewed for accuracy and updated if needed
219
+
-[x][README.md](https://github.com/kubernetes/community/blob/master/sig-architecture/README.md) reviewed for accuracy and updated if needed
220
+
-[x][CONTRIBUTING.md](https://github.com/kubernetes/community/blob/master/sig-architecture/CONTRIBUTING.md) reviewed for accuracy and updated if needed
127
221
(or created if missing and your contributor steps and experience are different or more
128
222
in-depth than the documentation listed in the general [contributor guide] and [devel] folder.)
129
-
-[ ] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed
223
+
**We need to create this:**
224
+
- [ ] [HackMD](https://hackmd.io/GY081dMNThS16WWWB46unw) for template started - Riaan
225
+
-[ ][Subprojects list](https://github.com/kubernetes/community/blob/master/sig-architecture/README.md#subprojects) and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed
130
226
-[ ] SIG leaders (chairs, tech leads, and subproject owners) in [sigs.yaml] are accurate and active, and updated if needed
131
-
-[ ] Meeting notes and recordings for 2021 are linked from [README.md] and updated/uploaded if needed
227
+
- [ ] **MAYBE SOME REVIEW IS NEEDED, SOME OWNERS FILES LAST UPDATED 2019**
228
+
-[ ][Meeting notes and recordings](https://github.com/kubernetes/community/blob/master/sig-architecture/README.md#meetings) for 2021 are linked from [README.md] and updated/uploaded if needed
229
+
- [ ] **NEED UPDATES**
230
+
- [ ] Dead link to Enhancements Subproject Meeting Youtube
231
+
- [ ] Last SIG Recording uploaded Jul 2021
132
232
-[ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings:
133
-
-
134
-
-
233
+
- 2021 Kubecon EU Virtual Kubernetes Conformance
234
+
[A talk on what Kubernetes Conformance is and how to contribute to it](https://www.youtube.com/watch?v=05NMwOhD6Ks) by Zach Mandeville and Caleb Woodbine.
235
+
- 2021 Kubecon NA Virtual - Kubernetes Conformance
236
+
[A talk on the tooling that has been used the community to bring Kubernetes Conformance coverage up to 77%](https://www.youtube.com/watch?v=IQsBahak7PQ) by Stephen Heywood and Caleb Woodbine.
0 commit comments