kubernetes / kubernetes/community
REQUEST: New Slack channel for Thai-speaking Kubernetes docs localization
- Dominant language
- Jupyter Notebook
- Stars
- 13k
- Forks
- 5.4k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 29
Description
### GitHub Username
jaruwat-panturat
### Slack Username
Benz Panturat
### What Type of Request is it (Channel, User Group, Bot, Token, or Webhook)?
channel
### Name of Requested Resource
kubernetes-docs-th
### Is this request supported by an existing Kubernetes group (SIG, WG, Team, Subproject)? If so, please name them here, and tag a SIG lead who can verify the request.
_No response_
### Description of Request
Requesting a Slack channel for the newly-forming Thai (th) localization of the Kubernetes documentation, following the same pattern as existing localization channels (e.g. kubernetes-docs-id, kubernetes-docs-ko, kubernetes-docs-fa).
We are members of #sig-docs and #sig-docs-localizations, and have landed a first contribution (Thai translation of the CNCF Code of Conduct, merged: cncf/foundation#1479). We're about to post an announcement in #sig-docs-localizations and would like this channel available for the team to coordinate the localization launch per https://kubernetes.io/docs/contribute/localization/.
### Justification for Request
A dedicated channel lets the Thai localization team coordinate translation work, PR reviews, and terminology decisions without adding noise to the general #sig-docs-localizations channel. It's the same pattern other active language teams (e.g. Indonesian, Korean, Portuguese) already use, and gives SIG Docs a clear, persistent place to track this effort as the contributor base grows.
Contributor guide
Research direction
Start by reviewing the localization guidance at https://kubernetes.io/docs/contribute/localization/ and the existing #kubernetes-docs-id, #kubernetes-docs-ko, and #kubernetes-docs-fa channel pattern. Confirm the Thai team’s coordination in #sig-docs and #sig-docs-localizations, then request or create kubernetes-docs-th; done means the dedicated channel is available for the localization launch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- documentation, localization
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100