i18n changes approvable by sig-localization teams #26921
Labels
area/web-development
Issues or PRs related to the kubernetes.io's infrastructure, design, or build processes
kind/feature
Categorizes issue or PR as related to a new feature.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
sig/docs
Categorizes an issue or PR as relevant to SIG Docs.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
What would you like to be added
Currently, i18n files live under /i18n at the root folder and only sig-docs-en-owners can approve those files. Under the
i18n
folder resides the toml files containing localised strings for each language used across the site. It would be nice to add some mechanism to enable sig-docs-localisation approvers permission to approve changes on their language toml files.Why is this needed
This will enable better handling of the i18n language files as will be owned by the corresponding localization team and instead of failing to the sig-docs-en team.
Comments
This was discussed on the last sig-docs and sig-docs-localization meetings.
/area web-development
/kind feature
/sig docs
/language en
/language es
The text was updated successfully, but these errors were encountered: