Advanced Contribution Roles: New Contributor Ambassador, Sponsor, and SIG Co-chair

the release. - Mentor other SIG Docs contributors who want to learn how to do this role in the future. This is known as "shadowing". - Publish the documentation changes related to the release when the release artifacts are published. Coordinating a release is typically a 3-4 month commitment, and the duty is rotated among SIG Docs approvers. ## Serve as a New Contributor Ambassador SIG Docs [approvers](/docs/contribute/participate/roles-and-responsibilities/#approvers) can serve as New Contributor Ambassadors. New Contributor Ambassadors welcome new contributors to SIG-Docs, suggest PRs to new contributors, and mentor new contributors through their first few PR submissions. Responsibilities for New Contributor Ambassadors include: - Monitoring the [#sig-docs Slack channel](https://kubernetes.slack.com) for questions from new contributors. - Working with PR wranglers to identify [good first issues](https://kubernetes.dev/docs/guide/help-wanted/#good-first-issue) for new contributors. - Mentoring new contributors through their first few PRs to the docs repo. - Helping new contributors create the more complex PRs they need to become Kubernetes members. - [Sponsoring contributors](/docs/contribute/advanced/#sponsor-a-new-contributor) on their path to becoming Kubernetes members. - Hosting a monthly meeting to help and mentor new contributors. Current New Contributor Ambassadors are announced at each SIG-Docs meeting and in the [Kubernetes #sig-docs channel](https://kubernetes.slack.com). ## Sponsor a new contributor SIG Docs [reviewers](/docs/contribute/participate/roles-and-responsibilities/#reviewers) can sponsor new contributors. After a new contributor has successfully submitted 5 substantive pull requests to one or more Kubernetes repositories, they are eligible to apply for [membership](/docs/contribute/participate/roles-and-responsibilities/#members) in the Kubernetes organization. The contributor's membership needs to be backed by two sponsors who are already reviewers. New docs contributors can request sponsors by asking in the #sig-docs channel on the [Kubernetes Slack instance](https://kubernetes.slack.com) or on the [SIG Docs mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-docs). If you feel confident about the applicant's work, you volunteer to sponsor them. When they submit their membership application, reply to the application with a "+1" and include details about why you think the applicant is a good fit for membership in the Kubernetes organization. ## Serve as a SIG Co-chair SIG Docs [members](/docs/contribute/participate/roles-and-responsibilities/#members) can serve a term as a co-chair of SIG Docs. ### Prerequisites A Kubernetes member must meet the following requirements to be a co-chair: - Understand SIG Docs workflows and tooling: git, Hugo, localization, blog subproject - Understand how other Kubernetes SIGs and repositories affect the SIG Docs workflow, including: [teams in k/org](https://github.com/kubernetes/org/blob/master/config/kubernetes/sig-docs/teams.yaml), the [process in k/community](https://github.com/kubernetes/community/tree/master/sig-docs), plugins in [k/test-infra](https://github.com/kubernetes/test-infra/), and the role of

This section describes the roles of New Contributor Ambassadors (welcoming and mentoring new contributors), Sponsors (recommending contributors for Kubernetes membership after 5 PRs), and SIG Co-chairs (leading SIG Docs, requiring knowledge of workflows, tooling, and interactions with other SIGs).