Skip to content

Latest commit

 

History

History
103 lines (78 loc) · 4.25 KB

community-maintenance.md

File metadata and controls

103 lines (78 loc) · 4.25 KB
Raw

Community Maintenance

This document outlines maintenance tasks that SIG Contributor Experience should be doing on a regular basis. Copy this list into a new Github issue, for example "Community Maintenance Tasks for 2Q 2018". Then people can volunteer to audit different parts of the project at once. These tasks should be done at a minimum of twice a year, but ideally once a quarter.

If any of these tasks can be automated, then do so, however most of these require a human to make a judgement decision. If you find that any one person is in charge of a resource it is your responsibility to bring this issue to SIG Contributor Experience so that important parts of Kubernetes infrastructure are not assigned to one sole person.

Slack

  • Channels - Anything out of place or not following the guidelines?
    • For community group channels - Check to see if there is a purpose, pinned documents like agendas, and other best practices being used in the channel. These are not required but are useful.
  • Audit the Integrations and apps
  • Audit the user tokens
  • Audit the Emojis
  • Generate a Slack data report to share with the community (optional)

GitHub

  • Audit Org admin permissions
  • Audit Integrations
  • Check Label usage (education, deprecation, etc)
  • Is the PR and/or issue message still good/the best?
  • Check community PR Template
  • Check community Issue Templates

Calendars

  • Check that the calendar works
  • Make sure all SIG, WG, and other community meetings are showing - especially check new groups that were created in the last quarter
  • Make sure that invites have more than one owner, shared with the mailing list distro, and have an agenda attached plus zoom URL and telephone dial information.

SIGS

  • Ensure everyone in sigs.yaml is subscribed to sigs-leads mailing list
  • Ensure that chairs and leads are accurate in the sigs.yaml

YouTube

  • Check sharing on all the playlists
    • Should only be shared with leads or people appointed by leads
    • Either remove other people or regenerate a new collaboration URL
  • Check admin permissions on the Kubernetes account
  • Fix any videos accidentally tagged as unlisted
  • Generate a YouTube traffic report to share with the community (optional)

Zoom

  • Ensure leads have access to their upgraded Zoom account
  • If appropriate change the password if a SIG has changed leadership
    • Contact CNCF to adjust upgraded licenses if necessary

Community Meeting

  • Generate an archive of the community meeting notes for the quarter if necessary
    • Ensure the retrospective section has links to the retrospective for the releases
    • Ensure the demo section is filled out and demos are assigned dates
    • Ensure the agenda template and hosting guide are up to date
  • Ensure the SIG Schedule have SIGs assigned for the next few months
    • Ensure the assigned SIGs in this sheet match the actual SIGs in sigs.yaml. Double check that a SIG hasn't missed an update this past cycle and if they have schedule them for an upcoming meeting

Devstats

  • Ensure new repos have been added to the correct repo group.

Properties Managed by the CNCF

The CNCF provides support to Kubernetes for the following properties, you do not need to check them, however members of SIG Contributor Experience should have a working relationship with the administrators of the following properties:

  • Twitter
  • Blog
  • GCP Organization
  • Devstats

Unknown State

Properties we should learn how to maintain, or at least document:

  • Kubernetes.io DNS
  • Kubernetes.io URL redirector