Change:
This is a Feature Request Well not really a feature, but neither a real bug. <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --I noticed that while the German "What is Kubernetes" page has a tiny section about the meaning of Kubernetes in it at the end, the English counterpart lacks this info. I want to add it. I have not checked with other languages. Why is this needed The documentation content should be equal across translations. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
The English article explains the meaning of Kubernetes in the second paragraph ("The name Kubernetes originates from Greek, meaning helmsman or pilot. "), before explaining its origin. Either the German version of the page should be adapted, or the English one. The English version does not explain where "K8s" comes from.
/language en /kind feature
BTW SIG Docs convention is that localizations are downstream from the English version, which is canonical.
/triage accepted
In my humble opinion, the difference between the English and German versions of the documentation is a bigger problem and not limited to this case. See as well vs . I mean, my use case is kind of special, I am writing a thesis and want to cite the Documentation in some places. I first had the German links and then decided to write this thing in English, so I wanted to substitute the links with their English counterparts. This did not work as I expected, as parts of the docs moved to a different place.
we 100% welcome pull requests to bring the German localization in syncrhronization with English. If you have any friends itching to contribute to open source, and who speak both languages, or you're keen yourself - jump right in!
alright, I might have some spare time over the holidays. Seems like contributing to open source documentation is my thing :D One questions remains: like in the initial case, the German version had more info than the English one. Shall I keep this info in a list and suggest adding it in the English version as well? Because somebody took an effort to add it in there in the first place, though they did not think about adding it to the canonical English version, too.
I haven't checked the commit history but I assume that the extra text was at some point in the English version and that the upstream (English) page has since changed. We don't accept changes that land first in the downstream localization if these revise the meaning of the text. It's possible the history is different - I'd expect that to be very rare. Localization is not translation, though, and there are pages where the localized text differs from a literal translation because the overall intent and meaning is preserve from upstream.
Difficult matter I suppose, where do you draw the line ... I will try to at least make the pages look more equal to one another, so that there are no surprises as in my case, where the page structure is somehow different and it is not so easy to link to the correct page in English, coming from German.
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /lifecycle rotten
Seems this issue is now talking about updating the German page rather than the English page? should we update the label here to be German? Either we change this to a German language updating issue, or close the issue, since the English version is canonical and it does contain the origin of the word Kubernetes:
/assign
you might have misunderstood. We should not close this issue until mentions “k8s” /retitle Mention k8s abbreviation in “What is Kubernetes”.
Gotcha I'm on it

Discussion:
<!-- body --> Kubernetes is a portable, extensible, open-source platform for managing containerized workloads and services, that facilitates both declarative configuration and automation. It has a large, rapidly growing ecosystem. Kubernetes services, support, and tools are widely available. <del> The name Kubernetes originates from Greek, meaning helmsman or pilot. Google open-sourced the Kubernetes project in 2014. Kubernetes combines [over 15 years of Google's experience](/blog/2015/04/borg-predecessor-to-kubernetes/) running production workloads at scale with best-of-breed ideas and practices from the community. </del> <ins> The name Kubernetes originates from Greek, meaning helmsman or pilot. K8s as an abbreviation results from counting the eight letters between the "K" and the "s". Google open-sourced the Kubernetes project in 2014. Kubernetes combines [over 15 years of Google's experience](/blog/2015/04/borg-predecessor-to-kubernetes/) running production workloads at scale with best-of-breed ideas and practices from the community. </ins> ## Going back in time