Setting Up OWNERS Files, Opening a Pull Request, and Launching a New Localization

[`cncf/foundation`](https://github.com/cncf/foundation/tree/main/code-of-conduct-languages) repository to add the code of conduct in your language. ### Set up the OWNERS files To set the roles of each user contributing to the localization, create an `OWNERS` file inside the language-specific subdirectory with: - **reviewers**: A list of kubernetes teams with reviewer roles, in this case, - the `sig-docs-**-reviews` team created in [Add your localization team in GitHub](#add-your-localization-team-in-github). - **approvers**: A list of kubernetes teams with approvers roles, in this case, - the `sig-docs-**-owners` team created in [Add your localization team in GitHub](#add-your-localization-team-in-github). - **labels**: A list of GitHub labels to automatically apply to a PR, in this case, the language label created in [Configure the workflow](#configure-the-workflow). More information about the `OWNERS` file can be found at [go.k8s.io/owners](https://go.k8s.io/owners). The [Spanish OWNERS file](https://git.k8s.io/website/content/es/OWNERS), with language code `es`, looks like this: ```yaml # See the OWNERS docs at https://go.k8s.io/owners # This is the localization project for Spanish. # Teams and members are visible at https://github.com/orgs/kubernetes/teams. reviewers: - sig-docs-es-reviews approvers: - sig-docs-es-owners labels: - area/localization - language/es ``` After adding the language-specific `OWNERS` file, update the [root `OWNERS_ALIASES`](https://git.k8s.io/website/OWNERS_ALIASES) file with the new Kubernetes teams for the localization, `sig-docs-**-owners` and `sig-docs-**-reviews`. For each team, add the list of GitHub users requested in [Add your localization team in GitHub](#add-your-localization-team-in-github), in alphabetical order. ```diff --- a/OWNERS_ALIASES +++ b/OWNERS_ALIASES @@ -48,6 +48,14 @@ aliases: - stewart-yu - xiangpengzhao - zhangxiaoyu-zidif + sig-docs-es-owners: # Admins for Spanish content + - alexbrand + - raelga + sig-docs-es-reviews: # PR reviews for Spanish content + - alexbrand + - electrocucaracha + - glo-pena + - raelga sig-docs-fr-owners: # Admins for French content - perriea - remyleone ``` ### Open a pull request Next, [open a pull request](/docs/contribute/new-content/open-a-pr/#open-a-pr) (PR) to add a localization to the `kubernetes/website` repository. The PR must include all the [minimum required content](#minimum-required-content) before it can be approved. For an example of adding a new localization, see the PR to enable [docs in French](https://github.com/kubernetes/website/pull/12548). ### Add a localized README file To guide other localization contributors, add a new [`README-**.md`](https://help.github.com/articles/about-readmes/) to the top level of [kubernetes/website](https://github.com/kubernetes/website/), where `**` is the two-letter language code. For example, a German README file would be `README-de.md`. Guide localization contributors in the localized `README-**.md` file. Include the same information contained in `README.md` as well as: - A point of contact for the localization project - Any information specific to the localization After you create the localized README, add a link to the file from the main English `README.md`, and include contact information in English. You can provide a GitHub ID, email address, [Slack channel](https://slack.com/), or another method of contact. You must also provide a link to your localized Community Code of Conduct. ### Launch your new localization When a localization meets the requirements for workflow and minimum output, SIG Docs does the following: - Enables language selection on the website. - Publicizes the localization's availability through [Cloud Native Computing Foundation](https://www.cncf.io/about/)(CNCF) channels, including the [Kubernetes blog](/blog/). ## Localize content Localizing *all* the Kubernetes documentation is an enormous task. It's okay to

This section details the steps to set up OWNERS files by defining reviewers, approvers, and labels for the language-specific subdirectory, updating the `OWNERS_ALIASES` file with the new Kubernetes teams for the localization, and providing an example of a Spanish OWNERS file. It also covers opening a pull request to add the localization to the `kubernetes/website` repository, including all minimum required content. Furthermore, it explains how to add a localized README file to guide localization contributors, and the steps SIG Docs takes to launch a new localization, including enabling language selection on the website and publicizing the localization's availability through CNCF channels.