Update README.md

This commit is contained in:
Abigail McCarthy 2023-02-23 11:08:06 -05:00
parent ca84f578f1
commit a15a289c16
1 changed files with 15 additions and 15 deletions

View File

@ -4,11 +4,11 @@ The Kubernetes Localization Subproject is owned by [SIG Docs](https://github.com
The Kubernetes documentation has been localized into several different languages. Each localization is owned by a team of individuals that speaks the 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.
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 (biweekly). [Convert it to your timezone](http://www.thetimezoneconverter.com/?t=15:00&tz=UTC)
Regular Localization Meeting: The first Monday of the month at 15:00 UTC. [Convert it to your timezone](http://www.thetimezoneconverter.com/?t=15:00&tz=UTC)
- [Meeting notes and Agenda](https://docs.google.com/document/d/1NwO1AN8Ea2zlK8uAdaDAKf1-LZDAFvSewIfrKqfl5No/edit#)
- [Meeting recordings](https://www.youtube.com/playlist?list=PL69nYSiGNLP3b5hlx0YV7Lo7DtckM84y8)
@ -23,7 +23,7 @@ A localization team may also hold language specific meetings. If you are interes
## Contact
- Slack: [#sig-docs-localizations](https://kubernetes.slack.com/archives/C0191RDKHU1) Each localization also has a language specific channel, noted [below](#localization-teams).
- Slack: [#sig-docs-localizations](https://kubernetes.slack.com/archives/C0191RDKHU1) Each localization team also has a language specific channel, noted [below](#localization-teams).
- Mailing list: https://groups.google.com/g/kubernetes-sig-docs-localization
## Responsibilities
@ -34,30 +34,30 @@ The Localization Subproject lead is **responsible** for
- 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
- Helping localization teams understand SIG Docs processes, especially when languages are starting out.
- Making sure that [Localization process documentation](https://kubernetes.io/docs/contribute/localization/) 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
- 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
## Skills and Experience Required
- Familiar with the [localization processes](https://kubernetes.io/docs/contribute/localization/).
- Have strong written and verbal communication skills.
- A working knowledge of Github
- A working knowledge of Github.
- A working knowledge of kubernetes/website [review and merge processes](https://kubernetes.io/docs/contribute/review/).
Time commitment for a Localization lead is 1-2 hours per week.
# Localization teams
## Localization teams
The following is a list of all localization teams. Localization teams are responsible for keeping this list up-to-date.
| Language | Leads | Docs Link | Slack Channel | Language specific meeting details (if available)|
|--|--|--|--|--|
| Language | Leads | Docs Link | Slack Channel |
|--|--|--|--|
| Arabic | | In progress | [#kubernetes-docs-ar](https://kubernetes.slack.com/archives/CP9FKRD51) |
| Bengali | Shahriyar Al Mustakim Mitul ([@mitul3737](https://github.com/mitul3737)) | In progress | [#kubernetes-docs-bn](https://kubernetes.slack.com/archives/CQ0TD298C) |
| Chinese | Qiming Teng ([@tengqm](https://github.com/tengqm)) | https://kubernetes.io/zh-cn/ | [#kubernetes-docs-zh](https://kubernetes.slack.com/archives/CE3LNFYJ1) |
@ -76,14 +76,14 @@ The following is a list of all localization teams. Localization teams are respon
"In progress" teams have started localization work, but are not yet live on the Kubernetes site.
## Localization team structure
### 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](https://kubernetes.io/docs/contribute/localization/).
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 precesses](https://kubernetes.io/docs/contribute/review/) of the kubernetes/website repo.
- Timely reviews and merging PRs for their languages according to the [review and merge processes](https://kubernetes.io/docs/contribute/review/) 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](https://kubernetes.io/community/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](https://github.com/kubernetes/community/tree/master/committee-code-of-conduct).