Skip to content
Switch branches/tags
Go to file
Cannot retrieve contributors at this time

SIG CLI Annual Report 2020

This report reflects back on CY 2020 and was written in March 2021.


  • How are you doing with operational tasks in

    • Is your README accurate? have a file?

    • All subprojects correctly mapped and listed in sigs.yaml?

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


  • 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), 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.
    • 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?

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?

  • 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?

    • 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.