community/sig-docs/localization-subproject
Abigail McCarthy fb896507d7
Apply suggestions from code review
Co-authored-by: Seokho Son <shsongist@gmail.com>
2023-09-22 12:05:17 -04:00
..
README.md Apply suggestions from code review 2023-09-22 12:05:17 -04:00

README.md

Localization Subproject

The Kubernetes Localization Subproject is owned by SIG Docs and run by the Subproject leads.

The Kubernetes documentation is localized into many different languages. Each localization is owned by a team of contributors that specialize in translating (localizing) the Kubernetes docs into a specific language. A localization team is a self-sufficient community responsible for prioritizing work, translating content, and reviewing and merging PRs into the kubernetes/website repo for their localization.

The Localization Subproject's aim is to provide a place for localization teams to share ideas and standardize processes across all localizations. This page covers documentation, processes, and roles for the Kubernetes localization teams and the Localization Subproject.

Meetings

Regular Localization Meeting: The first Monday of the month at 15:00 UTC. Convert it to your timezone

A localization team may also hold language specific meetings. If you are interested in attending a language specific meeting see the Localization Teams section for details on how to contact each localization team.

Subproject Leadership

  • Subproject leads:

Contact

Responsibilities

The Localization Subproject lead is responsible for

  • Leading Subproject meetings and taking notes.
  • Driving collaborative discussions and decisions around localization processes and standards.
  • Ensuring the communication of localization and SIG Docs policy changes to localization teams.
  • Advocating for localization-friendly practices within SIG Docs and the broader Kubernetes community.
  • Helping localization teams understand SIG Docs processes, especially when languages are starting out.
  • Making sure that Localization process documentation is kept up to date.

The Localization Subproject lead is not responsible for

  • Running localization efforts for a language.
  • Dictating how localization teams do work or organize.
  • Making decisions for localizations policies or teams without the localization team's input.

Skills and Experience Required

Time commitment for a Localization lead is 1-2 hours per week.

Localization teams

The following is a list of all localization teams. Localization teams are responsible for keeping this list up-to-date.

Language Docs Links Owners Slack Channel
Arabic In progress In progress #kubernetes-docs-ar
Bengali In progress In progress #kubernetes-docs-bn
Chinese https://kubernetes.io/zh-cn/ sig-docs-zh-owners #kubernetes-docs-zh
French https://kubernetes.io/fr/ sig-docs-fr-owners #kubernetes-docs-fr
German https://kubernetes.io/de/ sig-docs-de-owners #kubernetes-docs-de
Hindi https://kubernetes.io/hi/ sig-docs-hi-owners #kubernetes-docs-hi
Indonesian https://kubernetes.io/id/ sig-docs-id-owners #kubernetes-docs-id
Italian https://kubernetes.io/it/ sig-docs-it-owners #kubernetes-docs-it
Japanese https://kubernetes.io/ja/ sig-docs-ja-owners #kubernetes-docs-ja
Korean https://kubernetes.io/ko/ sig-docs-ko-owners #kubernetes-docs-ko
Portuguese https://kubernetes.io/pt-br/ sig-docs-pt-owners #kubernetes-docs-pt
Russian https://kubernetes.io/ru/ sig-docs-ru-owners #kubernetes-docs-ru
Spanish https://kubernetes.io/es/ sig-docs-es-owners #kubernetes-docs-es
Ukrainian https://kubernetes.io/uk/ sig-docs-uk-owners #kubernetes-docs-uk
Vietnamese https://kubernetes.io/vi/ sig-docs-vi-owners #kubernetes-docs-vi

"In progress" teams have started localization work, but are not yet live on the Kubernetes site.

Localization team structure

Anyone can start a new localization effort for any language or join an ongoing localization team. If you are interested in learning more about specific localization requirements or processes, see the Localization Contributing Guide.

Localization teams are self-sufficient communities within SIG Docs and are responsible for

  • Localizing content on kubernetes.io into their chosen language.
  • Timely reviews and merging PRs for their languages according to the review and merge processes of the kubernetes/website repo.
  • Building a community that can support their localization efforts. Note that you need at least two contributors to begin a localization team because contributors can't approve their pull requests. You will likely need more contributors, reviewers, and approvers to create a sustainable localization effort.
  • Organizing and prioritizing work to localize content.
  • Understanding and following the Kubernetes Code of Conduct within their teams. Questions or concerns around Code of Conduct violations should be raised to the SIG Docs, Localization Subproject leadership, or Kubernetes Code of Conduct Committee.

The Localization Subproject leads and the SIG Docs leadership are always available to help localization teams by answering questions and providing feedback.

Localization team leads

A leader of a localization team is someone who is responsible for helping to guide the localization efforts for a given language. Its recommended that each localization team has at least 2 leads.

Some recommended skills for localization leads include,

  • Excellent written and verbal skills in the given language.
  • Experience with the kubernetes/website repo localization branching strategy.
  • Experience reviewing English language PRs to develop an understanding the review processes and repo structure. It is recommended that leaders participate in the SIG Docs PR Wrangler Shadow Program.

Localization processes

See the Localization Contributing Guide for full information on localization processes and policies. This page includes information on starting a new localization, branching strategies for localizing content, and more.