|
4 | 4 |
|
5 | 5 | 1. What work did the SIG do this year that should be highlighted?
|
6 | 6 |
|
7 |
| - - |
8 |
| - - |
9 |
| - - |
| 7 | + - Kubernetes Dashboard v2.5.0 - v2.7.0 released in 2022, and latest release is v2.7.0 in Sep 2022. Each releases support latest release of Kubernetes at the time. |
| 8 | + - Not only Kubernetes modules, but also almost all dependencies are updated to the latest versions. |
| 9 | + - The biggest highlight is that new archtecture was introduced. This splited containers for frontend and backend into each and this makes it possible to tune the each performance. |
| 10 | + - We are now preparing new release that includes the new architecture. |
10 | 11 |
|
11 | 12 | 2. What initiatives are you working on that aren't being tracked in KEPs?
|
12 | 13 |
|
13 |
| - - |
14 |
| - - |
15 |
| - - |
16 |
| - |
17 |
| - |
| 14 | + - We are aiming to adapt tools to new architecture. |
| 15 | + - [Helm Chart](https://github.com/kubernetes/dashboard/pull/7544) |
| 16 | + - [Development environment](https://github.com/kubernetes/dashboard/pull/7602) |
18 | 17 |
|
19 | 18 | 3. KEP work in 2022 (v1.24, v1.25, v1.26):
|
20 | 19 |
|
| 20 | + - None |
21 | 21 |
|
22 | 22 | ## Project health
|
23 | 23 |
|
24 | 24 | 1. What areas and/or subprojects does your group need the most help with?
|
25 | 25 | Any areas with 2 or fewer OWNERs? (link to more details)
|
26 | 26 |
|
27 |
| - - |
28 |
| - - |
29 |
| - - |
| 27 | + - Recruiting new contributors even if in partial area. To be able to traverse/contribute, a new contributor needs to have an understanding of Angular, Golang, and a reasonably knowledge of Kubernetes client-go package. |
| 28 | + - More contributors needed for fixing functional gaps between dashboard and Kubernetes API or kubectl. |
| 29 | + - To support for RTL languages, we needs who can develop dashbboard and review RTL languages. |
| 30 | + - More approvers/reviewers are needed for following translation sub teams: |
| 31 | + - [French translation sub team for Kubernetes Dashboard](https://github.com/kubernetes/dashboard/blob/master/modules/web/i18n/fr/OWNERS) |
| 32 | + - [Korean translation sub team for Kubernetes Dashboard](https://github.com/kubernetes/dashboard/blob/master/modules/web/i18n/ko/OWNERS) |
| 33 | + - [Spanish translation sub team for Kubernetes Dashboard](https://github.com/kubernetes/dashboard/blob/master/modules/web/i18n/es/OWNERS) |
30 | 34 |
|
31 | 35 | 2. What metrics/community health stats does your group care about and/or measure?
|
32 | 36 |
|
33 |
| - - |
34 |
| - - |
35 |
| - - |
| 37 | + - There are two primary sources of PRs: Automated dependency PRs (Dependabot) and contributor-created PRs. Dependabot PRs are merged or closed within 24h, while contributor-created PRs are typically reviewed within 3-4 days. |
| 38 | + - Currently there are no real metrics that we measure regarding Issue/PR turnaround. |
36 | 39 |
|
37 | 40 | 3. Does your [CONTRIBUTING.md] help **new** contributors engage with your group specifically by pointing
|
38 | 41 | to activities or programs that provide useful context or allow easy participation?
|
39 | 42 |
|
40 |
| - - |
| 43 | + - We have well documented guide for [getting started](https://github.com/kubernetes/dashboard/blob/master/docs/developer/getting-started.md) and our [CONTRIBUTING.md](https://github.com/kubernetes/dashboard/blob/master/CONTRIBUTING.md) leads to it. |
| 44 | + - Also, we attempt to maintain Good First Issue labels on things that we think early-lifecycle contributors could begin with. During KubeCons we also do introduction presentations and mentoring sessions to try and funnel contributors in to our SIG. |
41 | 45 |
|
42 | 46 | 4. If your group has special training, requirements for reviewers/approvers, or processes beyond the general [contributor guide],
|
43 | 47 | does your [CONTRIBUTING.md] document those to help **existing** contributors grow throughout the [contributor ladder]?
|
44 | 48 |
|
45 |
| - - |
| 49 | + - We have translation sub teams in Kubernetes Dashboard that have responsibility to manage translation files for each languages. And we have [special guide](https://github.com/kubernetes/dashboard/blob/master/docs/developer/internationalization.md) to organize and to manage the translation sub teams. |
| 50 | + - Also, the development environment container is available to facilitate translation work. |
46 | 51 |
|
47 | 52 | 5. Does the group have contributors from multiple companies/affiliations?
|
48 | 53 |
|
49 |
| - - |
| 54 | + - Yes, current chairs are spread between Plural and NEC. And contributors are also spread across multiple companies including Wiremind, PWC and Tencent. See more [contributors in 2021](https://github.com/kubernetes/dashboard/graphs/contributors?from=2022-01-01&to=2022-12-31&type=c). |
50 | 55 |
|
51 | 56 | 6. Are there ways end users/companies can contribute that they currently are not?
|
52 | 57 | If one of those ways is more full time support, what would they work on and why?
|
53 | 58 |
|
54 |
| - - |
55 |
| - - |
| 59 | + - [Internationalization](https://github.com/kubernetes/dashboard/blob/master/docs/developer/internationalization.md) is easy for contributing. |
56 | 60 |
|
57 | 61 | ## Membership
|
58 | 62 |
|
59 |
| -- Primary slack channel member count: |
60 |
| -- Primary mailing list member count: |
61 |
| -- Primary meeting attendee count (estimated, if needed): |
62 |
| -- Primary meeting participant count (estimated, if needed): |
63 |
| -- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> |
64 |
| -- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> |
| 63 | +- Primary slack channel member count: 1245 |
| 64 | +- Primary mailing list member count: 223 |
| 65 | +- Primary meeting attendee count (estimated, if needed): N/A |
| 66 | +- Primary meeting participant count (estimated, if needed): N/A |
| 67 | +- Unique reviewers for SIG-owned packages: 3<!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> |
| 68 | +- Unique approvers for SIG-owned packages: 3<!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> |
65 | 69 |
|
66 | 70 | Include any other ways you measure group membership
|
67 | 71 |
|
68 | 72 | ## [Subprojects](https://git.k8s.io/community/sig-ui#subprojects)
|
69 | 73 |
|
70 |
| - |
71 |
| - |
72 | 74 | **Continuing:**
|
73 | 75 |
|
74 |
| - - dashboard |
75 |
| - |
| 76 | +- [kubernetes/dashboard](https://github.com/kubernetes/dashboard) |
| 77 | +- [kubernetes-sigs/dashboard-metrics-scraper](https://github.com/kubernetes-sigs/dashboard-metrics-scraper) |
76 | 78 |
|
77 | 79 | ## [Working groups](https://git.k8s.io/community/sig-ui#working-groups)
|
78 | 80 |
|
| 81 | +- None |
79 | 82 |
|
80 | 83 | ## Operational
|
81 | 84 |
|
82 | 85 | Operational tasks in [sig-governance.md]:
|
83 | 86 |
|
84 |
| -- [ ] [README.md] reviewed for accuracy and updated if needed |
85 |
| -- [ ] [CONTRIBUTING.md] reviewed for accuracy and updated if needed |
| 87 | +- [x] [README.md] reviewed for accuracy and updated if needed |
| 88 | +- [x] [CONTRIBUTING.md] reviewed for accuracy and updated if needed |
86 | 89 | (or created if missing and your contributor steps and experience are different or more
|
87 | 90 | in-depth than the documentation listed in the general [contributor guide] and [devel] folder.)
|
88 |
| -- [ ] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed |
89 |
| -- [ ] SIG leaders (chairs, tech leads, and subproject owners) in [sigs.yaml] are accurate and active, and updated if needed |
90 |
| -- [ ] Meeting notes and recordings for 2022 are linked from [README.md] and updated/uploaded if needed |
91 |
| -- [ ] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: |
92 |
| - - |
93 |
| - - |
| 91 | +- [x] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed |
| 92 | +- [x] SIG leaders (chairs, tech leads, and subproject owners) in [sigs.yaml] are accurate and active, and updated if needed |
| 93 | +- [x] Meeting notes and recordings for 2022 are linked from [README.md] and updated/uploaded if needed |
| 94 | + - None |
| 95 | +- [x] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: |
| 96 | + - [Kubernetes SIG UI Introduction and Updates at KubeCon+CloudNativeCon Europe 2022](https://sched.co/ytpx) |
94 | 97 |
|
95 | 98 | [CONTRIBUTING.md]: https://git.k8s.io/community/sig-ui/CONTRIBUTING.md
|
96 | 99 | [contributor ladder]: https://git.k8s.io/community/community-membership.md
|
|
0 commit comments