|
4 | 4 |
|
5 | 5 | 1. What work did the WG do this year that should be highlighted?
|
6 | 6 | For example, artifacts, reports, white papers produced this year.
|
7 |
| - |
8 |
| - - |
9 |
| - - |
10 |
| - - |
| 7 | + - Server-side Apply went GA this summer |
| 8 | + - Started new initiatives around OpenAPI v3 |
| 9 | + - Enum for built-in types in OpenAPI |
| 10 | + - Server-side field validation |
11 | 11 |
|
12 | 12 | 2. What initiatives are you working on that aren't being tracked in KEPs?
|
13 |
| - |
14 |
| - - |
15 |
| - - |
16 |
| - - |
| 13 | + - N/A |
17 | 14 |
|
18 | 15 | ## Project health
|
19 | 16 |
|
20 | 17 | 1. What's the current roadmap until completion of the working group?
|
21 | 18 |
|
22 |
| - - |
23 |
| - - |
24 |
| - - |
| 19 | + - Address server-side apply field deletion and improve CSA -> SSA story |
| 20 | + - Complete OpenAPI v3 roll-out |
| 21 | + - Finish using existing OpenAPI primitives for built-ins and CRDs |
| 22 | + - Allow OpenAPI extensions to be used by CRD authors |
| 23 | + - Discovery cache-busting |
25 | 24 |
|
26 | 25 | 2. Does the group have contributors from multiple companies/affiliations?
|
27 |
| - |
28 |
| - - |
| 26 | + - Yes |
29 | 27 |
|
30 | 28 | 3. Are there ways end users/companies can contribute that they currently are not?
|
31 | 29 | If one of those ways is more full time support, what would they work on and why?
|
32 |
| - |
33 |
| - - |
34 |
| - - |
| 30 | + - No |
35 | 31 |
|
36 | 32 | ## Membership
|
37 | 33 |
|
38 |
| -- Primary slack channel member count: |
39 |
| -- Primary mailing list member count: |
40 |
| -- Primary meeting attendee count (estimated, if needed): |
41 |
| -- Primary meeting participant count (estimated, if needed): |
42 |
| - |
43 |
| -Include any other ways you measure group membership |
| 34 | +- Primary slack channel member count: 123 |
| 35 | +- Primary mailing list member count: 33 |
| 36 | +- Primary meeting attendee count (estimated, if needed): 4-5 |
| 37 | +- Primary meeting participant count (estimated, if needed): 6-8 |
44 | 38 |
|
45 | 39 | ## Operational
|
46 | 40 |
|
47 | 41 | Operational tasks in [wg-governance.md]:
|
48 | 42 |
|
49 |
| -- [ ] [README.md] reviewed for accuracy and updated if needed |
50 |
| -- [ ] WG leaders in [sigs.yaml] are accurate and active, and updated if needed |
51 |
| -- [ ] Meeting notes and recordings for 2021 are linked from [README.md] and updated/uploaded if needed |
| 43 | +- [x] [README.md] reviewed for accuracy and updated if needed |
| 44 | +- [x] WG leaders in [sigs.yaml] are accurate and active, and updated if needed |
| 45 | +- [x] Meeting notes and recordings for 2021 are linked from [README.md] and updated/uploaded if needed |
52 | 46 | - [ ] Updates provided to sponsoring SIGs in 2021
|
53 |
| - - [$sig-name](https://git.k8s.io/community/$sig-id/) |
54 |
| - - links to email, meeting notes, slides, or recordings, etc |
55 |
| - - [$sig-name](https://git.k8s.io/community/$sig-id/) |
56 |
| - - links to email, meeting notes, slides, or recordings, etc |
57 |
| - - |
58 | 47 |
|
59 | 48 | [wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md
|
60 | 49 | [README.md]: https://git.k8s.io/community/wg-api-expression/README.md
|
|
0 commit comments