SIG Docs Co-chair Responsibilities, Effective Meetings, and Offboarding

In addition, understand how the [Kubernetes docs release process](/docs/contribute/advanced/#coordinate-docs-for-a-kubernetes-release) works. - Approved by the SIG Docs community either directly or via lazy consensus. - Commit at least 5 hours per week (and often more) to the role for a minimum of 6 months ### Responsibilities The role of co-chair is one of service: co-chairs build contributor capacity, handle process and policy, schedule and run meetings, schedule PR wranglers, advocate for docs in the Kubernetes community, make sure that docs succeed in Kubernetes release cycles, and keep SIG Docs focused on effective priorities. Responsibilities include: - Keep SIG Docs focused on maximizing developer happiness through excellent documentation - Exemplify the [community code of conduct](https://github.com/cncf/foundation/blob/main/code-of-conduct.md) and hold SIG members accountable to it - Learn and set best practices for the SIG by updating contribution guidelines - Schedule and run SIG meetings: weekly status updates, quarterly retro/planning sessions, and others as needed - Schedule and run doc sprints at KubeCon events and other conferences - Recruit for and advocate on behalf of SIG Docs with the {{< glossary_tooltip text="CNCF" term_id="cncf" >}} and its platinum partners, including Google, Oracle, Azure, IBM, and Huawei - Keep the SIG running smoothly ### Running effective meetings To schedule and run effective meetings, these guidelines show what to do, how to do it, and why. **Uphold the [community code of conduct](https://github.com/cncf/foundation/blob/main/code-of-conduct.md)**: - Hold respectful, inclusive discussions with respectful, inclusive language. **Set a clear agenda**: - Set a clear agenda of topics - Publish the agenda in advance For weekly meetings, copypaste the previous week's notes into the "Past meetings" section of the notes **Collaborate on accurate notes**: - Record the meeting's discussion - Consider delegating the role of note-taker **Assign action items clearly and accurately**: - Record the action item, who is assigned to it, and the expected completion date **Moderate as needed**: - If discussion strays from the agenda, refocus participants on the current topic - Make room for different discussion styles while keeping the discussion focused and honoring folks' time **Honor folks' time**: Begin and end meetings on time. **Use Zoom effectively**: - Familiarize yourself with [Zoom guidelines for Kubernetes](https://github.com/kubernetes/community/blob/master/communication/zoom-guidelines.md) - Claim the host role when you log in by entering the host key <img src="/images/docs/contribute/claim-host.png" width="75%" alt="Claiming the host role in Zoom" /> ### Recording meetings on Zoom When you're ready to start the recording, click Record to Cloud. When you're ready to stop recording, click Stop. The video uploads automatically to YouTube. ### Offboarding a SIG Co-chair (Emeritus) See: [k/community/sig-docs/offboarding.md](https://github.com/kubernetes/community/blob/master/sig-docs/offboarding.md)

This section details the responsibilities of a SIG Docs co-chair, including maximizing developer happiness, upholding the code of conduct, scheduling meetings, and advocating for the SIG. It provides guidelines for running effective meetings, such as setting a clear agenda, taking accurate notes, assigning action items, and using Zoom effectively. Finally, it links to the offboarding process for co-chairs.