Skip to content

Latest commit

 

History

History
182 lines (128 loc) · 13 KB

annual-report-2022.md

File metadata and controls

182 lines (128 loc) · 13 KB
Raw

2022 Annual Report: SIG Storage

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. What initiatives are you working on that aren't being tracked in KEPs?

  4. 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)

    • We need more contributors to help with fixing bugs and code reviewing across the board. For contributors who are interested in getting more involved in SIG-Storage, please review the CONTRIBUTING Guide and come to SIG-Storage meetings to find a project that you are interested in helping with. Help make code contributions and learn how storage works in Kubernetes. After you are getting familiar with the code, help with code reviews.
    • We now have a weekly issue triage meeting to discuss issues: https://github.com/orgs/kubernetes-csi/projects/52/views/3. We hope more people can join this meeting and contribute.

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

  3. 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?

    • Our CONTRIBUTING.md has presentations, docs, and videos to help new contributors get familiar with Kubernetes Storage concepts. It also has instructions on how to get involved in SIG Storage.

  4. 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?

    • We don’t have special training or documents. We just follow the contributor guide available in the K8s community. Any suggestions are welcome.

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

    • Yes.

  6. 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?

    • We do have a small number of contributors from end user companies. Some are working on adding new features. Any help to get them to contribute more will be great.
    • Here is our ask:
      • CSI conformance tests for CSI drivers.
      • Write more tests; monitor test grid health; work on test framework out of tree; enhance CSI release tools.
      • Doc writer to improve docs on CSI side and in general in Storage side.
      • We have a weekly issue triage meeting, but would appreciate help with more efficient issue triage.

Membership

  • Primary slack channel member count: 5373 (sig-storage), 1399 (csi)
  • Primary mailing list member count: 749
  • Primary meeting attendee count (estimated, if needed): 25
  • Primary meeting participant count (estimated, if needed): 25
  • Unique reviewers for SIG-owned packages: 36
  • Unique approvers for SIG-owned packages: 30

Include any other ways you measure group membership

Subprojects

Continuing:

  • external-storage
  • git-sync
  • gluster-provisioner
  • kubernetes-cosi
  • kubernetes-csi
  • mount-utils
  • nfs-provisioner
  • volume-populators
  • volumes

Working groups

Continuing:

  • Data Protection

    • KEP related work done by the DP WG is tracked in our project tracking spreadsheet and discussed in SIG Storage meetings.

  • Multitenancy

    • We don’t have regular communication with Multi Tenancy WG.

  • Policy

    • We don’t have regular communication with Policy WG.

  • Structured Logging

    • Communication is through Structured Logging PR submission and reviews.

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: