kubernetes
🇺🇦 Ukrainian localization of Kubernetes documentation
Description
As per request https://github.com/kubernetes/website/pull/45382#issuecomment-2391198533 from @sftim I provide this huge PR with Ukrainian localization of the Kubernetes.
This PR contains a complete translation of all Kubernetes documentation materials as of now (Saturday, October 26, 2024)
I hope that the adoption of this PR allows us to further expand the spread of new technologies around the world.
Issue
Closes: #
Pull request preview available for checking
Built without sensitive environment variables
| Name | Link |
|---|---|
| Latest commit | 2828c3363e5bf51a022e3ee9c81d6016027c840b |
| Latest deploy log | https://app.netlify.com/projects/kubernetes-io-main-staging/deploys/698614f05ce46c000843dee2 |
| Deploy Preview | https://deploy-preview-48551--kubernetes-io-main-staging.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify project configuration.
![netlify[bot] avatar](https://avatars.githubusercontent.com/in/13473?v=4 "Published by a pub.dev verified publisher"){kind=small}
/hold
This PR is too large to review, but it is still really useful: other contributors can carve out smaller reviewable PRs, and get those merged one by one.
Because there's a lot of valuable work in here: /lifecycle frozen
We should only close this if / when we are sure we no longer want to keep it around.
@sftim: The lifecycle/frozen label cannot be applied to Pull Requests.
In response to this:
Because there's a lot of valuable work in here: /lifecycle frozen
We should only close this if / when we are sure we no longer want to keep it around.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
@sftim thanks for helping 🙏.
I would like to ask, how do you estimate how much time it will take with the current workflow to accept the entire Ukrainian translation?
It's hard to estimate because the situation may change. At the current rate: maybe 5 years. However before then, more contributors may arrive.
At the current rate: maybe 5 years. However before then, more contributors may arrive.
Perhaps the move toward implementing a system of support and work with translations (https://github.com/kubernetes/website/issues/45756) will help speed up the process?
Perhaps the move toward implementing a system of support and work with translations (https://github.com/kubernetes/website/issues/45756) will help speed up the process?
It's unlikely to directly help, even if that improvement would be really lovely to have. What needs to change is the number of people willing to do final review for Ukrainian, and their capacity. The contribution level of work (actual localization work writing or updating pages) is not the constraint here.
the number of people willing to do final review
Perhaps the introduction of this system allows more people to be involved in the review and contribution process, making it easier for them to join the project.
Якщо ви володієте українською (та англійською), надішліть відгук на https://github.com/kubernetes/website/pull/48554
Неформальни відгук також корисни.
If you can speak Ukrainian (and English), please review https://github.com/kubernetes/website/pull/48554
Informal checking is helpful.
Hi, @salaxander what is the problem with this PR?
This set of changes needs reviewing by the Ukrainian localization team, but also it is really too big (and has too many commits) to accept as-is. We should not unhold it.
If you speak Ukrainian yourself @themoriarti and would be willing to review a smaller PR derived from this, see https://github.com/kubernetes/website/pull/48554.
Hi, @salaxander what is the problem with this PR?
This set of changes needs reviewing by the Ukrainian localization team, but also it is really too big (and has too many commits) to accept as-is. We should not unhold it.
If you speak Ukrainian yourself @themoriarti and would be willing to review a smaller PR derived from this, see #48554.
Sure, this PR is really big, but it is very important for the Ukrainian-speaking community. Given that I am a Ukrainian-native speaker, I can do a review. I carefully reread the smaller PR https://github.com/kubernetes/website/pull/48554, the translation is all good there.
@themoriarti if you are on Kubernetes' Slack workspace, come and say Hi in #kubernetes-docs-uk. You can get a workspace invitation via https://slack.k8s.io/
This is promising, but: we really need PRs small enough for one person to have time to check them.
If anyone's up for helping out, there are a few ways to do so. The first one's quite simple, but it does need you to do some manual work: you just split off a part of this PR into a separate one, and I can lgtm and approve it pretty quickly[^1]. How quickly all this translated documentation ends up on the main website depends entirely on how quickly you can create PRs. The other, more complicated way is to become a member of the Kubernetes organisation on GitHub and approve the PR yourself.
If you've got experience setting up and working with translations using translation support platforms, you can help the project adapt CrowdIn to support translation work for all language teams. This will significantly reduce the overheads of these teams for working with translations.
[^1]: Why don't I approve this PR myself? The whole workflow is set up so that at least two people are needed for this: one creates the PR and the other approves it. You can't approve your own PRs.
Hey @Andygol I could help with creating smaller PRs. I will try by myself on a weekend and let you know if I face any issues.
Hey @Andygol, I created a "Pilot" PR with a part of your changes. Please, take a look: https://github.com/kubernetes/website/pull/52713
If we decide going this path, I would follow this approach for future changes.
@andygol would you be willing to open a PR that v just includes the glossary term changes from this branch?
@Andygol: The label(s) /remove-label needs-sig cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor, ci-short, ci-extended, ci-full. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?
In response to this:
/remove-label needs-sig
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
@Andygol: Those labels are not set on the issue: area/needs-sig
In response to this:
/remove-area needs-sig
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.