Skip to content

Latest commit

 

History

History
146 lines (106 loc) · 9.11 KB

annual-report-2022.md

File metadata and controls

146 lines (106 loc) · 9.11 KB

2022 Annual Report: SIG API Machinery

Current initiatives

  1. What work did the SIG do this year that should be highlighted?

  2. What initiatives are you working on that aren't being tracked in KEPs?

  3. KEP work in 2022 (v1.24, v1.25, v1.26):

Project health

  1. What areas and/or subprojects does your group need the most help with? Any areas with 2 or fewer OWNERs? (link to more details)

    • 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 - dependency updates span multiple SIGs due to which the entire PR also comes under the purview of API Machinery.
    • Technical support for triages could have improvements, for example sometimes we remove API Machinery in PRs, and every update to the issue / PR get's us re-tagged again.
    • 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.
    • The subprojects that have a total reviewer + approver count <= 2 across all its OWNERS files are as follows:
    • There also exist parts of a subproject that come under review/approver crunch. One example is the cacher component. Components like this come under a subproject with enough OWNERS but the particular component itself might be dependent on the expertise of a small subset of these OWNERS.

  2. What metrics/community health stats does your group care about and/or measure?

On the technical health of the SIG, we look at the following metrics tracked in Devstats:

  • Ratio of open/close PRs
  • Ratio of open/close issues
  • Overall age of open issues
  • Number of active contributors to the SIG

On the inclusion health of the SIG, we look at:

  • Representation of diversity and of multiple companies in the SIG participants

  1. Does your CONTRIBUTING.md help new contributors engage with your group specifically by pointing to activities or programs that provide useful context or allow easy participation?

    • No, one can be created. The README points contributors to SIG meetings and triage meetings that happens twice a week.

  2. If your group has special training, requirements for reviewers/approvers, or processes beyond the general contributor guide, does your CONTRIBUTING.md document those to help existing contributors grow throughout the contributor ladder?

    • No, it can be improved.

  3. Does the group have contributors from multiple companies/affiliations?

    • Yes, there are contributors from multiple companies. We see all sorts of contributions, varying from issues, to comments, to PRs, to designs, to sig meeting participation, and user-survey data.

  4. Are there ways end users/companies can contribute that they currently are not? If one of those ways is more full time support, what would they work on and why?

    • There currently isn't a charted course for end users/companies to get more involved.
    • The most common, albeit ad-hoc, method has been showing up in the SIG meeting and starting/continuing discussions on the slack channel.
    • There is plenty of areas were the SIG could use help in reviewing and maintaining the code, but it's a complicated code base to ramp up. If people don't stick around long enough, the effort does not make sense.

Membership

  • Primary slack channel member count: 3912
  • Primary mailing list member count: 771
  • Primary meeting attendee count (estimated, if needed): 30
  • Primary meeting participant count (estimated, if needed): 10
  • Unique reviewers for SIG-owned packages: 111
  • Unique approvers for SIG-owned packages: 94

Include any other ways you measure group membership

Subprojects

Continuing:

  • component-base
  • control-plane-features
  • idl-schema-client-pipeline
  • json
  • kubernetes-clients
  • server-api-aggregation
  • server-binaries
  • server-crd
  • server-frameworks
  • server-sdk
  • universal-machinery
  • yaml

Working groups

Continuing:

  • API Expression
  • Multitenancy
  • Structured Logging

Operational

Operational tasks in sig-governance.md:

  • README.md reviewed for accuracy and updated if needed
  • CONTRIBUTING.md reviewed for accuracy and updated if needed (or created if missing and your contributor steps and experience are different or more in-depth than the documentation listed in the general contributor guide and devel folder.)
  • Subprojects list and linked OWNERS files in sigs.yaml reviewed for accuracy and updated if needed
  • SIG leaders (chairs, tech leads, and subproject owners) in sigs.yaml are accurate and active, and updated if needed
  • Meeting notes and recordings for 2022 are linked from README.md and updated/uploaded if needed
  • Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: - KubeCon + CloudNativeCon NA 2022 Maintainer Track