kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
community/sig-docs/annual-report-2022.md

9.0 KiB
Raw Permalink Blame History

2022 Annual Report: SIG Docs

Current initiatives

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

    • Contributors across many SIGs, companies, and foundations worked together with SIG Docs to finalize the dockershim removal from the Kubernetes website
    • Our Localization subproject was officially documented in our community resources, with two subproject leads appointed and the area/localization label created
    • The Hindi localization, our first localized set of documentation using the Devanagari script, officially launched

  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):

N/A

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)

    • Our localizations have two owners as a minimum default, thus, SIG Docs doesn't count this as a project health issue. Our Localization subproject had one of its leads move to Emeritus in early 2023, however, we're in the process of mentoring a second lead throughout 2023.
    • Our blog subproject is still short on resources, however, we have been able to add an additional reviewer over the last year. We're still looking to add to the very small pool of active editors, which are our most critical resource for article publication.
    • We're looking for active contributors to take on the Issue Wrangling role, which would require some involvement in community meetings and Slack discussion to better triage issues and bugs.
    • Project management is an area that our leads have been trying to cover, but SIG Docs overall could use more help in this space. Help with coordinating large-scale efforts such as the Katacoda tutorial replacement, or organizing the various attempts to debug Netlify issues, would be a huge benefit

  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?

    • It is updated to the best of our knowledge.

  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 have a well-documented guide that details how folks can get started and the various ways in which they can scale the contributor ladder.
    • We actively assign good-first-issue labels to issues that we think early-lifecycle contributors could begin with, with other contributors sharing these issues actively in the #sig-docs Slack channel. We've also created introduction presentations and mentoring sessions at various KubeCon events to try and funnel contributors into our SIG. Some of them are listed below:

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

    • Yes. We have a contributor base spread across 98 companies with the top 50% of contributions coming from IBM, DaoCloud, Google, NEC Corporation, VMWare, and Red Hat. We'd like to give a shout-out to all of the independent contributors who feature third on this ranking in terms of number of contributions
    • Our group also strives to be a positive example when it comes to Diversity, Equity, and Inclusion, where we ensure we have SIG leads from some of our biggest membership bases (India, China), alongside women in technical leadership roles (co-chairs, tech leads)

  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?

    With a contributor base that is spread globally, SIG Docs identified a potential opportunity for diversifying our documentation via multiple language support. Given the wide audience, this helps in making it more inclusive and user friendly for non-native English users of Kubernetes. Towards formalizing this ongoing initiative, SIG Docs finalized a localization subproject to, potentially, provide more avenues for contribution.

Membership

  • Primary slack channel member count: 2264
  • Subproject slack channel member count:
    • #sig-docs-blog: 342
    • #sig-docs-localizations: 320
  • Primary mailing list member count: 576
  • Primary meeting attendee count (estimated, if needed): 12
  • Primary meeting participant count (estimated, if needed): 6
  • Unique reviewers for SIG-owned packages:
  • Unique approvers for SIG-owned packages:

Include any other ways you measure group membership

Subprojects

New in 2022:

  • localization

Continuing:

  • kubernetes-blog
  • reference-docs
  • website

Working groups

Operational

Operational tasks in sig-governance.md: