Tracking Ukrainian localization progress

[MaxymVlasov]

Hey folks!

Maintainers

@MaxymVlasov

For New Contributors:

1. Assign to one of most wanted issues or any non-assigned issue.
   ^{If you have troubles with assign - just leave message in issue like "Work on this" and I send invite to org and assign this issue to you}
2. Make fork of k/website.
3. Read Localization guidelines.
4. Translate.
5. Create PR to k/website.

Help

If you need any help - join #kubernetes-docs-uk channel in Kubernetes Slack and feel free to ask.

Existing localization problems/updates

If you found any issues with translated content - create issue in k/website with /language uk.

kubernetes-i18n-ukrainian/website should be used only for simplify localization progress.

/assign
/language uk
/kind feature
/priority backlog
/lifecycle frozen

[sftim]

🇺🇦 🎉

[sftim]

/area localization

[seokho-son]

Hi @MaxymVlasov
As a sig-docs localization subproject lead, I would like to check if this issue remains useful and if there's a general willingness to keep it open as is. (sig-docs is endeavoring to manage the quantity of open issues.)

[MaxymVlasov]

Hi @seokho-son
If you can suggest how to better point newcomers to what that should do - I'm all ears.

In theory, it could be moved to https://github.com/kubernetes/website/blob/main/README-uk.md, but I'm not sure that someone will go to it, as in repo README there are no mentions that in localization README could be something specific for localization, and "go check it first and only then general contribution guides"

[seokho-son]

Hi @MaxymVlasov :)
Thanks for the feedback. I think the Ukrainian team can create language-specific-localization-guide and share the guide to tentative contributors. And feel free to utilize README-uk.md for something specific for localization.

Also, you can keep this issue as well if you think it is still useful. We are just checking if there is not useful open issues.