Skip to content
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Go to file
Cannot retrieve contributors at this time

2021 Annual Report: SIG Docs

Current initiatives

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

    • SIG Docs put meaningful effort into growing its contributor and reviewer base in 2021, introducing a shadow program for PR Wrangling as well as dedicating more time to being active via our Slack community channel. This is an ongoing effort to grow our contributor base to a stable number, alongside easing the burden on our small group of reviewers and approvers.
    • Ahead of the dockershim removal in the Kubernetes 1.24 release, SIG Docs has been collaborating with various community members and the CNCF towards ensuring updation and creation of content in the form of documentation, blog posts etc. With weekly meetings and a project board to track progress, this has allowed for us to invite contributors across experience levels to help us keep the Kubernetes website updated and relevant ahead of the major change.
    • Alongside growing our contributor base, SIG Docs also worked on a leadership transition strategy to bring community members into leadership roles. Via a specialized six month mentorship program expertly led by Steering Committee member Paris Pittman, SIG Docs was able to grow its leadership cohort for the main SIG, as well as some of its subgroups, adding new co-chairs and tech leads.
  2. What initiatives are you working on that aren't being tracked in KEPs?

    • One of our main initiatives is to ensure consistent maintenance of the Kubernetes documentation website and blog. As an existing subproject within SIG Docs, we have a project board tracking our efforts for the Kubernetes blog.
    • Localization Subproject: SIG Docs is working on formalizing the localization work that has been ongoing for some time, with appointed leads of this initiative as well as recognizing the contributions of various community members across the different languages the Kubernetes website has been translated into. This subproject will be finalized by Q1 2022, with all active localizations informed and updated. The issue tracking the formalizing process can be viewed here.
    • New Contributor Ambassador Program: As a continuation of our push to grow the SIG Docs contributor base, we're working on a specalized role that aims to support new and would-be contributors get up to speed with our processes and workflows. This role would be capped at six months for it to be shared amongst the community, with this feeding into a possible reviewer funnel as contributors get more comfortable with providing feedback to others. The issue tracking the formalization and documentation of this role can be viewed here.
  3. KEP work in 2021 (continuous and does not target any release):

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)

    • The blog subproject is particularly short on resources and attention. At the moment a very small pool of active editors are the constraint / most critical resource for article publication. One editor is involved in the majority of published articles; other editors are perhaps even more stretched with other Kubernetes contributions and involvement with other SIGs.
      • Whilst there is work under way to move other people along the contribution ladder, the blog subproject remains constrained.
    • SIG Docs would welcome more contributors to form a stable pool for the blog subproject in particular and for SIG Docs, generally.
    • Require guidelines on how we could ramp up folks nominated to the New Contributor Ambassador role specific to SIG Docs.
    • One localization (Ukrainian) is primarily worked on by people based in Ukraine, where the ongoing and intensifying conflict creates challenges that take priority over open source contribution.
  2. What metrics/community health stats does your group care about and/or measure?

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

  4. If your group has special training, requirements for reviewers/approvers, or processes beyond the general contributor guide, does your 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. During KubeCons we also do introduction presentations and mentoring sessions to try and funnel contributors in to our SIG. Some of them are listed below,
  5. Does the group have contributors from multiple companies/affiliations?

    • We have a contributor base spread across 98 companies with top 50% contributions coming our way from IBM, Google, VMWare, RedHat, and NEC Corporation. A special mention for all the independent contributors who feature third on the list in terms of number of contributions.
  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 will be finalizing it as a localization subproject. We aim for the subproject to, potentially, provide more avenues for contribution. More details around leadership and the formalization process can be found in this message sent to


  • Primary slack channel member count: 1876
  • Primary mailing list member count: 453
  • Primary meeting attendee count (estimated, if needed): 10
  • Primary meeting participant count (estimated, if needed): 6
  • Unique reviewers for SIG-owned packages: 76
  • Unique approvers for SIG-owned packages: 93

Include any other ways you measure group membership



In 2021, SIG Docs started to formalize the localization subgroup into an official subproject.


Operational tasks in