From 696e1fbe45649cf86556b525714a6a79c3bb9114 Mon Sep 17 00:00:00 2001 From: Bob Killen Date: Fri, 4 Jun 2021 14:47:52 -0400 Subject: Rename annual reports to match calendar year --- sig-api-machinery/annual-report-2020.md | 160 ++++++++++++++++++++++ sig-api-machinery/annual-report-2021.md | 160 ---------------------- sig-apps/annual-report-2020.md | 59 ++++++++ sig-apps/annual-report-2021.md | 59 -------- sig-architecture/annual-report-2020.md | 116 ++++++++++++++++ sig-architecture/annual-report-2021.md | 116 ---------------- sig-auth/annual-report-2020.md | 116 ++++++++++++++++ sig-auth/annual-report-2021.md | 116 ---------------- sig-cli/annual-report-2020.md | 73 ++++++++++ sig-cli/annual-report-2021.md | 73 ---------- sig-cloud-provider/2020-annual-report.md | 86 ------------ sig-cloud-provider/annual-report-2020.md | 86 ++++++++++++ sig-cluster-lifecycle/annual-report-2020.md | 99 ++++++++++++++ sig-cluster-lifecycle/annual-report-2021.md | 99 -------------- sig-contributor-experience/annual-report-2020.md | 141 +++++++++++++++++++ sig-contributor-experience/annual-report-2021.md | 141 ------------------- sig-docs/annual-report-2020.md | 131 ++++++++++++++++++ sig-docs/annual-report-2021.md | 131 ------------------ sig-instrumentation/annual-report-2020.md | 77 +++++++++++ sig-instrumentation/annual-report-2021.md | 77 ----------- sig-multicluster/annual-report-2020.md | 73 ++++++++++ sig-multicluster/annual-report-2021.md | 73 ---------- sig-node/annual-report-2020.md | 72 ++++++++++ sig-node/annual-report-2021.md | 72 ---------- sig-release/annual-report-2020.md | 99 ++++++++++++++ sig-release/annual-report-2021.md | 99 -------------- sig-scalability/annual-report-2020.md | 119 ++++++++++++++++ sig-scalability/annual-report-2021.md | 119 ---------------- sig-scheduling/annual-report-2020.md | 125 +++++++++++++++++ sig-scheduling/annual-report-2021.md | 125 ----------------- sig-security/annual-report-2020.md | 81 +++++++++++ sig-security/annual-report-2021.md | 81 ----------- sig-storage/annual-report-2020.md | 166 +++++++++++++++++++++++ sig-storage/annual-report-2021.md | 166 ----------------------- sig-ui/annual-report-2020.md | 108 +++++++++++++++ sig-ui/annual-report-2021.md | 108 --------------- sig-usability/annual-report-2020.md | 53 ++++++++ sig-usability/annual-report-2021.md | 53 -------- sig-windows/annual-report-2020.md | 69 ++++++++++ sig-windows/annual-report-2021.md | 69 ---------- wg-data-protection/annual-report-2020.md | 46 +++++++ wg-data-protection/annual-report-2021.md | 46 ------- wg-multitenancy/annual-report-2020.md | 53 ++++++++ wg-multitenancy/annual-report-2021.md | 53 -------- 44 files changed, 2122 insertions(+), 2122 deletions(-) create mode 100644 sig-api-machinery/annual-report-2020.md delete mode 100644 sig-api-machinery/annual-report-2021.md create mode 100644 sig-apps/annual-report-2020.md delete mode 100644 sig-apps/annual-report-2021.md create mode 100644 sig-architecture/annual-report-2020.md delete mode 100644 sig-architecture/annual-report-2021.md create mode 100644 sig-auth/annual-report-2020.md delete mode 100644 sig-auth/annual-report-2021.md create mode 100644 sig-cli/annual-report-2020.md delete mode 100644 sig-cli/annual-report-2021.md delete mode 100644 sig-cloud-provider/2020-annual-report.md create mode 100644 sig-cloud-provider/annual-report-2020.md create mode 100644 sig-cluster-lifecycle/annual-report-2020.md delete mode 100644 sig-cluster-lifecycle/annual-report-2021.md create mode 100644 sig-contributor-experience/annual-report-2020.md delete mode 100644 sig-contributor-experience/annual-report-2021.md create mode 100644 sig-docs/annual-report-2020.md delete mode 100644 sig-docs/annual-report-2021.md create mode 100644 sig-instrumentation/annual-report-2020.md delete mode 100644 sig-instrumentation/annual-report-2021.md create mode 100644 sig-multicluster/annual-report-2020.md delete mode 100644 sig-multicluster/annual-report-2021.md create mode 100644 sig-node/annual-report-2020.md delete mode 100644 sig-node/annual-report-2021.md create mode 100644 sig-release/annual-report-2020.md delete mode 100644 sig-release/annual-report-2021.md create mode 100644 sig-scalability/annual-report-2020.md delete mode 100644 sig-scalability/annual-report-2021.md create mode 100644 sig-scheduling/annual-report-2020.md delete mode 100644 sig-scheduling/annual-report-2021.md create mode 100644 sig-security/annual-report-2020.md delete mode 100644 sig-security/annual-report-2021.md create mode 100644 sig-storage/annual-report-2020.md delete mode 100644 sig-storage/annual-report-2021.md create mode 100644 sig-ui/annual-report-2020.md delete mode 100644 sig-ui/annual-report-2021.md create mode 100644 sig-usability/annual-report-2020.md delete mode 100644 sig-usability/annual-report-2021.md create mode 100644 sig-windows/annual-report-2020.md delete mode 100644 sig-windows/annual-report-2021.md create mode 100644 wg-data-protection/annual-report-2020.md delete mode 100644 wg-data-protection/annual-report-2021.md create mode 100644 wg-multitenancy/annual-report-2020.md delete mode 100644 wg-multitenancy/annual-report-2021.md diff --git a/sig-api-machinery/annual-report-2020.md b/sig-api-machinery/annual-report-2020.md new file mode 100644 index 00000000..d6d5ba8d --- /dev/null +++ b/sig-api-machinery/annual-report-2020.md @@ -0,0 +1,160 @@ +# Kubernetes SIG API Machinery - 2020 Annual report +David Eads, Daniel Smith, Federico Bongiovanni + + +[Source](https://github.com/kubernetes/community/blob/master/committee-steering/governance/annual-reports.md) + +## Checklist +- [x] Read about the process [here](https://git.k8s.io/community/committee-steering/governance/annual-reports.md#reporting-process) +- [ ] Copy this template into a new document and share with your mailing list/slack channel/meeting on whatever platform (gdocs, hackmd, etc.) that the team prefers. +- [x] Remove sections that are not applicable (example: if you are a working group, delete the special interest group questions) +- [ ] Pick graphs from Devstats to pull supporting data for your responses. +- [ ] Schedule a time with your Steering liaison and other Chairs, TLs, and Organizers of your group to check-in on your + roles as Chair or Working Group Organizer. + If anyone would rather meet 1:1, please have them reach out to the liaison directly, we are happy to. + We’d like to talk about: challenges, wins, things you didn’t know before but wish you did, want to continue in the + role or help finding a replacement; and lastly any feedback you have for us as a body and how we can help you + succeed and feel comfortable in these leadership roles. +- [x] PR this document into your community group directory in kubernetes/community (example: sig-architecture/) + - [x] by March 8th, 2021 + - [x] titled: annual-report-YEAR.md +- [x] are there any responses that you’d like to share privately first? steering-private@kubernetes.io or tag your liaison in for discussion. + +## Operational +1. How are you doing with operational tasks in SIG-governance.md? + 1. Is your README accurate? have a CONTRIBUTING.md file? + + Yes, the [README](https://github.com/kubernetes/community/blob/master/sig-api-machinery/README.md) is accurate. + 2. All subprojects correctly mapped and listed in sigs.yaml? + + Yes, our [subprojects](https://github.com/kubernetes/community/blob/master/sig-api-machinery/README.md#subprojects) are current. + 3. What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? + + Are you keeping recordings up to date/trends in community members watching recordings? + + We have two main meetings, both fairly small, with [notes and agenda up to date](https://docs.google.com/document/d/1x9RNaaysyO0gXHIr1y50QFbiL1x8OWnk2v3XnrdkT5Y/edit). + [Our recordings](https://www.youtube.com/playlist?list=PL69nYSiGNLP21oW3hbLyjjj4XhrwKxH2R) are usually uploaded within two weeks. + + There are bug scrub meetings every Tuesday and Thursday. + +2. How does the group get updates, reports, or feedback from subprojects? + Are there any springing up or being retired? Are OWNERS.md files up to date in these areas? + + We get updates on an ad-hoc basis. + We have approved a prototyping project ([apiserver-runtime](https://github.com/kubernetes-sigs/apiserver-runtime)) and have no plans to retire any at this time. + We have not actively pruned OWNERS, some people have been added to various subprojects. + +3. Same question as above but for working groups. + [wg-api-expression](https://github.com/kubernetes/community/blob/master/wg-api-expression/README.md) has its own + regular meeting cadence and did its own [annual report](https://github.com/kubernetes/community/blob/master/wg-api-expression/2020-annual-report.md). + + [wg-component-standard](https://github.com/kubernetes/community/blob/master/wg-component-standard/README.md) has its own + regular meeting cadence. + The working group is not as active as it once was, see the [mailing list thread](https://groups.google.com/g/kubernetes-dev/c/sQGrk6HWyj0). + + [wg-multitenancy](https://github.com/kubernetes/community/tree/master/wg-multitenancy) has its own regular meeting cadence + and did its own [annual report](https://github.com/kubernetes/community/blob/master/wg-multitenancy/2021-annual-report.md). + +4. When was your last public community-wide update? (provide link to deck and/or recording) + [May 2020](https://docs.google.com/presentation/d/1UWRaMVtTD3yVhJ3MGBpt7LRIaRHTaQZoGlDT7Bl7jLE/edit#slide=id.g401c104a3c_0_0) + +## Membership +1. Are all listed SIG leaders (chairs, tech leads, and subproject owners) active? + + Yes. + +2. How do you measure membership? By mailing list members, OWNERs, or something else? + + We don’t measure membership. + +3. How does the group measure reviewer and approver bandwidth? + Do you need help in any area now? What are you doing about it? + + Our predicted rate of feature delivery and stability roughly matches the achieved rate. + While we would be happy to see developers move up the ladder, we don’t see a pressing need to adjust the current rate. + + We perform twice a week triage and our [issue open/close rates are holding steady](https://k8s.devstats.cncf.io/d/39/issues-opened-closed-by-sig?orgId=1&var-period=d7&var-sig_name=api-machinery&var-kind_name=All). + +4. Is there a healthy onboarding and growth path for contributors in your SIG? What are some activities that the group + does to encourage this? What programs are you participating in to grow contributors throughout the contributor ladder? + + We see patches from first time contributors, we regularly accept agenda items from contributors from other sigs and + first time contributors. + +5. What programs do you participate in for new contributors? + + We don’t participate in any particular programs. + We find many contributors via slack, PRs, and issues. + +6. Does the group have contributors from multiple companies/affiliations? + Can end users/companies contribute in some way that they currently are not? + + Yes, there are contributors from [multiple companies](https://k8s.devstats.cncf.io/d/74/contributions-chart?orgId=1&var-period=d7&var-metric=contributions&var-repogroup_name=SIG%20API%20Machinery&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. + + +## Current initiatives and project health +1. What are initiatives that should be highlighted, lauded, shout outs, that your group is proud of? Currently underway? + What are some of the longer tail projects that your group is working on? + + Currently underway: + 1. [server-side-apply](https://github.com/kubernetes/enhancements/issues/555) to GA + 2. [server-side-apply client](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/2144-clientgo-apply#alternative-1-generated-structs-where-all-fields-are-pointers) + 3. [optionally skip backend TLS verifiction](https://github.com/kubernetes/enhancements/issues/1295) + 4. [namespace labels](https://github.com/kubernetes/enhancements/pull/2162) + 5. Getting ready for CRD and admission webhook v1beta1 API removal: [reminder on kubernetes-dev](https://groups.google.com/g/kubernetes-dev/c/z_AE1EHhZF4/m/kBd3HkWxAwAJ). + 6. [Immutable fields API](https://github.com/kubernetes/enhancements/issues/1101) + 7. [API unions](https://github.com/kubernetes/enhancements/issues/1027) + 8. [warnings to GA](https://github.com/kubernetes/enhancements/issues/1693) + 9. [apiserver network proxy to beta](https://github.com/kubernetes/enhancements/issues/1281) + 10. [priority and fairness to GA](https://github.com/kubernetes/enhancements/issues/1040) + +2. Year to date KEP work: What's now stable? Beta? Alpha? Road to alpha? + 1. Stable + 1. [Selector index](https://github.com/kubernetes/kubernetes/commit/fea3042f1f84129ab1cb6e481bd51343061673b7) - 1.20 + 2. [Permabeta machinery (sig-arch policy)](https://github.com/kubernetes/enhancements/blob/master/keps/sig-architecture/1635-prevent-permabeta/README.md) - 1.19 + 3. [Client-go context](https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/1601-client-go-context/README.md) - 1.18 + 4. [Client-go options](https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/1601-client-go-context/README.md) - 1.18 + 5. [Dry run](https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/576-dry-run/README.md) - 1.18 + 6. [Standardize conditions](https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/1623-standardize-conditions/README.md) - 1.19 + 2. Beta + 1. [Priority and fairness](https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/1040-priority-and-fairness/README.md) - 1.20 + 2. [Selector index](https://github.com/kubernetes/kubernetes/pull/92503) - 1.19 + 3. [Self-link removal](https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/1164-remove-selflink/README.md) - 1.20 + 4. [Warning headers](https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/1693-warnings/README.md) - 1.19 + 5. [Server-side apply evolution while in beta](https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/555-server-side-apply/README.md) - 1.18, 1.19, 1.20 + 3. Alpha + 1. [Selector index](https://github.com/kubernetes/kubernetes/pull/87939) - 1.18 + 2. [API server identity](https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/1965-kube-apiserver-identity/README.md) - 1.20 + 3. [Efficient watch resumption](https://github.com/kubernetes/enhancements/issues/1904) - 1.20 + 4. Pre-alpha + 1. [Manifest-based admission webhook](https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/1872-manifest-based-admission-webhooks/README.md) + + +3. What initiatives are you working on that aren't being tracked in KEPs? + + We are working on mitigating the impact of removing beta APIs in 1.22. + +4. What areas and/or subprojects does the group need the most help with? + + The SIG sponsors some working groups that are largely independent. + + There are several areas where regularly the SIG becomes under pressure, especially closer to code freezes and the + vast amount of code owned by API Machinery. + + The ecosystem of the different Kubernetes Clients that we own grows more or less organically. Client-go and + Python-client are probably the bigger ones. + + There are some packages that API Machinery owns and come out usually in our triage meetings, and that we most likely + don't know much about: this happens often when Kubernetes is upgrading libraries for example. + + +5. What metrics/community health stats does your group care about and/or measure? Examples? + + On the technical health of the SIG, we look at + - the ratio of open/close PRs + - the ratio of open/close Issues + - overall age of open Issues + - Number of active contributors to the sig + - diverse representation of companies in the sig participants diff --git a/sig-api-machinery/annual-report-2021.md b/sig-api-machinery/annual-report-2021.md deleted file mode 100644 index d6d5ba8d..00000000 --- a/sig-api-machinery/annual-report-2021.md +++ /dev/null @@ -1,160 +0,0 @@ -# Kubernetes SIG API Machinery - 2020 Annual report -David Eads, Daniel Smith, Federico Bongiovanni - - -[Source](https://github.com/kubernetes/community/blob/master/committee-steering/governance/annual-reports.md) - -## Checklist -- [x] Read about the process [here](https://git.k8s.io/community/committee-steering/governance/annual-reports.md#reporting-process) -- [ ] Copy this template into a new document and share with your mailing list/slack channel/meeting on whatever platform (gdocs, hackmd, etc.) that the team prefers. -- [x] Remove sections that are not applicable (example: if you are a working group, delete the special interest group questions) -- [ ] Pick graphs from Devstats to pull supporting data for your responses. -- [ ] Schedule a time with your Steering liaison and other Chairs, TLs, and Organizers of your group to check-in on your - roles as Chair or Working Group Organizer. - If anyone would rather meet 1:1, please have them reach out to the liaison directly, we are happy to. - We’d like to talk about: challenges, wins, things you didn’t know before but wish you did, want to continue in the - role or help finding a replacement; and lastly any feedback you have for us as a body and how we can help you - succeed and feel comfortable in these leadership roles. -- [x] PR this document into your community group directory in kubernetes/community (example: sig-architecture/) - - [x] by March 8th, 2021 - - [x] titled: annual-report-YEAR.md -- [x] are there any responses that you’d like to share privately first? steering-private@kubernetes.io or tag your liaison in for discussion. - -## Operational -1. How are you doing with operational tasks in SIG-governance.md? - 1. Is your README accurate? have a CONTRIBUTING.md file? - - Yes, the [README](https://github.com/kubernetes/community/blob/master/sig-api-machinery/README.md) is accurate. - 2. All subprojects correctly mapped and listed in sigs.yaml? - - Yes, our [subprojects](https://github.com/kubernetes/community/blob/master/sig-api-machinery/README.md#subprojects) are current. - 3. What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? - - Are you keeping recordings up to date/trends in community members watching recordings? - - We have two main meetings, both fairly small, with [notes and agenda up to date](https://docs.google.com/document/d/1x9RNaaysyO0gXHIr1y50QFbiL1x8OWnk2v3XnrdkT5Y/edit). - [Our recordings](https://www.youtube.com/playlist?list=PL69nYSiGNLP21oW3hbLyjjj4XhrwKxH2R) are usually uploaded within two weeks. - - There are bug scrub meetings every Tuesday and Thursday. - -2. How does the group get updates, reports, or feedback from subprojects? - Are there any springing up or being retired? Are OWNERS.md files up to date in these areas? - - We get updates on an ad-hoc basis. - We have approved a prototyping project ([apiserver-runtime](https://github.com/kubernetes-sigs/apiserver-runtime)) and have no plans to retire any at this time. - We have not actively pruned OWNERS, some people have been added to various subprojects. - -3. Same question as above but for working groups. - [wg-api-expression](https://github.com/kubernetes/community/blob/master/wg-api-expression/README.md) has its own - regular meeting cadence and did its own [annual report](https://github.com/kubernetes/community/blob/master/wg-api-expression/2020-annual-report.md). - - [wg-component-standard](https://github.com/kubernetes/community/blob/master/wg-component-standard/README.md) has its own - regular meeting cadence. - The working group is not as active as it once was, see the [mailing list thread](https://groups.google.com/g/kubernetes-dev/c/sQGrk6HWyj0). - - [wg-multitenancy](https://github.com/kubernetes/community/tree/master/wg-multitenancy) has its own regular meeting cadence - and did its own [annual report](https://github.com/kubernetes/community/blob/master/wg-multitenancy/2021-annual-report.md). - -4. When was your last public community-wide update? (provide link to deck and/or recording) - [May 2020](https://docs.google.com/presentation/d/1UWRaMVtTD3yVhJ3MGBpt7LRIaRHTaQZoGlDT7Bl7jLE/edit#slide=id.g401c104a3c_0_0) - -## Membership -1. Are all listed SIG leaders (chairs, tech leads, and subproject owners) active? - - Yes. - -2. How do you measure membership? By mailing list members, OWNERs, or something else? - - We don’t measure membership. - -3. How does the group measure reviewer and approver bandwidth? - Do you need help in any area now? What are you doing about it? - - Our predicted rate of feature delivery and stability roughly matches the achieved rate. - While we would be happy to see developers move up the ladder, we don’t see a pressing need to adjust the current rate. - - We perform twice a week triage and our [issue open/close rates are holding steady](https://k8s.devstats.cncf.io/d/39/issues-opened-closed-by-sig?orgId=1&var-period=d7&var-sig_name=api-machinery&var-kind_name=All). - -4. Is there a healthy onboarding and growth path for contributors in your SIG? What are some activities that the group - does to encourage this? What programs are you participating in to grow contributors throughout the contributor ladder? - - We see patches from first time contributors, we regularly accept agenda items from contributors from other sigs and - first time contributors. - -5. What programs do you participate in for new contributors? - - We don’t participate in any particular programs. - We find many contributors via slack, PRs, and issues. - -6. Does the group have contributors from multiple companies/affiliations? - Can end users/companies contribute in some way that they currently are not? - - Yes, there are contributors from [multiple companies](https://k8s.devstats.cncf.io/d/74/contributions-chart?orgId=1&var-period=d7&var-metric=contributions&var-repogroup_name=SIG%20API%20Machinery&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. - - -## Current initiatives and project health -1. What are initiatives that should be highlighted, lauded, shout outs, that your group is proud of? Currently underway? - What are some of the longer tail projects that your group is working on? - - Currently underway: - 1. [server-side-apply](https://github.com/kubernetes/enhancements/issues/555) to GA - 2. [server-side-apply client](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/2144-clientgo-apply#alternative-1-generated-structs-where-all-fields-are-pointers) - 3. [optionally skip backend TLS verifiction](https://github.com/kubernetes/enhancements/issues/1295) - 4. [namespace labels](https://github.com/kubernetes/enhancements/pull/2162) - 5. Getting ready for CRD and admission webhook v1beta1 API removal: [reminder on kubernetes-dev](https://groups.google.com/g/kubernetes-dev/c/z_AE1EHhZF4/m/kBd3HkWxAwAJ). - 6. [Immutable fields API](https://github.com/kubernetes/enhancements/issues/1101) - 7. [API unions](https://github.com/kubernetes/enhancements/issues/1027) - 8. [warnings to GA](https://github.com/kubernetes/enhancements/issues/1693) - 9. [apiserver network proxy to beta](https://github.com/kubernetes/enhancements/issues/1281) - 10. [priority and fairness to GA](https://github.com/kubernetes/enhancements/issues/1040) - -2. Year to date KEP work: What's now stable? Beta? Alpha? Road to alpha? - 1. Stable - 1. [Selector index](https://github.com/kubernetes/kubernetes/commit/fea3042f1f84129ab1cb6e481bd51343061673b7) - 1.20 - 2. [Permabeta machinery (sig-arch policy)](https://github.com/kubernetes/enhancements/blob/master/keps/sig-architecture/1635-prevent-permabeta/README.md) - 1.19 - 3. [Client-go context](https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/1601-client-go-context/README.md) - 1.18 - 4. [Client-go options](https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/1601-client-go-context/README.md) - 1.18 - 5. [Dry run](https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/576-dry-run/README.md) - 1.18 - 6. [Standardize conditions](https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/1623-standardize-conditions/README.md) - 1.19 - 2. Beta - 1. [Priority and fairness](https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/1040-priority-and-fairness/README.md) - 1.20 - 2. [Selector index](https://github.com/kubernetes/kubernetes/pull/92503) - 1.19 - 3. [Self-link removal](https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/1164-remove-selflink/README.md) - 1.20 - 4. [Warning headers](https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/1693-warnings/README.md) - 1.19 - 5. [Server-side apply evolution while in beta](https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/555-server-side-apply/README.md) - 1.18, 1.19, 1.20 - 3. Alpha - 1. [Selector index](https://github.com/kubernetes/kubernetes/pull/87939) - 1.18 - 2. [API server identity](https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/1965-kube-apiserver-identity/README.md) - 1.20 - 3. [Efficient watch resumption](https://github.com/kubernetes/enhancements/issues/1904) - 1.20 - 4. Pre-alpha - 1. [Manifest-based admission webhook](https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/1872-manifest-based-admission-webhooks/README.md) - - -3. What initiatives are you working on that aren't being tracked in KEPs? - - We are working on mitigating the impact of removing beta APIs in 1.22. - -4. What areas and/or subprojects does the group need the most help with? - - The SIG sponsors some working groups that are largely independent. - - There are several areas where regularly the SIG becomes under pressure, especially closer to code freezes and the - vast amount of code owned by API Machinery. - - The ecosystem of the different Kubernetes Clients that we own grows more or less organically. Client-go and - Python-client are probably the bigger ones. - - There are some packages that API Machinery owns and come out usually in our triage meetings, and that we most likely - don't know much about: this happens often when Kubernetes is upgrading libraries for example. - - -5. What metrics/community health stats does your group care about and/or measure? Examples? - - On the technical health of the SIG, we look at - - the ratio of open/close PRs - - the ratio of open/close Issues - - overall age of open Issues - - Number of active contributors to the sig - - diverse representation of companies in the sig participants diff --git a/sig-apps/annual-report-2020.md b/sig-apps/annual-report-2020.md new file mode 100644 index 00000000..43c81f15 --- /dev/null +++ b/sig-apps/annual-report-2020.md @@ -0,0 +1,59 @@ +# Operational +How are you doing with operational tasks in sig-governance.md? +Is your README accurate? have a CONTRIBUTING.md file? +Yes, both the [README.md](https://github.com/kubernetes/community/blob/master/sig-apps/README.md) +and the [CONTRIBUTING.md](https://github.com/kubernetes/community/blob/master/sig-apps/CONTRIBUTING.md) +are up-to-date. + +All subprojects correctly mapped and listed in sigs.yaml? +Yes + +What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? Are you keeping recordings up to date/trends in community members watching recordings? +We hold small and active biweekly meeting. The call is divided into few sections, such as important announcements, then demos and finally discussions on the current topics. If time allows, we try to review issues and pull requests. All of the meetings are recorded and available online, all the meeting invites are up-to-date and present in community calendar. + + +How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being retired? Are OWNERS files up to date in these areas? +Every subproject is free to provide an update at our biweekly meeting, but we don’t enforce that specifically. OWNERS files are up-to-date. + +When was your last monthly community-wide update? (provide link to deck and/or recording) +Our last update presentation was on June 18, 2020 +- [Slides](https://docs.google.com/presentation/d/18UcJQs3ThW6Vdgl_mdc1984uU16GwuIhuD0Pujl42xU/edit#slide=id.g401c104a3c_0_0) +- [Recording](https://youtu.be/ObqQxRRl9RQ?t=1111) +- [KubeCon NA 2019](https://www.youtube.com/watch?v=uqYStFxu578) + +# Membership +Are all listed SIG leaders (chairs, tech leads, and subproject owners) active? +Yes, all the lists are up-to-date. + +How do you measure membership? By mailing list members, OWNERs, or something else? +Reviewers and approvers are measured through repository OWNERS file. Membership is measured through mailing list and zoom calls. + +How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it? +We periodically remove inactive reviewers and approvers, invite new contributors we have seen active in to join the reviewers. The bar to be accepted as an approver is significantly higher since we need to ensure the stability of the core controllers and the entire project. + +Is there a healthy onboarding and growth path for contributors in your SIG? What are some activities that the group does to encourage this? What programs are you participating in to grow contributors throughout the contributor ladder? +Recently we reviewed and unified the sig-apps-approvers alias which holds the approvers, similarly sig-apps-reviewers was reviewed for the reviewers ranks. + +What programs do you participate in for new contributors? + - KubeCon updates. + - Individual/1-1 mentoring. + +Does the group have contributors from multiple companies/affiliations? Can end users/companies contribute in some way that they currently are not? +The group has contributors from multiple companies/affiliations. +[14 companies](https://k8s.devstats.cncf.io/d/8/company-statistics-by-repository-group?orgId=1&var-period=y&var-metric=contributions&var-repogroup_name=SIG%20Apps&var-repo_name=kubernetes%2Fkubernetes&var-companies=All) contributed code in the last year. + + + +# Current initiatives and project health + +What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? Currently underway? What are some of the longer tail projects that your group is working on? +- [CronJob to GA](https://github.com/kubernetes/enhancements/issues/19) +- [PDB to GA](https://github.com/kubernetes/enhancements/issues/85) + +Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha? +What areas and/or subprojects does the group need the most help with? + - [New CronJob controller as part of work from promoting CronJobs to GA (alpha)](https://github.com/kubernetes/enhancements/issues/19) + - [MaxSurge for DaemonSet (alpha)](https://github.com/kubernetes/enhancements/issues/1591) + +What's the average open days of a PR and Issue in your group? / what metrics does your group care about and/or measure? +The average time to merge the PR is around [~7 days](https://k8s.devstats.cncf.io/d/44/pr-time-to-approve-and-merge?viewPanel=8&orgId=1&from=1577865600000&to=1609401600000&var-period=d7&var-repogroup_name=SIG%20Apps&var-repo_name=kubernetes%2Fkubernetes&var-apichange=All&var-size_name=All&var-kind_name=All) diff --git a/sig-apps/annual-report-2021.md b/sig-apps/annual-report-2021.md deleted file mode 100644 index 43c81f15..00000000 --- a/sig-apps/annual-report-2021.md +++ /dev/null @@ -1,59 +0,0 @@ -# Operational -How are you doing with operational tasks in sig-governance.md? -Is your README accurate? have a CONTRIBUTING.md file? -Yes, both the [README.md](https://github.com/kubernetes/community/blob/master/sig-apps/README.md) -and the [CONTRIBUTING.md](https://github.com/kubernetes/community/blob/master/sig-apps/CONTRIBUTING.md) -are up-to-date. - -All subprojects correctly mapped and listed in sigs.yaml? -Yes - -What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? Are you keeping recordings up to date/trends in community members watching recordings? -We hold small and active biweekly meeting. The call is divided into few sections, such as important announcements, then demos and finally discussions on the current topics. If time allows, we try to review issues and pull requests. All of the meetings are recorded and available online, all the meeting invites are up-to-date and present in community calendar. - - -How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being retired? Are OWNERS files up to date in these areas? -Every subproject is free to provide an update at our biweekly meeting, but we don’t enforce that specifically. OWNERS files are up-to-date. - -When was your last monthly community-wide update? (provide link to deck and/or recording) -Our last update presentation was on June 18, 2020 -- [Slides](https://docs.google.com/presentation/d/18UcJQs3ThW6Vdgl_mdc1984uU16GwuIhuD0Pujl42xU/edit#slide=id.g401c104a3c_0_0) -- [Recording](https://youtu.be/ObqQxRRl9RQ?t=1111) -- [KubeCon NA 2019](https://www.youtube.com/watch?v=uqYStFxu578) - -# Membership -Are all listed SIG leaders (chairs, tech leads, and subproject owners) active? -Yes, all the lists are up-to-date. - -How do you measure membership? By mailing list members, OWNERs, or something else? -Reviewers and approvers are measured through repository OWNERS file. Membership is measured through mailing list and zoom calls. - -How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it? -We periodically remove inactive reviewers and approvers, invite new contributors we have seen active in to join the reviewers. The bar to be accepted as an approver is significantly higher since we need to ensure the stability of the core controllers and the entire project. - -Is there a healthy onboarding and growth path for contributors in your SIG? What are some activities that the group does to encourage this? What programs are you participating in to grow contributors throughout the contributor ladder? -Recently we reviewed and unified the sig-apps-approvers alias which holds the approvers, similarly sig-apps-reviewers was reviewed for the reviewers ranks. - -What programs do you participate in for new contributors? - - KubeCon updates. - - Individual/1-1 mentoring. - -Does the group have contributors from multiple companies/affiliations? Can end users/companies contribute in some way that they currently are not? -The group has contributors from multiple companies/affiliations. -[14 companies](https://k8s.devstats.cncf.io/d/8/company-statistics-by-repository-group?orgId=1&var-period=y&var-metric=contributions&var-repogroup_name=SIG%20Apps&var-repo_name=kubernetes%2Fkubernetes&var-companies=All) contributed code in the last year. - - - -# Current initiatives and project health - -What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? Currently underway? What are some of the longer tail projects that your group is working on? -- [CronJob to GA](https://github.com/kubernetes/enhancements/issues/19) -- [PDB to GA](https://github.com/kubernetes/enhancements/issues/85) - -Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha? -What areas and/or subprojects does the group need the most help with? - - [New CronJob controller as part of work from promoting CronJobs to GA (alpha)](https://github.com/kubernetes/enhancements/issues/19) - - [MaxSurge for DaemonSet (alpha)](https://github.com/kubernetes/enhancements/issues/1591) - -What's the average open days of a PR and Issue in your group? / what metrics does your group care about and/or measure? -The average time to merge the PR is around [~7 days](https://k8s.devstats.cncf.io/d/44/pr-time-to-approve-and-merge?viewPanel=8&orgId=1&from=1577865600000&to=1609401600000&var-period=d7&var-repogroup_name=SIG%20Apps&var-repo_name=kubernetes%2Fkubernetes&var-apichange=All&var-size_name=All&var-kind_name=All) diff --git a/sig-architecture/annual-report-2020.md b/sig-architecture/annual-report-2020.md new file mode 100644 index 00000000..db7ce36f --- /dev/null +++ b/sig-architecture/annual-report-2020.md @@ -0,0 +1,116 @@ +# 2020 SIG Architecture Annual Report + +## Operational + +**How are you doing with operational tasks in sig-governance.md?** + +**Is your README accurate? have a CONTRIBUTING.md file?** + + - Yes, our README is accurate. We do not have a CONTRIBUTING.md file, and so will add one. + +**All subprojects correctly mapped and listed in sigs.yaml?** + + - Yes. + +**What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? Are you keeping recordings up to date/trends in community members watching recordings?** + + - Our bi-weekly meeting is normally well attended, with approximately 20 individuals on a typical day, though it varies from a handful of folks to 40 or 50 depending on topics. + + - Subproject meetings are smaller, generally in the half dozen range. + +**How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being retired? Are OWNERS files up to date in these areas?** + + - We have a rotating schedule of subproject updates in the bi-weekly community meeting. Our OWNERS files are up-to-date as well. + +**How does the group get updates, reports, or feedback from working groups? Are there any springing up or being retired? Are OWNERS files up to date in these areas?** + + - We have not been getting updates from the working groups on any regular cadence. + - We will make it a priority to get updates in the next upcoming meetings. + - Currently sponsored workgroups are: + - wg-api-expression + - wg-component-standard + - wg-k8s-infra + - wg-naming + - wg-policy + - wg-reliability + +**When was your last monthly community-wide update? (provide link to deck and/or recording)** + + - [June, 2020](https://youtu.be/ObqQxRRl9RQ?t=2277) at Kubernetes Community Meeting. [Slides](https://docs.google.com/presentation/d/1NytMrpVYKzFo7rLcEEHnFl8zOx05fnjs3xBSZXVE0nI/edit?usp=sharing). + - [December, 2020](https://youtu.be/rnNqcUeCD8E) at KubeCon NA, published on YouTube. We do not have anything lined up for Kubecon EU. We will prioritize giving our next update in Kubecon NA. + +## Membership + +**Are all listed SIG leaders (chairs, tech leads, and subproject owners) active?** + +- All SIG chairs are active and attend most bi-weekly full SIG meetings. We do not have separate tech leads. + +- For the conformance subproject, all owners are active in PR review and meeting attendance. + +- For the production readiness subproject, all owners are active in both KEP reviews and meetings. + +- For the enhancements subproject, all owners are all active. + +- For the API review subproject, there are no standing meetings. The subproject coordinates via a [project board](https://github.com/orgs/kubernetes/projects/13) and [mailing list](https://groups.google.com/g/kubernetes-api-reviewers). + +- For the code organization subproject, @dims and @liggitt run regular meetings and review PRs and issues, pulling in other owners as needed. + +**How do you measure membership? By mailing list members, OWNERs, or something else?** + +- Mailing list members, though based on bounces during calendar updates, there are quite a few out-of-date memberships. + +**How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it?** + +- PRR assigns specific approvers to each KEP that is targeting a release. Therefore, we have a clear picture of how much each + approver must do each cycle. In 1.21, each approver reviewed 22 KEPs. for the 1.22 cycle, we have a new approver (@ehashman) to + help reduce the load on each approver. Go Elana! +- Code Organization is coming along. Though we haven't updated dep-approvers in a while. Currently the root OWNERS are a bottleneck as their time is limited for dependency updates. We have a new approval plugin that will help. + + - [kubernetes/test-infra#7690](https://github.com/kubernetes/test-infra/issues/7690) would allow routing dep approval to a distinct group + - Started dep-reviewers alias in [kubernetes/kubernetes#101670](https://github.com/kubernetes/kubernetes/pull/101670), can use to get additional help on reviews + +**Is there a healthy onboarding and growth path for contributors in your SIG? What are some activities that the group does to encourage this? What programs are you participating in to grow contributors throughout the contributor ladder?** + +- SIG Architecture owns very little code. The API review and Production Readiness Review projects do have reviewers and approvers + for those specialized purposes. Each of those programs has a documented shadow program to add new reviewers and approvers. +- The main meeting itself is losing steam a bit. We could use more across the board attendance. We have to find ways to do this with better timely topics. +- The sub projects are in sustainable shape for the most part. We could use more people in conformance, code-organization, and PRR for sure. +- We want to rework the API reviews as well to make sure SIGs can for the most part do their own API reviews. +- The Enhancements subproject has some tooling code, and is a good place for newer folks to contribute. It has been quite active recently, and as a process-focused subproject is a place where program managers can collaborate with other contributors on optimising processes regarding feature development, deprecations, policy rollouts, and other substantial changes. + +**What programs do you participate in for new contributors?** +- Mainly through code-organization, we have a new mentee from LFX for example. +- We do need to grow more folks who can work across SIGs somehow. We might need to put together a mentoring program to help with this. +- We are reviving the idea of a reading group for KEPs. + +**Does the group have contributors from multiple companies/affiliations? Can end users/companies contribute in some way that they currently are not?** + +- Yes. Our chairs are from three different companies. We have many participants and subproject owners from those same companies and others. + +## Current initiatives and project health + +**What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? Currently underway? What are some of the longer tail projects that your group is working on?** + +- We are proud of the work of the conformance subproject in burning down the [list of API endpoints that were untested](https://apisnoop.cncf.io/conformance-progress). +- the code-organization has come a long way as well, helping coordinate updates to dependencies across various projects to help make our dependencies cleaner (example grpc update across etcd/containerd etc) +- PRR ([policy](https://github.com/kubernetes/community/blob/master/sig-architecture/production-readiness.md), [KEP](https://github.com/kubernetes/enhancements/tree/master/keps/sig-architecture/1194-prod-readiness)) was made mandatory in 1.21 and the PRR team reviewed 66 KEPs, improving the scalability and supportability, and ensuring monitoring and feature enablement is properly conducted to make features production ready. +- Policies to move features across the project to GA, including: + - [Conformance Without Beta](https://github.com/kubernetes/enhancements/tree/master/keps/sig-architecture/1333-conformance-without-beta) + - [Preventing Permabeta](https://github.com/kubernetes/enhancements/tree/master/keps/sig-architecture/1635-prevent-permabeta) +- The Enhancements subproject has a number of initiatives, including: + - Process changes: the team has been working with the Release Team to assist SIGs in taking greater ownership of their KEPs during the release cycle, reducing reliance on the RT and allowing them to better organize their work and increase communication between SIGs and authors. + - The Receipts Project (ongoing) is working on automating some of the mechanics of KEP process to streamline and better track KEPs in a release cycle. + - KEPs have been transitioned to the new format which includes kep.yamls and a new directory structure (special thanks to @wojtek-t and new contributor @shekhar-rajak for all of their hard work on this!). + +**Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha?** + +- We are working on updates to enhancements process to make it easier for everyone involved. + +**What areas and/or subprojects does the group need the most help with?** + +- Setting up a mentoring program to increase the number of folks who can work across SIGs. +- Increasing the number of API reviewers and PRR approvers. + +**What's the average open days of a PR and Issue in your group? / what metrics does your group care about and/or measure?** + +- We mostly care about landing changes for the conformance subproject as it directly affects every end user. That has been going well the last few cycles. diff --git a/sig-architecture/annual-report-2021.md b/sig-architecture/annual-report-2021.md deleted file mode 100644 index 6feadfd3..00000000 --- a/sig-architecture/annual-report-2021.md +++ /dev/null @@ -1,116 +0,0 @@ -# 2021 SIG Architecture Annual Report - -## Operational - -**How are you doing with operational tasks in sig-governance.md?** - -**Is your README accurate? have a CONTRIBUTING.md file?** - - - Yes, our README is accurate. We do not have a CONTRIBUTING.md file, and so will add one. - -**All subprojects correctly mapped and listed in sigs.yaml?** - - - Yes. - -**What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? Are you keeping recordings up to date/trends in community members watching recordings?** - - - Our bi-weekly meeting is normally well attended, with approximately 20 individuals on a typical day, though it varies from a handful of folks to 40 or 50 depending on topics. - - - Subproject meetings are smaller, generally in the half dozen range. - -**How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being retired? Are OWNERS files up to date in these areas?** - - - We have a rotating schedule of subproject updates in the bi-weekly community meeting. Our OWNERS files are up-to-date as well. - -**How does the group get updates, reports, or feedback from working groups? Are there any springing up or being retired? Are OWNERS files up to date in these areas?** - - - We have not been getting updates from the working groups on any regular cadence. - - We will make it a priority to get updates in the next upcoming meetings. - - Currently sponsored workgroups are: - - wg-api-expression - - wg-component-standard - - wg-k8s-infra - - wg-naming - - wg-policy - - wg-reliability - -**When was your last monthly community-wide update? (provide link to deck and/or recording)** - - - [June, 2020](https://youtu.be/ObqQxRRl9RQ?t=2277) at Kubernetes Community Meeting. [Slides](https://docs.google.com/presentation/d/1NytMrpVYKzFo7rLcEEHnFl8zOx05fnjs3xBSZXVE0nI/edit?usp=sharing). - - [December, 2020](https://youtu.be/rnNqcUeCD8E) at KubeCon NA, published on YouTube. We do not have anything lined up for Kubecon EU. We will prioritize giving our next update in Kubecon NA. - -## Membership - -**Are all listed SIG leaders (chairs, tech leads, and subproject owners) active?** - -- All SIG chairs are active and attend most bi-weekly full SIG meetings. We do not have separate tech leads. - -- For the conformance subproject, all owners are active in PR review and meeting attendance. - -- For the production readiness subproject, all owners are active in both KEP reviews and meetings. - -- For the enhancements subproject, all owners are all active. - -- For the API review subproject, there are no standing meetings. The subproject coordinates via a [project board](https://github.com/orgs/kubernetes/projects/13) and [mailing list](https://groups.google.com/g/kubernetes-api-reviewers). - -- For the code organization subproject, @dims and @liggitt run regular meetings and review PRs and issues, pulling in other owners as needed. - -**How do you measure membership? By mailing list members, OWNERs, or something else?** - -- Mailing list members, though based on bounces during calendar updates, there are quite a few out-of-date memberships. - -**How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it?** - -- PRR assigns specific approvers to each KEP that is targeting a release. Therefore, we have a clear picture of how much each - approver must do each cycle. In 1.21, each approver reviewed 22 KEPs. for the 1.22 cycle, we have a new approver (@ehashman) to - help reduce the load on each approver. Go Elana! -- Code Organization is coming along. Though we haven't updated dep-approvers in a while. Currently the root OWNERS are a bottleneck as their time is limited for dependency updates. We have a new approval plugin that will help. - - - [kubernetes/test-infra#7690](https://github.com/kubernetes/test-infra/issues/7690) would allow routing dep approval to a distinct group - - Started dep-reviewers alias in [kubernetes/kubernetes#101670](https://github.com/kubernetes/kubernetes/pull/101670), can use to get additional help on reviews - -**Is there a healthy onboarding and growth path for contributors in your SIG? What are some activities that the group does to encourage this? What programs are you participating in to grow contributors throughout the contributor ladder?** - -- SIG Architecture owns very little code. The API review and Production Readiness Review projects do have reviewers and approvers - for those specialized purposes. Each of those programs has a documented shadow program to add new reviewers and approvers. -- The main meeting itself is losing steam a bit. We could use more across the board attendance. We have to find ways to do this with better timely topics. -- The sub projects are in sustainable shape for the most part. We could use more people in conformance, code-organization, and PRR for sure. -- We want to rework the API reviews as well to make sure SIGs can for the most part do their own API reviews. -- The Enhancements subproject has some tooling code, and is a good place for newer folks to contribute. It has been quite active recently, and as a process-focused subproject is a place where program managers can collaborate with other contributors on optimising processes regarding feature development, deprecations, policy rollouts, and other substantial changes. - -**What programs do you participate in for new contributors?** -- Mainly through code-organization, we have a new mentee from LFX for example. -- We do need to grow more folks who can work across SIGs somehow. We might need to put together a mentoring program to help with this. -- We are reviving the idea of a reading group for KEPs. - -**Does the group have contributors from multiple companies/affiliations? Can end users/companies contribute in some way that they currently are not?** - -- Yes. Our chairs are from three different companies. We have many participants and subproject owners from those same companies and others. - -## Current initiatives and project health - -**What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? Currently underway? What are some of the longer tail projects that your group is working on?** - -- We are proud of the work of the conformance subproject in burning down the [list of API endpoints that were untested](https://apisnoop.cncf.io/conformance-progress). -- the code-organization has come a long way as well, helping coordinate updates to dependencies across various projects to help make our dependencies cleaner (example grpc update across etcd/containerd etc) -- PRR ([policy](https://github.com/kubernetes/community/blob/master/sig-architecture/production-readiness.md), [KEP](https://github.com/kubernetes/enhancements/tree/master/keps/sig-architecture/1194-prod-readiness)) was made mandatory in 1.21 and the PRR team reviewed 66 KEPs, improving the scalability and supportability, and ensuring monitoring and feature enablement is properly conducted to make features production ready. -- Policies to move features across the project to GA, including: - - [Conformance Without Beta](https://github.com/kubernetes/enhancements/tree/master/keps/sig-architecture/1333-conformance-without-beta) - - [Preventing Permabeta](https://github.com/kubernetes/enhancements/tree/master/keps/sig-architecture/1635-prevent-permabeta) -- The Enhancements subproject has a number of initiatives, including: - - Process changes: the team has been working with the Release Team to assist SIGs in taking greater ownership of their KEPs during the release cycle, reducing reliance on the RT and allowing them to better organize their work and increase communication between SIGs and authors. - - The Receipts Project (ongoing) is working on automating some of the mechanics of KEP process to streamline and better track KEPs in a release cycle. - - KEPs have been transitioned to the new format which includes kep.yamls and a new directory structure (special thanks to @wojtek-t and new contributor @shekhar-rajak for all of their hard work on this!). - -**Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha?** - -- We are working on updates to enhancements process to make it easier for everyone involved. - -**What areas and/or subprojects does the group need the most help with?** - -- Setting up a mentoring program to increase the number of folks who can work across SIGs. -- Increasing the number of API reviewers and PRR approvers. - -**What's the average open days of a PR and Issue in your group? / what metrics does your group care about and/or measure?** - -- We mostly care about landing changes for the conformance subproject as it directly affects every end user. That has been going well the last few cycles. diff --git a/sig-auth/annual-report-2020.md b/sig-auth/annual-report-2020.md new file mode 100644 index 00000000..9e3fb8b9 --- /dev/null +++ b/sig-auth/annual-report-2020.md @@ -0,0 +1,116 @@ +# Kubernetes SIG Auth 2020 Annual Report + +## Operational + +**How are you doing with operational tasks in sig-governance.md?** + +**Is your README accurate? have a CONTRIBUTING.md file?** + + - Yes, our README is accurate. As of this report, we do not have a CONTRIBUTING.md file. We will be [creating one](https://github.com/kubernetes/community/issues/5760) shortly. + +**All subprojects correctly mapped and listed in sigs.yaml?** + + - Yes. + +**What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? Are you keeping recordings up to date/trends in community members watching recordings?** + + - Our bi-weekly meetings are usually pretty active with medium size attendance consists of mostly the same people. Some meetings may get more people depending on the topic. + + - Subproject meetings are smaller. + + - We take [meeting notes](https://docs.google.com/document/d/1woLGRoONE3EBVx-wTb4pvp4CI7tmLZ6lS26VTbosLKM/edit#) during the meeting. Unfortunately we do not do a great job of keeping good meeting notes. We are discussing various ways to improve. + + - The recordings serve as a historical record for bi-weekly SIG meeting and special topics meetings. They are uploaded to YouTube automatically. Then SIG chairs add the video to the [SIG Auth playlist](https://www.youtube.com/playlist?list=PL69nYSiGNLP0VMOZ-V7-5AchXTHAQFzJw). + +**How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being retired? Are OWNERS files up to date in these areas?** + + - We do not do much here today. We will ask subproject owners to give updates in the main SIG meeting on some cadence. + + - Our OWNERS files are up-to-date. + +**How does the group get updates, reports, or feedback from working groups? Are there any springing up or being retired? Are OWNERS files up to date in these areas?** + + - We do not do much here today. We will ask working group owners to give updates in the main SIG meeting on some cadence. + + - Our OWNERS files are up-to-date. + +**When was your last monthly community-wide update? (provide link to deck and/or recording)** + + - [February, 2020 Slides](https://docs.google.com/presentation/d/1HBMqr5V79S8BSrSMAxPdQiyyCL9byBBWj2D4WrR3hPY). + +## Membership + +**Are all listed SIG leaders (chairs, tech leads, and subproject owners) active?** + +- Yes, all SIG chairs and leads are active. + +- Need to review subproject owners to confirm. + +**How do you measure membership? By mailing list members, OWNERs, or something else?** + +- We do not currently measure membership. We could start with Slack, mailing list members, and meeting attendance. As of this report, there are 2,136 members of the main SIG Auth Slack channel and 447 members of the mailing list. + +**How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it?** + +- We do not currently measure this. Need to look at how other SIGs do this today. + +**Is there a healthy onboarding and growth path for contributors in your SIG? What are some activities that the group does to encourage this? What programs are you participating in to grow contributors throughout the contributor ladder?** + +- Currently there is no onboarding or growth path. This is something we are working on and learning from other SIGs. We will start by creating a CONTRIBUTING.md file. + +**What programs do you participate in for new contributors?** + +- We have intro sessions at KubeCon to help new contributors get started. + +- We now have weekly issues and PRs triage meetings. New contributors can join to help with new issues and PRs. + +**Does the group have contributors from multiple companies/affiliations? Can end users/companies contribute in some way that they currently are not?** + +- Yes. Our chairs, leads, contributors, participants, and subproject owners are from various companies. + +## Current initiatives and project health + +- Please include links to KEPs and other supporting information that will be beneficial to multiple types of community members. + +**What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? Currently underway? What are some of the longer tail projects that your group is working on?** + +- [CSR v1](https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/1513-certificate-signing-request) +- [Token Request / bound SA token admission](https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/1205-bound-service-account-tokens) +- [client-go auth plugins](https://github.com/kubernetes/enhancements/blob/master/keps/sig-auth/541-external-credential-providers) +- [external kubelet credential providers](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/2133-kubelet-credential-providers) +- [New features in Secrets Store CSI driver](https://secrets-store-csi-driver.sigs.k8s.io/introduction.html#features) +- [Pod Security Policy Replacement](https://github.com/kubernetes/enhancements/issues/2579) + +**Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha?** + +- Stable + - BoundServiceAccountToken (v1.22) + - Certificates API (v1.19) + - TokenRequest (v1.20) + - TokenRequestProjection (v1.20) + - RootCAConfigMap (v1.21) + - ServiceAccountIssuerDiscovery (v1.21) + - client-go auth plugins (v1.22) +- Beta + - CSIServiceAccountToken (v1.21) +- Alpha + - Hierarchical Namespace Controller +- Road to alpha + - Pod Security Policy Replacement + +**What areas and/or subprojects does the group need the most help with?** + +- Audit Logging + - https://github.com/kubernetes/kubernetes/issues/101597 + - https://github.com/kubernetes/kubernetes/issues/84571 + - https://github.com/kubernetes/kubernetes/issues/82295 + - https://github.com/kubernetes/kubernetes/issues?q=is%3Aopen+is%3Aissue+label%3Aarea%2Faudit+ +- Testing + - https://github.com/kubernetes/enhancements/issues/541#issuecomment-799372909 +- KMS + - [KMS-Plugin: Areas for improvement](https://docs.google.com/document/d/1-WHXX_Dh_MNcJb2QJxF0gOAvLjh0fAnc3QrylWdMZJA/edit) + +**What's the average open days of a PR and Issue in your group? / what metrics does your group care about and/or measure?** + +- Based on devstats [Issue Velocity / Inactive Issues by SIG for 90 days or more](https://k8s.devstats.cncf.io/d/73/inactive-issues-by-sig?orgId=1&var-sigs=%22auth%22) at the time of writing this report, average is 7. +- Based on devstats [PR Velocity / Awaiting PRs by SIG for 90 days or more](https://k8s.devstats.cncf.io/d/70/awaiting-prs-by-sig?orgId=1&var-sigs=%22auth%22) at the time of writing this report, average is 47. diff --git a/sig-auth/annual-report-2021.md b/sig-auth/annual-report-2021.md deleted file mode 100644 index 71c0e404..00000000 --- a/sig-auth/annual-report-2021.md +++ /dev/null @@ -1,116 +0,0 @@ -# Kubernetes SIG Auth 2021 Annual Report - -## Operational - -**How are you doing with operational tasks in sig-governance.md?** - -**Is your README accurate? have a CONTRIBUTING.md file?** - - - Yes, our README is accurate. As of this report, we do not have a CONTRIBUTING.md file. We will be [creating one](https://github.com/kubernetes/community/issues/5760) shortly. - -**All subprojects correctly mapped and listed in sigs.yaml?** - - - Yes. - -**What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? Are you keeping recordings up to date/trends in community members watching recordings?** - - - Our bi-weekly meetings are usually pretty active with medium size attendance consists of mostly the same people. Some meetings may get more people depending on the topic. - - - Subproject meetings are smaller. - - - We take [meeting notes](https://docs.google.com/document/d/1woLGRoONE3EBVx-wTb4pvp4CI7tmLZ6lS26VTbosLKM/edit#) during the meeting. Unfortunately we do not do a great job of keeping good meeting notes. We are discussing various ways to improve. - - - The recordings serve as a historical record for bi-weekly SIG meeting and special topics meetings. They are uploaded to YouTube automatically. Then SIG chairs add the video to the [SIG Auth playlist](https://www.youtube.com/playlist?list=PL69nYSiGNLP0VMOZ-V7-5AchXTHAQFzJw). - -**How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being retired? Are OWNERS files up to date in these areas?** - - - We do not do much here today. We will ask subproject owners to give updates in the main SIG meeting on some cadence. - - - Our OWNERS files are up-to-date. - -**How does the group get updates, reports, or feedback from working groups? Are there any springing up or being retired? Are OWNERS files up to date in these areas?** - - - We do not do much here today. We will ask working group owners to give updates in the main SIG meeting on some cadence. - - - Our OWNERS files are up-to-date. - -**When was your last monthly community-wide update? (provide link to deck and/or recording)** - - - [February, 2020 Slides](https://docs.google.com/presentation/d/1HBMqr5V79S8BSrSMAxPdQiyyCL9byBBWj2D4WrR3hPY). - -## Membership - -**Are all listed SIG leaders (chairs, tech leads, and subproject owners) active?** - -- Yes, all SIG chairs and leads are active. - -- Need to review subproject owners to confirm. - -**How do you measure membership? By mailing list members, OWNERs, or something else?** - -- We do not currently measure membership. We could start with Slack, mailing list members, and meeting attendance. As of this report, there are 2,136 members of the main SIG Auth Slack channel and 447 members of the mailing list. - -**How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it?** - -- We do not currently measure this. Need to look at how other SIGs do this today. - -**Is there a healthy onboarding and growth path for contributors in your SIG? What are some activities that the group does to encourage this? What programs are you participating in to grow contributors throughout the contributor ladder?** - -- Currently there is no onboarding or growth path. This is something we are working on and learning from other SIGs. We will start by creating a CONTRIBUTING.md file. - -**What programs do you participate in for new contributors?** - -- We have intro sessions at KubeCon to help new contributors get started. - -- We now have weekly issues and PRs triage meetings. New contributors can join to help with new issues and PRs. - -**Does the group have contributors from multiple companies/affiliations? Can end users/companies contribute in some way that they currently are not?** - -- Yes. Our chairs, leads, contributors, participants, and subproject owners are from various companies. - -## Current initiatives and project health - -- Please include links to KEPs and other supporting information that will be beneficial to multiple types of community members. - -**What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? Currently underway? What are some of the longer tail projects that your group is working on?** - -- [CSR v1](https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/1513-certificate-signing-request) -- [Token Request / bound SA token admission](https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/1205-bound-service-account-tokens) -- [client-go auth plugins](https://github.com/kubernetes/enhancements/blob/master/keps/sig-auth/541-external-credential-providers) -- [external kubelet credential providers](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/2133-kubelet-credential-providers) -- [New features in Secrets Store CSI driver](https://secrets-store-csi-driver.sigs.k8s.io/introduction.html#features) -- [Pod Security Policy Replacement](https://github.com/kubernetes/enhancements/issues/2579) - -**Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha?** - -- Stable - - BoundServiceAccountToken (v1.22) - - Certificates API (v1.19) - - TokenRequest (v1.20) - - TokenRequestProjection (v1.20) - - RootCAConfigMap (v1.21) - - ServiceAccountIssuerDiscovery (v1.21) - - client-go auth plugins (v1.22) -- Beta - - CSIServiceAccountToken (v1.21) -- Alpha - - Hierarchical Namespace Controller -- Road to alpha - - Pod Security Policy Replacement - -**What areas and/or subprojects does the group need the most help with?** - -- Audit Logging - - https://github.com/kubernetes/kubernetes/issues/101597 - - https://github.com/kubernetes/kubernetes/issues/84571 - - https://github.com/kubernetes/kubernetes/issues/82295 - - https://github.com/kubernetes/kubernetes/issues?q=is%3Aopen+is%3Aissue+label%3Aarea%2Faudit+ -- Testing - - https://github.com/kubernetes/enhancements/issues/541#issuecomment-799372909 -- KMS - - [KMS-Plugin: Areas for improvement](https://docs.google.com/document/d/1-WHXX_Dh_MNcJb2QJxF0gOAvLjh0fAnc3QrylWdMZJA/edit) - -**What's the average open days of a PR and Issue in your group? / what metrics does your group care about and/or measure?** - -- Based on devstats [Issue Velocity / Inactive Issues by SIG for 90 days or more](https://k8s.devstats.cncf.io/d/73/inactive-issues-by-sig?orgId=1&var-sigs=%22auth%22) at the time of writing this report, average is 7. -- Based on devstats [PR Velocity / Awaiting PRs by SIG for 90 days or more](https://k8s.devstats.cncf.io/d/70/awaiting-prs-by-sig?orgId=1&var-sigs=%22auth%22) at the time of writing this report, average is 47. diff --git a/sig-cli/annual-report-2020.md b/sig-cli/annual-report-2020.md new file mode 100644 index 00000000..483c4f12 --- /dev/null +++ b/sig-cli/annual-report-2020.md @@ -0,0 +1,73 @@ +# SIG CLI Annual Report 2020 + +This report reflects back on CY 2020 and was written in March 2021. + +## Operational + +* How are you doing with operational tasks in [sig-governance.md](https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md)? + + * Is your README accurate? have a CONTRIBUTING.md file? + * Yes, [README.md](https://github.com/kubernetes/community/blob/master/sig-cli/README.md) is accurate and up-to-date. + * Our [CONTRIBUTING.md](https://github.com/kubernetes/community/blob/master/sig-cli/CONTRIBUTING.md) requires an update as a follow-up to our recent completion of the [move to staging](https://github.com/kubernetes/enhancements/issues/1020). + + * All subprojects correctly mapped and listed in sigs.yaml? + * The current list is up-to-date, but this will soon require an update as soon as [KUI moves to kubernetes-sig](https://github.com/kubernetes/org/issues/2461). + + * What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? Are you keeping recordings up to date/trends in community members watching recordings? + * We have two recurring meetings: + 1. Our main meeting happens biweekly, during those calls we always reserve time for important announcements, such as important release dates, recognitions, etc. After that we leave time for newcomers to introduce themselves. The remaining part of the call is devoted to discuss items which are in the agenda. We close the call with a round of standups from subprojects. + 2. Bug scrub every four weeks, during which we go through issues and pull requests, assigning them to contributors who are interested in working on them. + All of the meetings are recorded and available online, all the meeting invites are up-to-date and present in community calendar. + +* How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being retired? Are OWNERS files up to date in these areas? + * As mentioned above, all the subprojects have a spot to report their progress during standups at the end of our biweekly calls. OWNERS files are up-to-date. + +* When was your last monthly community-wide update? (provide link to deck and/or recording) + * Last presentation was on April 16, 2020: + * [Slides](https://docs.google.com/presentation/d/1Y8SHFz6yyYS6rvRCgYUrSgF-moPk_YB6A-7Ykw5eWnU/edit#slide=id.g401c104a3c_0_) + * [Recording](https://youtu.be/Y3z2grPHRh4?t=415) + * [KubeCon NA 2020 recording](https://www.youtube.com/watch?v=gTzv6mpTYWw) + +## Membership + +* Are all listed SIG leaders (chairs, tech leads, and subproject owners) active? + * Yes, all the lists are up-to-date. + +* How do you measure membership? By mailing list members, OWNERs, or something else? + * Anyone can be considered a SIG member if they join the Zoom calls or general discussions regularly. + +* How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it? + * At our biweekly meetings (see [notes](https://docs.google.com/document/d/1r0YElcXt6G5mOWxwZiXgGu_X6he3F--wKwg-9UBc29I/edit)), we track the progress of each feature the SIG is working on. Each feature has dev leads assigned to it. If a developer does not have time to complete the task we try to find someone else who has the bandwidth or we defer the feature to the next release. + * We periodically remove inactive reviewers and approvers, invite new contributors we have seen active in SIG meetings and activities to join the ranks. + +* Is there a healthy onboarding and growth path for contributors in your SIG? What are some activities that the group does to encourage this? What programs are you participating in to grow contributors throughout the contributor ladder? + * Over the past months the leads take a bit more aggressive approach to closely monitor contributions and recognize the most active members by promoting them to reviewers and eventually approvers. + +* What programs do you participate in for new contributors? + * We try to feature “good-first-issue”s. + * As mentioned above, we give newcomers a spot to introduce at our biweekly calls. + * KubeCon updates. + * Individual/1-1 mentoring. + * In 2020 we participated in Google Season of Docs which resulted in [new documentation for kubectl and kustomize](https://kubectl.docs.kubernetes.io/). + * Meet our contributors. + +* Does the group have contributors from multiple companies/affiliations? Can end users/companies contribute in some way that they currently are not? + * The group has contributors from multiple companies/affiliations. + * [28 companies contributed code in the last year](https://k8s.devstats.cncf.io/d/8/company-statistics-by-repository-group?orgId=1&var-period=y&var-metric=contributions&var-repogroup_name=SIG%20CLI&var-companies=All) + +## Current initiatives and project health + +* What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? Currently underway? What are some of the longer tail projects that your group is working on? + * [Moving kubectl package code to staging](https://github.com/kubernetes/enhancements/issues/1020) + +* Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha? + * [Moving kubectl package code to staging](https://github.com/kubernetes/enhancements/issues/1020) + * Our multi-year effort to split out of the main kubernetes repository. + * [kubectl debug](https://github.com/kubernetes/enhancements/issues/1441) (beta) + * Several smaller efforts to unify code across all the commands, and removing technical debt. + +* What areas and/or subprojects does the group need the most help with? + * Feature management - we're looking for a person who is familiar with managing feature delivery/product management in a broad sense. As mentioned before, the current process is that during our bi-weekly calls at the beginning of every release we write down planned features and a person responsible for delivering it. We would like to see a single person driving this effort and transforming that to a more asynchronous process. For example, gathering features through our mailing list and reporting progress during our bi-weekly calls. + +* What's the average open days of a PR and Issue in your group? / what metrics does your group care about and/or measure? + * Over the past year we've introduced monthly blocker bug scrubs which allowed us to shorten the average PR time to approve and merge by more than half, [from over a 8.5 days to 3 days](https://k8s.devstats.cncf.io/d/44/pr-time-to-approve-and-merge?orgId=1&from=1577865600000&to=1609488000000&var-period=y&var-repogroup_name=SIG%20CLI&var-apichange=All&var-size_name=All&var-kind_name=All). diff --git a/sig-cli/annual-report-2021.md b/sig-cli/annual-report-2021.md deleted file mode 100644 index 8883c898..00000000 --- a/sig-cli/annual-report-2021.md +++ /dev/null @@ -1,73 +0,0 @@ -# SIG CLI Annual Report 2021 - -This report reflects back on CY 2020 and was written in March 2021. - -## Operational - -* How are you doing with operational tasks in [sig-governance.md](https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md)? - - * Is your README accurate? have a CONTRIBUTING.md file? - * Yes, [README.md](https://github.com/kubernetes/community/blob/master/sig-cli/README.md) is accurate and up-to-date. - * Our [CONTRIBUTING.md](https://github.com/kubernetes/community/blob/master/sig-cli/CONTRIBUTING.md) requires an update as a follow-up to our recent completion of the [move to staging](https://github.com/kubernetes/enhancements/issues/1020). - - * All subprojects correctly mapped and listed in sigs.yaml? - * The current list is up-to-date, but this will soon require an update as soon as [KUI moves to kubernetes-sig](https://github.com/kubernetes/org/issues/2461). - - * What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? Are you keeping recordings up to date/trends in community members watching recordings? - * We have two recurring meetings: - 1. Our main meeting happens biweekly, during those calls we always reserve time for important announcements, such as important release dates, recognitions, etc. After that we leave time for newcomers to introduce themselves. The remaining part of the call is devoted to discuss items which are in the agenda. We close the call with a round of standups from subprojects. - 2. Bug scrub every four weeks, during which we go through issues and pull requests, assigning them to contributors who are interested in working on them. - All of the meetings are recorded and available online, all the meeting invites are up-to-date and present in community calendar. - -* How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being retired? Are OWNERS files up to date in these areas? - * As mentioned above, all the subprojects have a spot to report their progress during standups at the end of our biweekly calls. OWNERS files are up-to-date. - -* When was your last monthly community-wide update? (provide link to deck and/or recording) - * Last presentation was on April 16, 2020: - * [Slides](https://docs.google.com/presentation/d/1Y8SHFz6yyYS6rvRCgYUrSgF-moPk_YB6A-7Ykw5eWnU/edit#slide=id.g401c104a3c_0_) - * [Recording](https://youtu.be/Y3z2grPHRh4?t=415) - * [KubeCon NA 2020 recording](https://www.youtube.com/watch?v=gTzv6mpTYWw) - -## Membership - -* Are all listed SIG leaders (chairs, tech leads, and subproject owners) active? - * Yes, all the lists are up-to-date. - -* How do you measure membership? By mailing list members, OWNERs, or something else? - * Anyone can be considered a SIG member if they join the Zoom calls or general discussions regularly. - -* How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it? - * At our biweekly meetings (see [notes](https://docs.google.com/document/d/1r0YElcXt6G5mOWxwZiXgGu_X6he3F--wKwg-9UBc29I/edit)), we track the progress of each feature the SIG is working on. Each feature has dev leads assigned to it. If a developer does not have time to complete the task we try to find someone else who has the bandwidth or we defer the feature to the next release. - * We periodically remove inactive reviewers and approvers, invite new contributors we have seen active in SIG meetings and activities to join the ranks. - -* Is there a healthy onboarding and growth path for contributors in your SIG? What are some activities that the group does to encourage this? What programs are you participating in to grow contributors throughout the contributor ladder? - * Over the past months the leads take a bit more aggressive approach to closely monitor contributions and recognize the most active members by promoting them to reviewers and eventually approvers. - -* What programs do you participate in for new contributors? - * We try to feature “good-first-issue”s. - * As mentioned above, we give newcomers a spot to introduce at our biweekly calls. - * KubeCon updates. - * Individual/1-1 mentoring. - * In 2020 we participated in Google Season of Docs which resulted in [new documentation for kubectl and kustomize](https://kubectl.docs.kubernetes.io/). - * Meet our contributors. - -* Does the group have contributors from multiple companies/affiliations? Can end users/companies contribute in some way that they currently are not? - * The group has contributors from multiple companies/affiliations. - * [28 companies contributed code in the last year](https://k8s.devstats.cncf.io/d/8/company-statistics-by-repository-group?orgId=1&var-period=y&var-metric=contributions&var-repogroup_name=SIG%20CLI&var-companies=All) - -## Current initiatives and project health - -* What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? Currently underway? What are some of the longer tail projects that your group is working on? - * [Moving kubectl package code to staging](https://github.com/kubernetes/enhancements/issues/1020) - -* Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha? - * [Moving kubectl package code to staging](https://github.com/kubernetes/enhancements/issues/1020) - * Our multi-year effort to split out of the main kubernetes repository. - * [kubectl debug](https://github.com/kubernetes/enhancements/issues/1441) (beta) - * Several smaller efforts to unify code across all the commands, and removing technical debt. - -* What areas and/or subprojects does the group need the most help with? - * Feature management - we're looking for a person who is familiar with managing feature delivery/product management in a broad sense. As mentioned before, the current process is that during our bi-weekly calls at the beginning of every release we write down planned features and a person responsible for delivering it. We would like to see a single person driving this effort and transforming that to a more asynchronous process. For example, gathering features through our mailing list and reporting progress during our bi-weekly calls. - -* What's the average open days of a PR and Issue in your group? / what metrics does your group care about and/or measure? - * Over the past year we've introduced monthly blocker bug scrubs which allowed us to shorten the average PR time to approve and merge by more than half, [from over a 8.5 days to 3 days](https://k8s.devstats.cncf.io/d/44/pr-time-to-approve-and-merge?orgId=1&from=1577865600000&to=1609488000000&var-period=y&var-repogroup_name=SIG%20CLI&var-apichange=All&var-size_name=All&var-kind_name=All). diff --git a/sig-cloud-provider/2020-annual-report.md b/sig-cloud-provider/2020-annual-report.md deleted file mode 100644 index cbe81bbd..00000000 --- a/sig-cloud-provider/2020-annual-report.md +++ /dev/null @@ -1,86 +0,0 @@ -# 2020 - SIG Cloud Provider - Community Meeting Annual Reports ---- -## Operational -**How are you doing with operational tasks in sig-governance.md?** - -**Is your README accurate? have a CONTRIBUTING.md file?** - -Our README is accurate but we do not currently have a contributing.md file. - -**All subprojects correctly mapped and listed in [sigs.yaml](https://github.com/kubernetes/community/blob/master/sigs.yaml)?** - -I believe so. - -**What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? Are you keeping recordings up to date/trends in community members watching recordings?** - -Our meetings tends to be small and quiet. We try to keep the meeting notes upto date during the meeting. - -**How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being retired? Are OWNERS files up to date in these areas?** -_Same question as above but for working groups._ - -We go over the sub project updates during our primary biweekly meeting. -I believe the OWNERS files are all upto date. - -**When was your last monthly community-wide update? (provide link to deck and/or recording)** - ---- -## Membership -**Are all listed SIG leaders (chairs, tech leads, and subproject owners) active?** - -I believe so. - -**How do you measure membership? By mailing list members, OWNERs, or something else?** - -1. We look at the number of people attending our meetings, messaing on our slack channels and contributing to our repos. -1. We look at the number of cloud providers who have people doing the above. - -**How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it?** - -1. For changes to cloud provider infrastructure where all approvers can approve, I think things are going reasonably well. But I'd like to hear what others think. -1. For changes to a specific cloud provider implementation, where an approval is required from someone outside the company, I think there is a bigger problem, particularly for VMWare and Google since the SIG Chairs (the most active approvers) are from those respective companies. I feel like we need to work toward having more approvers (e.g. get to the point where the defacto bus factor is at least 2 for any change). I don't think this necessarily requires more top level approvers in the short term-- getting more sub-tree approvers (with good diversity across cloud providers) and expanding their ownership seem like a good steps. - -**Is there a healthy onboarding and growth path for contributors in your SIG? What are some activities that the group does to encourage this? What programs are you participating in to grow contributors throughout the contributor ladder?** - -Most of our SIG members are contributors from at least one cloud provider. We try to reach our to the various cloud providers during KubeCon to make sure they are aware of us and that their voices are being heard. New members come in slowly enough that we can generally provide direct mentorship and arrange this through our slack channel or meetings. - -**What programs do you participate in for new contributors?** - -None, our contributors tend to be representatives from the various companies who provider Kubernetes on the Cloud. It would be nice to expand this however. - -**Does the group have contributors from multiple companies/affiliations? Can end users/companies contribute in some way that they currently are not?** - -We try hard to make sure we have presentation from each of the interested cloud providers. - ---- -## Current initiatives and project health -_Please include links to KEPs and other supporting information that will be beneficial to multiple types of community members._ - -**What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? Currently underway? What are some of the longer tail projects that your group is working on?** - -[Feature: implement the BackendManager list](https://github.com/kubernetes-sigs/apiserver-network-proxy/pull/144) fixes a long standing issue for people running clusters with nodes which are either not routable or at least not close to one another. -[Fix flag passing in CCM](https://github.com/kubernetes/kubernetes/pull/98210) fixes a significant problem/cost most cloud providers experienced trying to remain current on their CCM dependency. -[Extending Apiserver Network Proxy to handle traffic originated from Node network](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cloud-provider/2025-extend-konnectivity-for-both-directions) is an interesting and difficult initiative around build out K8s where the control plane and data plane are remote. - - -**Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha?** - -[Promoting Cloud Provider Labels to GA](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cloud-provider/837-cloud-provider-labels) to GA - -[API Server Network Proxy](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/1281-network-proxy) to Beta - -[Reporting Conformance Test Results to Testgrid](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cloud-provider/2390-reporting-conformance-test-results-to-testgrid) ongoing. -[Building Kubernetes Without In-Tree Cloud Providers](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cloud-provider/1179-building-without-in-tree-providers) to Alpha -[Extending Apiserver Network Proxy to handle traffic originated from Node network](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cloud-provider/2025-extend-konnectivity-for-both-directions) -[Kubelet Credential Providers](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2133-kubelet-credential-providers) to Alpha -[Leader Migration for Controller Managers](https://github.com/kubernetes/enhancements/issues/2436) to Alpha - -**What areas and/or subprojects does the group need the most help with?** - -We run the cloud provider extraction working group initiative. We need help engaging more with cloud providers. We also really need help dealing with the both the K/K "cluster" directory and resolving how we properly test K/K in the absence of a cloud provider. - -**What's the average open days of a PR and Issue in your group? / what metrics does your group care about and/or measure?** - -Pretty long :( -We are trying to build up a team of multiple contributors for every cloud provider to help triage and handle these. We are slowly growing this and its getting better but more so with some cloud providers than others. - ---- diff --git a/sig-cloud-provider/annual-report-2020.md b/sig-cloud-provider/annual-report-2020.md new file mode 100644 index 00000000..cbe81bbd --- /dev/null +++ b/sig-cloud-provider/annual-report-2020.md @@ -0,0 +1,86 @@ +# 2020 - SIG Cloud Provider - Community Meeting Annual Reports +--- +## Operational +**How are you doing with operational tasks in sig-governance.md?** + +**Is your README accurate? have a CONTRIBUTING.md file?** + +Our README is accurate but we do not currently have a contributing.md file. + +**All subprojects correctly mapped and listed in [sigs.yaml](https://github.com/kubernetes/community/blob/master/sigs.yaml)?** + +I believe so. + +**What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? Are you keeping recordings up to date/trends in community members watching recordings?** + +Our meetings tends to be small and quiet. We try to keep the meeting notes upto date during the meeting. + +**How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being retired? Are OWNERS files up to date in these areas?** +_Same question as above but for working groups._ + +We go over the sub project updates during our primary biweekly meeting. +I believe the OWNERS files are all upto date. + +**When was your last monthly community-wide update? (provide link to deck and/or recording)** + +--- +## Membership +**Are all listed SIG leaders (chairs, tech leads, and subproject owners) active?** + +I believe so. + +**How do you measure membership? By mailing list members, OWNERs, or something else?** + +1. We look at the number of people attending our meetings, messaing on our slack channels and contributing to our repos. +1. We look at the number of cloud providers who have people doing the above. + +**How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it?** + +1. For changes to cloud provider infrastructure where all approvers can approve, I think things are going reasonably well. But I'd like to hear what others think. +1. For changes to a specific cloud provider implementation, where an approval is required from someone outside the company, I think there is a bigger problem, particularly for VMWare and Google since the SIG Chairs (the most active approvers) are from those respective companies. I feel like we need to work toward having more approvers (e.g. get to the point where the defacto bus factor is at least 2 for any change). I don't think this necessarily requires more top level approvers in the short term-- getting more sub-tree approvers (with good diversity across cloud providers) and expanding their ownership seem like a good steps. + +**Is there a healthy onboarding and growth path for contributors in your SIG? What are some activities that the group does to encourage this? What programs are you participating in to grow contributors throughout the contributor ladder?** + +Most of our SIG members are contributors from at least one cloud provider. We try to reach our to the various cloud providers during KubeCon to make sure they are aware of us and that their voices are being heard. New members come in slowly enough that we can generally provide direct mentorship and arrange this through our slack channel or meetings. + +**What programs do you participate in for new contributors?** + +None, our contributors tend to be representatives from the various companies who provider Kubernetes on the Cloud. It would be nice to expand this however. + +**Does the group have contributors from multiple companies/affiliations? Can end users/companies contribute in some way that they currently are not?** + +We try hard to make sure we have presentation from each of the interested cloud providers. + +--- +## Current initiatives and project health +_Please include links to KEPs and other supporting information that will be beneficial to multiple types of community members._ + +**What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? Currently underway? What are some of the longer tail projects that your group is working on?** + +[Feature: implement the BackendManager list](https://github.com/kubernetes-sigs/apiserver-network-proxy/pull/144) fixes a long standing issue for people running clusters with nodes which are either not routable or at least not close to one another. +[Fix flag passing in CCM](https://github.com/kubernetes/kubernetes/pull/98210) fixes a significant problem/cost most cloud providers experienced trying to remain current on their CCM dependency. +[Extending Apiserver Network Proxy to handle traffic originated from Node network](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cloud-provider/2025-extend-konnectivity-for-both-directions) is an interesting and difficult initiative around build out K8s where the control plane and data plane are remote. + + +**Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha?** + +[Promoting Cloud Provider Labels to GA](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cloud-provider/837-cloud-provider-labels) to GA + +[API Server Network Proxy](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/1281-network-proxy) to Beta + +[Reporting Conformance Test Results to Testgrid](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cloud-provider/2390-reporting-conformance-test-results-to-testgrid) ongoing. +[Building Kubernetes Without In-Tree Cloud Providers](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cloud-provider/1179-building-without-in-tree-providers) to Alpha +[Extending Apiserver Network Proxy to handle traffic originated from Node network](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cloud-provider/2025-extend-konnectivity-for-both-directions) +[Kubelet Credential Providers](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2133-kubelet-credential-providers) to Alpha +[Leader Migration for Controller Managers](https://github.com/kubernetes/enhancements/issues/2436) to Alpha + +**What areas and/or subprojects does the group need the most help with?** + +We run the cloud provider extraction working group initiative. We need help engaging more with cloud providers. We also really need help dealing with the both the K/K "cluster" directory and resolving how we properly test K/K in the absence of a cloud provider. + +**What's the average open days of a PR and Issue in your group? / what metrics does your group care about and/or measure?** + +Pretty long :( +We are trying to build up a team of multiple contributors for every cloud provider to help triage and handle these. We are slowly growing this and its getting better but more so with some cloud providers than others. + +--- diff --git a/sig-cluster-lifecycle/annual-report-2020.md b/sig-cluster-lifecycle/annual-report-2020.md new file mode 100644 index 00000000..664313c0 --- /dev/null +++ b/sig-cluster-lifecycle/annual-report-2020.md @@ -0,0 +1,99 @@ +# SIG Cluster Lifecycle Annual Report 2020 + +## Operational + +* How are you doing with operational tasks in +[sig-governance.md](https://git.k8s.io/community/committee-steering/governance/sig-governance.md)? + * Is your README accurate? have a CONTRIBUTING.md file? + * Yes, [README.md](https://git.k8s.io/community/sig-cluster-lifecycle/README.md) is accurate + * We have a [CONTRIBUTING.md](https://git.k8s.io/community/sig-cluster-lifecycle/CONTRIBUTING.md) + * All subprojects correctly mapped and listed in [sigs.yaml](https://git.k8s.io/community/sig-list.md)? + * [Yes](https://git.k8s.io/community/sig-cluster-lifecycle/README.md#subprojects) + * What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? Are you keeping + recordings up to date/trends in community members watching recordings? + * The main SIG meeting has ~10 people on average. Some projects like kubeadm have low attendance, + while others like Cluster API have high attendance. Meeting notes usually are a best effort. + [We record all SIG meetings](https://www.youtube.com/playlist?list=PL69nYSiGNLP29D0nYgAGWt1ZFqS9Z7lw4). +* How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being +retired? Are OWNERS.md files up to date in these areas? + * [We do regular subproject updates](https://docs.google.com/document/d/1Gmc7LyCIL_148a9Tft7pdhdee0NBHdOfHS1SAF0duI4/edit) + as part of the main SIG call. + * We recently retired [https://github.com/kubernetes/kube-deploy](https://github.com/kubernetes/kube-deploy) and + [https://github.com/kubernetes-retired/kube-aws](https://github.com/kubernetes-retired/kube-aws). + * Keeping OWNERS files up-to-date falls under maintenance of subproject leads. We hope that they keep + them up-to-date as they know their community better. We update OWNER files and send occasional reminders for that: + * [Recent mailing list notification](https://groups.google.com/g/kubernetes-sig-cluster-lifecycle/c/KH8g4WRjOAE) + * [https://github.com/kubernetes/kubernetes/pull/98547](https://github.com/kubernetes/kubernetes/pull/98547) + * [https://github.com/kubernetes/kubeadm/pull/2390](https://github.com/kubernetes/kubeadm/pull/2390) +* Same question as above but for working groups. + * The [WG Component Standard ](https://git.k8s.io/community/wg-component-standard) which we co-own with + SIG API Machinery [is looking for new leads](https://groups.google.com/g/kubernetes-wg-component-standard/c/sNAqDptjJug/m/P87KtaZuAgAJ). + On private we proposed that we should ideally find new leads instead of disbanding the WG, + but if no leads volunteer we are going to have to do that. The WG is not very active, due to the current + leads being busy with other work. + * We do not own other WGs. +* When was your last monthly community-wide update? (provide link to deck and/or recording) + * Last presentation was on July 16, 2020: + * [Slides](https://docs.google.com/presentation/d/1ZEDeF6lqxP-LmxCRa2EBmDS1sZFAv3RmrdQOUyd6IAc/edit?usp=sharing) + * [VOD](https://www.youtube.com/watch?v=J3O8fXTm3HE) + +## Membership + +* Are all listed SIG leaders (chairs, tech leads, and subproject owners) active? + * For the SIG leads yes. + * For subproject owners, likely there are some inactive maintainers, but it’s up to the subproject to prune their OWNERs files. +* How do you measure membership? By mailing list members, OWNERs, or something else? + * Anyone can be considered a SIG member if they join the Zoom calls or general discussions regularly. + * In terms of repository scope - an active contributor with PRs / Issues / Reviews becomes eligible to be part of an OWNERS file. +* How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it? + * For sub-projects, it’s up to the active subproject maintainers to allocate review resources. + * Some projects like etcdadm, cluster-addons and kubeadm are currently looking for more contributors. + * We use the common methods of + [“help-wanted” labels](https://github.com/kubernetes-sigs/cluster-api/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22) + and announcing the request for help on slack / mailing list. + * For the main SIG (e.g. when reviewing KEPs) the lead who has the time usually reviews, but we try to notify everyone + so that they can comment if they have the time too. +* Is there a healthy onboarding and growth path for contributors in your SIG? +What are some activities that the group does to encourage this? What programs are you participating in to grow contributors +throughout the contributor ladder? + * One of our methods is to just record onboarding videos / hold Zoom sessions discussing a certain problem / area: + * [kubeadm instructional videos](https://git.k8s.io/kubeadm/CONTRIBUTING.md#instructional-videos) + * [Cluster API e2e walkthrough](https://groups.google.com/g/kubernetes-sig-cluster-lifecycle/c/gBbbXrUThT4/m/uS3-Z2mfDAAJ) + * New contributors interested in such an areas should join these calls and ask questions. + * Most of our meetings have a dedicated slot for welcoming newcomers. +* What programs do you participate in for new contributors? + * [We participated in Google Summer of code 2020](https://kubernetes.io/blog/2020/09/16/gsoc20-building-operators-for-cluster-addons/) + with the Cluster Addons project. +* Does the group have contributors from multiple companies/affiliations? Can end users/companies contribute in some way that +they currently are not? + * We have contributors from a number of different companies interested in Kubernetes: + * [Cluster API stats](https://k8s.devstats.cncf.io/d/8/company-statistics-by-repository-group?orgId=1&var-period=d7&var-metric=contributions&var-repogroup_name=SIG%20Cluster%20Lifecycle%20(Cluster%20API)&var-companies=All) + * [Overall Cluster Lifecycle stats](https://k8s.devstats.cncf.io/d/8/company-statistics-by-repository-group?orgId=1&var-period=d7&var-metric=contributions&var-repogroup_name=SIG%20Cluster%20Lifecycle&var-companies=All) + * Everyone can contribute as long as they have the motivation and their ideas are good. + +## Current initiatives and project health + +* [x] Please include links to KEPs and other supporting information that will be beneficial to multiple types of community members. +* What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? Currently underway? +What are some of the longer tail projects that your group is working on? + * We did a KEP to standardize how clusters define insecure local container registries: + * [1755-communicating-a-local-registry](https://git.k8s.io/enhancements/keps/sig-cluster-lifecycle/generic/1755-communicating-a-local-registry) + * Cluster API has its own spin of the KEP process and has a number of interesting active proposals: + * [Cluster API proposals](https://github.com/kubernetes-sigs/cluster-api/tree/master/docs/proposals) + * Most of our subprojects have existed for a long time - including, kubeadm, kops, minikube, etc. +* Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha? + * Only kubeadm features go through the Alpha->GA stages of the Kubernetes release process: + * [keps/sig-cluster-lifecycle](https://https://git.k8s.io/enhancements/keps/sig-cluster-lifecycle) + * Projects like kops, minikube, kubeadm, kubespray are mostly stable. + * Projects like Cluster API and etcdadm are alpha and moving towards graduation following a process similar to Kubernetes. +* What areas and/or subprojects does the group need the most help with? + * Here are a few picks from more to less: + * [Etcdadm](https://github.com/kubernetes-sigs/etcdadm) + * [Cluster-addons](https://github.com/kubernetes-sigs/cluster-addons) + * [Kubeadm](https://github.com/kubernetes/kubeadm) +* What's the average open days of a PR and Issue in your group? / what metrics does your group care about and/or measure? + * Our SIG is quite big and it depends on the subprojects. + * It’s up to the subproject to monitor the metrics they care about. + * For the SIG as a whole we track what tickets we have here: + * [kubernetes/enhancements](https://github.com/kubernetes/enhancements/labels/sig%2Fcluster-lifecycle) + * [kubernetes/kubernetes](https://github.com/kubernetes/kubernetes/labels/sig%2Fcluster-lifecycle) diff --git a/sig-cluster-lifecycle/annual-report-2021.md b/sig-cluster-lifecycle/annual-report-2021.md deleted file mode 100644 index 3c57b44c..00000000 --- a/sig-cluster-lifecycle/annual-report-2021.md +++ /dev/null @@ -1,99 +0,0 @@ -# SIG Cluster Lifecycle Annual Report 2021 - -## Operational - -* How are you doing with operational tasks in -[sig-governance.md](https://git.k8s.io/community/committee-steering/governance/sig-governance.md)? - * Is your README accurate? have a CONTRIBUTING.md file? - * Yes, [README.md](https://git.k8s.io/community/sig-cluster-lifecycle/README.md) is accurate - * We have a [CONTRIBUTING.md](https://git.k8s.io/community/sig-cluster-lifecycle/CONTRIBUTING.md) - * All subprojects correctly mapped and listed in [sigs.yaml](https://git.k8s.io/community/sig-list.md)? - * [Yes](https://git.k8s.io/community/sig-cluster-lifecycle/README.md#subprojects) - * What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? Are you keeping - recordings up to date/trends in community members watching recordings? - * The main SIG meeting has ~10 people on average. Some projects like kubeadm have low attendance, - while others like Cluster API have high attendance. Meeting notes usually are a best effort. - [We record all SIG meetings](https://www.youtube.com/playlist?list=PL69nYSiGNLP29D0nYgAGWt1ZFqS9Z7lw4). -* How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being -retired? Are OWNERS.md files up to date in these areas? - * [We do regular subproject updates](https://docs.google.com/document/d/1Gmc7LyCIL_148a9Tft7pdhdee0NBHdOfHS1SAF0duI4/edit) - as part of the main SIG call. - * We recently retired [https://github.com/kubernetes/kube-deploy](https://github.com/kubernetes/kube-deploy) and - [https://github.com/kubernetes-retired/kube-aws](https://github.com/kubernetes-retired/kube-aws). - * Keeping OWNERS files up-to-date falls under maintenance of subproject leads. We hope that they keep - them up-to-date as they know their community better. We update OWNER files and send occasional reminders for that: - * [Recent mailing list notification](https://groups.google.com/g/kubernetes-sig-cluster-lifecycle/c/KH8g4WRjOAE) - * [https://github.com/kubernetes/kubernetes/pull/98547](https://github.com/kubernetes/kubernetes/pull/98547) - * [https://github.com/kubernetes/kubeadm/pull/2390](https://github.com/kubernetes/kubeadm/pull/2390) -* Same question as above but for working groups. - * The [WG Component Standard ](https://git.k8s.io/community/wg-component-standard) which we co-own with - SIG API Machinery [is looking for new leads](https://groups.google.com/g/kubernetes-wg-component-standard/c/sNAqDptjJug/m/P87KtaZuAgAJ). - On private we proposed that we should ideally find new leads instead of disbanding the WG, - but if no leads volunteer we are going to have to do that. The WG is not very active, due to the current - leads being busy with other work. - * We do not own other WGs. -* When was your last monthly community-wide update? (provide link to deck and/or recording) - * Last presentation was on July 16, 2020: - * [Slides](https://docs.google.com/presentation/d/1ZEDeF6lqxP-LmxCRa2EBmDS1sZFAv3RmrdQOUyd6IAc/edit?usp=sharing) - * [VOD](https://www.youtube.com/watch?v=J3O8fXTm3HE) - -## Membership - -* Are all listed SIG leaders (chairs, tech leads, and subproject owners) active? - * For the SIG leads yes. - * For subproject owners, likely there are some inactive maintainers, but it’s up to the subproject to prune their OWNERs files. -* How do you measure membership? By mailing list members, OWNERs, or something else? - * Anyone can be considered a SIG member if they join the Zoom calls or general discussions regularly. - * In terms of repository scope - an active contributor with PRs / Issues / Reviews becomes eligible to be part of an OWNERS file. -* How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it? - * For sub-projects, it’s up to the active subproject maintainers to allocate review resources. - * Some projects like etcdadm, cluster-addons and kubeadm are currently looking for more contributors. - * We use the common methods of - [“help-wanted” labels](https://github.com/kubernetes-sigs/cluster-api/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22) - and announcing the request for help on slack / mailing list. - * For the main SIG (e.g. when reviewing KEPs) the lead who has the time usually reviews, but we try to notify everyone - so that they can comment if they have the time too. -* Is there a healthy onboarding and growth path for contributors in your SIG? -What are some activities that the group does to encourage this? What programs are you participating in to grow contributors -throughout the contributor ladder? - * One of our methods is to just record onboarding videos / hold Zoom sessions discussing a certain problem / area: - * [kubeadm instructional videos](https://git.k8s.io/kubeadm/CONTRIBUTING.md#instructional-videos) - * [Cluster API e2e walkthrough](https://groups.google.com/g/kubernetes-sig-cluster-lifecycle/c/gBbbXrUThT4/m/uS3-Z2mfDAAJ) - * New contributors interested in such an areas should join these calls and ask questions. - * Most of our meetings have a dedicated slot for welcoming newcomers. -* What programs do you participate in for new contributors? - * [We participated in Google Summer of code 2020](https://kubernetes.io/blog/2020/09/16/gsoc20-building-operators-for-cluster-addons/) - with the Cluster Addons project. -* Does the group have contributors from multiple companies/affiliations? Can end users/companies contribute in some way that -they currently are not? - * We have contributors from a number of different companies interested in Kubernetes: - * [Cluster API stats](https://k8s.devstats.cncf.io/d/8/company-statistics-by-repository-group?orgId=1&var-period=d7&var-metric=contributions&var-repogroup_name=SIG%20Cluster%20Lifecycle%20(Cluster%20API)&var-companies=All) - * [Overall Cluster Lifecycle stats](https://k8s.devstats.cncf.io/d/8/company-statistics-by-repository-group?orgId=1&var-period=d7&var-metric=contributions&var-repogroup_name=SIG%20Cluster%20Lifecycle&var-companies=All) - * Everyone can contribute as long as they have the motivation and their ideas are good. - -## Current initiatives and project health - -* [x] Please include links to KEPs and other supporting information that will be beneficial to multiple types of community members. -* What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? Currently underway? -What are some of the longer tail projects that your group is working on? - * We did a KEP to standardize how clusters define insecure local container registries: - * [1755-communicating-a-local-registry](https://git.k8s.io/enhancements/keps/sig-cluster-lifecycle/generic/1755-communicating-a-local-registry) - * Cluster API has its own spin of the KEP process and has a number of interesting active proposals: - * [Cluster API proposals](https://github.com/kubernetes-sigs/cluster-api/tree/master/docs/proposals) - * Most of our subprojects have existed for a long time - including, kubeadm, kops, minikube, etc. -* Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha? - * Only kubeadm features go through the Alpha->GA stages of the Kubernetes release process: - * [keps/sig-cluster-lifecycle](https://https://git.k8s.io/enhancements/keps/sig-cluster-lifecycle) - * Projects like kops, minikube, kubeadm, kubespray are mostly stable. - * Projects like Cluster API and etcdadm are alpha and moving towards graduation following a process similar to Kubernetes. -* What areas and/or subprojects does the group need the most help with? - * Here are a few picks from more to less: - * [Etcdadm](https://github.com/kubernetes-sigs/etcdadm) - * [Cluster-addons](https://github.com/kubernetes-sigs/cluster-addons) - * [Kubeadm](https://github.com/kubernetes/kubeadm) -* What's the average open days of a PR and Issue in your group? / what metrics does your group care about and/or measure? - * Our SIG is quite big and it depends on the subprojects. - * It’s up to the subproject to monitor the metrics they care about. - * For the SIG as a whole we track what tickets we have here: - * [kubernetes/enhancements](https://github.com/kubernetes/enhancements/labels/sig%2Fcluster-lifecycle) - * [kubernetes/kubernetes](https://github.com/kubernetes/kubernetes/labels/sig%2Fcluster-lifecycle) diff --git a/sig-contributor-experience/annual-report-2020.md b/sig-contributor-experience/annual-report-2020.md new file mode 100644 index 00000000..c12bae68 --- /dev/null +++ b/sig-contributor-experience/annual-report-2020.md @@ -0,0 +1,141 @@ +# Special Interest Groups: Contributor Experience + +#### Operational + +- How are you doing with operational tasks in [SIG]-governance.md? + - Is your README accurate? have a CONTRIBUTING.md file? + - The README is up to date and accurate, we do not have a + CONTRIBUTING.md file. + - All subprojects correctly mapped and listed in sigs.yaml? + - Yes + - What’s your meeting culture? Large/small, active/quiet, learnings? Meeting + notes up to date? Are you keeping recordings up to date/trends in community + members watching recordings? + - We have biweekly zoom meetings. It is small, but active. + - The APAC-friendly zoom meeting was poorly attended so we are + discontinuing it. + - We are also hosting biweekly asynchronous meetings on slack, which has + made it easier for members from APAC regions to participate. + - Meeting notes are up to date, recordings of the meetings are published. + The YouTube recordings often have <10 views with jumps to 30~ when they + are featured on the front page of the channel. Collectively during 2020 + the SIG ContribEx playlist had 167 views with an average watch time of + 00:03:55. Compared to the previous year, this was an increase in views, + but a decrease in average watch time. +- How does the group get updates, reports, or feedback from subprojects? Are + there any springing up or being retired? Are OWNERS.md files up to date in + these areas? + - The weekly meeting (zoom or in slack) serves as a subproject status update. + The notes are then sent to the mailing list. + - A [subproject owner audit][audit] was completed in the first half of 2020 + - Some processes/meetings have been retired or retooled to reduce administrative + overhead and become more async friendly. +- Same question as above but for working groups. + - There is no formal reporting mechanism from the working groups. The updates + largely come from issues or discussions that bubble up into the SIG. + - SIG Contributor Experience TLs also participate in WG Infra directly, so we haven't + found the need for a formal reporting process. +- When was your last public community-wide update? (provide link to deck and/or + recording) + - August 2020 at KubeCon Europe Virtual - [link] to the session. + A similar Contribex session is also planned for KubeCon Europe 2021. + - July 2020 in the community meeting. Links to [updates] are added to the SIG ContribEx README. + +[link]: https://kccnceu20.sched.com/event/c9yh/intro-contributor-experience-sig-jorge-castro-vmware-bob-killen-university-of-michigan +[audit]: https://github.com/kubernetes/community/issues/4585 +[updates]: https://github.com/kubernetes/community/tree/master/sig-contributor-experience#current-status + + +#### Membership + +- Are all listed SIG leaders (chairs, tech leads, and subproject owners) active? + - No, there are several subproject owners that have become inactive and should + be moved to emeritus status. An audit is planned for 2021. +- How do you measure membership? By mailing list members, OWNERs, or something + else? + - Those that are actively engaged with meetings +- How does the group measure reviewer and approver bandwidth? Do you need help + in any area now? What are you doing about it? + - We do not actively monitor reviewer/approver bandwidth in a formalized way. + However, our [relative PR velocity][vel] is in a good state. We could use more + reviewers/approvers to help reduce risk and improve long-term sustainability. +- Is there a healthy onboarding and growth path for contributors in your SIG? + What are some activities that the group does to encourage this? What programs + are you participating in to grow contributors throughout the contributor ladder? + - We have lost many contributors over the past year. General calls for help did + not attract many new contributors, but with some additional outreach and + raising the problem areas in an [easier to see way][pr] has attracted new folk. + - We are actively applying the `good-first-issue` and `help-wanted` labels to issues + and are closely mentoring new contributors who pick up these issues. +- What programs do you participate in for new contributors? + - We have previously participated with Outreachy and Season of Docs. +- Does the group have contributors from multiple companies/affiliations? Can end + users/companies contribute in some way that they currently are not? + - Yes, we have multiple avenues for contributing for both code and non-code + projects alike. + + +#### Current initiatives and project health + +- What are initiatives that should be highlighted, lauded, shout outs, that + your group is proud of? Currently underway? What are some of the longer tail + projects that your group is working on? + - The contributor website (https://k8s.dev) + - Triage process improvements + - The 2020 Contributor Celebration + - Retired the Kubernetes-Incubator Org + - In Progress: Migrating the default branch on GitHub from `master` to `main` + - In Progress: Revamping the prow approval plugin to support granual approvals +- Year to date KEP work: + - [KEP-1553: Issue Triage Workflow and Automation][kep] + - In Progress: KEP for revamping the prow approval plugin +- What initiatives are you working on that aren't being tracked in KEPs? + + | Subproject | Initiative / Program | + |:-------------------------:|:--------------------------------------:| + | Community | Community Repo Stewardship | + | Community Management | Annual Contributor Survey | + | Community Management | Calendar Admin | + | Community Management | Chair and TL Meetings + Docs | + | Community Management | Discuss Admin | + | Community Management | Mailing List Admin | + | Community Management | Slack Admin | + | Community Management | Zoom / YouTube Admin | + | Community Management | Zoom / YouTube Automation (zapier) | + | Contributor Documentation | Contributor Guide Stewardship | + | Contributor Documentation | Contributor Site | + | Contributor Documentation | Developer Guide Audit | + | Contributor Documentation | Developer Guide Stewardship | + | Contributor Documentation | Season of Docs | + | Contributors Comms | Contributor / SIG Profiling | + | Contributors Comms | Stewardship of k8scontributors twitter | + | Devstats | Devstats Dashboard Update | + | Events | Monthly Community Meeting | + | Events | Office Hours | + | GitHub Management | GitHub Admin / Moderation | + | GitHub Management | GitHub Master -> Main rename | + | GitHub Management | GitHub New Membership Coordinator | + | Mentoring | 1:1 Hour | + | Mentoring | Google Summer of Code | + | Mentoring | Group Mentoring | + | Mentoring | LFX Mentor Program | + | Mentoring | Meet our Contributors | + | Mentoring | New Contributor Workshop | + | Mentoring | Outreachy | + | Slack Infra | slack-infra | + + **source:** [ContribEx Initatives and Prioritization spreadsheet][pr] + +- What areas and/or subprojects does the group need the most help with? + - Many need help. These are being tracked separately in the + [ContribEx Initatives and Prioritization spreadsheet][pr]. +- What metrics/community health stats does your group care about and/or measure? + - The only dashboard we use at this point in time is the + [PR workloads table][vel] in devstats. + + + +[vel]: https://k8s.devstats.cncf.io/d/34/pr-workload-per-sig-table?orgId=1&var-period_name=Last%20year +[kep]: https://git.k8s.io/enhancements/keps/sig-contributor-experience/1553-issue-triage +[pr]: https://docs.google.com/spreadsheets/d/1glhdFcUdqYAByW16hujxK1X_0k9mt_nrkCO4POeDNbs/edit#gid=0 + diff --git a/sig-contributor-experience/annual-report-2021.md b/sig-contributor-experience/annual-report-2021.md deleted file mode 100644 index c12bae68..00000000 --- a/sig-contributor-experience/annual-report-2021.md +++ /dev/null @@ -1,141 +0,0 @@ -# Special Interest Groups: Contributor Experience - -#### Operational - -- How are you doing with operational tasks in [SIG]-governance.md? - - Is your README accurate? have a CONTRIBUTING.md file? - - The README is up to date and accurate, we do not have a - CONTRIBUTING.md file. - - All subprojects correctly mapped and listed in sigs.yaml? - - Yes - - What’s your meeting culture? Large/small, active/quiet, learnings? Meeting - notes up to date? Are you keeping recordings up to date/trends in community - members watching recordings? - - We have biweekly zoom meetings. It is small, but active. - - The APAC-friendly zoom meeting was poorly attended so we are - discontinuing it. - - We are also hosting biweekly asynchronous meetings on slack, which has - made it easier for members from APAC regions to participate. - - Meeting notes are up to date, recordings of the meetings are published. - The YouTube recordings often have <10 views with jumps to 30~ when they - are featured on the front page of the channel. Collectively during 2020 - the SIG ContribEx playlist had 167 views with an average watch time of - 00:03:55. Compared to the previous year, this was an increase in views, - but a decrease in average watch time. -- How does the group get updates, reports, or feedback from subprojects? Are - there any springing up or being retired? Are OWNERS.md files up to date in - these areas? - - The weekly meeting (zoom or in slack) serves as a subproject status update. - The notes are then sent to the mailing list. - - A [subproject owner audit][audit] was completed in the first half of 2020 - - Some processes/meetings have been retired or retooled to reduce administrative - overhead and become more async friendly. -- Same question as above but for working groups. - - There is no formal reporting mechanism from the working groups. The updates - largely come from issues or discussions that bubble up into the SIG. - - SIG Contributor Experience TLs also participate in WG Infra directly, so we haven't - found the need for a formal reporting process. -- When was your last public community-wide update? (provide link to deck and/or - recording) - - August 2020 at KubeCon Europe Virtual - [link] to the session. - A similar Contribex session is also planned for KubeCon Europe 2021. - - July 2020 in the community meeting. Links to [updates] are added to the SIG ContribEx README. - -[link]: https://kccnceu20.sched.com/event/c9yh/intro-contributor-experience-sig-jorge-castro-vmware-bob-killen-university-of-michigan -[audit]: https://github.com/kubernetes/community/issues/4585 -[updates]: https://github.com/kubernetes/community/tree/master/sig-contributor-experience#current-status - - -#### Membership - -- Are all listed SIG leaders (chairs, tech leads, and subproject owners) active? - - No, there are several subproject owners that have become inactive and should - be moved to emeritus status. An audit is planned for 2021. -- How do you measure membership? By mailing list members, OWNERs, or something - else? - - Those that are actively engaged with meetings -- How does the group measure reviewer and approver bandwidth? Do you need help - in any area now? What are you doing about it? - - We do not actively monitor reviewer/approver bandwidth in a formalized way. - However, our [relative PR velocity][vel] is in a good state. We could use more - reviewers/approvers to help reduce risk and improve long-term sustainability. -- Is there a healthy onboarding and growth path for contributors in your SIG? - What are some activities that the group does to encourage this? What programs - are you participating in to grow contributors throughout the contributor ladder? - - We have lost many contributors over the past year. General calls for help did - not attract many new contributors, but with some additional outreach and - raising the problem areas in an [easier to see way][pr] has attracted new folk. - - We are actively applying the `good-first-issue` and `help-wanted` labels to issues - and are closely mentoring new contributors who pick up these issues. -- What programs do you participate in for new contributors? - - We have previously participated with Outreachy and Season of Docs. -- Does the group have contributors from multiple companies/affiliations? Can end - users/companies contribute in some way that they currently are not? - - Yes, we have multiple avenues for contributing for both code and non-code - projects alike. - - -#### Current initiatives and project health - -- What are initiatives that should be highlighted, lauded, shout outs, that - your group is proud of? Currently underway? What are some of the longer tail - projects that your group is working on? - - The contributor website (https://k8s.dev) - - Triage process improvements - - The 2020 Contributor Celebration - - Retired the Kubernetes-Incubator Org - - In Progress: Migrating the default branch on GitHub from `master` to `main` - - In Progress: Revamping the prow approval plugin to support granual approvals -- Year to date KEP work: - - [KEP-1553: Issue Triage Workflow and Automation][kep] - - In Progress: KEP for revamping the prow approval plugin -- What initiatives are you working on that aren't being tracked in KEPs? - - | Subproject | Initiative / Program | - |:-------------------------:|:--------------------------------------:| - | Community | Community Repo Stewardship | - | Community Management | Annual Contributor Survey | - | Community Management | Calendar Admin | - | Community Management | Chair and TL Meetings + Docs | - | Community Management | Discuss Admin | - | Community Management | Mailing List Admin | - | Community Management | Slack Admin | - | Community Management | Zoom / YouTube Admin | - | Community Management | Zoom / YouTube Automation (zapier) | - | Contributor Documentation | Contributor Guide Stewardship | - | Contributor Documentation | Contributor Site | - | Contributor Documentation | Developer Guide Audit | - | Contributor Documentation | Developer Guide Stewardship | - | Contributor Documentation | Season of Docs | - | Contributors Comms | Contributor / SIG Profiling | - | Contributors Comms | Stewardship of k8scontributors twitter | - | Devstats | Devstats Dashboard Update | - | Events | Monthly Community Meeting | - | Events | Office Hours | - | GitHub Management | GitHub Admin / Moderation | - | GitHub Management | GitHub Master -> Main rename | - | GitHub Management | GitHub New Membership Coordinator | - | Mentoring | 1:1 Hour | - | Mentoring | Google Summer of Code | - | Mentoring | Group Mentoring | - | Mentoring | LFX Mentor Program | - | Mentoring | Meet our Contributors | - | Mentoring | New Contributor Workshop | - | Mentoring | Outreachy | - | Slack Infra | slack-infra | - - **source:** [ContribEx Initatives and Prioritization spreadsheet][pr] - -- What areas and/or subprojects does the group need the most help with? - - Many need help. These are being tracked separately in the - [ContribEx Initatives and Prioritization spreadsheet][pr]. -- What metrics/community health stats does your group care about and/or measure? - - The only dashboard we use at this point in time is the - [PR workloads table][vel] in devstats. - - - -[vel]: https://k8s.devstats.cncf.io/d/34/pr-workload-per-sig-table?orgId=1&var-period_name=Last%20year -[kep]: https://git.k8s.io/enhancements/keps/sig-contributor-experience/1553-issue-triage -[pr]: https://docs.google.com/spreadsheets/d/1glhdFcUdqYAByW16hujxK1X_0k9mt_nrkCO4POeDNbs/edit#gid=0 - diff --git a/sig-docs/annual-report-2020.md b/sig-docs/annual-report-2020.md new file mode 100644 index 00000000..a4c29c23 --- /dev/null +++ b/sig-docs/annual-report-2020.md @@ -0,0 +1,131 @@ +# SIG Docs 2020 Annual Report + +**Authors:** + +Irvi Aini ([@irvifa](https://github.com/irvifa)), +Jim Angel ([@jimangel](https://github.com/jimangel)), +Karen Bradshaw ([kbhawkey](https://github.com/kbhawkey)), +Kaitlyn Barnard ([@kbarnard10](https://github.com/kbarnard10)), +Taylor Dolezal ([onlydole](https://github.com/onlydole)), +Tim Bannister ([sftim](https://github.com/sftim)) + +- [Operational](#operational) +- [Membership](#membership) +- [Current initiatives and project health](#current-initiatives-and-project-health) + +## Operational + +**How are you doing with operational tasks in [sig-governance.md](/committee-steering/governance/sig-governance.md)?** + + - **Is your README accurate? have a CONTRIBUTING.md file?** + + Yes. We also have `Contributing.md` file. + - **All subprojects correctly mapped and listed in [sigs.yaml](/sig-list.md)?** + + Yes. + + - **What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? + Are you keeping recordings up to date/trends in community members watching recordings?** + + Quite small (usually 5-10 people) and generally we try to make people feel comfortable to give their opinion. + Meeting notes are up to date. We have recording of the meetings uploaded. + + We have a new sub-project, it's localization sub-project, where we conduct monthly meeting + attended by all people from the localization team. This sub-project focusing on sharing any concerns, + tips, or toolings that may be can be reused by other team as well. + + +**How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being retired? +Are OWNERS files up to date in these areas?** + +Yes it is. + +**How does the group get updates, reports, or feedback from Working Groups? Are there any springing up or being retired? +Are OWNERS files up to date in these areas?** + +Yes it is. + +**When was your last monthly community-wide update? (provide link to deck and/or recording)** + +[Q2 of 2020 (created April 8 2020)](https://docs.google.com/presentation/d/12WnYz8SbjWRZbK4k2qlc1Ab7Z-f2F7kk-Tb2eRTfTy8/edit?usp=sharing). + +## Membership + +**Are all listed SIG leaders (chairs, tech leads, and subproject owners) active?** + +Yes, they are. + +**How do you measure membership? By mailing list members, OWNERs, or something else?** + +We don't have an official way of measuring membership. + +**How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it?** + +PR are generally open for anyone to review. We have [PR wrangler rotation](https://github.com/kubernetes/website/wiki/PR-Wranglers). +In general each of the approver will taking the rotation. Each approver participates in the PR wrangler rotation. Approvers are supported during their rotation by other reviewers and approvers. + +For technical reviews, other than SIG Docs Tech Leads, we also notify respective SIGs with necessary knowledge of the technical aspect of the content. SIG Docs receives contributions from community members representing different SIGs. During the PR review process, SIG Docs reaches out to other SIGs when a pull request requires technical review. + +**Is there a healthy onboarding and growth path for contributors in your SIG? +What are some activities that the group does to encourage this? +What programs are you participating in to grow contributors throughout the contributor ladder?** + +There is no official onboarding process. However, the SIG is supportive of new contributors, +willing to walk through the contribution process and eager to see contributions completed. +Issues are created regularly and triaged. Issues are also created specifically for new +contributors. There are issues labelled for the different contribution areas (web development, +blog, first time contributors, task, concept, API, etc) which helps new contributors +identify how to get started. + +From time to time we use the weekly meeting Zoom calls to help new contributors get onboard. + +**What programs do you participate in for new contributors?** + +We used to host doc sprints during the KubeCon, +the doc sprints acted as a way to onboard new contributors as well as tackle a lot of open issues. + +**Does the group have contributors from multiple companies/affiliations?** + +Yes + +**Can end users/companies contribute in some way that they currently are not?** + +I suppose we're particular keen to hear about suggested improvements from people who are using Kubernetes in production and can see gaps in what's there. + +## Current initiatives and project health + +- [x] Please include links to KEPs and other supporting information that will be beneficial to multiple types of community members. + +Longer term projects include + +- coordination with WG naming for things like removing the word “slave” (and other problematic terms) from docs. +- publishing better information about releases kubernetes/website#20293 + +**What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? +Currently underway? What are some of the longer tail projects that your group is working on?** + +Shoutout to docsy theme work as well as the reference documentation generation :tada:. + +**Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha?** + +We have ongoing KEP, but we don't have a deadline set on when it should be finished. + +- [Doc policies for third party content](https://github.com/kubernetes/enhancements/tree/master/keps/sig-docs/1326-third-party-content-in-docs) + There's also an umbrella issue written as well [kubernetes/website#20232](https://github.com/kubernetes/website/issues/20232). + + +**What areas and/or subprojects does the group need the most help with?** + +- Blog subproject + +**What's the average open days of a PR and Issue in your group? / what metrics does your group care about and/or measure?** + +We have the information from [devstat](https://k8s.devstats.cncf.io/d/25/open-pr-age-by-repository-group?orgId=1&var-period=q&var-repogroup_name=SIG%20Docs&var-kind_name=All): + +![Devstat 2020](devstats/devstats-quarter-2021.png) + +For example, based on 10/01/2020 data, we have: +Average number of opened PRs 1.23 K with the median opened PRs age 3 days 13 hours 52 minutes 10 seconds. +In addition, we informally review metrics quarterly as well as ad hoc if anyone brings it up at a weekly meeting. +We aim to have < 100 open PRs for the English localization, +and will take steps as needed if we see the figure climbing much above that. diff --git a/sig-docs/annual-report-2021.md b/sig-docs/annual-report-2021.md deleted file mode 100644 index a4c29c23..00000000 --- a/sig-docs/annual-report-2021.md +++ /dev/null @@ -1,131 +0,0 @@ -# SIG Docs 2020 Annual Report - -**Authors:** - -Irvi Aini ([@irvifa](https://github.com/irvifa)), -Jim Angel ([@jimangel](https://github.com/jimangel)), -Karen Bradshaw ([kbhawkey](https://github.com/kbhawkey)), -Kaitlyn Barnard ([@kbarnard10](https://github.com/kbarnard10)), -Taylor Dolezal ([onlydole](https://github.com/onlydole)), -Tim Bannister ([sftim](https://github.com/sftim)) - -- [Operational](#operational) -- [Membership](#membership) -- [Current initiatives and project health](#current-initiatives-and-project-health) - -## Operational - -**How are you doing with operational tasks in [sig-governance.md](/committee-steering/governance/sig-governance.md)?** - - - **Is your README accurate? have a CONTRIBUTING.md file?** - - Yes. We also have `Contributing.md` file. - - **All subprojects correctly mapped and listed in [sigs.yaml](/sig-list.md)?** - - Yes. - - - **What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? - Are you keeping recordings up to date/trends in community members watching recordings?** - - Quite small (usually 5-10 people) and generally we try to make people feel comfortable to give their opinion. - Meeting notes are up to date. We have recording of the meetings uploaded. - - We have a new sub-project, it's localization sub-project, where we conduct monthly meeting - attended by all people from the localization team. This sub-project focusing on sharing any concerns, - tips, or toolings that may be can be reused by other team as well. - - -**How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being retired? -Are OWNERS files up to date in these areas?** - -Yes it is. - -**How does the group get updates, reports, or feedback from Working Groups? Are there any springing up or being retired? -Are OWNERS files up to date in these areas?** - -Yes it is. - -**When was your last monthly community-wide update? (provide link to deck and/or recording)** - -[Q2 of 2020 (created April 8 2020)](https://docs.google.com/presentation/d/12WnYz8SbjWRZbK4k2qlc1Ab7Z-f2F7kk-Tb2eRTfTy8/edit?usp=sharing). - -## Membership - -**Are all listed SIG leaders (chairs, tech leads, and subproject owners) active?** - -Yes, they are. - -**How do you measure membership? By mailing list members, OWNERs, or something else?** - -We don't have an official way of measuring membership. - -**How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it?** - -PR are generally open for anyone to review. We have [PR wrangler rotation](https://github.com/kubernetes/website/wiki/PR-Wranglers). -In general each of the approver will taking the rotation. Each approver participates in the PR wrangler rotation. Approvers are supported during their rotation by other reviewers and approvers. - -For technical reviews, other than SIG Docs Tech Leads, we also notify respective SIGs with necessary knowledge of the technical aspect of the content. SIG Docs receives contributions from community members representing different SIGs. During the PR review process, SIG Docs reaches out to other SIGs when a pull request requires technical review. - -**Is there a healthy onboarding and growth path for contributors in your SIG? -What are some activities that the group does to encourage this? -What programs are you participating in to grow contributors throughout the contributor ladder?** - -There is no official onboarding process. However, the SIG is supportive of new contributors, -willing to walk through the contribution process and eager to see contributions completed. -Issues are created regularly and triaged. Issues are also created specifically for new -contributors. There are issues labelled for the different contribution areas (web development, -blog, first time contributors, task, concept, API, etc) which helps new contributors -identify how to get started. - -From time to time we use the weekly meeting Zoom calls to help new contributors get onboard. - -**What programs do you participate in for new contributors?** - -We used to host doc sprints during the KubeCon, -the doc sprints acted as a way to onboard new contributors as well as tackle a lot of open issues. - -**Does the group have contributors from multiple companies/affiliations?** - -Yes - -**Can end users/companies contribute in some way that they currently are not?** - -I suppose we're particular keen to hear about suggested improvements from people who are using Kubernetes in production and can see gaps in what's there. - -## Current initiatives and project health - -- [x] Please include links to KEPs and other supporting information that will be beneficial to multiple types of community members. - -Longer term projects include - -- coordination with WG naming for things like removing the word “slave” (and other problematic terms) from docs. -- publishing better information about releases kubernetes/website#20293 - -**What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? -Currently underway? What are some of the longer tail projects that your group is working on?** - -Shoutout to docsy theme work as well as the reference documentation generation :tada:. - -**Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha?** - -We have ongoing KEP, but we don't have a deadline set on when it should be finished. - -- [Doc policies for third party content](https://github.com/kubernetes/enhancements/tree/master/keps/sig-docs/1326-third-party-content-in-docs) - There's also an umbrella issue written as well [kubernetes/website#20232](https://github.com/kubernetes/website/issues/20232). - - -**What areas and/or subprojects does the group need the most help with?** - -- Blog subproject - -**What's the average open days of a PR and Issue in your group? / what metrics does your group care about and/or measure?** - -We have the information from [devstat](https://k8s.devstats.cncf.io/d/25/open-pr-age-by-repository-group?orgId=1&var-period=q&var-repogroup_name=SIG%20Docs&var-kind_name=All): - -![Devstat 2020](devstats/devstats-quarter-2021.png) - -For example, based on 10/01/2020 data, we have: -Average number of opened PRs 1.23 K with the median opened PRs age 3 days 13 hours 52 minutes 10 seconds. -In addition, we informally review metrics quarterly as well as ad hoc if anyone brings it up at a weekly meeting. -We aim to have < 100 open PRs for the English localization, -and will take steps as needed if we see the figure climbing much above that. diff --git a/sig-instrumentation/annual-report-2020.md b/sig-instrumentation/annual-report-2020.md new file mode 100644 index 00000000..ebc3dfba --- /dev/null +++ b/sig-instrumentation/annual-report-2020.md @@ -0,0 +1,77 @@ +# SIG Instrumentation Annual Report 2020 + +This report reflects back on CY 2020 and was written in Feb-Mar. 2021. + +## Operational + +* How are you doing with operational tasks in [sig-governance.md](https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md)? + * Is your README accurate? have a CONTRIBUTING.md file? + * Yes. We do not require a separate CONTRIBUTING.md file. + * All subprojects correctly mapped and listed in [sigs.yaml](https://github.com/kubernetes/community/blob/master/sig-list.md)? + * Yes. + * What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? Are you keeping recordings up to date/trends in community members watching recordings? + * We have lively biweekly regular meetings and biweekly triage sessions. Our recordings are relatively up to date and we receive requests for them so we believe they are being watched. Our community archives are all up to date. +* How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being retired? Are OWNERS files up to date in these areas? + * We request these in SIG meetings and asynchronously for KubeCon and other community updates. + * See above for OWNERS updates. +* Same question as above but for working groups. + * N/A +* When was your last monthly community-wide update? (provide link to deck and/or recording) + * Oct. 2020 [https://groups.google.com/g/kubernetes-dev/c/x1xr7bSuzv8/m/Oz49ZJgRBgAJ](https://groups.google.com/g/kubernetes-dev/c/x1xr7bSuzv8/m/Oz49ZJgRBgAJ) + +## Membership + +* Are all listed SIG leaders (chairs, tech leads, and subproject owners) active? + * [https://k8s.devstats.cncf.io/d/13/developer-activity-counts-by-repository-group?orgId=1&var-period_name=Last%20quarter&var-metric=contributions&var-repogroup_name=All&var-country_name=All](https://k8s.devstats.cncf.io/d/13/developer-activity-counts-by-repository-group?orgId=1&var-period_name=Last%20quarter&var-metric=contributions&var-repogroup_name=All&var-country_name=All) + * All active in last quarter +* How do you measure membership? By mailing list members, OWNERs, or something else? + * [https://github.com/kubernetes/org/blob/main/config/kubernetes/sig-instrumentation/teams.yaml](https://github.com/kubernetes/org/blob/main/config/kubernetes/sig-instrumentation/teams.yaml) + * We have three teams: leads (chairs/TLs), approvers, and members + * We annually remove inactive members (using the same criteria used for voting) and invite members to join that we have seen active in SIG meetings and activities +* How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it? + * Approver: we have limited areas that need our approval so we are ok on bandwidth + * Review: distributed around SIG via biweekly triage meetings +* Is there a healthy onboarding and growth path for contributors in your SIG? What are some activities that the group does to encourage this? What programs are you participating in to grow contributors throughout the contributor ladder? + * We would like to grow more contributors into SIG leadership roles for sustainability. + * We invite newbies to come to triage meetings to learn how to review and triage code. + * We go over all features as a SIG in our regular meetings. + * We do not have a lot of code to own for people to progress on our SIG ladder but we are open to adding new approvers for people that put in the work. +* What programs do you participate in for new contributors? + * Individual/1-1 mentoring + * We try to feature “good-first-issue”s and raise them on k-dev (e.g. structured logging) +* Does the group have contributors from multiple companies/affiliations? Can end users/companies contribute in some way that they currently are not? + * Yes: Google, Red Hat, and many first contributors across multiple companies + * Cross referencing [PRs by contributor + company](https://k8s.devstats.cncf.io/d/66/developer-activity-counts-by-companies?orgId=1&var-period_name=Last%20quarter&var-metric=contributions&var-repogroup_name=All&var-country_name=All&var-companies=All) with our [members](https://github.com/kubernetes/org/blob/main/config/kubernetes/sig-instrumentation/teams.yaml#L20), we have 6 companies with contributions: Google, Red Hat, Polar Signals, Huawei, Salesforce, and ByteDance. The vast (80%) majority of our contributions from members in the past quarter are from Google and Red Hat. + * In [only sig-instrumentation-owned repositories](https://k8s.devstats.cncf.io/d/66/developer-activity-counts-by-companies?orgId=1&var-period_name=Last%20quarter&var-metric=contributions&var-repogroup_name=SIG%20Instrumentation&var-country_name=All&var-companies=All), there are 18 contributors with >10 contributions in the last quarter, from 14 different companies. + +## Current initiatives and project health + +* What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? Currently underway? What are some of the longer tail projects that your group is working on? + * [Structured Logging](https://github.com/kubernetes/enhancements/issues/1602) + * [Tracing](https://github.com/kubernetes/enhancements/issues/647) + * [Reducing metrics exposed by the kubelet](https://github.com/kubernetes/kubernetes/issues/68522?notification_referrer_id=MDE4Ok5vdGlmaWNhdGlvblRocmVhZDM3ODU4MzI4NTo0NzA2MTMx¬ifications_query=is%3Asaved#issuecomment-715462010) +* Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha? + * [Structured logging Alpha in 1.19](https://github.com/kubernetes/enhancements/issues/1602) + * Flag to enable structured logs: --logging-format=json + * For beta: perf tests, continued migration, verify decisions through one complete component migrated + * [Defend Against Logging Secrets via Static Analysis: Alpha in 1.20](https://github.com/kubernetes/enhancements/issues/1933) + * Test static analysis against sampled PRs using prow + * [Pod Resource Metrics Alpha in 1.20](https://github.com/kubernetes/enhancements/issues/1748) + * Pod Resource Metrics representing the view of the scheduler + * [Log sanitization Alpha 1.20](https://github.com/kubernetes/enhancements/issues/1753) + * Allow filtering out known sensitive data via flag --logging-sanitization + * [kube-state-metrics](https://github.com/kubernetes/kube-state-metrics/) is on its way to a new major breaking v2.0.0 release, with v2.0.0-rc.0 being released recently. + * custom-metrics-apiserver is shepherding a new initiative to support multiple custom and external metrics servers. [kubernetes-sigs/custom-metrics-apiserver#70](https://github.com/kubernetes-sigs/custom-metrics-apiserver/issues/70) + * prometheus-adapter recently joined the kubernetes-sigs organization and is still being integrated. The next important step for the project is its complete overhaul to improve its scability and make its configuration [more user friendly](https://github.com/s-urbaniak/prometheus-adapter/blob/master/design.md). + * Next: + * Promote *above* + * [APIServer tracing](https://github.com/kubernetes/enhancements/issues/647) + * [Dynamic cardinality enforcement](https://github.com/kubernetes/enhancements/issues/2305) + * [Metrics stability GA](https://github.com/kubernetes/enhancements/issues/1209) +* What areas and/or subprojects does the group need the most help with? + * Structured Logging + * [Promq](https://github.com/kubernetes-sigs/instrumentation-tools/tree/master/promq) +* What's the average open days of a PR and Issue in your group? / what metrics does your group care about and/or measure? + * [devstats: time to approve and merge](https://k8s.devstats.cncf.io/d/44/pr-time-to-approve-and-merge?orgId=1&from=1577865600000&to=1609488000000&var-period=m&var-repogroup_name=SIG%20Instrumentation&var-apichange=All&var-size_name=All&var-kind_name=All) \ +Varies from month to month, median time to merge is ~15 hours. 85th percentile is 1-2 weeks. \ +However, we don’t guarantee PRs will be merged, so the time to merge isn’t very meaningful. As well, this data only covers SIG repos and not work covered in kubernetes/kubernetes. As a SIG, we ensure PRs are triaged and reviewed through the bi-weekly triage meeting in all org:kubernetes components. kubernetes-sigs components are triaged by their respective owners. diff --git a/sig-instrumentation/annual-report-2021.md b/sig-instrumentation/annual-report-2021.md deleted file mode 100644 index 98332ff4..00000000 --- a/sig-instrumentation/annual-report-2021.md +++ /dev/null @@ -1,77 +0,0 @@ -# SIG Instrumentation Annual Report 2021 - -This report reflects back on CY 2020 and was written in Feb-Mar. 2021. - -## Operational - -* How are you doing with operational tasks in [sig-governance.md](https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md)? - * Is your README accurate? have a CONTRIBUTING.md file? - * Yes. We do not require a separate CONTRIBUTING.md file. - * All subprojects correctly mapped and listed in [sigs.yaml](https://github.com/kubernetes/community/blob/master/sig-list.md)? - * Yes. - * What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? Are you keeping recordings up to date/trends in community members watching recordings? - * We have lively biweekly regular meetings and biweekly triage sessions. Our recordings are relatively up to date and we receive requests for them so we believe they are being watched. Our community archives are all up to date. -* How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being retired? Are OWNERS files up to date in these areas? - * We request these in SIG meetings and asynchronously for KubeCon and other community updates. - * See above for OWNERS updates. -* Same question as above but for working groups. - * N/A -* When was your last monthly community-wide update? (provide link to deck and/or recording) - * Oct. 2020 [https://groups.google.com/g/kubernetes-dev/c/x1xr7bSuzv8/m/Oz49ZJgRBgAJ](https://groups.google.com/g/kubernetes-dev/c/x1xr7bSuzv8/m/Oz49ZJgRBgAJ) - -## Membership - -* Are all listed SIG leaders (chairs, tech leads, and subproject owners) active? - * [https://k8s.devstats.cncf.io/d/13/developer-activity-counts-by-repository-group?orgId=1&var-period_name=Last%20quarter&var-metric=contributions&var-repogroup_name=All&var-country_name=All](https://k8s.devstats.cncf.io/d/13/developer-activity-counts-by-repository-group?orgId=1&var-period_name=Last%20quarter&var-metric=contributions&var-repogroup_name=All&var-country_name=All) - * All active in last quarter -* How do you measure membership? By mailing list members, OWNERs, or something else? - * [https://github.com/kubernetes/org/blob/main/config/kubernetes/sig-instrumentation/teams.yaml](https://github.com/kubernetes/org/blob/main/config/kubernetes/sig-instrumentation/teams.yaml) - * We have three teams: leads (chairs/TLs), approvers, and members - * We annually remove inactive members (using the same criteria used for voting) and invite members to join that we have seen active in SIG meetings and activities -* How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it? - * Approver: we have limited areas that need our approval so we are ok on bandwidth - * Review: distributed around SIG via biweekly triage meetings -* Is there a healthy onboarding and growth path for contributors in your SIG? What are some activities that the group does to encourage this? What programs are you participating in to grow contributors throughout the contributor ladder? - * We would like to grow more contributors into SIG leadership roles for sustainability. - * We invite newbies to come to triage meetings to learn how to review and triage code. - * We go over all features as a SIG in our regular meetings. - * We do not have a lot of code to own for people to progress on our SIG ladder but we are open to adding new approvers for people that put in the work. -* What programs do you participate in for new contributors? - * Individual/1-1 mentoring - * We try to feature “good-first-issue”s and raise them on k-dev (e.g. structured logging) -* Does the group have contributors from multiple companies/affiliations? Can end users/companies contribute in some way that they currently are not? - * Yes: Google, Red Hat, and many first contributors across multiple companies - * Cross referencing [PRs by contributor + company](https://k8s.devstats.cncf.io/d/66/developer-activity-counts-by-companies?orgId=1&var-period_name=Last%20quarter&var-metric=contributions&var-repogroup_name=All&var-country_name=All&var-companies=All) with our [members](https://github.com/kubernetes/org/blob/main/config/kubernetes/sig-instrumentation/teams.yaml#L20), we have 6 companies with contributions: Google, Red Hat, Polar Signals, Huawei, Salesforce, and ByteDance. The vast (80%) majority of our contributions from members in the past quarter are from Google and Red Hat. - * In [only sig-instrumentation-owned repositories](https://k8s.devstats.cncf.io/d/66/developer-activity-counts-by-companies?orgId=1&var-period_name=Last%20quarter&var-metric=contributions&var-repogroup_name=SIG%20Instrumentation&var-country_name=All&var-companies=All), there are 18 contributors with >10 contributions in the last quarter, from 14 different companies. - -## Current initiatives and project health - -* What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? Currently underway? What are some of the longer tail projects that your group is working on? - * [Structured Logging](https://github.com/kubernetes/enhancements/issues/1602) - * [Tracing](https://github.com/kubernetes/enhancements/issues/647) - * [Reducing metrics exposed by the kubelet](https://github.com/kubernetes/kubernetes/issues/68522?notification_referrer_id=MDE4Ok5vdGlmaWNhdGlvblRocmVhZDM3ODU4MzI4NTo0NzA2MTMx¬ifications_query=is%3Asaved#issuecomment-715462010) -* Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha? - * [Structured logging Alpha in 1.19](https://github.com/kubernetes/enhancements/issues/1602) - * Flag to enable structured logs: --logging-format=json - * For beta: perf tests, continued migration, verify decisions through one complete component migrated - * [Defend Against Logging Secrets via Static Analysis: Alpha in 1.20](https://github.com/kubernetes/enhancements/issues/1933) - * Test static analysis against sampled PRs using prow - * [Pod Resource Metrics Alpha in 1.20](https://github.com/kubernetes/enhancements/issues/1748) - * Pod Resource Metrics representing the view of the scheduler - * [Log sanitization Alpha 1.20](https://github.com/kubernetes/enhancements/issues/1753) - * Allow filtering out known sensitive data via flag --logging-sanitization - * [kube-state-metrics](https://github.com/kubernetes/kube-state-metrics/) is on its way to a new major breaking v2.0.0 release, with v2.0.0-rc.0 being released recently. - * custom-metrics-apiserver is shepherding a new initiative to support multiple custom and external metrics servers. [kubernetes-sigs/custom-metrics-apiserver#70](https://github.com/kubernetes-sigs/custom-metrics-apiserver/issues/70) - * prometheus-adapter recently joined the kubernetes-sigs organization and is still being integrated. The next important step for the project is its complete overhaul to improve its scability and make its configuration [more user friendly](https://github.com/s-urbaniak/prometheus-adapter/blob/master/design.md). - * Next: - * Promote *above* - * [APIServer tracing](https://github.com/kubernetes/enhancements/issues/647) - * [Dynamic cardinality enforcement](https://github.com/kubernetes/enhancements/issues/2305) - * [Metrics stability GA](https://github.com/kubernetes/enhancements/issues/1209) -* What areas and/or subprojects does the group need the most help with? - * Structured Logging - * [Promq](https://github.com/kubernetes-sigs/instrumentation-tools/tree/master/promq) -* What's the average open days of a PR and Issue in your group? / what metrics does your group care about and/or measure? - * [devstats: time to approve and merge](https://k8s.devstats.cncf.io/d/44/pr-time-to-approve-and-merge?orgId=1&from=1577865600000&to=1609488000000&var-period=m&var-repogroup_name=SIG%20Instrumentation&var-apichange=All&var-size_name=All&var-kind_name=All) \ -Varies from month to month, median time to merge is ~15 hours. 85th percentile is 1-2 weeks. \ -However, we don’t guarantee PRs will be merged, so the time to merge isn’t very meaningful. As well, this data only covers SIG repos and not work covered in kubernetes/kubernetes. As a SIG, we ensure PRs are triaged and reviewed through the bi-weekly triage meeting in all org:kubernetes components. kubernetes-sigs components are triaged by their respective owners. diff --git a/sig-multicluster/annual-report-2020.md b/sig-multicluster/annual-report-2020.md new file mode 100644 index 00000000..792c4864 --- /dev/null +++ b/sig-multicluster/annual-report-2020.md @@ -0,0 +1,73 @@ +# 2020 SIG Multicluster Annual Report + +This report reflects back on CY 2020 and was written in March 2021. + +## Operational + +How are you doing with operational tasks in sig-governance.md? + +* Is your README accurate? have a CONTRIBUTING.md file? + * Yes, our README is accurate: https://github.com/kubernetes/community/blob/master/sig-multicluster/README.md + * Our CONTRIBUTING.md file is up to date: https://github.com/kubernetes/community/blob/master/sig-multicluster/CONTRIBUTING.md + +* All subprojects correctly mapped and listed in sigs.yaml? + * Yes + +* What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? Are you keeping recordings up to date/trends in community members watching recordings? + * SIG Multicluster holds regular weekly meetings which are normally well attended with ~10 participants. + * Due to the increase in activity in 2020, SIG meetings went from bi-weekly to weekly and almost always have a solid agenda. + * We attribute this to a shift in approach to focus on smaller, more clearly defined problems (Cluster ID, Multi-Cluster Services, Work) as well as calls for participation at KubeCon. + * Meetings are recorded and kept up to date. + * We'd love to see more participation, more contributors bringing their perspectives and use cases. Specifically: + * Help drive KEPs to GA, filling gaps in documentation. + * Example/test implementations of our defined APIs. + * What other problems are uncovered in the multi-cluster space now that e.g. connecting services across clusters is easier? +* How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being retired? Are OWNERS.md files up to date in these areas? + * Most group updates are at the weekly SIG meeting, big changes/ideas are shared with the list. +* Same question as above but for working groups. + * Working groups join SIG weekly to discuss major updates, we don’t have separate meetings. Most WG discussion is on slack. +* When was your last monthly community-wide update? (provide link to deck and/or recording) + * Our last community wide update was 2020-09-17: [SIG MC Community Update Slides](https://docs.google.com/presentation/d/1WKtsiSQn0sQ3IaSql4pGnH8Qt9ibBjHXMFBYZBhWeII). + +## Membership +* Are all listed SIG leaders (chairs, tech leads, and subproject owners) active? + * Both SIG chairs are active and attend most SIG meetings. + * Kubefed owners are active on slack and GitHub issues. +* How do you measure membership? By mailing list members, OWNERs, or something else? + * Mailing list members for general interest. Slack, weekly meeting attendance, and messages to the list for active engagement. +* How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it? + * The SIG tracks progress at weekly meetings and tends to closely watch and report on PRs and progress as a group so reviewer/approver bandwidth is not an issue. + * Kubefed tends to operate independently. Reviewer bandwidth has not been an issue, questions on PRs and Slack tend to get relatively quick response. +* Is there a healthy onboarding and growth path for contributors in your SIG? What are some activities that the group does to encourage this? What programs are you participating in to grow contributors throughout the contributor ladder? + * This SIG is in growth mode, and tries to create room for new ideas and projects driven by new and existing members alike. In 2020 we've seen two new initiatives kick off driven by relatively new members (Work API, Cluster ID). + * We are actively soliciting new ideas and looking for new people to drive them. + * We ask for new members to add their thoughts to docs and PRs, show of their prototypes, and present ideas and problems to the SIG at weekly meetings or via the list. +* What programs do you participate in for new contributors? + * At Kubecon we use the contributor track to give insight into what the SIG is working on and ask for new contributors. We've seen growth in weekly meeting attendance and new presenters as a result. + * When in-person Kubecons return we'll have Meet & Greets for new contributors (and everyone we didn't see in 2020!) +* Does the group have contributors from multiple companies/affiliations? Can end users/companies contribute in some way that they currently are not? + * Yes, our chairs are from two different companies. We have regular participation in SIG projects from those companies and several others. We'd like to see additional users and companies bring their use cases and contribute to solutions. + +## Current initiatives and project health +* What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? Currently underway? What are some of the longer tail projects that your group is working on? + * [Kubefed](http://sigs.k8s.io/kubefed) - long running subproject with active contribution. The big initiative for 2020 was to [kick off support for pull-based reconciliation](https://github.com/kubernetes-sigs/kubefed/blob/master/docs/keps/20200619-kubefed-pull-reconciliation.md). + * [Work API](https://docs.google.com/document/d/1cWcdB40pGg3KS1eSyb9Q6SIRvWVI8dEjFp9RI0Gk0vg) - [sigs.k8s.io/work-api](https://sigs.k8s.io/work-api) + * MCS API [KEP-1645](https://github.com/kubernetes/enhancements/tree/master/keps/sig-multicluster/1645-multi-cluster-services-api) - [sigs.k8s.io/mcs-api](https://sigs.k8s.io/mcs-api) + * Cluster ID [KEP-2149](https://github.com/kubernetes/enhancements/tree/master/keps/sig-multicluster/2149-clusterid) +* Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha? + * Kubefed: nearly Beta. Expected in Q2 2021. + * Work API: nascent, on the road to alpha. + * MCS API: nearly Beta. Expected in Q2 2021, following Cluster ID alpha. + * Cluster ID: nascent, on the road to alpha. Ready to implement in Q2 2021. +* What areas and/or subprojects does the group need the most help with? + * SIG MC needs help with all of the above - especially when it comes to use cases and validating our approaches for different environments and deployment models. +* What's the average open days of a PR and Issue in your group? / what metrics does your group care about and/or measure? + * According to recent [dev stats](https://k8s.devstats.cncf.io/d/44/pr-time-to-approve-and-merge?orgId=1&var-period=d7&var-repogroup_name=SIG%20Multicluster&var-apichange=All&var-size_name=All&var-kind_name=All) + * Open to LGTM: avg 2.94 day, max 7.96 week + * LGTM to approve: avg 3.91 hour, max 2.39 week + * Approve to merge: avg 1.52 day, max 7.72 week + * 85% Open to LGTM: avg 1.28 week, max 10.36 week + * 85% LGTM to approve: avg 17.38 hour, max 2.39 week + * 85% Approve to merge: avg 5.97 day, max 10.36 week + * A lot of our focus has been on KEPs, which tend to have longer review cycles. We hope these timelines will contract when we shift to implementation. + \ No newline at end of file diff --git a/sig-multicluster/annual-report-2021.md b/sig-multicluster/annual-report-2021.md deleted file mode 100644 index 5e0faa6d..00000000 --- a/sig-multicluster/annual-report-2021.md +++ /dev/null @@ -1,73 +0,0 @@ -# 2021 SIG Multicluster Annual Report - -This report reflects back on CY 2020 and was written in March 2021. - -## Operational - -How are you doing with operational tasks in sig-governance.md? - -* Is your README accurate? have a CONTRIBUTING.md file? - * Yes, our README is accurate: https://github.com/kubernetes/community/blob/master/sig-multicluster/README.md - * Our CONTRIBUTING.md file is up to date: https://github.com/kubernetes/community/blob/master/sig-multicluster/CONTRIBUTING.md - -* All subprojects correctly mapped and listed in sigs.yaml? - * Yes - -* What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? Are you keeping recordings up to date/trends in community members watching recordings? - * SIG Multicluster holds regular weekly meetings which are normally well attended with ~10 participants. - * Due to the increase in activity in 2020, SIG meetings went from bi-weekly to weekly and almost always have a solid agenda. - * We attribute this to a shift in approach to focus on smaller, more clearly defined problems (Cluster ID, Multi-Cluster Services, Work) as well as calls for participation at KubeCon. - * Meetings are recorded and kept up to date. - * We'd love to see more participation, more contributors bringing their perspectives and use cases. Specifically: - * Help drive KEPs to GA, filling gaps in documentation. - * Example/test implementations of our defined APIs. - * What other problems are uncovered in the multi-cluster space now that e.g. connecting services across clusters is easier? -* How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being retired? Are OWNERS.md files up to date in these areas? - * Most group updates are at the weekly SIG meeting, big changes/ideas are shared with the list. -* Same question as above but for working groups. - * Working groups join SIG weekly to discuss major updates, we don’t have separate meetings. Most WG discussion is on slack. -* When was your last monthly community-wide update? (provide link to deck and/or recording) - * Our last community wide update was 2020-09-17: [SIG MC Community Update Slides](https://docs.google.com/presentation/d/1WKtsiSQn0sQ3IaSql4pGnH8Qt9ibBjHXMFBYZBhWeII). - -## Membership -* Are all listed SIG leaders (chairs, tech leads, and subproject owners) active? - * Both SIG chairs are active and attend most SIG meetings. - * Kubefed owners are active on slack and GitHub issues. -* How do you measure membership? By mailing list members, OWNERs, or something else? - * Mailing list members for general interest. Slack, weekly meeting attendance, and messages to the list for active engagement. -* How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it? - * The SIG tracks progress at weekly meetings and tends to closely watch and report on PRs and progress as a group so reviewer/approver bandwidth is not an issue. - * Kubefed tends to operate independently. Reviewer bandwidth has not been an issue, questions on PRs and Slack tend to get relatively quick response. -* Is there a healthy onboarding and growth path for contributors in your SIG? What are some activities that the group does to encourage this? What programs are you participating in to grow contributors throughout the contributor ladder? - * This SIG is in growth mode, and tries to create room for new ideas and projects driven by new and existing members alike. In 2020 we've seen two new initiatives kick off driven by relatively new members (Work API, Cluster ID). - * We are actively soliciting new ideas and looking for new people to drive them. - * We ask for new members to add their thoughts to docs and PRs, show of their prototypes, and present ideas and problems to the SIG at weekly meetings or via the list. -* What programs do you participate in for new contributors? - * At Kubecon we use the contributor track to give insight into what the SIG is working on and ask for new contributors. We've seen growth in weekly meeting attendance and new presenters as a result. - * When in-person Kubecons return we'll have Meet & Greets for new contributors (and everyone we didn't see in 2020!) -* Does the group have contributors from multiple companies/affiliations? Can end users/companies contribute in some way that they currently are not? - * Yes, our chairs are from two different companies. We have regular participation in SIG projects from those companies and several others. We'd like to see additional users and companies bring their use cases and contribute to solutions. - -## Current initiatives and project health -* What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? Currently underway? What are some of the longer tail projects that your group is working on? - * [Kubefed](http://sigs.k8s.io/kubefed) - long running subproject with active contribution. The big initiative for 2020 was to [kick off support for pull-based reconciliation](https://github.com/kubernetes-sigs/kubefed/blob/master/docs/keps/20200619-kubefed-pull-reconciliation.md). - * [Work API](https://docs.google.com/document/d/1cWcdB40pGg3KS1eSyb9Q6SIRvWVI8dEjFp9RI0Gk0vg) - [sigs.k8s.io/work-api](https://sigs.k8s.io/work-api) - * MCS API [KEP-1645](https://github.com/kubernetes/enhancements/tree/master/keps/sig-multicluster/1645-multi-cluster-services-api) - [sigs.k8s.io/mcs-api](https://sigs.k8s.io/mcs-api) - * Cluster ID [KEP-2149](https://github.com/kubernetes/enhancements/tree/master/keps/sig-multicluster/2149-clusterid) -* Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha? - * Kubefed: nearly Beta. Expected in Q2 2021. - * Work API: nascent, on the road to alpha. - * MCS API: nearly Beta. Expected in Q2 2021, following Cluster ID alpha. - * Cluster ID: nascent, on the road to alpha. Ready to implement in Q2 2021. -* What areas and/or subprojects does the group need the most help with? - * SIG MC needs help with all of the above - especially when it comes to use cases and validating our approaches for different environments and deployment models. -* What's the average open days of a PR and Issue in your group? / what metrics does your group care about and/or measure? - * According to recent [dev stats](https://k8s.devstats.cncf.io/d/44/pr-time-to-approve-and-merge?orgId=1&var-period=d7&var-repogroup_name=SIG%20Multicluster&var-apichange=All&var-size_name=All&var-kind_name=All) - * Open to LGTM: avg 2.94 day, max 7.96 week - * LGTM to approve: avg 3.91 hour, max 2.39 week - * Approve to merge: avg 1.52 day, max 7.72 week - * 85% Open to LGTM: avg 1.28 week, max 10.36 week - * 85% LGTM to approve: avg 17.38 hour, max 2.39 week - * 85% Approve to merge: avg 5.97 day, max 10.36 week - * A lot of our focus has been on KEPs, which tend to have longer review cycles. We hope these timelines will contract when we shift to implementation. - \ No newline at end of file diff --git a/sig-node/annual-report-2020.md b/sig-node/annual-report-2020.md new file mode 100644 index 00000000..99693959 --- /dev/null +++ b/sig-node/annual-report-2020.md @@ -0,0 +1,72 @@ +# SIG Node Annual Report 2020 + +## Operational + +* How are you doing with operational tasks in +[sig-governance.md](https://git.k8s.io/community/committee-steering/governance/sig-governance.md)? + * Is your README accurate? have a CONTRIBUTING.md file? + * Yes, [README.md](https://github.com/kubernetes/community/blob/master/sig-node/README.md) is accurate + * Opened [issue](https://github.com/kubernetes/community/issues/5600) to track completion CONTRIBUTING.md + * All subprojects correctly mapped and listed in [sigs.yaml](https://git.k8s.io/community/sig-list.md)? + * [Yes](https://github.com/kubernetes/community/tree/master/sig-node#subprojects) + * What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? Are you keeping + recordings up to date/trends in community members watching recordings? + * The SIG operates two recurring meetings. The Regular SIG Meeting occurs weekly. It focuses on top-level trends for the SIG, and provides a forum to discuss enhancements, blocked PRs, and release plans. Each meeting has approximately 15-30 participants depending on the topic. The meetings are relatively active. The Chairs host the SIG meeting. A member of the SIG reports on velocity metrics, and tries to draw attention to overall trends. The agenda is open for members of the community to discuss an idea or enhancement. Discussion may ensue for each topic. SIG members that have participated in the SIG for an extended period will share historical context. Recordings are up-to-date. The Weekly CI meeting focuses on improving CI health and improving the number of SIG participants that have sufficient understanding of our test apparatus. Each meeting has ~7 participants, but participation may improve with new scheduled time. Each meeting focuses on supporting active triage and review of the project board. [Recordings are kept up to date with regular SIG meetings](https://www.youtube.com/playlist?list=PL69nYSiGNLP1wJPj5DYWXjiArF-MJ5fNG). +* How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being +retired? Are OWNERS.md files up to date in these areas? + * The regular SIG meetings provide a forum to discuss sub-projects closely tied to the Kubernetes release. This includes cri-api, cri-tools, kubelet, and node-api. A major focus in the SIG this year has been the graduation of existing features. Other sub-projects get less frequent updates as development velocity has slowed as the project reached sufficient maturity. +* Same question as above but for working groups. + * There is no regular interlock between working groups and the SIG. SIG members based on interest and/ or desire may attend particular working group meetings. The SIG did create a dedicated set of meetings to talk through particular areas like topology management for a limited period of time in order to provide room for discussion outside of the regular SIG meeting. Once consensus was reached, those meetings ceased. +* When was your last monthly community-wide update? (provide link to deck and/or recording) + * Last presentation was on April 16, 2020: + * [Slides](https://docs.google.com/document/d/1VQDIAB0OqiSjIHI8AWMvSdceWhnz56jNpZrLs6o7NJY/edit#heading=h.di6sf3cdf3yr) + +## Membership + +* Are all listed SIG leaders (chairs, tech leads, and subproject owners) active? + * For the SIG leads yes. + * For subproject owners, likely there are some inactive maintainers, but it’s up to the subproject to prune their OWNERs files. + * For 2021, the SIG will look to audit the set of sponsored sub-projects to ensure OWNERs files are updated. +* How do you measure membership? By mailing list members, OWNERs, or something else? + * Anyone can be considered a SIG member if they join the Zoom calls or general discussions regularly. +* How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it? + * The SIG identifies the set of items they wish to focus on each release. A primary engineer and approver is identified up-front. This provides a baseline understanding of responsibility and capacity going into the release. As we near release milestones, we measure where we are relative to our planned goals and ensure attention is redirected where appropriate. + * The SIG suffered from atrophy in CI health and awareness. Members of the SIG have developed a dedicated CI group to focus on health and train up new community members to assist. The group started meeting in May 2020 with ~30 individuals volunteered to assist. The group has created a large amount of learning materials, improved the CI health, and instituted project boards and triage processes. The sub-group meets each week with ~7 regular attendees as the CI health has stabilized. + * The SIG has elevated 3 members to approver status for the kubelet sub-project in the past year. It has shifted 2 members to emeritus status. The SIG has members who have expressed interest and desire to grow their scope in particular parts, and we try to encourage that over a set of releases by focusing on particular sub-components. We anticipate growing more approvers over the calendar year. +* Is there a healthy onboarding and growth path for contributors in your SIG? +What are some activities that the group does to encourage this? What programs are you participating in to grow contributors +throughout the contributor ladder? + * The SIG identifies the set of items that we would like to tackle each release and clearly identifies the primary engineering owner and primary approver. We try to pair new engineers with senior approvers to grow scope and comfort. In the CI health meetings, we have established a project board to try and provide directional guidance on where and how to best contribute. +* What programs do you participate in for new contributors? + * KubeCon updates with “how to get involved”, beginning at KubeCon EU 2021 + * Improving documentation and process so new individuals can join, see e.g. [Node Project Board](https://github.com/orgs/kubernetes/projects/49), [Node PR Triage Guidelines](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/triage.md) + * Mentoring group for underrepresented individuals to become reviewers, first cohort (July-Dec. 2020) run by @dims and second cohort (Jan-Mar. 2021) run by @ehashman + * Next cohort leader/participants TBD +* Does the group have contributors from multiple companies/affiliations? Can end users/companies contribute in some way that +they currently are not? + * The group has contributors from multiple companies/affiliations. + * [39 companies made 1+](https://k8s.devstats.cncf.io/d/8/company-statistics-by-repository-group?orgId=1&var-period=y&var-metric=contributions&var-repogroup_name=SIG%20Node&var-companies=All) contributions over the last year (70 if all activity is counted). + * Deprecating of dockershim is a big project that will require many end user to make a step to migrate and some companies who are not active on SIG Node, namely monitoring vendors, to help end users with this migration. + +## Current initiatives and project health + +* [x] Please include links to KEPs and other supporting information that will be beneficial to multiple types of community members. +* What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? Currently underway? +What are some of the longer tail projects that your group is working on? + * Better tracking of [PRs setup](https://github.com/orgs/kubernetes/projects/49) and [Node PR Triage Guide](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/triage.md) by @ehashaman + * cgroups v2 + * [Graduating features](https://docs.google.com/document/d/1U10J0WwgWXkdYrqWGGvO8iH2HKeerQAlygnqgDgWv4E/edit#) + * Topology manager / device alignment +* Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha? + * The enumerated links list graduated KEPs for each of the related releases. + * 1.18: [GA-ed KEPs](https://github.com/kubernetes/enhancements/issues?q=is%3Aissue+milestone%3Av1.18+label%3Asig%2Fnode) + * 1.19: [GA-ed KEPs](https://github.com/kubernetes/enhancements/issues?q=is%3Aissue+milestone%3Av1.19+label%3Asig%2Fnode+) + * 1.20: [GA-ed KEPs](https://github.com/kubernetes/enhancements/issues?q=is%3Aissue+milestone%3Av1.20+label%3Asig%2Fnode+) +* What areas and/or subprojects does the group need the most help with? + * The SIG could always use more help in sustaining CI. +* What's the average open days of a PR and Issue in your group? / what metrics does your group care about and/or measure? + * Weekly sig meeting starts with an overview of how PRs were opened/reviewed/approved. + * The reporting is generally applicable to other SIGs and is based on following [template](https://docs.google.com/document/d/1JOXKBDgXmQzz8YQSYa7XYcfVteM79iMtvId1aQXC1e8/edit) + * The goal is to keep the reviews going so the numbers don’t spin out of control. It also provides an overview of the week + as the scope of the SIG is large and it may be hard to keep up with all changes. + * [DevStats report](https://k8s.devstats.cncf.io/d/44/pr-time-to-approve-and-merge?orgId=1&var-period=y&var-repogroup_name=SIG%20Node&var-apichange=All&var-size_name=All&var-kind_name=All) \ No newline at end of file diff --git a/sig-node/annual-report-2021.md b/sig-node/annual-report-2021.md deleted file mode 100644 index 941a3ab1..00000000 --- a/sig-node/annual-report-2021.md +++ /dev/null @@ -1,72 +0,0 @@ -# SIG Node Annual Report 2021 - -## Operational - -* How are you doing with operational tasks in -[sig-governance.md](https://git.k8s.io/community/committee-steering/governance/sig-governance.md)? - * Is your README accurate? have a CONTRIBUTING.md file? - * Yes, [README.md](https://github.com/kubernetes/community/blob/master/sig-node/README.md) is accurate - * Opened [issue](https://github.com/kubernetes/community/issues/5600) to track completion CONTRIBUTING.md - * All subprojects correctly mapped and listed in [sigs.yaml](https://git.k8s.io/community/sig-list.md)? - * [Yes](https://github.com/kubernetes/community/tree/master/sig-node#subprojects) - * What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? Are you keeping - recordings up to date/trends in community members watching recordings? - * The SIG operates two recurring meetings. The Regular SIG Meeting occurs weekly. It focuses on top-level trends for the SIG, and provides a forum to discuss enhancements, blocked PRs, and release plans. Each meeting has approximately 15-30 participants depending on the topic. The meetings are relatively active. The Chairs host the SIG meeting. A member of the SIG reports on velocity metrics, and tries to draw attention to overall trends. The agenda is open for members of the community to discuss an idea or enhancement. Discussion may ensue for each topic. SIG members that have participated in the SIG for an extended period will share historical context. Recordings are up-to-date. The Weekly CI meeting focuses on improving CI health and improving the number of SIG participants that have sufficient understanding of our test apparatus. Each meeting has ~7 participants, but participation may improve with new scheduled time. Each meeting focuses on supporting active triage and review of the project board. [Recordings are kept up to date with regular SIG meetings](https://www.youtube.com/playlist?list=PL69nYSiGNLP1wJPj5DYWXjiArF-MJ5fNG). -* How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being -retired? Are OWNERS.md files up to date in these areas? - * The regular SIG meetings provide a forum to discuss sub-projects closely tied to the Kubernetes release. This includes cri-api, cri-tools, kubelet, and node-api. A major focus in the SIG this year has been the graduation of existing features. Other sub-projects get less frequent updates as development velocity has slowed as the project reached sufficient maturity. -* Same question as above but for working groups. - * There is no regular interlock between working groups and the SIG. SIG members based on interest and/ or desire may attend particular working group meetings. The SIG did create a dedicated set of meetings to talk through particular areas like topology management for a limited period of time in order to provide room for discussion outside of the regular SIG meeting. Once consensus was reached, those meetings ceased. -* When was your last monthly community-wide update? (provide link to deck and/or recording) - * Last presentation was on April 16, 2020: - * [Slides](https://docs.google.com/document/d/1VQDIAB0OqiSjIHI8AWMvSdceWhnz56jNpZrLs6o7NJY/edit#heading=h.di6sf3cdf3yr) - -## Membership - -* Are all listed SIG leaders (chairs, tech leads, and subproject owners) active? - * For the SIG leads yes. - * For subproject owners, likely there are some inactive maintainers, but it’s up to the subproject to prune their OWNERs files. - * For 2021, the SIG will look to audit the set of sponsored sub-projects to ensure OWNERs files are updated. -* How do you measure membership? By mailing list members, OWNERs, or something else? - * Anyone can be considered a SIG member if they join the Zoom calls or general discussions regularly. -* How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it? - * The SIG identifies the set of items they wish to focus on each release. A primary engineer and approver is identified up-front. This provides a baseline understanding of responsibility and capacity going into the release. As we near release milestones, we measure where we are relative to our planned goals and ensure attention is redirected where appropriate. - * The SIG suffered from atrophy in CI health and awareness. Members of the SIG have developed a dedicated CI group to focus on health and train up new community members to assist. The group started meeting in May 2020 with ~30 individuals volunteered to assist. The group has created a large amount of learning materials, improved the CI health, and instituted project boards and triage processes. The sub-group meets each week with ~7 regular attendees as the CI health has stabilized. - * The SIG has elevated 3 members to approver status for the kubelet sub-project in the past year. It has shifted 2 members to emeritus status. The SIG has members who have expressed interest and desire to grow their scope in particular parts, and we try to encourage that over a set of releases by focusing on particular sub-components. We anticipate growing more approvers over the calendar year. -* Is there a healthy onboarding and growth path for contributors in your SIG? -What are some activities that the group does to encourage this? What programs are you participating in to grow contributors -throughout the contributor ladder? - * The SIG identifies the set of items that we would like to tackle each release and clearly identifies the primary engineering owner and primary approver. We try to pair new engineers with senior approvers to grow scope and comfort. In the CI health meetings, we have established a project board to try and provide directional guidance on where and how to best contribute. -* What programs do you participate in for new contributors? - * KubeCon updates with “how to get involved”, beginning at KubeCon EU 2021 - * Improving documentation and process so new individuals can join, see e.g. [Node Project Board](https://github.com/orgs/kubernetes/projects/49), [Node PR Triage Guidelines](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/triage.md) - * Mentoring group for underrepresented individuals to become reviewers, first cohort (July-Dec. 2020) run by @dims and second cohort (Jan-Mar. 2021) run by @ehashman - * Next cohort leader/participants TBD -* Does the group have contributors from multiple companies/affiliations? Can end users/companies contribute in some way that -they currently are not? - * The group has contributors from multiple companies/affiliations. - * [39 companies made 1+](https://k8s.devstats.cncf.io/d/8/company-statistics-by-repository-group?orgId=1&var-period=y&var-metric=contributions&var-repogroup_name=SIG%20Node&var-companies=All) contributions over the last year (70 if all activity is counted). - * Deprecating of dockershim is a big project that will require many end user to make a step to migrate and some companies who are not active on SIG Node, namely monitoring vendors, to help end users with this migration. - -## Current initiatives and project health - -* [x] Please include links to KEPs and other supporting information that will be beneficial to multiple types of community members. -* What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? Currently underway? -What are some of the longer tail projects that your group is working on? - * Better tracking of [PRs setup](https://github.com/orgs/kubernetes/projects/49) and [Node PR Triage Guide](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/triage.md) by @ehashaman - * cgroups v2 - * [Graduating features](https://docs.google.com/document/d/1U10J0WwgWXkdYrqWGGvO8iH2HKeerQAlygnqgDgWv4E/edit#) - * Topology manager / device alignment -* Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha? - * The enumerated links list graduated KEPs for each of the related releases. - * 1.18: [GA-ed KEPs](https://github.com/kubernetes/enhancements/issues?q=is%3Aissue+milestone%3Av1.18+label%3Asig%2Fnode) - * 1.19: [GA-ed KEPs](https://github.com/kubernetes/enhancements/issues?q=is%3Aissue+milestone%3Av1.19+label%3Asig%2Fnode+) - * 1.20: [GA-ed KEPs](https://github.com/kubernetes/enhancements/issues?q=is%3Aissue+milestone%3Av1.20+label%3Asig%2Fnode+) -* What areas and/or subprojects does the group need the most help with? - * The SIG could always use more help in sustaining CI. -* What's the average open days of a PR and Issue in your group? / what metrics does your group care about and/or measure? - * Weekly sig meeting starts with an overview of how PRs were opened/reviewed/approved. - * The reporting is generally applicable to other SIGs and is based on following [template](https://docs.google.com/document/d/1JOXKBDgXmQzz8YQSYa7XYcfVteM79iMtvId1aQXC1e8/edit) - * The goal is to keep the reviews going so the numbers don’t spin out of control. It also provides an overview of the week - as the scope of the SIG is large and it may be hard to keep up with all changes. - * [DevStats report](https://k8s.devstats.cncf.io/d/44/pr-time-to-approve-and-merge?orgId=1&var-period=y&var-repogroup_name=SIG%20Node&var-apichange=All&var-size_name=All&var-kind_name=All) \ No newline at end of file diff --git a/sig-release/annual-report-2020.md b/sig-release/annual-report-2020.md new file mode 100644 index 00000000..0d7024ac --- /dev/null +++ b/sig-release/annual-report-2020.md @@ -0,0 +1,99 @@ +# Kubernetes SIG Release Community Group Annual Reports 2020 + +This report reflects back on CY 2020 and was written in April 2021. + +## Operational + +- How are you doing with operational tasks in [SIG]-governance.md? + - Is your README accurate? have a CONTRIBUTING.md file? + - The README is up to date and accurate, we do not have a CONTRIBUTING.md + file. + - All subprojects correctly mapped and listed in sigs.yaml? + - Yes + - What’s your meeting culture? Large/small, active/quiet, learnings? Meeting + notes up to date? Are you keeping recordings up to date/trends in community + members watching recordings? + - We have weekly zoom meetings with a duration of 45min: one for the overall + SIG and one for the Release Engineering subproject. Both meetings have ~20 + people, where sometimes new contributors or members of other SIGs join as + well. + - We refined the meeting structure to have a fixed 20 minute block to walk + our project boards. + - There is a timebox of 20minutes for informal status updates, too. + - The last 5 minutes are free for open discussion. + - Meeting notes are up to date and all meetings are recorded. +- How does the group get updates, reports, or feedback from subprojects? Are + there any springing up or being retired? Are OWNERS.md files up to date in + these areas? + - The SIG Release meeting serves updates for the release cycle as well as the + Engineering subproject. + - The release Engineering meeting give more in-depth details about the + technical topics within the SIG. + - We have an additional agreement how to work together in terms of [Release + Engineering](https://github.com/kubernetes/sig-release/tree/master/release-engineering#release-engineering) +- Same question as above but for working groups. + - We do not have any working groups within the SIG. +- When was your last public community-wide update? (provide link to deck and/or + recording) + - KubeCon NA 2019: https://www.youtube.com/watch?v=sQuxWeVlrJQ + +#### Membership + +- Are all listed SIG leaders (chairs, tech leads, and subproject owners) active? + - Yes +- How do you measure membership? By mailing list members, OWNERs, or something + else? + - Those that are contributing and actively engaged with the meetings. +- How does the group measure reviewer and approver bandwidth? Do you need help + in any area now? What are you doing about it? + - We do not actively monitor reviewer/approver bandwidth in a formalized way. + We walk the project boards during our meetings and triage incoming issues + and PRs in dedicated sessions. We also have to do the cherry-pick reviews + for patches, which is done by the release managers in a continuous process. +- Is there a healthy onboarding and growth path for contributors in your SIG? + What are some activities that the group does to encourage this? What programs + are you participating in to grow contributors throughout the contributor ladder? + - We have the SIG Release Shadowing Program for new members to join the + release cycle. + - There is the opportunity to become a Release Manager (associate) within the + Release Engineering subproject, too. + - The SIG has Technical Lead and a Program Manager roles to further support + the SIG. + - We are actively applying the `good-first-issue` and `help-wanted` labels to issues + and are closely mentoring new contributors who pick up these issues. +- What programs do you participate in for new contributors? + - The SIG Release Shadowing program +- Does the group have contributors from multiple companies/affiliations? Can end + users/companies contribute in some way that they currently are not? + - Yes, we have multiple avenues for contributing for both code and non-code + projects alike. + +#### Current initiatives and project health + +- What are initiatives that should be highlighted, lauded, shout outs, that + your group is proud of? Currently underway? What are some of the longer tail + projects that your group is working on? + - The introduced Program Manager role is our highlight to keep the SIG making + continuously progress + - Dedicated issue triage session + - Building a North Star Vision Roadmap for long term planning + - Continuously enhancing the release cycle timings and tooling around it +- Year to date KEP work: + - [KEP-2572: Release Cadence][kep] +- What initiatives are you working on that aren't being tracked in KEPs? + - Formalize supported release platforms: + https://github.com/kubernetes/sig-release/issues/1337 + - Implement a Bill of Materials (BOM) for release artifacts + https://github.com/kubernetes/release/issues/1837 + - Enhance Kubernetes binary artifact management + - Simplify CVE process for release management (Secure) + https://github.com/kubernetes/sig-release/issues/896 + https://github.com/kubernetes/release/issues/1354 +- What areas and/or subprojects does the group need the most help with? + - Nothing to mention right now, we're always looking for help in Release + Engineering related topics. Beside that we have to assemble a Release Team + each cycle which follows its own process. +- What metrics/community health stats does your group care about and/or measure? + - We mainly stick to our project boards + +[kep]: https://github.com/kubernetes/enhancements/issues/2572 diff --git a/sig-release/annual-report-2021.md b/sig-release/annual-report-2021.md deleted file mode 100644 index 3b303fd4..00000000 --- a/sig-release/annual-report-2021.md +++ /dev/null @@ -1,99 +0,0 @@ -# Kubernetes SIG Release Community Group Annual Reports 2021 - -This report reflects back on CY 2020 and was written in April 2021. - -## Operational - -- How are you doing with operational tasks in [SIG]-governance.md? - - Is your README accurate? have a CONTRIBUTING.md file? - - The README is up to date and accurate, we do not have a CONTRIBUTING.md - file. - - All subprojects correctly mapped and listed in sigs.yaml? - - Yes - - What’s your meeting culture? Large/small, active/quiet, learnings? Meeting - notes up to date? Are you keeping recordings up to date/trends in community - members watching recordings? - - We have weekly zoom meetings with a duration of 45min: one for the overall - SIG and one for the Release Engineering subproject. Both meetings have ~20 - people, where sometimes new contributors or members of other SIGs join as - well. - - We refined the meeting structure to have a fixed 20 minute block to walk - our project boards. - - There is a timebox of 20minutes for informal status updates, too. - - The last 5 minutes are free for open discussion. - - Meeting notes are up to date and all meetings are recorded. -- How does the group get updates, reports, or feedback from subprojects? Are - there any springing up or being retired? Are OWNERS.md files up to date in - these areas? - - The SIG Release meeting serves updates for the release cycle as well as the - Engineering subproject. - - The release Engineering meeting give more in-depth details about the - technical topics within the SIG. - - We have an additional agreement how to work together in terms of [Release - Engineering](https://github.com/kubernetes/sig-release/tree/master/release-engineering#release-engineering) -- Same question as above but for working groups. - - We do not have any working groups within the SIG. -- When was your last public community-wide update? (provide link to deck and/or - recording) - - KubeCon NA 2019: https://www.youtube.com/watch?v=sQuxWeVlrJQ - -#### Membership - -- Are all listed SIG leaders (chairs, tech leads, and subproject owners) active? - - Yes -- How do you measure membership? By mailing list members, OWNERs, or something - else? - - Those that are contributing and actively engaged with the meetings. -- How does the group measure reviewer and approver bandwidth? Do you need help - in any area now? What are you doing about it? - - We do not actively monitor reviewer/approver bandwidth in a formalized way. - We walk the project boards during our meetings and triage incoming issues - and PRs in dedicated sessions. We also have to do the cherry-pick reviews - for patches, which is done by the release managers in a continuous process. -- Is there a healthy onboarding and growth path for contributors in your SIG? - What are some activities that the group does to encourage this? What programs - are you participating in to grow contributors throughout the contributor ladder? - - We have the SIG Release Shadowing Program for new members to join the - release cycle. - - There is the opportunity to become a Release Manager (associate) within the - Release Engineering subproject, too. - - The SIG has Technical Lead and a Program Manager roles to further support - the SIG. - - We are actively applying the `good-first-issue` and `help-wanted` labels to issues - and are closely mentoring new contributors who pick up these issues. -- What programs do you participate in for new contributors? - - The SIG Release Shadowing program -- Does the group have contributors from multiple companies/affiliations? Can end - users/companies contribute in some way that they currently are not? - - Yes, we have multiple avenues for contributing for both code and non-code - projects alike. - -#### Current initiatives and project health - -- What are initiatives that should be highlighted, lauded, shout outs, that - your group is proud of? Currently underway? What are some of the longer tail - projects that your group is working on? - - The introduced Program Manager role is our highlight to keep the SIG making - continuously progress - - Dedicated issue triage session - - Building a North Star Vision Roadmap for long term planning - - Continuously enhancing the release cycle timings and tooling around it -- Year to date KEP work: - - [KEP-2572: Release Cadence][kep] -- What initiatives are you working on that aren't being tracked in KEPs? - - Formalize supported release platforms: - https://github.com/kubernetes/sig-release/issues/1337 - - Implement a Bill of Materials (BOM) for release artifacts - https://github.com/kubernetes/release/issues/1837 - - Enhance Kubernetes binary artifact management - - Simplify CVE process for release management (Secure) - https://github.com/kubernetes/sig-release/issues/896 - https://github.com/kubernetes/release/issues/1354 -- What areas and/or subprojects does the group need the most help with? - - Nothing to mention right now, we're always looking for help in Release - Engineering related topics. Beside that we have to assemble a Release Team - each cycle which follows its own process. -- What metrics/community health stats does your group care about and/or measure? - - We mainly stick to our project boards - -[kep]: https://github.com/kubernetes/enhancements/issues/2572 diff --git a/sig-scalability/annual-report-2020.md b/sig-scalability/annual-report-2020.md new file mode 100644 index 00000000..092b20ee --- /dev/null +++ b/sig-scalability/annual-report-2020.md @@ -0,0 +1,119 @@ +# 2020 - SIG Scalability - Community Meeting Annual Report + +## Operational + +**How are you doing with operational tasks in sig-governance.md?** + +- **Is your README accurate? have a CONTRIBUTING.md file?** + +The README is accurate an up-to-date. +We don't have CONTRIBUTING.md and we're planning to update our +[developer documentation]. The [desired documentation] is mentioned +in the corresponding bug. + +[developer documentation]:https://github.com/kubernetes/community/tree/master/contributors/devel/sig-scalability +[desired documentation]:https://github.com/kubernetes/community/issues/5236#issuecomment-805607895 + +- **All subprojects correctly mapped and listed in sigs.yaml?** + +Yes. + +- **What’s your meeting culture? Large/small, active/quiet, learnings? +Meeting notes up to date? Are you keeping recordings up to date/trends +in community members watching recordings?** + +Quite small (usually 5-10 people) and generally quiet. We try to keep +meeting notes up to date. We're often lagging with updating recordings :( + +**How does the group get updates, reports, or feedback from subprojects? +Are there any springing up or being retired? Are OWNERS files up to date +in these areas?** + +There isn't any formal process. Updates are given during regular SIG meetings. + +**When was your last monthly community-wide update? (provide link to deck and/or recording)** + +- [Aug 20](https://docs.google.com/presentation/d/1-NOmFvwBqIGkZNQPe4R44hLvv0BuxbZy3DLleipKPHg/edit) +- [Jan 20](https://docs.google.com/presentation/d/1M81X3_SWwHrJaWdJsecJReOVNxjjWSBFBkhPKEV35hs/edit) + + +## Membership + +**Are all listed SIG leaders (chairs, tech leads, and subproject owners) active?** + +Yes. +We don't have a good process for keeping it up-to-date, rather triggerred by special events +(like this annual report). + +**How do you measure membership? By mailing list members, OWNERs, or something else?** + +Active participants in SIG meetings and/or sending/reviewing PRs. + +**How does the group measure reviewer and approver bandwidth? +Do you need help in any area now? What are you doing about it?** + +We're not doing a very good job here. It happens that some PRs are waiting for weeks. + +**Is there a healthy onboarding and growth path for contributors in your SIG? +What are some activities that the group does to encourage this? +What programs are you participating in to grow contributors throughout the contributor ladder?** + +We maintain a list of `help-wanted` issues and recommend particular ones for people +interested in contributing. + +**What programs do you participate in for new contributors?** + +None + +**Does the group have contributors from multiple companies/affiliations? +Can end users/companies contribute in some way that they currently are not?** + +Yes - there are people from multiple companies. +End users mostly come with questions, they rarely want to contribute. + + +## Current initiatives and project health + +**What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? +Currently underway? What are some of the longer tail projects that your group is working on?** + +The critical initiative in 2020 was speeding up scalability tests. We managed to reduce time +take by our 5k-node scalability tests from ~14h to less than 5h (~3x). + +We helped validating scalability and performance impact of multiple features across the whole year +(by consulting multiple contributors from across many different SIGs). + +We also visibly improved the testing framework to support other environments, tracking new +scalability/performance aspects (e.g. as OOM-killing) and extended portfolio of tested features. + +Given SIG-Scalability doesn't own non-test-related code, many efforts are driven under +the auspicies of other SIGs. This includes: +- [Efficient Watch Resumption] with sig-api-machinery (Alpha 1.20) +- [Immutable Secrets and ConfigMaps] with sig-storage (Alpha 1.18, Beta 1.19) + +[Efficient Watch Resumption]: https://github.com/kubernetes/enhancements/issues/1904 +[Immutable Secrets and ConfigMaps]: https://github.com/kubernetes/enhancements/issues/1412 + + +**Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha?** + +Given that SIG-Scalability doesn't really own code (other than test frameworks and tests +themselves), there aren't SIG-Scalability KEPs per-se. However, we initiate and drive many +KEPs that are officially owned by other SIGs though (and SIG-Scalability is listed as +participating SIG even though it's often doing most of the work - examples above). + +**What areas and/or subprojects does the group need the most help with?** + +Each subproject could benefit from additional hands. +However, the `Scalability Test Frameworks` and `Scalability and Performance tests and validation` +are the ones where we can grow contributors - the other require both very deep and wide +understanding of Kubernetes before making reasonable contributions. + +**What's the average open days of a PR and Issue in your group? / what metrics does your group care about and/or measure?** + +We weren't measuring it unfortunately. +What what be useful is out-of-the-box support for that across repositories +(in particular perf-tests repo is very interesting for us). + +[sig-governance.md]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md +[sigs.yaml]: https://github.com/kubernetes/community/blob/master/sig-list.md diff --git a/sig-scalability/annual-report-2021.md b/sig-scalability/annual-report-2021.md deleted file mode 100644 index 092b20ee..00000000 --- a/sig-scalability/annual-report-2021.md +++ /dev/null @@ -1,119 +0,0 @@ -# 2020 - SIG Scalability - Community Meeting Annual Report - -## Operational - -**How are you doing with operational tasks in sig-governance.md?** - -- **Is your README accurate? have a CONTRIBUTING.md file?** - -The README is accurate an up-to-date. -We don't have CONTRIBUTING.md and we're planning to update our -[developer documentation]. The [desired documentation] is mentioned -in the corresponding bug. - -[developer documentation]:https://github.com/kubernetes/community/tree/master/contributors/devel/sig-scalability -[desired documentation]:https://github.com/kubernetes/community/issues/5236#issuecomment-805607895 - -- **All subprojects correctly mapped and listed in sigs.yaml?** - -Yes. - -- **What’s your meeting culture? Large/small, active/quiet, learnings? -Meeting notes up to date? Are you keeping recordings up to date/trends -in community members watching recordings?** - -Quite small (usually 5-10 people) and generally quiet. We try to keep -meeting notes up to date. We're often lagging with updating recordings :( - -**How does the group get updates, reports, or feedback from subprojects? -Are there any springing up or being retired? Are OWNERS files up to date -in these areas?** - -There isn't any formal process. Updates are given during regular SIG meetings. - -**When was your last monthly community-wide update? (provide link to deck and/or recording)** - -- [Aug 20](https://docs.google.com/presentation/d/1-NOmFvwBqIGkZNQPe4R44hLvv0BuxbZy3DLleipKPHg/edit) -- [Jan 20](https://docs.google.com/presentation/d/1M81X3_SWwHrJaWdJsecJReOVNxjjWSBFBkhPKEV35hs/edit) - - -## Membership - -**Are all listed SIG leaders (chairs, tech leads, and subproject owners) active?** - -Yes. -We don't have a good process for keeping it up-to-date, rather triggerred by special events -(like this annual report). - -**How do you measure membership? By mailing list members, OWNERs, or something else?** - -Active participants in SIG meetings and/or sending/reviewing PRs. - -**How does the group measure reviewer and approver bandwidth? -Do you need help in any area now? What are you doing about it?** - -We're not doing a very good job here. It happens that some PRs are waiting for weeks. - -**Is there a healthy onboarding and growth path for contributors in your SIG? -What are some activities that the group does to encourage this? -What programs are you participating in to grow contributors throughout the contributor ladder?** - -We maintain a list of `help-wanted` issues and recommend particular ones for people -interested in contributing. - -**What programs do you participate in for new contributors?** - -None - -**Does the group have contributors from multiple companies/affiliations? -Can end users/companies contribute in some way that they currently are not?** - -Yes - there are people from multiple companies. -End users mostly come with questions, they rarely want to contribute. - - -## Current initiatives and project health - -**What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? -Currently underway? What are some of the longer tail projects that your group is working on?** - -The critical initiative in 2020 was speeding up scalability tests. We managed to reduce time -take by our 5k-node scalability tests from ~14h to less than 5h (~3x). - -We helped validating scalability and performance impact of multiple features across the whole year -(by consulting multiple contributors from across many different SIGs). - -We also visibly improved the testing framework to support other environments, tracking new -scalability/performance aspects (e.g. as OOM-killing) and extended portfolio of tested features. - -Given SIG-Scalability doesn't own non-test-related code, many efforts are driven under -the auspicies of other SIGs. This includes: -- [Efficient Watch Resumption] with sig-api-machinery (Alpha 1.20) -- [Immutable Secrets and ConfigMaps] with sig-storage (Alpha 1.18, Beta 1.19) - -[Efficient Watch Resumption]: https://github.com/kubernetes/enhancements/issues/1904 -[Immutable Secrets and ConfigMaps]: https://github.com/kubernetes/enhancements/issues/1412 - - -**Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha?** - -Given that SIG-Scalability doesn't really own code (other than test frameworks and tests -themselves), there aren't SIG-Scalability KEPs per-se. However, we initiate and drive many -KEPs that are officially owned by other SIGs though (and SIG-Scalability is listed as -participating SIG even though it's often doing most of the work - examples above). - -**What areas and/or subprojects does the group need the most help with?** - -Each subproject could benefit from additional hands. -However, the `Scalability Test Frameworks` and `Scalability and Performance tests and validation` -are the ones where we can grow contributors - the other require both very deep and wide -understanding of Kubernetes before making reasonable contributions. - -**What's the average open days of a PR and Issue in your group? / what metrics does your group care about and/or measure?** - -We weren't measuring it unfortunately. -What what be useful is out-of-the-box support for that across repositories -(in particular perf-tests repo is very interesting for us). - -[sig-governance.md]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md -[sigs.yaml]: https://github.com/kubernetes/community/blob/master/sig-list.md diff --git a/sig-scheduling/annual-report-2020.md b/sig-scheduling/annual-report-2020.md new file mode 100644 index 00000000..540cecaa --- /dev/null +++ b/sig-scheduling/annual-report-2020.md @@ -0,0 +1,125 @@ +# 2020 SIG-Scheduling Annual Report + +## Operational + +**How are you doing with operational tasks in [sig-governance.md]?** + +- **Is your README accurate? have a CONTRIBUTING.md file?** + Yes. Developer-oriented guides are under [contributors/devel/sig-scheduling]. + +- **All subprojects correctly mapped and listed in [sigs.yaml]?** + Yes. + +- **What's your meeting culture? Large/small, active/quiet, learnings? +Meeting notes up to date? Are you keeping recordings up to date/trends +in community members watching recordings?** + Our meetings tends to be small and quiet. The agenda usually consists of items suggested + by users, and debatable items that need a consensus during issues/PR reviews. + The meeting notes and recordings are up to date. + +**How does the group get updates, reports, or feedback from subprojects? Are there any +springing up or being retired? Are OWNERS files up to date in these areas?** + +Owners from (active) subprojects introduce the latest development, and sometime demonstrate +cool features. +OWNER files in k/k are not that up to date. We may need a cleanup. + +**When was your last monthly community-wide update? (provide link to deck and/or recording)** + +Aug 20, 2020. [Slides] & [Recording]. + +[Slides]: https://docs.google.com/presentation/d/1H27SDMqkzq8zCRveWWtK5g9hCAomKbrzTTVZ5r4h6Xo/edit +[Recording]: https://www.youtube.com/watch?v=oDL3Kp5-9eM&feature=youtu.be + +## Membership + +**Are all listed SIG leaders (chairs, tech leads, and subproject owners) active?** + +Yes, except for inactive subprojects. + +**How do you measure membership? By mailing list members, OWNERs, or something else?** + +We don't have an official way of measuring membership, there is some churn in the number of active +members and so membership is hard to keep track of. + +**How does the group measure reviewer and approver bandwidth? Do you need help in any area now? + What are you doing about it?** + +PRs are usually directed to the reviewer most familiar with the code base the PR is modifying. +We don't quite measure bandwidth, but one way of doing that is by looking at pending PRs broken +by assignment. + +**Is there a healthy onboarding and growth path for contributors in your SIG? What are some +activities that the group does to encourage this? What programs are you participating in to +grow contributors throughout the contributor ladder?** + +There is no official onboarding process. One thing we try to do frequently is breaking up +larger features into smaller enough tasks for new members to contribute. + +**What programs do you participate in for new contributors?** + +Currently we don't. + +**Does the group have contributors from multiple companies/affiliations? Can end users/companies +contribute in some way that they currently are not?** + +Yes. + +## Current initiatives and project health + +**What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? + Currently underway? What are some of the longer tail projects that your group is working on?** + +- Initiatives: + - Focusing on turning the scheduler into a pluggable framework to allow developing new custom + features outside the main repo. + [k-sigs/scheduler-plugins] initiated this to build a scheduler plugin ecosystem. It has a wide + participation from different companies, by either direct contributions from Alibaba, Tencent, + Apple, etc., as well as adoption by companies like [OpenAI]. + - Improving scheduler performance. We're working on some items like optimizing internal queues, + tailored preemption logic, as well as exposing meaningful metrics to help define SLA/SLOs. +- Longer tail projects: + - Continuing to refactor the core code around the scheduling framework. + - Graduating the scheduler's ComponentConfig to GA. + +**Year to date KEP work review: What's now stable? Beta? Alpha? Road to alpha?** + +- Alpha + - [Prefer Nominated Node] + - [Node Resource Strategy] + - [Pod Affinity Namespace Selector] + - [Volume Capacity Priority] (co-owned by sig-storage) +- Beta + - [Default topology spread] (will graduate with CC) + - [Multi Scheduling Profiles] + - [Non-preempting priority class] + - [Component Config] + +**What areas and/or subprojects does the group need the most help with?** + +- **Docs improvement**: + - developer oriented docs to understand more details of scheduler internals, so that they can come + up with k8s-scheduler-native extensions to fit their business needs + - user or cluster-admin oriented docs to make the most of scheduler, like best practices and tips + that are not documented well +- **Standardize issue triage process**: + +**What's the average open days of a PR and Issue in your group? What metrics does your group care about and/or measure?** + +We haven't started leveraging devstat data or Github board to get a high-level picture of PR/Issue. + +[sig-governance.md]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md +[contributors/devel/sig-scheduling]: https://github.com/kubernetes/community/tree/master/contributors/devel/sig-scheduling +[sigs.yaml]: https://github.com/kubernetes/community/blob/master/sig-list.md +[k-sigs/scheduler-plugins]: https://github.com/kubernetes-sigs/scheduler-plugins + +[Prefer Nominated Node]: https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/1923-prefer-nominated-node +[Node Resource Strategy]: https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/2458-node-resource-score-strategy +[Pod Affinity Namespace Selector]: https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/2249-pod-affinity-namespace-selector +[Volume Capacity Priority]: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1845-prioritization-on-volume-capacity +[Default topology spread]: https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/1258-default-pod-topology-spread +[Multi Scheduling Profiles]: https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/1451-multi-scheduling-profiles +[Non-preempting priority class]: https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/902-non-preempting-priorityclass +[Component Config]: https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/785-scheduler-component-config-api + +[OpenAI]: https://openai.com/blog/scaling-kubernetes-to-7500-nodes/#gangscheduling diff --git a/sig-scheduling/annual-report-2021.md b/sig-scheduling/annual-report-2021.md deleted file mode 100644 index 540cecaa..00000000 --- a/sig-scheduling/annual-report-2021.md +++ /dev/null @@ -1,125 +0,0 @@ -# 2020 SIG-Scheduling Annual Report - -## Operational - -**How are you doing with operational tasks in [sig-governance.md]?** - -- **Is your README accurate? have a CONTRIBUTING.md file?** - Yes. Developer-oriented guides are under [contributors/devel/sig-scheduling]. - -- **All subprojects correctly mapped and listed in [sigs.yaml]?** - Yes. - -- **What's your meeting culture? Large/small, active/quiet, learnings? -Meeting notes up to date? Are you keeping recordings up to date/trends -in community members watching recordings?** - Our meetings tends to be small and quiet. The agenda usually consists of items suggested - by users, and debatable items that need a consensus during issues/PR reviews. - The meeting notes and recordings are up to date. - -**How does the group get updates, reports, or feedback from subprojects? Are there any -springing up or being retired? Are OWNERS files up to date in these areas?** - -Owners from (active) subprojects introduce the latest development, and sometime demonstrate -cool features. -OWNER files in k/k are not that up to date. We may need a cleanup. - -**When was your last monthly community-wide update? (provide link to deck and/or recording)** - -Aug 20, 2020. [Slides] & [Recording]. - -[Slides]: https://docs.google.com/presentation/d/1H27SDMqkzq8zCRveWWtK5g9hCAomKbrzTTVZ5r4h6Xo/edit -[Recording]: https://www.youtube.com/watch?v=oDL3Kp5-9eM&feature=youtu.be - -## Membership - -**Are all listed SIG leaders (chairs, tech leads, and subproject owners) active?** - -Yes, except for inactive subprojects. - -**How do you measure membership? By mailing list members, OWNERs, or something else?** - -We don't have an official way of measuring membership, there is some churn in the number of active -members and so membership is hard to keep track of. - -**How does the group measure reviewer and approver bandwidth? Do you need help in any area now? - What are you doing about it?** - -PRs are usually directed to the reviewer most familiar with the code base the PR is modifying. -We don't quite measure bandwidth, but one way of doing that is by looking at pending PRs broken -by assignment. - -**Is there a healthy onboarding and growth path for contributors in your SIG? What are some -activities that the group does to encourage this? What programs are you participating in to -grow contributors throughout the contributor ladder?** - -There is no official onboarding process. One thing we try to do frequently is breaking up -larger features into smaller enough tasks for new members to contribute. - -**What programs do you participate in for new contributors?** - -Currently we don't. - -**Does the group have contributors from multiple companies/affiliations? Can end users/companies -contribute in some way that they currently are not?** - -Yes. - -## Current initiatives and project health - -**What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? - Currently underway? What are some of the longer tail projects that your group is working on?** - -- Initiatives: - - Focusing on turning the scheduler into a pluggable framework to allow developing new custom - features outside the main repo. - [k-sigs/scheduler-plugins] initiated this to build a scheduler plugin ecosystem. It has a wide - participation from different companies, by either direct contributions from Alibaba, Tencent, - Apple, etc., as well as adoption by companies like [OpenAI]. - - Improving scheduler performance. We're working on some items like optimizing internal queues, - tailored preemption logic, as well as exposing meaningful metrics to help define SLA/SLOs. -- Longer tail projects: - - Continuing to refactor the core code around the scheduling framework. - - Graduating the scheduler's ComponentConfig to GA. - -**Year to date KEP work review: What's now stable? Beta? Alpha? Road to alpha?** - -- Alpha - - [Prefer Nominated Node] - - [Node Resource Strategy] - - [Pod Affinity Namespace Selector] - - [Volume Capacity Priority] (co-owned by sig-storage) -- Beta - - [Default topology spread] (will graduate with CC) - - [Multi Scheduling Profiles] - - [Non-preempting priority class] - - [Component Config] - -**What areas and/or subprojects does the group need the most help with?** - -- **Docs improvement**: - - developer oriented docs to understand more details of scheduler internals, so that they can come - up with k8s-scheduler-native extensions to fit their business needs - - user or cluster-admin oriented docs to make the most of scheduler, like best practices and tips - that are not documented well -- **Standardize issue triage process**: - -**What's the average open days of a PR and Issue in your group? What metrics does your group care about and/or measure?** - -We haven't started leveraging devstat data or Github board to get a high-level picture of PR/Issue. - -[sig-governance.md]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md -[contributors/devel/sig-scheduling]: https://github.com/kubernetes/community/tree/master/contributors/devel/sig-scheduling -[sigs.yaml]: https://github.com/kubernetes/community/blob/master/sig-list.md -[k-sigs/scheduler-plugins]: https://github.com/kubernetes-sigs/scheduler-plugins - -[Prefer Nominated Node]: https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/1923-prefer-nominated-node -[Node Resource Strategy]: https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/2458-node-resource-score-strategy -[Pod Affinity Namespace Selector]: https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/2249-pod-affinity-namespace-selector -[Volume Capacity Priority]: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1845-prioritization-on-volume-capacity -[Default topology spread]: https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/1258-default-pod-topology-spread -[Multi Scheduling Profiles]: https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/1451-multi-scheduling-profiles -[Non-preempting priority class]: https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/902-non-preempting-priorityclass -[Component Config]: https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/785-scheduler-component-config-api - -[OpenAI]: https://openai.com/blog/scaling-kubernetes-to-7500-nodes/#gangscheduling diff --git a/sig-security/annual-report-2020.md b/sig-security/annual-report-2020.md new file mode 100644 index 00000000..dccc7961 --- /dev/null +++ b/sig-security/annual-report-2020.md @@ -0,0 +1,81 @@ +# Kubernetes SIG Security 2020 Annual Report + +## Operational + +* **How are you doing with operational tasks in [sig-governance.md](https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md)?** + * **Is your README accurate? have a CONTRIBUTING.md file?** + * Our README is accurate. As of this report, we don’t yet have a CONTRIBUTING.md file. Through the process of building this report, we have figured out more about ourselves and our vision as a newer SIG, and we have come to realize we need one specific to our SIG, which highlights our differences and encourages new contributors more effectively. Accordingly, we will be writing one shortly. + * **All subprojects correctly mapped and listed in [sigs.yaml](https://github.com/kubernetes/community/blob/master/sig-list.md)?** + * Yes. As a horizontal SIG, we do not naturally have a large number of OWNERS files, but we have created some to ensure our subproject owners are easy to identify by viewing our README.md. + * **What’s your meeting culture? Large/small, active/quiet, learnings?** + * Our meetings are open, collaborative, and loosely planned. We actively ask for sharing to encourage fuller participation, and give time to foster community discussion. In every meeting we hear reports from our subprojects, review selected security-related issues and PRs together, and hear and discuss thoughts and ideas community members have brought to share. Much of what happens in any given meeting depends on who shows up and what they choose to bring. + * **Meeting notes up to date?** + * Yes. In keeping with the open, collaborative culture we foster, [we take notes](https://docs.google.com/document/d/1GgmmNYN88IZ2v2NBiO3gdU8Riomm0upge_XNVxEYXp0) collectively during the meetings, led by a volunteer note taker. We ask for a new volunteer note taker at the start of each meeting, which gives people an additional way to participate. + * **Are you keeping recordings up to date?** + * Yes. SIG chairs upload the recording videos to YouTube, typically within a few days of the meeting. + * **Trends in community members watching recordings?** + * [Recordings](https://www.youtube.com/playlist?list=PL69nYSiGNLP1mXOLAc9ti0oX8s_ookQCi) mostly serve as a historical record. There have been 18 SIG-related meetings between Jan 1 and April 8 2021, including the main SIG meeting and subproject meetings, which have an average of 2.94 views on YouTube. +* **How does the group get updates, reports, or feedback from subprojects?** + * Subproject owners or designees talk about it in the main SIG meeting as a standing agenda item. + * **Are there any springing up or being retired?** + * Because we are a newer SIG, there hasn’t been much opportunity for turnover. We have two established and active subprojects: security-docs and security-audit. A third and newer, security-tooling, is just starting to spring up. + * **Are OWNERS files up to date in these areas?** + * Yes. As a horizontal SIG that mostly works by interacting with and contributing to other SIGs’ code and projects, we don’t have much need for OWNERS files right now. We have directories for both of the more established subprojects to ensure they are recognized. +* **Same question as above but for working groups.** + * We do not currently have any working groups. +* **When was your last monthly community-wide update? (provide link to deck and/or recording)** + * Since our founding in October 2020, we haven’t given a monthly community-wide update yet. We have a maintainer track session coming up [at KubeCon EU 2021](https://kccnceu2021.sched.com/event/iE5u/). + +## Membership + +* **Are all listed SIG leaders (chairs, tech leads, and subproject owners) active?** + * Yes +* **How do you measure membership? By mailing list members, OWNERs, or something else?** + * We are interested in membership metrics for the purposes of gauging the health and activity of our community. This leads us to two types of measures: measures of reach and measures of collaboration. + * We measure reach using the number of members of our Slack channel and mailing list; these are potential future collaborators on SIG projects. As of April 8, 2021, there are 438 members of the main Slack channel and 131 members of the mailing list. + * We measure collaboration by noting who regularly contributes to our community activities. We take attendance at our meetings, which helps with this. The 7 main SIG meetings between January 14, 2021 and April 8, 2021 have had an average of 12.4 documented attendees. + * A definitive count of collaborating members across all media at any given moment is difficult to calculate, which we are comfortable with at this time. +* **How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it?** + * Our role in the Kubernetes project means that the majority of our reviewer bandwidth is used on triaging other SIGs’ PRs, KEPs, and Issues to bring them to our membership for comment. Note that this is a different concept of “reviewer” than is typical in a code-owning SIG. + * We measure our reviewer bandwidth by noting whether everything brought to SIG Security’s attention is getting addressed in a timely fashion, and the feelings of the reviewers about their workload. + * Much of this review is currently done by the SIG chairs, and it is starting to become a bottleneck. We are looking to improve our review bandwidth by bringing review of triaged issues to the regular SIG meetings for more open and inclusive participation. +* **Is there a healthy onboarding and growth path for contributors in your SIG? What are some activities that the group does to encourage this? What programs are you participating in to grow contributors throughout the contributor ladder?** + * We are onboarding and growing contributors continuously through our processes and culture. We actively practice behaviors of inclusion to help new and growing contributors feel more confident to participate. For example, we list appropriate pronouns in our meeting attendance list, and before changing subjects we pause to ask for additional comments. + * In addition to participating in SIG discussions, new contributors can also begin by assisting the subprojects with their tasks. Subproject members guide new contributors to where assistance is needed. + * Our open environment creates space for interested contributors to become leaders [by sharing their ideas and energy](https://twitter.com/PuDiJoglekar/status/1380205701994147845). If someone brings an idea that other members are excited about and want to help work on, [those members can organize a subproject together](https://twitter.com/coffeeartgirl/status/1331046904306622465), and we can help them grow. + * The chairs help grow emerging leaders by keeping in close contact with them and providing 1:1 mentorship, [encouragement](https://twitter.com/coffeeartgirl/status/1337078959020912642), and concrete help leveling up skills such as improving communication, leading more inclusive meetings, and presenting at conferences. +* **What programs do you participate in for new contributors?** + * Our broadly welcoming culture is a good opportunity for security-minded Kubernetes users who want to get involved in the upstream Kubernetes community. We plan to extend this further by participating in formal “new contributor” programs in the future. +* **Does the group have contributors from multiple companies/affiliations?** + * Yes + * **Can end users/companies contribute in some way that they currently are not?** + * End users are currently contributing at all levels. Our contributors represent both end user organizations and Kubernetes vendors. Both SIG Security co-chairs work at companies that are Kubernetes end users. + +## Current initiatives and project health + +* **What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? Currently underway? What are some of the longer tail projects that your group is working on?** + * We’re proud of the work that our security-docs subproject has started to create a Kubernetes hardening guide. They have collected contributions from across the Kubernetes community into a document outline, and now they’re writing it as a team. You may learn more about this effort in the Kubernetes SIG Security Docs Subproject [meeting notes](https://docs.google.com/document/d/11LZn7qWB0OzbpF8va_YYGQE4fuRARCGY9KL87hwBLBI). + * Our third-party security audit subproject is moving forward through the complexity of organizing an audit of one of the world’s largest open-source projects. The key challenges are the scale of our codebase and limited auditor experience with the Go language and cloud-native technologies. They are utilizing members’ existing relationships with audit firms, as well as building new ones, to find solutions to these challenges. + * PodSecurityPolicy was deprecated in the Kubernetes 1.21 release, and SIG Security worked closely with SIG Auth to figure out what comes next. We are delighted to have contributed to [KEP 2579](https://github.com/kubernetes/enhancements/issues/2579) by writing and reviewing proposals, adding our members’ voices to the design meetings, and [blogging about it for the broader Kubernetes community](https://kubernetes.io/blog/2021/04/06/podsecuritypolicy-deprecation-past-present-and-future/). We hope to make our close collaboration with SIG Auth a model for future cross-SIG efforts throughout Kubernetes. Thanks again to everyone who has been involved! +* **Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha?** + * We have accepted stewardship of KEPs [1753](https://github.com/kubernetes/enhancements/issues/1753) and [1933](https://github.com/kubernetes/enhancements/issues/1933) from SIG Instrumentation. Their owners and progress remain the same, and we look forward to helping them move toward graduation. + * KEP [1933](https://github.com/kubernetes/enhancements/issues/1933) - Defend against logging secrets via static analysis - [graduated](https://github.com/kubernetes/test-infra/pull/20836) to General Availability! As a SIG, we will continue to provide review and technical input for future static analysis rule updates. + * KEP [2568](https://github.com/kubernetes/enhancements/issues/2568) - Run control-plane as non-root in kubeadm - has been maturing steadily with help from the Kubernetes community. SIG Security has provided a forum to discuss it and feedback to advance it toward implementable status. + * KEP [1981](https://github.com/kubernetes/enhancements/issues/1981) - Support for Windows privileged containers - has matured toward alpha, including SIG Security member feedback. Nice work, team! +* **What areas and/or subprojects does the group need the most help with?** + * We always welcome help from anyone aligned with our vision of improving Kubernetes security by learning together, sharing our expertise, and encouraging cross-SIG collaboration. Ideally, we would like to eventually have participating members with crossover to every SIG, providing a natural conduit of ideas and forming a network of helpful hackers throughout Kubernetes. + * As a newer SIG with a broad mission, our most pressing needs right now are around outreach and expertise. + * Today, people can help broaden our outreach in a few concrete ways: + * Look out for one another, so we can be safer together! If you see a Kubernetes PR or Issue (or Enhancement, or whatever!) that looks like it may be security-relevant, you can tag sig/security to bring them to our attention and get SIG Security input. You can also bring them to our meetings as a topic for discussion! + * If you spot things happening in other SIGs that may be relevant, or if something that is relevant to security interests is happening in your own SIG, let us know! Post in #sig-security to get community attention on it, or DM the SIG Security chairs on Slack so we can help. + * We don’t always have to be involved; another way you can help is by reaching out directly to other SIGs whose work may be affected by or related to your own. We all benefit when we work together better, especially on security-related topics. + * Come to our meetings and get more involved! If you have friends who are interested in Kubernetes security, encourage them to come and bring their energy and ideas too. We’d love to see you and hear what you have to say! + * To bring additional expertise to the table and help balance the load for SIG Leads, we would like to grow new Leads in the future, and are determining how best to implement the Tech Lead role in a SIG like ours. We would like to grow one or two interested members into that new role, and will be looking for help with this bootstrapping process when that time comes. +* **What's the average open days of a PR and Issue in your group?** + * As a SIG who doesn’t own code in a project that encourages non-code contributions, we find the question of which PRs and issues belong to us to be difficult to answer, and would like to encourage further inclusivity of different kinds of contribution in questions on future reports. + * **What metrics does your group care about and/or measure?** + * The metrics we are most immediately interested in are community engagement metrics, as discussed above under “Membership”. + * As we grow and mature as a SIG, we seek to better understand how well we are achieving our overall goal of holistically improving Kubernetes security. To do so, we’d like to find metrics that help answer questions like these: + * Are the services that we offer to the project achieving their goals? + * Are there further services that we should be offering? + * As a newer SIG, we know what we care deeply about, and are working toward it. We haven’t entirely figured out how to measure it all yet, but we’ll get there. diff --git a/sig-security/annual-report-2021.md b/sig-security/annual-report-2021.md deleted file mode 100644 index 897d975b..00000000 --- a/sig-security/annual-report-2021.md +++ /dev/null @@ -1,81 +0,0 @@ -# Kubernetes SIG Security 2021 Annual Report - -## Operational - -* **How are you doing with operational tasks in [sig-governance.md](https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md)?** - * **Is your README accurate? have a CONTRIBUTING.md file?** - * Our README is accurate. As of this report, we don’t yet have a CONTRIBUTING.md file. Through the process of building this report, we have figured out more about ourselves and our vision as a newer SIG, and we have come to realize we need one specific to our SIG, which highlights our differences and encourages new contributors more effectively. Accordingly, we will be writing one shortly. - * **All subprojects correctly mapped and listed in [sigs.yaml](https://github.com/kubernetes/community/blob/master/sig-list.md)?** - * Yes. As a horizontal SIG, we do not naturally have a large number of OWNERS files, but we have created some to ensure our subproject owners are easy to identify by viewing our README.md. - * **What’s your meeting culture? Large/small, active/quiet, learnings?** - * Our meetings are open, collaborative, and loosely planned. We actively ask for sharing to encourage fuller participation, and give time to foster community discussion. In every meeting we hear reports from our subprojects, review selected security-related issues and PRs together, and hear and discuss thoughts and ideas community members have brought to share. Much of what happens in any given meeting depends on who shows up and what they choose to bring. - * **Meeting notes up to date?** - * Yes. In keeping with the open, collaborative culture we foster, [we take notes](https://docs.google.com/document/d/1GgmmNYN88IZ2v2NBiO3gdU8Riomm0upge_XNVxEYXp0) collectively during the meetings, led by a volunteer note taker. We ask for a new volunteer note taker at the start of each meeting, which gives people an additional way to participate. - * **Are you keeping recordings up to date?** - * Yes. SIG chairs upload the recording videos to YouTube, typically within a few days of the meeting. - * **Trends in community members watching recordings?** - * [Recordings](https://www.youtube.com/playlist?list=PL69nYSiGNLP1mXOLAc9ti0oX8s_ookQCi) mostly serve as a historical record. There have been 18 SIG-related meetings between Jan 1 and April 8 2021, including the main SIG meeting and subproject meetings, which have an average of 2.94 views on YouTube. -* **How does the group get updates, reports, or feedback from subprojects?** - * Subproject owners or designees talk about it in the main SIG meeting as a standing agenda item. - * **Are there any springing up or being retired?** - * Because we are a newer SIG, there hasn’t been much opportunity for turnover. We have two established and active subprojects: security-docs and security-audit. A third and newer, security-tooling, is just starting to spring up. - * **Are OWNERS files up to date in these areas?** - * Yes. As a horizontal SIG that mostly works by interacting with and contributing to other SIGs’ code and projects, we don’t have much need for OWNERS files right now. We have directories for both of the more established subprojects to ensure they are recognized. -* **Same question as above but for working groups.** - * We do not currently have any working groups. -* **When was your last monthly community-wide update? (provide link to deck and/or recording)** - * Since our founding in October 2020, we haven’t given a monthly community-wide update yet. We have a maintainer track session coming up [at KubeCon EU 2021](https://kccnceu2021.sched.com/event/iE5u/). - -## Membership - -* **Are all listed SIG leaders (chairs, tech leads, and subproject owners) active?** - * Yes -* **How do you measure membership? By mailing list members, OWNERs, or something else?** - * We are interested in membership metrics for the purposes of gauging the health and activity of our community. This leads us to two types of measures: measures of reach and measures of collaboration. - * We measure reach using the number of members of our Slack channel and mailing list; these are potential future collaborators on SIG projects. As of April 8, 2021, there are 438 members of the main Slack channel and 131 members of the mailing list. - * We measure collaboration by noting who regularly contributes to our community activities. We take attendance at our meetings, which helps with this. The 7 main SIG meetings between January 14, 2021 and April 8, 2021 have had an average of 12.4 documented attendees. - * A definitive count of collaborating members across all media at any given moment is difficult to calculate, which we are comfortable with at this time. -* **How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it?** - * Our role in the Kubernetes project means that the majority of our reviewer bandwidth is used on triaging other SIGs’ PRs, KEPs, and Issues to bring them to our membership for comment. Note that this is a different concept of “reviewer” than is typical in a code-owning SIG. - * We measure our reviewer bandwidth by noting whether everything brought to SIG Security’s attention is getting addressed in a timely fashion, and the feelings of the reviewers about their workload. - * Much of this review is currently done by the SIG chairs, and it is starting to become a bottleneck. We are looking to improve our review bandwidth by bringing review of triaged issues to the regular SIG meetings for more open and inclusive participation. -* **Is there a healthy onboarding and growth path for contributors in your SIG? What are some activities that the group does to encourage this? What programs are you participating in to grow contributors throughout the contributor ladder?** - * We are onboarding and growing contributors continuously through our processes and culture. We actively practice behaviors of inclusion to help new and growing contributors feel more confident to participate. For example, we list appropriate pronouns in our meeting attendance list, and before changing subjects we pause to ask for additional comments. - * In addition to participating in SIG discussions, new contributors can also begin by assisting the subprojects with their tasks. Subproject members guide new contributors to where assistance is needed. - * Our open environment creates space for interested contributors to become leaders [by sharing their ideas and energy](https://twitter.com/PuDiJoglekar/status/1380205701994147845). If someone brings an idea that other members are excited about and want to help work on, [those members can organize a subproject together](https://twitter.com/coffeeartgirl/status/1331046904306622465), and we can help them grow. - * The chairs help grow emerging leaders by keeping in close contact with them and providing 1:1 mentorship, [encouragement](https://twitter.com/coffeeartgirl/status/1337078959020912642), and concrete help leveling up skills such as improving communication, leading more inclusive meetings, and presenting at conferences. -* **What programs do you participate in for new contributors?** - * Our broadly welcoming culture is a good opportunity for security-minded Kubernetes users who want to get involved in the upstream Kubernetes community. We plan to extend this further by participating in formal “new contributor” programs in the future. -* **Does the group have contributors from multiple companies/affiliations?** - * Yes - * **Can end users/companies contribute in some way that they currently are not?** - * End users are currently contributing at all levels. Our contributors represent both end user organizations and Kubernetes vendors. Both SIG Security co-chairs work at companies that are Kubernetes end users. - -## Current initiatives and project health - -* **What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? Currently underway? What are some of the longer tail projects that your group is working on?** - * We’re proud of the work that our security-docs subproject has started to create a Kubernetes hardening guide. They have collected contributions from across the Kubernetes community into a document outline, and now they’re writing it as a team. You may learn more about this effort in the Kubernetes SIG Security Docs Subproject [meeting notes](https://docs.google.com/document/d/11LZn7qWB0OzbpF8va_YYGQE4fuRARCGY9KL87hwBLBI). - * Our third-party security audit subproject is moving forward through the complexity of organizing an audit of one of the world’s largest open-source projects. The key challenges are the scale of our codebase and limited auditor experience with the Go language and cloud-native technologies. They are utilizing members’ existing relationships with audit firms, as well as building new ones, to find solutions to these challenges. - * PodSecurityPolicy was deprecated in the Kubernetes 1.21 release, and SIG Security worked closely with SIG Auth to figure out what comes next. We are delighted to have contributed to [KEP 2579](https://github.com/kubernetes/enhancements/issues/2579) by writing and reviewing proposals, adding our members’ voices to the design meetings, and [blogging about it for the broader Kubernetes community](https://kubernetes.io/blog/2021/04/06/podsecuritypolicy-deprecation-past-present-and-future/). We hope to make our close collaboration with SIG Auth a model for future cross-SIG efforts throughout Kubernetes. Thanks again to everyone who has been involved! -* **Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha?** - * We have accepted stewardship of KEPs [1753](https://github.com/kubernetes/enhancements/issues/1753) and [1933](https://github.com/kubernetes/enhancements/issues/1933) from SIG Instrumentation. Their owners and progress remain the same, and we look forward to helping them move toward graduation. - * KEP [1933](https://github.com/kubernetes/enhancements/issues/1933) - Defend against logging secrets via static analysis - [graduated](https://github.com/kubernetes/test-infra/pull/20836) to General Availability! As a SIG, we will continue to provide review and technical input for future static analysis rule updates. - * KEP [2568](https://github.com/kubernetes/enhancements/issues/2568) - Run control-plane as non-root in kubeadm - has been maturing steadily with help from the Kubernetes community. SIG Security has provided a forum to discuss it and feedback to advance it toward implementable status. - * KEP [1981](https://github.com/kubernetes/enhancements/issues/1981) - Support for Windows privileged containers - has matured toward alpha, including SIG Security member feedback. Nice work, team! -* **What areas and/or subprojects does the group need the most help with?** - * We always welcome help from anyone aligned with our vision of improving Kubernetes security by learning together, sharing our expertise, and encouraging cross-SIG collaboration. Ideally, we would like to eventually have participating members with crossover to every SIG, providing a natural conduit of ideas and forming a network of helpful hackers throughout Kubernetes. - * As a newer SIG with a broad mission, our most pressing needs right now are around outreach and expertise. - * Today, people can help broaden our outreach in a few concrete ways: - * Look out for one another, so we can be safer together! If you see a Kubernetes PR or Issue (or Enhancement, or whatever!) that looks like it may be security-relevant, you can tag sig/security to bring them to our attention and get SIG Security input. You can also bring them to our meetings as a topic for discussion! - * If you spot things happening in other SIGs that may be relevant, or if something that is relevant to security interests is happening in your own SIG, let us know! Post in #sig-security to get community attention on it, or DM the SIG Security chairs on Slack so we can help. - * We don’t always have to be involved; another way you can help is by reaching out directly to other SIGs whose work may be affected by or related to your own. We all benefit when we work together better, especially on security-related topics. - * Come to our meetings and get more involved! If you have friends who are interested in Kubernetes security, encourage them to come and bring their energy and ideas too. We’d love to see you and hear what you have to say! - * To bring additional expertise to the table and help balance the load for SIG Leads, we would like to grow new Leads in the future, and are determining how best to implement the Tech Lead role in a SIG like ours. We would like to grow one or two interested members into that new role, and will be looking for help with this bootstrapping process when that time comes. -* **What's the average open days of a PR and Issue in your group?** - * As a SIG who doesn’t own code in a project that encourages non-code contributions, we find the question of which PRs and issues belong to us to be difficult to answer, and would like to encourage further inclusivity of different kinds of contribution in questions on future reports. - * **What metrics does your group care about and/or measure?** - * The metrics we are most immediately interested in are community engagement metrics, as discussed above under “Membership”. - * As we grow and mature as a SIG, we seek to better understand how well we are achieving our overall goal of holistically improving Kubernetes security. To do so, we’d like to find metrics that help answer questions like these: - * Are the services that we offer to the project achieving their goals? - * Are there further services that we should be offering? - * As a newer SIG, we know what we care deeply about, and are working toward it. We haven’t entirely figured out how to measure it all yet, but we’ll get there. diff --git a/sig-storage/annual-report-2020.md b/sig-storage/annual-report-2020.md new file mode 100644 index 00000000..9b059f1c --- /dev/null +++ b/sig-storage/annual-report-2020.md @@ -0,0 +1,166 @@ +# Kubernetes SIG Storage Community Group Annual Reports 2020 + +This report reflects back on CY 2020 and was written in Feb-Mar. 2021. + +## Operational + +* How are you doing with operational tasks in sig-governance.md? + * Is your README accurate? have a CONTRIBUTING.md file? + * Yes, our README is accurate: https://github.com/kubernetes/community/blob/master/sig-storage/README.md + * Our CONTRIBUTING.md file is up to date: https://github.com/kubernetes/community/blob/master/sig-storage/CONTRIBUTING.md + * We also have a section in the following doc for new contributors that is up to date: https://github.com/kubernetes/community/blob/master/contributors/devel/README.md#sig-storage + + * All subprojects correctly mapped and listed in sigs.yaml? + * Yes + + * What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? Are you keeping recordings up to date/trends in community members watching recordings? + * SIG-Storage has bi-weekly meetings where we do project tracking followed up discussions on PRs, issues if any. Meetings are fairly well attended. Meetings are recorded and meeting notes are up to date. +https://github.com/kubernetes/community/blob/master/sig-storage/README.md#meetings + * We also have sub-projects meetings such as CSI implementation meetings that happen twice a week and COSI weekly standup and weekly design meetings. There are also regular meetings for Data Protection WG, CSI migration, CSI windows, volume populator, etc. as well as one-off design meetings on specific topics/features. + * https://calendar.google.com/calendar/u/0/embed?src=vvvo48r6cprccii1lsava6p2uc@group.calendar.google.com + * We would love to see more contributors, new and existing, to join the meetings and participate in SIG projects. + + * How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being retired? Are OWNERS.md files up to date in these areas? + * Features worked by sub-projects are tracked by SIG-Storage and will be reported regularly in SIG-Storage bi-weekly meetings. SIG leads also participate in sub-projects meetings, i.e., meetings for CSI and COSI. +https://docs.google.com/spreadsheets/d/1t4z5DYKjX2ZDlkTpCnp18icRAQqOE85C1T1r2gqJVck/edit#gid=2027057294 + * There are also project repos that are deprecated. For example, https://github.com/kubernetes/external-storage is deprecated and moved to https://github.com/kubernetes-retired/external-storage. Some of the sub-projects in the original repo were moved out and became independent repos and are still managed by sig-storage with new maintainers. Some of the sub-projects were moved out because it is getting harder and harder to maintain such a big and complicated project. Moving them to independent repos allow some contributors to take new responsibilities and become maintainers of these projects. For example, the following 2 nfs projects were moved out of external-storage and became independent projects with new maintainers: + * https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner + * https://github.com/kubernetes-sigs/nfs-ganesha-server-and-external-provisioner + + * Same question as above but for working groups. + * Features worked by WGs are tracked by SIG-Storage and reported at SIG-Storage meetings, i.e., ContainerNotifier and CBT are worked on by Data Protection WG and are tracked in the SIG-Storage feature tracking sheet. +https://docs.google.com/spreadsheets/d/1t4z5DYKjX2ZDlkTpCnp18icRAQqOE85C1T1r2gqJVck/edit#gid=2027057294 + + * When was your last monthly community-wide update? (provide link to deck and/or recording) + * Our last monthly update was 10/15/2020. Here’s the deck: https://docs.google.com/presentation/d/1uzS6Q1OmttV-0hzlu_Eublx24nRmWiJQ__J65Sr3hIs/edit#slide=id.g401c104a3c_0_0 + +## Membership + + * Are all listed SIG leaders (chairs, tech leads, and subproject owners) active? + * Yes + + * How do you measure membership? By mailing list members, OWNERs, or something else? + * Mailing list members, participants of SIG meetings, and folks working on SIG-Storage projects. + + * How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it? + * At the SIG-Storage bi-weekly meetings, we track the progress of each feature the SIG is working on. Each feature has dev leads and reviewers assigned to it. If a developer/reviewer does not have time to do the design/development/reviews, we’ll try to find someone else who has the bandwidth. + * For features that are GA, we still continue to maintain and fix bugs and make enhancements. For example, dynamic provisioning has been a GA feature for quite a while now. We still fix bugs and continue to enhance it if needed. Another example is volume snapshot which just moved to GA in 1.20. We are still working on small enhancements, adding tests, fixing bugs, etc. The work is still being tracked in weekly standup meetings. + * We also have this new sub-project COSI which has been very active. It has a weekly standup meeting and a weekly design meeting. A few contributors have been actively working on design and development there. + + * Is there a healthy onboarding and growth path for contributors in your SIG? What are some activities that the group does to encourage this? What programs are you participating in to grow contributors throughout the contributor ladder? + * For each feature the SIG is working on, the SIG lead or dev lead will be looking for contributors by adding the “Help wanted” tag on an issue and/or asking for helpers in SIG-Storage bi-weekly meetings. This is a great opportunity for new contributors to step up to contribute and become members of kubernetes and eventually owners of a project. + * In the beginning of each kubernetes release, we have a planning meeting to go over all features targeted for that release. We encourage everyone to add features they want to work on in the planning spreadsheet. This is a good time for new contributors to learn our planning process, and volunteer to be involved in some of the feature development work. + + * What programs do you participate in for new contributors? + * At the Contributor Summit at KubeCon, we usually have a Meet & Greet for new contributors. + * At the bi-weekly SIG-Storage meetings, we also call out to any new contributors who are willing to help on some projects that we are looking for developers or reviewers. + + * Does the group have contributors from multiple companies/affiliations? Can end users/companies contribute in some way that they currently are not? + * Yes, we do have contributors from multiple companies/affiliations as shown here: https://k8s.devstats.cncf.io/d/8/company-statistics-by-repository-group?orgId=1&var-period=d7&var-metric=contributions&var-repogroup_name=SIG%20Storage&var-companies=All + * End users are welcome to open issues and fix bugs that they discovered. They are also welcome to contribute code just like other developers. Suggestions are welcome to improve in this area. Ping one of the sig leads on slack, send an email to the SIG-Storage mailing list, or attend one of the SIG-Storage meetings to provide suggestions. + +## Current initiatives and project health +[ ] Please include links to KEPs and other supporting information that will be beneficial to multiple types of community members. + +What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? Currently underway? What are some of the longer tail projects that your group is working on? +* Container Object Storage Interface + * Building on the success of Container Storage Interface (CSI) which focused on Block and File, k8s SIG Storage is looking to build a similar interface for object Storage. + * KEP: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1979-object-storage-support + * Status: POC in progress +* Generic ephemeral volumes + * Ephemeral volume types are created at pod creation time and deleted at pod termination time, like EmptyDir, SecretVolumes, ConfigMapVolumes. Third-parties would like to be able to create their own ephemeral volume types. Kubernetes permits creation of new ephemeral volume types with CSI, but that requires creating a custom CSI driver dedicated to the new ephemeral volume type. Generic ephemeral volumes will permit any existing persistent CSI Driver to be used as a ephemeral volume (so for example, users can have a new external volume provisioned and used like an EmptyDir, and deleted after pod termination like EmptyDir). + * KEP: https://github.com/kubernetes/enhancements/pull/1701 + * Status: Alpha in 1.19 +* CSI Support for Windows + * The new CSI Proxy for Windows enables CSI Drivers to work on Windows overcoming a Windows limitation that prevented containerized CSI Drivers. + * Blog: https://kubernetes.io/blog/2020/04/03/kubernetes-1-18-feature-windows-csi-support-alpha/ + * Status: Beta in 1.19 +* Volume snapshots GA: + * Volume Snapshot feature provides standardized Kubernetes APIs and CSI spec to support snapshot and restore functionality for CSI volume drivers. + * Blog: https://kubernetes.io/blog/2020/12/10/kubernetes-1.20-volume-snapshot-moves-to-ga/ + * KEP: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/177-volume-snapshot + * Status: GA in 1.20 + +Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha? +* Stable: + * Volume snapshots GA 1.20: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/177-volume-snapshot +https://kubernetes.io/blog/2020/12/10/kubernetes-1.20-volume-snapshot-moves-to-ga/ + * Raw block GA 1.18: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/351-raw-block-support + * CSI raw block GA 1.18: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/565-csi-block-support + * CSI Cloning GA 1.18: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/989-extend-datasource + * CSI Skip attach GA 1.18: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/770-csi-skip-attach + * CSI Pod info on mount GA 1.18 (CSIDriver): https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/603-csi-pod-info + +* Beta: + * CSI Windows beta 1.19 + * Immutable secrets and configmaps beta 1.19: https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/1412-immutable-secrets-and-configmaps + * Non-recursive volume ownership (fsgroup) beta 1.20: https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/695-skip-permission-change/kep.yaml + * CSIDriver policy for fsgroup beta 1.20 + * https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/1682-csi-driver-skip-permission/kep.yaml + * https://kubernetes.io/blog/2020/12/14/kubernetes-release-1.20-fsgroupchangepolicy-fsgrouppolicy/ + * CSI Migration beta 1.17: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/625-csi-migration + * Azure Disk and vSphere CSI migration beta in 1.19 + * OpenStack CSI migration beta in 1.18 + * GCE CSI migration beta 1.17 + * AWS CSI migration beta 1.17 + * Azure File alpha 1.15 + * CSI Volume expansion: beta in 1.16 + * https://github.com/kubernetes/enhancements/issues/556 + * https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/284-enable-volume-expansion + * CSI inline volume beta 1.16: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/596-csi-inline-volumes + +* Alpha: + * Volume populator alpha 1.18: https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/1495-generic-data-populators/kep.yaml + * Storage capacity tracking alpha 1.19: https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/1472-storage-capacity-tracking/kep.yaml + * Generic ephemeral volume alpha 1.19: https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/1698-generic-ephemeral-volumes/kep.yaml + * Volume health alpha 1.19: https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/1432-volume-health-monitor/kep.yaml + * Service account token alpha 1.20: https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/1855-csi-driver-service-account-token/kep.yaml + * https://kubernetes.io/blog/2020/12/18/kubernetes-1.20-pod-impersonation-short-lived-volumes-in-csi/ + +* Road to alpha: + * COSI: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1979-object-storage-support + * Non-graceful node shutdown: https://github.com/kubernetes/enhancements/pull/1116 + * Allow Kubernetes to supply pod's fsgroup to CSI driver on mount: https://github.com/kubernetes/enhancements/pull/2323 + * Volume group: https://github.com/kubernetes/enhancements/pull/1551 + * Recover from resize failures: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1790-recover-resize-failure + * SELinux recursive permission handling: https://github.com/kubernetes/enhancements/issues/1710 + * Volume/Snapshot namespace transfer: https://github.com/kubernetes/enhancements/pull/2326 + * Volume health (2nd alpha due to re-design): https://github.com/kubernetes/enhancements/pull/2286 + * Prioritization on volume capacity (sig-scheduling): https://github.com/kubernetes/enhancements/pull/1862 + * PVC created by statefulset will not be auto removed (sig-apps): https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/1847-autoremove-statefulset-pvcs + * Volume expansion for Stateful sets (sig-apps): https://github.com/kubernetes/enhancements/pull/1848 + * Enable User namespaces in kubelet so UIDs get shifted (sig-node): https://github.com/kubernetes/enhancements/pull/2101 +ContainerNotifier (sig-node): https://github.com/kubernetes/enhancements/pull/1995 + * User id ownership in configmaps and secrets (sig-auth) + +What areas and/or subprojects does the group need the most help with? +* There are features that we co-owned with sig-node, sig-apps, etc. We would need help from other SIGs to move things forward. + * Features co-owned with sig-node: + * ContainerNotifier: https://github.com/kubernetes/enhancements/pull/1995 + * Volume health: https://github.com/kubernetes/enhancements/pull/2286 + * Features co-owned with sig-apps: + * PVC created by statefulset will not be auto removed: https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/1847-autoremove-statefulset-pvcs + * Volume expansion for statefulset: https://github.com/kubernetes/enhancements/pull/1848 + * Features co-owned with sig-scheduling: + * Prioritization on volume capacity (sig-scheduling): https://github.com/kubernetes/enhancements/pull/1862 + +* There are also areas where we need sig-architecture’s help. For example, VolumeSnapshot is already GA and it is a core feature in sig-storage developed using CRDs. We have documented and blogged that components such as the snapshot CRDs and snapshot controller need to be deployed by Kubernetes distros, however, not every distro is installing them. This is a problem with any feature developed using CRD. We hope sig-architecture can help us resolve this problem. + +What's the average open days of a PR and Issue in your group? / what metrics does your group care about and/or measure? + +According to the following stats on 1/25/2021, it shows the 7 day MA for a PR Time to Approve and Merge in sig-storage repository group is: +* Open to lgtm: avg 3.55 days, max 14.11 week +* Lgtm to approve: avg 12.60 hour, max 3.92 week +* Approve to merge: avg 1.03 hour, max 1.14 day +* 85% open to lgtm: avg 1.4 week, max 14.11 week +* 85% lgtm to approve: avg 17.11 hour, max 3.92 week +* 85% approve to merge: avg 1.2 day, max 1.86 week +* https://k8s.devstats.cncf.io/d/44/pr-time-to-approve-and-merge?orgId=1&var-period=d7&var-repogroup_name=SIG%20Storage&var-apichange=All&var-size_name=All&var-kind_name=All + +Age of 7 day MA of issues by sig-storage repository group on 1/25/2021: +* Median time to close issue: Min 0.93 hour, Max 23.55 week, Avg 3.30 week +* https://k8s.devstats.cncf.io/d/15/issues-age-by-sig-and-repository-groups?orgId=1&var-period=d7&var-repogroup_name=SIG%20Storage&var-sig_name=All&var-kind_name=All&var-prio_name=All + +Suggestions on how to improve the PR/Issue velocity: +* Increase the reviewer pool +* Regular issue triage meetings diff --git a/sig-storage/annual-report-2021.md b/sig-storage/annual-report-2021.md deleted file mode 100644 index 27b90c70..00000000 --- a/sig-storage/annual-report-2021.md +++ /dev/null @@ -1,166 +0,0 @@ -# Kubernetes SIG Storage Community Group Annual Reports 2021 - -This report reflects back on CY 2020 and was written in Feb-Mar. 2021. - -## Operational - -* How are you doing with operational tasks in sig-governance.md? - * Is your README accurate? have a CONTRIBUTING.md file? - * Yes, our README is accurate: https://github.com/kubernetes/community/blob/master/sig-storage/README.md - * Our CONTRIBUTING.md file is up to date: https://github.com/kubernetes/community/blob/master/sig-storage/CONTRIBUTING.md - * We also have a section in the following doc for new contributors that is up to date: https://github.com/kubernetes/community/blob/master/contributors/devel/README.md#sig-storage - - * All subprojects correctly mapped and listed in sigs.yaml? - * Yes - - * What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? Are you keeping recordings up to date/trends in community members watching recordings? - * SIG-Storage has bi-weekly meetings where we do project tracking followed up discussions on PRs, issues if any. Meetings are fairly well attended. Meetings are recorded and meeting notes are up to date. -https://github.com/kubernetes/community/blob/master/sig-storage/README.md#meetings - * We also have sub-projects meetings such as CSI implementation meetings that happen twice a week and COSI weekly standup and weekly design meetings. There are also regular meetings for Data Protection WG, CSI migration, CSI windows, volume populator, etc. as well as one-off design meetings on specific topics/features. - * https://calendar.google.com/calendar/u/0/embed?src=vvvo48r6cprccii1lsava6p2uc@group.calendar.google.com - * We would love to see more contributors, new and existing, to join the meetings and participate in SIG projects. - - * How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being retired? Are OWNERS.md files up to date in these areas? - * Features worked by sub-projects are tracked by SIG-Storage and will be reported regularly in SIG-Storage bi-weekly meetings. SIG leads also participate in sub-projects meetings, i.e., meetings for CSI and COSI. -https://docs.google.com/spreadsheets/d/1t4z5DYKjX2ZDlkTpCnp18icRAQqOE85C1T1r2gqJVck/edit#gid=2027057294 - * There are also project repos that are deprecated. For example, https://github.com/kubernetes/external-storage is deprecated and moved to https://github.com/kubernetes-retired/external-storage. Some of the sub-projects in the original repo were moved out and became independent repos and are still managed by sig-storage with new maintainers. Some of the sub-projects were moved out because it is getting harder and harder to maintain such a big and complicated project. Moving them to independent repos allow some contributors to take new responsibilities and become maintainers of these projects. For example, the following 2 nfs projects were moved out of external-storage and became independent projects with new maintainers: - * https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner - * https://github.com/kubernetes-sigs/nfs-ganesha-server-and-external-provisioner - - * Same question as above but for working groups. - * Features worked by WGs are tracked by SIG-Storage and reported at SIG-Storage meetings, i.e., ContainerNotifier and CBT are worked on by Data Protection WG and are tracked in the SIG-Storage feature tracking sheet. -https://docs.google.com/spreadsheets/d/1t4z5DYKjX2ZDlkTpCnp18icRAQqOE85C1T1r2gqJVck/edit#gid=2027057294 - - * When was your last monthly community-wide update? (provide link to deck and/or recording) - * Our last monthly update was 10/15/2020. Here’s the deck: https://docs.google.com/presentation/d/1uzS6Q1OmttV-0hzlu_Eublx24nRmWiJQ__J65Sr3hIs/edit#slide=id.g401c104a3c_0_0 - -## Membership - - * Are all listed SIG leaders (chairs, tech leads, and subproject owners) active? - * Yes - - * How do you measure membership? By mailing list members, OWNERs, or something else? - * Mailing list members, participants of SIG meetings, and folks working on SIG-Storage projects. - - * How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it? - * At the SIG-Storage bi-weekly meetings, we track the progress of each feature the SIG is working on. Each feature has dev leads and reviewers assigned to it. If a developer/reviewer does not have time to do the design/development/reviews, we’ll try to find someone else who has the bandwidth. - * For features that are GA, we still continue to maintain and fix bugs and make enhancements. For example, dynamic provisioning has been a GA feature for quite a while now. We still fix bugs and continue to enhance it if needed. Another example is volume snapshot which just moved to GA in 1.20. We are still working on small enhancements, adding tests, fixing bugs, etc. The work is still being tracked in weekly standup meetings. - * We also have this new sub-project COSI which has been very active. It has a weekly standup meeting and a weekly design meeting. A few contributors have been actively working on design and development there. - - * Is there a healthy onboarding and growth path for contributors in your SIG? What are some activities that the group does to encourage this? What programs are you participating in to grow contributors throughout the contributor ladder? - * For each feature the SIG is working on, the SIG lead or dev lead will be looking for contributors by adding the “Help wanted” tag on an issue and/or asking for helpers in SIG-Storage bi-weekly meetings. This is a great opportunity for new contributors to step up to contribute and become members of kubernetes and eventually owners of a project. - * In the beginning of each kubernetes release, we have a planning meeting to go over all features targeted for that release. We encourage everyone to add features they want to work on in the planning spreadsheet. This is a good time for new contributors to learn our planning process, and volunteer to be involved in some of the feature development work. - - * What programs do you participate in for new contributors? - * At the Contributor Summit at KubeCon, we usually have a Meet & Greet for new contributors. - * At the bi-weekly SIG-Storage meetings, we also call out to any new contributors who are willing to help on some projects that we are looking for developers or reviewers. - - * Does the group have contributors from multiple companies/affiliations? Can end users/companies contribute in some way that they currently are not? - * Yes, we do have contributors from multiple companies/affiliations as shown here: https://k8s.devstats.cncf.io/d/8/company-statistics-by-repository-group?orgId=1&var-period=d7&var-metric=contributions&var-repogroup_name=SIG%20Storage&var-companies=All - * End users are welcome to open issues and fix bugs that they discovered. They are also welcome to contribute code just like other developers. Suggestions are welcome to improve in this area. Ping one of the sig leads on slack, send an email to the SIG-Storage mailing list, or attend one of the SIG-Storage meetings to provide suggestions. - -## Current initiatives and project health -[ ] Please include links to KEPs and other supporting information that will be beneficial to multiple types of community members. - -What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? Currently underway? What are some of the longer tail projects that your group is working on? -* Container Object Storage Interface - * Building on the success of Container Storage Interface (CSI) which focused on Block and File, k8s SIG Storage is looking to build a similar interface for object Storage. - * KEP: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1979-object-storage-support - * Status: POC in progress -* Generic ephemeral volumes - * Ephemeral volume types are created at pod creation time and deleted at pod termination time, like EmptyDir, SecretVolumes, ConfigMapVolumes. Third-parties would like to be able to create their own ephemeral volume types. Kubernetes permits creation of new ephemeral volume types with CSI, but that requires creating a custom CSI driver dedicated to the new ephemeral volume type. Generic ephemeral volumes will permit any existing persistent CSI Driver to be used as a ephemeral volume (so for example, users can have a new external volume provisioned and used like an EmptyDir, and deleted after pod termination like EmptyDir). - * KEP: https://github.com/kubernetes/enhancements/pull/1701 - * Status: Alpha in 1.19 -* CSI Support for Windows - * The new CSI Proxy for Windows enables CSI Drivers to work on Windows overcoming a Windows limitation that prevented containerized CSI Drivers. - * Blog: https://kubernetes.io/blog/2020/04/03/kubernetes-1-18-feature-windows-csi-support-alpha/ - * Status: Beta in 1.19 -* Volume snapshots GA: - * Volume Snapshot feature provides standardized Kubernetes APIs and CSI spec to support snapshot and restore functionality for CSI volume drivers. - * Blog: https://kubernetes.io/blog/2020/12/10/kubernetes-1.20-volume-snapshot-moves-to-ga/ - * KEP: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/177-volume-snapshot - * Status: GA in 1.20 - -Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha? -* Stable: - * Volume snapshots GA 1.20: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/177-volume-snapshot -https://kubernetes.io/blog/2020/12/10/kubernetes-1.20-volume-snapshot-moves-to-ga/ - * Raw block GA 1.18: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/351-raw-block-support - * CSI raw block GA 1.18: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/565-csi-block-support - * CSI Cloning GA 1.18: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/989-extend-datasource - * CSI Skip attach GA 1.18: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/770-csi-skip-attach - * CSI Pod info on mount GA 1.18 (CSIDriver): https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/603-csi-pod-info - -* Beta: - * CSI Windows beta 1.19 - * Immutable secrets and configmaps beta 1.19: https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/1412-immutable-secrets-and-configmaps - * Non-recursive volume ownership (fsgroup) beta 1.20: https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/695-skip-permission-change/kep.yaml - * CSIDriver policy for fsgroup beta 1.20 - * https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/1682-csi-driver-skip-permission/kep.yaml - * https://kubernetes.io/blog/2020/12/14/kubernetes-release-1.20-fsgroupchangepolicy-fsgrouppolicy/ - * CSI Migration beta 1.17: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/625-csi-migration - * Azure Disk and vSphere CSI migration beta in 1.19 - * OpenStack CSI migration beta in 1.18 - * GCE CSI migration beta 1.17 - * AWS CSI migration beta 1.17 - * Azure File alpha 1.15 - * CSI Volume expansion: beta in 1.16 - * https://github.com/kubernetes/enhancements/issues/556 - * https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/284-enable-volume-expansion - * CSI inline volume beta 1.16: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/596-csi-inline-volumes - -* Alpha: - * Volume populator alpha 1.18: https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/1495-generic-data-populators/kep.yaml - * Storage capacity tracking alpha 1.19: https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/1472-storage-capacity-tracking/kep.yaml - * Generic ephemeral volume alpha 1.19: https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/1698-generic-ephemeral-volumes/kep.yaml - * Volume health alpha 1.19: https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/1432-volume-health-monitor/kep.yaml - * Service account token alpha 1.20: https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/1855-csi-driver-service-account-token/kep.yaml - * https://kubernetes.io/blog/2020/12/18/kubernetes-1.20-pod-impersonation-short-lived-volumes-in-csi/ - -* Road to alpha: - * COSI: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1979-object-storage-support - * Non-graceful node shutdown: https://github.com/kubernetes/enhancements/pull/1116 - * Allow Kubernetes to supply pod's fsgroup to CSI driver on mount: https://github.com/kubernetes/enhancements/pull/2323 - * Volume group: https://github.com/kubernetes/enhancements/pull/1551 - * Recover from resize failures: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1790-recover-resize-failure - * SELinux recursive permission handling: https://github.com/kubernetes/enhancements/issues/1710 - * Volume/Snapshot namespace transfer: https://github.com/kubernetes/enhancements/pull/2326 - * Volume health (2nd alpha due to re-design): https://github.com/kubernetes/enhancements/pull/2286 - * Prioritization on volume capacity (sig-scheduling): https://github.com/kubernetes/enhancements/pull/1862 - * PVC created by statefulset will not be auto removed (sig-apps): https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/1847-autoremove-statefulset-pvcs - * Volume expansion for Stateful sets (sig-apps): https://github.com/kubernetes/enhancements/pull/1848 - * Enable User namespaces in kubelet so UIDs get shifted (sig-node): https://github.com/kubernetes/enhancements/pull/2101 -ContainerNotifier (sig-node): https://github.com/kubernetes/enhancements/pull/1995 - * User id ownership in configmaps and secrets (sig-auth) - -What areas and/or subprojects does the group need the most help with? -* There are features that we co-owned with sig-node, sig-apps, etc. We would need help from other SIGs to move things forward. - * Features co-owned with sig-node: - * ContainerNotifier: https://github.com/kubernetes/enhancements/pull/1995 - * Volume health: https://github.com/kubernetes/enhancements/pull/2286 - * Features co-owned with sig-apps: - * PVC created by statefulset will not be auto removed: https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/1847-autoremove-statefulset-pvcs - * Volume expansion for statefulset: https://github.com/kubernetes/enhancements/pull/1848 - * Features co-owned with sig-scheduling: - * Prioritization on volume capacity (sig-scheduling): https://github.com/kubernetes/enhancements/pull/1862 - -* There are also areas where we need sig-architecture’s help. For example, VolumeSnapshot is already GA and it is a core feature in sig-storage developed using CRDs. We have documented and blogged that components such as the snapshot CRDs and snapshot controller need to be deployed by Kubernetes distros, however, not every distro is installing them. This is a problem with any feature developed using CRD. We hope sig-architecture can help us resolve this problem. - -What's the average open days of a PR and Issue in your group? / what metrics does your group care about and/or measure? - -According to the following stats on 1/25/2021, it shows the 7 day MA for a PR Time to Approve and Merge in sig-storage repository group is: -* Open to lgtm: avg 3.55 days, max 14.11 week -* Lgtm to approve: avg 12.60 hour, max 3.92 week -* Approve to merge: avg 1.03 hour, max 1.14 day -* 85% open to lgtm: avg 1.4 week, max 14.11 week -* 85% lgtm to approve: avg 17.11 hour, max 3.92 week -* 85% approve to merge: avg 1.2 day, max 1.86 week -* https://k8s.devstats.cncf.io/d/44/pr-time-to-approve-and-merge?orgId=1&var-period=d7&var-repogroup_name=SIG%20Storage&var-apichange=All&var-size_name=All&var-kind_name=All - -Age of 7 day MA of issues by sig-storage repository group on 1/25/2021: -* Median time to close issue: Min 0.93 hour, Max 23.55 week, Avg 3.30 week -* https://k8s.devstats.cncf.io/d/15/issues-age-by-sig-and-repository-groups?orgId=1&var-period=d7&var-repogroup_name=SIG%20Storage&var-sig_name=All&var-kind_name=All&var-prio_name=All - -Suggestions on how to improve the PR/Issue velocity: -* Increase the reviewer pool -* Regular issue triage meetings diff --git a/sig-ui/annual-report-2020.md b/sig-ui/annual-report-2020.md new file mode 100644 index 00000000..7cb5f519 --- /dev/null +++ b/sig-ui/annual-report-2020.md @@ -0,0 +1,108 @@ +# SIG UI 2021 Annual Report + +**Authors:** + +Sebastian Florek ([@floreks](https://github.com/floreks)) +Marcin Maciaszczyk ([@maciaszczykm](https://github.com/maciaszczykm)) +Jeffrey Sica ([@jeefy](https://github.com/jeefy)) + +- [Operational](#operational) +- [Membership](#membership) +- [Current initiatives and project health](#current-initiatives-and-project-health) + +## Operational + +**How are you doing with operational tasks in [sig-governance.md](/committee-steering/governance/sig-governance.md)?** + +The SIG primarily works asynchronously. In the past, our meetings would last less than five minutes and be relatively disruptive. Since the release of the 2.0 Dashboard, meeting attendance transitioned from optional to near-non-existent. Instead, we coordinate through the #sig-ui Slack channel and handle any project planning via GitHub. All chairs are regular contributors of the Dashboard subproject and help review PRs and triage issues. + +**Is your README accurate? have a CONTRIBUTING.md file?** + +Yes, our README is accurate and is typically updated with every new Dashboard release. Also we do have a CONTRIBUTING.md file however it has not been updated with any more info beyond the standard template. Both of these files reside within our respective repositories. + +**All subprojects correctly mapped and listed in [sigs.yaml](/sig-list.md)?** + +Yes. The only subproject under SIG-UI is the Kubernetes Dashboard. There is an additional companion service that gets deployed to feed metrics into the Dashboard (Dashboard Metrics Scraper) but it isn't considered a subproject by the SIG. + +**What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? Are you keeping recordings up to date/trends in community members watching recordings?** + +As stated above, the SIG currently doesn't hold any meetings and instead has been asynchronous for roughly a year. All communication is done via the #sig-ui Slack channel and all planning activities are managed within the Dashboard GitHub repo. + +**How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being retired? Are OWNERS files up to date in these areas?** + +As we have no subproject other than the Dashboard, there is no real feedback loop besides GitHub Issues and Slack channel traction. + +**When was your last monthly community-wide update? (provide link to deck and/or recording)** + +Our last community-wide update was in May 2020 + +Slide Deck: https://docs.google.com/presentation/d/1W4NioOkAF2VFiu-5t80p2vlu3_OznpugiyiViFuitaM/edit?usp=sharing + +Recording: https://youtu.be/ZyUQiN3S6TE?list=PL69nYSiGNLP1pkHsbPjzAewvMgGUpkCnJ&t=837 + +## Membership + +**Are all listed SIG leaders (chairs, tech leads, and subproject owners) active?** + +Yes + +**How do you measure membership? By mailing list members, OWNERs, or something else?** + +We measure activity by activity within the GitHub repo. Filing/responding to issues and submitting/reviewing PRs. + +**How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it?** + +We currently have no metric for reviewer/approver bandwidth. We've worked in a communal manner to ensure nothing becomes stale. This has generally worked over the last several years, and isn't a major concern for us. Our existing OWNERS file is up to date and we have active reviewers/approvers. + +Over the course of 2020 we've added 9 people in OWNERS files within our i18n translations. + +**Is there a healthy onboarding and growth path for contributors in your SIG? What are some activities that the group does to encourage this? What programs are you participating in to grow contributors throughout the contributor ladder?** + +The SIG doesn't participate in any activities or programs explicitly meant to help grow contributors. We attempt to be responsive and welcoming within our issues and PRs to try and retain those who take the first step and engage in conversation however. With this, we've maintained a small albeit responsive pool of active contributors to the SIG. + +**What programs do you participate in for new contributors?** + +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. + +**Does the group have contributors from multiple companies/affiliations? Can end users/companies contribute in some way that they currently are not?** + +Yes, current chairs are spread between Kubermatic (formerly Loodse) and Red Hat. Additional contributors in OWNERS files are also spread across multiple companies including but not limited to NEC and Tencent. + +## Current initiatives and project health + +In addition to the ongoing effort of maintenance, we are improving support visualizing [various resource objects](https://github.com/kubernetes/dashboard/issues/5232) and adding the ability for installations to have custom themes. + +The often-unspoken reality is, a UI or Dashboard for Kubernetes is often a differentiator for many companies. Additionally, there are many different ways and opinions on what a front-end for Kubernetes should look like. + +**What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? Currently underway? What are some of the longer tail projects that your group is working on?** + +When the Dashboard was originally written, it used a pull/polling design. Now, we are working towards supporting the [shared informer pattern](https://github.com/kubernetes/dashboard/issues/5320), making the Dashboard more-real-time. + +Another major area to highlight is we are continually onboarding new language translations for the Dashboard. + +**Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha?** + +There have been no KEPs opened as part of SIG-UI. + +**What areas and/or subprojects does the group need the most help with?** + +Recruiting new contributors. Front-ends are very opinionated, and those with differing opinions seem to prefer starting from scratch rather than put in the effort in learning an existing project to contribute to. This has been observed time and time again. + +To be able to traverse/contribute, a new contributor needs to have an understanding of AngularJS, golang, and a reasonably in-depth knowledge of Kubernetes client-go package. + +**What's the average open days of a PR and Issue in your group? / what metrics does your group care about and/or measure?** + +There are two primary sources of PRs: Automated dependency PRs (Dependabot) and contributor-created PRs. + +At a glance, Dependabot PRs are merged or closed within 24h, while contributor-created PRs are typically reviewed within 3-4 days. + +Currently there are no real metrics that we measure regarding Issue/PR turnaround. + +## Additional Links + +[Developer Statistics](https://k8s.devstats.cncf.io/d/13/developer-activity-counts-by-repository-group?orgId=1&var-period_name=Last%20year&var-metric=contributions&var-repogroup_name=SIG%20UI&var-country_name=All) + +[27 New Contributors in the last year](https://k8s.devstats.cncf.io/d/52/new-contributors?orgId=1&var-repogroup_name=SIG%20UI&from=now-1y&to=now) + +[Opened PR Velocity](https://k8s.devstats.cncf.io/d/25/open-pr-age-by-repository-group?orgId=1&var-period=d7&var-repogroup_name=SIG%20UI&var-kind_name=All&from=now-1y&to=now) + diff --git a/sig-ui/annual-report-2021.md b/sig-ui/annual-report-2021.md deleted file mode 100644 index 7cb5f519..00000000 --- a/sig-ui/annual-report-2021.md +++ /dev/null @@ -1,108 +0,0 @@ -# SIG UI 2021 Annual Report - -**Authors:** - -Sebastian Florek ([@floreks](https://github.com/floreks)) -Marcin Maciaszczyk ([@maciaszczykm](https://github.com/maciaszczykm)) -Jeffrey Sica ([@jeefy](https://github.com/jeefy)) - -- [Operational](#operational) -- [Membership](#membership) -- [Current initiatives and project health](#current-initiatives-and-project-health) - -## Operational - -**How are you doing with operational tasks in [sig-governance.md](/committee-steering/governance/sig-governance.md)?** - -The SIG primarily works asynchronously. In the past, our meetings would last less than five minutes and be relatively disruptive. Since the release of the 2.0 Dashboard, meeting attendance transitioned from optional to near-non-existent. Instead, we coordinate through the #sig-ui Slack channel and handle any project planning via GitHub. All chairs are regular contributors of the Dashboard subproject and help review PRs and triage issues. - -**Is your README accurate? have a CONTRIBUTING.md file?** - -Yes, our README is accurate and is typically updated with every new Dashboard release. Also we do have a CONTRIBUTING.md file however it has not been updated with any more info beyond the standard template. Both of these files reside within our respective repositories. - -**All subprojects correctly mapped and listed in [sigs.yaml](/sig-list.md)?** - -Yes. The only subproject under SIG-UI is the Kubernetes Dashboard. There is an additional companion service that gets deployed to feed metrics into the Dashboard (Dashboard Metrics Scraper) but it isn't considered a subproject by the SIG. - -**What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? Are you keeping recordings up to date/trends in community members watching recordings?** - -As stated above, the SIG currently doesn't hold any meetings and instead has been asynchronous for roughly a year. All communication is done via the #sig-ui Slack channel and all planning activities are managed within the Dashboard GitHub repo. - -**How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being retired? Are OWNERS files up to date in these areas?** - -As we have no subproject other than the Dashboard, there is no real feedback loop besides GitHub Issues and Slack channel traction. - -**When was your last monthly community-wide update? (provide link to deck and/or recording)** - -Our last community-wide update was in May 2020 - -Slide Deck: https://docs.google.com/presentation/d/1W4NioOkAF2VFiu-5t80p2vlu3_OznpugiyiViFuitaM/edit?usp=sharing - -Recording: https://youtu.be/ZyUQiN3S6TE?list=PL69nYSiGNLP1pkHsbPjzAewvMgGUpkCnJ&t=837 - -## Membership - -**Are all listed SIG leaders (chairs, tech leads, and subproject owners) active?** - -Yes - -**How do you measure membership? By mailing list members, OWNERs, or something else?** - -We measure activity by activity within the GitHub repo. Filing/responding to issues and submitting/reviewing PRs. - -**How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it?** - -We currently have no metric for reviewer/approver bandwidth. We've worked in a communal manner to ensure nothing becomes stale. This has generally worked over the last several years, and isn't a major concern for us. Our existing OWNERS file is up to date and we have active reviewers/approvers. - -Over the course of 2020 we've added 9 people in OWNERS files within our i18n translations. - -**Is there a healthy onboarding and growth path for contributors in your SIG? What are some activities that the group does to encourage this? What programs are you participating in to grow contributors throughout the contributor ladder?** - -The SIG doesn't participate in any activities or programs explicitly meant to help grow contributors. We attempt to be responsive and welcoming within our issues and PRs to try and retain those who take the first step and engage in conversation however. With this, we've maintained a small albeit responsive pool of active contributors to the SIG. - -**What programs do you participate in for new contributors?** - -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. - -**Does the group have contributors from multiple companies/affiliations? Can end users/companies contribute in some way that they currently are not?** - -Yes, current chairs are spread between Kubermatic (formerly Loodse) and Red Hat. Additional contributors in OWNERS files are also spread across multiple companies including but not limited to NEC and Tencent. - -## Current initiatives and project health - -In addition to the ongoing effort of maintenance, we are improving support visualizing [various resource objects](https://github.com/kubernetes/dashboard/issues/5232) and adding the ability for installations to have custom themes. - -The often-unspoken reality is, a UI or Dashboard for Kubernetes is often a differentiator for many companies. Additionally, there are many different ways and opinions on what a front-end for Kubernetes should look like. - -**What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? Currently underway? What are some of the longer tail projects that your group is working on?** - -When the Dashboard was originally written, it used a pull/polling design. Now, we are working towards supporting the [shared informer pattern](https://github.com/kubernetes/dashboard/issues/5320), making the Dashboard more-real-time. - -Another major area to highlight is we are continually onboarding new language translations for the Dashboard. - -**Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha?** - -There have been no KEPs opened as part of SIG-UI. - -**What areas and/or subprojects does the group need the most help with?** - -Recruiting new contributors. Front-ends are very opinionated, and those with differing opinions seem to prefer starting from scratch rather than put in the effort in learning an existing project to contribute to. This has been observed time and time again. - -To be able to traverse/contribute, a new contributor needs to have an understanding of AngularJS, golang, and a reasonably in-depth knowledge of Kubernetes client-go package. - -**What's the average open days of a PR and Issue in your group? / what metrics does your group care about and/or measure?** - -There are two primary sources of PRs: Automated dependency PRs (Dependabot) and contributor-created PRs. - -At a glance, Dependabot PRs are merged or closed within 24h, while contributor-created PRs are typically reviewed within 3-4 days. - -Currently there are no real metrics that we measure regarding Issue/PR turnaround. - -## Additional Links - -[Developer Statistics](https://k8s.devstats.cncf.io/d/13/developer-activity-counts-by-repository-group?orgId=1&var-period_name=Last%20year&var-metric=contributions&var-repogroup_name=SIG%20UI&var-country_name=All) - -[27 New Contributors in the last year](https://k8s.devstats.cncf.io/d/52/new-contributors?orgId=1&var-repogroup_name=SIG%20UI&from=now-1y&to=now) - -[Opened PR Velocity](https://k8s.devstats.cncf.io/d/25/open-pr-age-by-repository-group?orgId=1&var-period=d7&var-repogroup_name=SIG%20UI&var-kind_name=All&from=now-1y&to=now) - diff --git a/sig-usability/annual-report-2020.md b/sig-usability/annual-report-2020.md new file mode 100644 index 00000000..9934a134 --- /dev/null +++ b/sig-usability/annual-report-2020.md @@ -0,0 +1,53 @@ +# 2021 Annual Report: SIG Usability + +## Operational + +How are you doing with operational tasks in sig-governance.md? +Is your README accurate? have a CONTRIBUTING.md file? +Yes, updated to reflect new meeting time +https://github.com/kubernetes-sigs/sig-usability + +All subprojects correctly mapped and listed in sigs.yaml? +N/A + +What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? Are you keeping recordings up to date/trends in community members watching recordings? +- Videos are all here: https://www.youtube.com/watch?v=cujQhg6JcgI&list=PL69nYSiGNLP0eY-U8DVJWHBwKvMDEtOxx +- We have small, interactive meetings, usually discuss and coordinate around our user research study that’s on-going + +How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being retired? Are OWNERS files up to date in these areas? +N/A + +Same question as above but for working groups. +N/A + +When was your last monthly community-wide update? (provide link to deck and/or recording) +https://www.youtube.com/watch?v=H6UuxSZEw3s + +## Membership + +Are all listed SIG leaders (chairs, tech leads, and subproject owners) active? +We need to finalize the PR on kubernetes/kubernetes to make Gaby formally a chair + +How do you measure membership? By mailing list members, OWNERs, or something else? +We engage with membership via Slack and mailing list + +How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it? +We are not focused on code PRs, we’re focused on staffing our user research study, which happens in Zoom. We’ve had steady growth of a small number of very senior user searchers from several different companies, and our goal is to do 2-4 in depth user research engagements a month. + +Is there a healthy onboarding and growth path for contributors in your SIG? What are some activities that the group does to encourage this? What programs are you participating in to grow contributors throughout the contributor ladder? +We’ve documented our user research procedures and invite people to sign up to do shadowing and help take notes. As they participate they are invited to graduate to leading interviews. + +What programs do you participate in for new contributors? +We are doing a Linux Foundation mentorship program, and new contributors are welcome at all of our meetings + +Does the group have contributors from multiple companies/affiliations? Can end users/companies contribute in some way that they currently are not? +We have contributors from VMware, IBM, RedHat, and others. End users are the focus of our research, and we are talking to them as often as possible. + +## Current initiatives and project health + +The nature of our work is currently not linked to KEPs or the release cycle. To learn more about what we’re working on, here are some helpful links: +- Meeting Agendas, recordings: https://docs.google.com/document/d/1gJHgt8RpH4TvqPuC8NtR31-CMqtTYkHy_loxubHq8lg/edit# +- Jobs to be done research proposal: https://docs.google.com/document/d/1lkPQdBEw-Xb5GEZ48WnpBgQdZ01EmTBhjcxJBlu5qJs/edit + +If you’re interested in our user research study, please join a meeting or ping us in our slack channel to learn more! Due to the sensitivity of user research data, our docs on these are not public. We will be doing a deep dive into the results at our Kubecon talk, with anonymized data to share. + diff --git a/sig-usability/annual-report-2021.md b/sig-usability/annual-report-2021.md deleted file mode 100644 index 9934a134..00000000 --- a/sig-usability/annual-report-2021.md +++ /dev/null @@ -1,53 +0,0 @@ -# 2021 Annual Report: SIG Usability - -## Operational - -How are you doing with operational tasks in sig-governance.md? -Is your README accurate? have a CONTRIBUTING.md file? -Yes, updated to reflect new meeting time -https://github.com/kubernetes-sigs/sig-usability - -All subprojects correctly mapped and listed in sigs.yaml? -N/A - -What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? Are you keeping recordings up to date/trends in community members watching recordings? -- Videos are all here: https://www.youtube.com/watch?v=cujQhg6JcgI&list=PL69nYSiGNLP0eY-U8DVJWHBwKvMDEtOxx -- We have small, interactive meetings, usually discuss and coordinate around our user research study that’s on-going - -How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being retired? Are OWNERS files up to date in these areas? -N/A - -Same question as above but for working groups. -N/A - -When was your last monthly community-wide update? (provide link to deck and/or recording) -https://www.youtube.com/watch?v=H6UuxSZEw3s - -## Membership - -Are all listed SIG leaders (chairs, tech leads, and subproject owners) active? -We need to finalize the PR on kubernetes/kubernetes to make Gaby formally a chair - -How do you measure membership? By mailing list members, OWNERs, or something else? -We engage with membership via Slack and mailing list - -How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it? -We are not focused on code PRs, we’re focused on staffing our user research study, which happens in Zoom. We’ve had steady growth of a small number of very senior user searchers from several different companies, and our goal is to do 2-4 in depth user research engagements a month. - -Is there a healthy onboarding and growth path for contributors in your SIG? What are some activities that the group does to encourage this? What programs are you participating in to grow contributors throughout the contributor ladder? -We’ve documented our user research procedures and invite people to sign up to do shadowing and help take notes. As they participate they are invited to graduate to leading interviews. - -What programs do you participate in for new contributors? -We are doing a Linux Foundation mentorship program, and new contributors are welcome at all of our meetings - -Does the group have contributors from multiple companies/affiliations? Can end users/companies contribute in some way that they currently are not? -We have contributors from VMware, IBM, RedHat, and others. End users are the focus of our research, and we are talking to them as often as possible. - -## Current initiatives and project health - -The nature of our work is currently not linked to KEPs or the release cycle. To learn more about what we’re working on, here are some helpful links: -- Meeting Agendas, recordings: https://docs.google.com/document/d/1gJHgt8RpH4TvqPuC8NtR31-CMqtTYkHy_loxubHq8lg/edit# -- Jobs to be done research proposal: https://docs.google.com/document/d/1lkPQdBEw-Xb5GEZ48WnpBgQdZ01EmTBhjcxJBlu5qJs/edit - -If you’re interested in our user research study, please join a meeting or ping us in our slack channel to learn more! Due to the sensitivity of user research data, our docs on these are not public. We will be doing a deep dive into the results at our Kubecon talk, with anonymized data to share. - diff --git a/sig-windows/annual-report-2020.md b/sig-windows/annual-report-2020.md new file mode 100644 index 00000000..6670700a --- /dev/null +++ b/sig-windows/annual-report-2020.md @@ -0,0 +1,69 @@ +# Operational +How are you doing with operational tasks in sig-governance.md? Good, we go over things as leads when needed and update stuff, and are growing the community to help with this. + +Is your README accurate?have a CONTRIBUTING.md file? +Yes / Yes - README.md is up to date, CONTRIBUTING.md is still accurate but could use some updates. + +All subprojects correctly mapped and listed in sigs.yaml? +Yes + +What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? Are you keeping recordings up to date/trends in community members watching recordings? +Meetings have decent attendance, but few active participants (i.e. not lots of questions or free discussion... we want more of that). +Meeting notes are used during the meetings are up to date. +Recordings are up to date but few views + +How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being retired? Are OWNERS files up to date in these areas? +Owners files are up to date. Existing subprojects are mostly in maintenance mode. We would like to try starting one or two subprojects to gather more interest / new participation in SIG-Windows. +Same question as above but for working groups. +We don't get updates from subprojects and are in the project of refactoring subprojects to match where active development is happening. + +When was your last monthly community-wide update? (provide link to deck and/or recording) +Sept 17, 2020. The recording is here https://www.youtube.com/watch?v=6Wn_dIEg0E8, slides are here https://docs.google.com/presentation/d/1FkS6FIes9opMR1B4qXyVzwGfUBnX0A-sh27Kcnyi-e4/edit#slide=id.g97ab5232db_0_0 . + +# Membership + +Are all listed SIG leaders (chairs, tech leads, and subproject owners) active? +Yes + +How do you measure membership? By mailing list members, OWNERs, or something else? +We don’t measure membership. + +How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it? +We are blocked on reviewer/approver bandwidth from other SIGs much more often than reviewer/approver bandwidth in our SIG. +Is there a healthy onboarding and growth path for contributors in your SIG? What are some activities that the group does to encourage this? What programs are you participating in to grow contributors throughout the contributor ladder? +We want to focus on this in the next few months. Some ideas we have are pairing with folks and establishing one or two new focused subprojects that will encourage new participants. + +What programs do you participate in for new contributors? We’re wanting to groom long-term/dedicated contributors to maintain testing, windows development environments, and add privileged container ecosystem tooling. + +Are there programs to help with this? Does the group have contributors from multiple companies/affiliations? Can end users/companies contribute in some way that they currently are not? Yes, we have contributors from many companies. Current initiatives and project health + +# Accomplishments + +What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? Currently underway? What are some of the longer tail projects that your group is working on? + +- Containerd support (proud of) +- Network policy support (currently underway) +- Cluster API support (proud of) +- Privileged containers (long tail) + +Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha? + +- Alpha / going alpha +- Privileged containers +- Node log viewer +- Beta / going beta +- DSR support +- Stable / going stable +- CSI proxy + +What areas and/or subprojects does the group need the most help with? + +- API Reviews, sig-auth +- E2e tests / coverage / keeping things green +- Testgrid +- Cross-SIG collaboration (auth, api reviews) + +What's the average open days of a PR and Issue in your group? / what metrics does your group care about and/or measure? +Average open days for PR is long weeks or months - mainly due to requiring reviews/approvals from multiple SIGs most of the time. + + diff --git a/sig-windows/annual-report-2021.md b/sig-windows/annual-report-2021.md deleted file mode 100644 index 6670700a..00000000 --- a/sig-windows/annual-report-2021.md +++ /dev/null @@ -1,69 +0,0 @@ -# Operational -How are you doing with operational tasks in sig-governance.md? Good, we go over things as leads when needed and update stuff, and are growing the community to help with this. - -Is your README accurate?have a CONTRIBUTING.md file? -Yes / Yes - README.md is up to date, CONTRIBUTING.md is still accurate but could use some updates. - -All subprojects correctly mapped and listed in sigs.yaml? -Yes - -What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? Are you keeping recordings up to date/trends in community members watching recordings? -Meetings have decent attendance, but few active participants (i.e. not lots of questions or free discussion... we want more of that). -Meeting notes are used during the meetings are up to date. -Recordings are up to date but few views - -How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being retired? Are OWNERS files up to date in these areas? -Owners files are up to date. Existing subprojects are mostly in maintenance mode. We would like to try starting one or two subprojects to gather more interest / new participation in SIG-Windows. -Same question as above but for working groups. -We don't get updates from subprojects and are in the project of refactoring subprojects to match where active development is happening. - -When was your last monthly community-wide update? (provide link to deck and/or recording) -Sept 17, 2020. The recording is here https://www.youtube.com/watch?v=6Wn_dIEg0E8, slides are here https://docs.google.com/presentation/d/1FkS6FIes9opMR1B4qXyVzwGfUBnX0A-sh27Kcnyi-e4/edit#slide=id.g97ab5232db_0_0 . - -# Membership - -Are all listed SIG leaders (chairs, tech leads, and subproject owners) active? -Yes - -How do you measure membership? By mailing list members, OWNERs, or something else? -We don’t measure membership. - -How does the group measure reviewer and approver bandwidth? Do you need help in any area now? What are you doing about it? -We are blocked on reviewer/approver bandwidth from other SIGs much more often than reviewer/approver bandwidth in our SIG. -Is there a healthy onboarding and growth path for contributors in your SIG? What are some activities that the group does to encourage this? What programs are you participating in to grow contributors throughout the contributor ladder? -We want to focus on this in the next few months. Some ideas we have are pairing with folks and establishing one or two new focused subprojects that will encourage new participants. - -What programs do you participate in for new contributors? We’re wanting to groom long-term/dedicated contributors to maintain testing, windows development environments, and add privileged container ecosystem tooling. - -Are there programs to help with this? Does the group have contributors from multiple companies/affiliations? Can end users/companies contribute in some way that they currently are not? Yes, we have contributors from many companies. Current initiatives and project health - -# Accomplishments - -What are initiatives that should be highlighted, lauded, shout out, that your group is proud of? Currently underway? What are some of the longer tail projects that your group is working on? - -- Containerd support (proud of) -- Network policy support (currently underway) -- Cluster API support (proud of) -- Privileged containers (long tail) - -Year to date KEP work review: What’s now stable? Beta? Alpha? Road to alpha? - -- Alpha / going alpha -- Privileged containers -- Node log viewer -- Beta / going beta -- DSR support -- Stable / going stable -- CSI proxy - -What areas and/or subprojects does the group need the most help with? - -- API Reviews, sig-auth -- E2e tests / coverage / keeping things green -- Testgrid -- Cross-SIG collaboration (auth, api reviews) - -What's the average open days of a PR and Issue in your group? / what metrics does your group care about and/or measure? -Average open days for PR is long weeks or months - mainly due to requiring reviews/approvals from multiple SIGs most of the time. - - diff --git a/wg-data-protection/annual-report-2020.md b/wg-data-protection/annual-report-2020.md new file mode 100644 index 00000000..95af3c03 --- /dev/null +++ b/wg-data-protection/annual-report-2020.md @@ -0,0 +1,46 @@ +# Data Protection WG Community Report 2020 + +This report reflects back on CY 2020 and was written in Mar. 2021. + +## You and your role: + +When did you become a chair and do you enjoy the role? +* Both Xiangqian Yu and Xing Yang became Data Protection WG co-chairs when the WG was formally established on Jan. 7, 2020. Yes, we do enjoy the role. +* https://github.com/kubernetes/community/pull/4301 + +What do you find challenging? +* One of the challenges we have lies in cross SIG collaboration. It is challenging to get other SIG’s alignments on some of the features we are designing, especially when it requires a good amount of engagement and investment (both short term and long term wise). For example, we are working on the ContainerNotifier feature which needs support from SIG-Node. SIG-Node has assigned a reviewer for the KEP so that we can move forward. + +Do you have goals for the group? +* Yes. As stated in the charter, the goal for this WG is to identify missing functionality and work together to design features to enable data protection support in Kubernetes. + +Do you want to continue or find a replacement? If you feel that you aren’t ready to pass the baton, what would you like to accomplish before you do? +* We want to continue. + +Is there something we can provide that would better support you? +* The most challenging thing is cross SIG collaboration. This WG is sponsored by both SIG-Storage and SIG-Apps. Recently we also need to collaborate with SIG-Node, and potentially with SIG-Arch. It will be great if the steering committee can provide guidance and help us get support from other SIGs. + +Do you have feedback for Steering? Suggestions for what we should work on? +* If the Steering Committee can help us get support from other SIGs, that will be great. + +## Working Groups +* What was the initial mission of the group and if it's changed, how? + * https://github.com/kubernetes/community/tree/master/wg-data-protection + * https://github.com/kubernetes/community/blob/master/wg-data-protection/charter.md + * The initial mission of this WG is to identify missing functionality and work together to design features to enable data protection support in Kubernetes. This is unchanged. + +* What’s the current roadmap until completion? + * We have many items listed in the in-scope section of the charter. We’d like to get them done. + * In the first paragraph of the [WG community page](https://github.com/kubernetes/community/tree/master/wg-data-protection#data-protection-working-group), we included a work-in-progress doc that listed all the items that we are working on. It includes WIP design docs or KEPs for all the features we are working on. + +* Have you produced any artifacts, reports, white papers to date? + * We have been working on design specs and white paper. They are all WIP. + +* Is the group active? healthy? contributors from multiple companies and/or end user companies? + * Yes, it is active and has participation from multiple companies. + +* Is everything in your readme accurate? posting meetings on youtube? + * Yes, it is accurate and posting to youtube regularly. + +* Do you have regular check-ins with your sponsoring SIGs? + * We report regularly in SIG-Storage meetings, but have not done so with SIG-Apps. One of the initial SIG-Apps co-chair who sponsored this WG is no longer actively involved. diff --git a/wg-data-protection/annual-report-2021.md b/wg-data-protection/annual-report-2021.md deleted file mode 100644 index 817c6218..00000000 --- a/wg-data-protection/annual-report-2021.md +++ /dev/null @@ -1,46 +0,0 @@ -# Data Protection WG Community Report 2021 - -This report reflects back on CY 2020 and was written in Mar. 2021. - -## You and your role: - -When did you become a chair and do you enjoy the role? -* Both Xiangqian Yu and Xing Yang became Data Protection WG co-chairs when the WG was formally established on Jan. 7, 2020. Yes, we do enjoy the role. -* https://github.com/kubernetes/community/pull/4301 - -What do you find challenging? -* One of the challenges we have lies in cross SIG collaboration. It is challenging to get other SIG’s alignments on some of the features we are designing, especially when it requires a good amount of engagement and investment (both short term and long term wise). For example, we are working on the ContainerNotifier feature which needs support from SIG-Node. SIG-Node has assigned a reviewer for the KEP so that we can move forward. - -Do you have goals for the group? -* Yes. As stated in the charter, the goal for this WG is to identify missing functionality and work together to design features to enable data protection support in Kubernetes. - -Do you want to continue or find a replacement? If you feel that you aren’t ready to pass the baton, what would you like to accomplish before you do? -* We want to continue. - -Is there something we can provide that would better support you? -* The most challenging thing is cross SIG collaboration. This WG is sponsored by both SIG-Storage and SIG-Apps. Recently we also need to collaborate with SIG-Node, and potentially with SIG-Arch. It will be great if the steering committee can provide guidance and help us get support from other SIGs. - -Do you have feedback for Steering? Suggestions for what we should work on? -* If the Steering Committee can help us get support from other SIGs, that will be great. - -## Working Groups -* What was the initial mission of the group and if it's changed, how? - * https://github.com/kubernetes/community/tree/master/wg-data-protection - * https://github.com/kubernetes/community/blob/master/wg-data-protection/charter.md - * The initial mission of this WG is to identify missing functionality and work together to design features to enable data protection support in Kubernetes. This is unchanged. - -* What’s the current roadmap until completion? - * We have many items listed in the in-scope section of the charter. We’d like to get them done. - * In the first paragraph of the [WG community page](https://github.com/kubernetes/community/tree/master/wg-data-protection#data-protection-working-group), we included a work-in-progress doc that listed all the items that we are working on. It includes WIP design docs or KEPs for all the features we are working on. - -* Have you produced any artifacts, reports, white papers to date? - * We have been working on design specs and white paper. They are all WIP. - -* Is the group active? healthy? contributors from multiple companies and/or end user companies? - * Yes, it is active and has participation from multiple companies. - -* Is everything in your readme accurate? posting meetings on youtube? - * Yes, it is accurate and posting to youtube regularly. - -* Do you have regular check-ins with your sponsoring SIGs? - * We report regularly in SIG-Storage meetings, but have not done so with SIG-Apps. One of the initial SIG-Apps co-chair who sponsored this WG is no longer actively involved. diff --git a/wg-multitenancy/annual-report-2020.md b/wg-multitenancy/annual-report-2020.md new file mode 100644 index 00000000..fb6a82c1 --- /dev/null +++ b/wg-multitenancy/annual-report-2020.md @@ -0,0 +1,53 @@ +# 2021 WG Multitenancy Annual Report + +### What was the initial mission of the group and if it's changed, how? + +**Initial Mission:** + +Define the models of multitenancy that Kubernetes will support. Discuss and execute upon any +remaining work that needs to be done to support these models. Create conformance tests that +will prove that these models can be built and used in production environments. + +**Current Mission:** + +We are focusing more on projects using Kubernetes than trying to directly change the API machinery, +which is a huge and potentially intractable problem. We are continuing to work on conformance +testing as part of one of our projects. + +### What’s the current roadmap until completion? + +**We have three projects we are incubating:** + +* Multi-Tenancy Benchmarks https://github.com/kubernetes-sigs/multi-tenancy/tree/master/benchmarks +* Virtual Cluster Project https://github.com/kubernetes-sigs/multi-tenancy/tree/master/incubator/virtualcluster +* Hierarchical Namespace Controller https://github.com/kubernetes-sigs/multi-tenancy/tree/master/incubator/hnc + +These are all in active development, and we’re making good progress. Google Cloud has adopted HNC in beta. +MTB is going to be a great platform for the conformance test suite expansion. Virtual Cluster Project is +graduating out of our incubator and into its own repo! HNC will probably follow soon. + +The roadmap is documented in the [working group project plan](https://docs.google.com/document/d/1U8RQQmTUjxgMZY05HG2f7b3KsB94BhK4Ko6aWbLNXcc/edit). + +### Have you produced any artifacts, reports, white papers to date? + +You can find a bunch of our docs here: https://github.com/kubernetes-sigs/multi-tenancy/tree/master/docs + +### Is the group active? healthy? contributors from multiple companies and/or end user companies? + +Yes, it’s one of the most egalitarian working groups I’ve seen. We have active contributors and participants +from all over the industry, and a lot of drive bys from consumers of Kubernetes who are just trying to +configure clusters for multi-tenancy and have questions. Our incubating projects are led by people from +Google, Nirmata, Alibaba, and Medtronic, have reviewers and participants from other companies, and the WG chairs work at VMware and Cisco. +We have a very diverse group of presenters from different companies who are all trying to solve the same problems, and we all have +the philosophy of learning from each other and sharing. + +### Is everything in your readme accurate? posting meetings on youtube? + +Yes and Yes. + +### Do you have regular check-ins with your sponsoring SIGs? + +We have a huge number of sponsoring SIGs, many of them send representatives to meetings on an adhoc basis. + +### Links to the last two community meeting updates the group has given and notable highlights you’d like to share from those. + diff --git a/wg-multitenancy/annual-report-2021.md b/wg-multitenancy/annual-report-2021.md deleted file mode 100644 index fb6a82c1..00000000 --- a/wg-multitenancy/annual-report-2021.md +++ /dev/null @@ -1,53 +0,0 @@ -# 2021 WG Multitenancy Annual Report - -### What was the initial mission of the group and if it's changed, how? - -**Initial Mission:** - -Define the models of multitenancy that Kubernetes will support. Discuss and execute upon any -remaining work that needs to be done to support these models. Create conformance tests that -will prove that these models can be built and used in production environments. - -**Current Mission:** - -We are focusing more on projects using Kubernetes than trying to directly change the API machinery, -which is a huge and potentially intractable problem. We are continuing to work on conformance -testing as part of one of our projects. - -### What’s the current roadmap until completion? - -**We have three projects we are incubating:** - -* Multi-Tenancy Benchmarks https://github.com/kubernetes-sigs/multi-tenancy/tree/master/benchmarks -* Virtual Cluster Project https://github.com/kubernetes-sigs/multi-tenancy/tree/master/incubator/virtualcluster -* Hierarchical Namespace Controller https://github.com/kubernetes-sigs/multi-tenancy/tree/master/incubator/hnc - -These are all in active development, and we’re making good progress. Google Cloud has adopted HNC in beta. -MTB is going to be a great platform for the conformance test suite expansion. Virtual Cluster Project is -graduating out of our incubator and into its own repo! HNC will probably follow soon. - -The roadmap is documented in the [working group project plan](https://docs.google.com/document/d/1U8RQQmTUjxgMZY05HG2f7b3KsB94BhK4Ko6aWbLNXcc/edit). - -### Have you produced any artifacts, reports, white papers to date? - -You can find a bunch of our docs here: https://github.com/kubernetes-sigs/multi-tenancy/tree/master/docs - -### Is the group active? healthy? contributors from multiple companies and/or end user companies? - -Yes, it’s one of the most egalitarian working groups I’ve seen. We have active contributors and participants -from all over the industry, and a lot of drive bys from consumers of Kubernetes who are just trying to -configure clusters for multi-tenancy and have questions. Our incubating projects are led by people from -Google, Nirmata, Alibaba, and Medtronic, have reviewers and participants from other companies, and the WG chairs work at VMware and Cisco. -We have a very diverse group of presenters from different companies who are all trying to solve the same problems, and we all have -the philosophy of learning from each other and sharing. - -### Is everything in your readme accurate? posting meetings on youtube? - -Yes and Yes. - -### Do you have regular check-ins with your sponsoring SIGs? - -We have a huge number of sponsoring SIGs, many of them send representatives to meetings on an adhoc basis. - -### Links to the last two community meeting updates the group has given and notable highlights you’d like to share from those. - -- cgit v1.2.3