Skip to content

Localization: Simplify the localization workflow and introduce language-specific localization committers #104

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
makihh wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Localization: Simplify the localization workflow and introduce language-specific localization committers #104

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion website/content/en/contribute/ways-to-contribute/localizations/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,16 @@ The Platform Engineering artifacts and website are initially developed in Englis

While each localization is unique, we encourage you to familiarlize yourself with [past localization PRs](https://github.com/Cloud-Native-Platform-Engineering/cnpe-community/issues?q=label%3Alocalization+) and the [Kubernetes SIG-Docs localization documentation](https://kubernetes.io/docs/contribute/localization) for general guidelines and lessons learned.

The SIG-Docs team has a much broader remit than this Community requires, so be aware that the workflow including slack channels, opening PRs, and website owner reviews will be done via the same process as all other Community postings, just with the added requirement of a native language speaker review.
To help maintain translation quality and consistency, each localization language should have at least one localization committer. These reviewers are managed through the corresponding language directory's `CODEOWNERS` file.

The general localization workflow is:

1. Optionally open an issue
2. Open a PR
3. Have the PR reviewed by at least one localization committer for that language
- Check grammar, syntax, and overall language quality
- Verify the accuracy of the translation
4. Merge

It is worth reiterating what the SIG-Docs team has stated:

Expand Down