[hi] Tracking Hindi localization progress

[anubha-v-ardhan]

Summary of progress till now: https://github.com/kubernetes/website/issues/29353#issuecomment-919357503

Our current aim is to get the localization live first with minimum required content. We will be ready to expand the localization including other pages once bare minimum version goes live.

Maintainers

Approvers:

• @anubha-v-ardhan
• @divya-mohan0209
• @mittalyashu

Reviewers:

• @anubha-v-ardhan
• @divya-mohan0209
• @verma-kunal
• @mittalyashu

  For New Contributors

To translate a page:

1. Check that no one else has claimed your page in the checklist and comments below.
2. Comment below with the location of the English page you would like to translate. Take only one page at a time.
3. Maintainers will add your username along your task in the checklist.
4. Fork this repo, make your localisations, and submit a pull request following the name convention [hi] [Add/Update/Fix] [content/hi/file/full/path] and base branch as dev-1.22-hi.1. Don't forget to use /language hi command. Also, tag/ping a maintainer to make it easier to track progress and add your PR to the checklist below. For example: [hi] Add content/hi/docs/concepts/architecture/nodes.md [hi] Update content/hi/setup/release/building-from-source.md

Note: To know about the preferred localization of common Kubernetes related terms, check this spreadsheet Note: To get an idea about the kind of language we are expecting, have a look at this PR

Points to remember:

1. You can use this script to know if a given file is touched by which PR: https://github.com/kubernetes/website/blob/master/scripts/find_pr.py By doing so, you can have a single source of truth about whether a file is currently being modified or not.
2. Please use the word localisation instead of translation in your PRs and comments.
3. Every new contribution should start with a new branch from dev-1.22-hi.1. For more detailed instruction, check the website-README.
4. Before contributing to docs, read the Community Documentation Style Guide and the Kubernetes Documentation Style Guide.

If you're still not sure about something, please don't hesitate to ask in Slack channel.

Please commit with your translations! If you find that you can't commit anymore, let the maintainers know so they can assign the page to someone else.

For Maintainers

When someone volunteers, edit this issue with the username of the volunteer, and with the PR. Example : Init Hindi localisation (@mittalyashu) #13910 When PRs are merged, make sure to mark that page as completed!

Website (content/en)

• [x] Landing (@verma-kunal)

  30087

releases (content/en/releases)

• [x] Landing (@AvineshTripathi)

  31273

  31292

includes (content/en/includes)

• [x] task-tutorial-prereqs.md (@Nawaz027)

  30590

  30602

case-studies (content/en/case-studies)

• [x] Landing (@harshmathurx)

  30731

  30733

Docs (content/en/docs)

• [x] Landing (@anubha-v-ardhan)

  29373

  concepts (content/en/docs/concepts)

  overview

  • [x] what-is-kubernetes.md (@kranurag7, @ashish-jaiswar)

    30732

    30847

    contribute (content/en/docs/contribute)

  • [x] Landing (@Nawaz027)

    31012

    31162

    reference (content/en/docs/reference)

  • [x] Landing (@Garima-Negi)

    31011

    31185

    glossary

  • [x] Landing (@Polokghosh53, @ashish-jaiswar)

    30591

    30652

    home (content/en/docs/home)

  • [x] Landing (@verma-kunal)

    29383

  • [x] supported-doc-versions (@verma-kunal)

    29372

    setup (content/en/docs/setup)

  • [x] Landing (@keshavcodex)

    29514

    best-practices

  • [x] Landing (@anubha-v-ardhan)

    29374

    learning-environment

  • [x] Landing (@Darshnadas)

    29416

    production-environment

  • [x] Landing (@keshavcodex)

    29518

  • [x] container-runtimes (@Darshnadas @ashish-jaiswar)

    31857

    31987

    32713

  • [x] turnkey-solutions (@ShivamTyagi12345)

    30303

    windows

    • [x] Landing (@anubha-v-ardhan)

      29413

      tasks (content/en/docs/tasks)

  • [x] Landing (@rajatgupta24)

    29434

    tools

  • [x] Landing (@rajatgupta24)

    29458

  • [x] install-kubectl-linux (@vedant-kakde)

    29457

  • [x] install-kubectl-macos (@vedant-kakde)

    29461

  • [x] install-kubectl-windows (@vedant-kakde)

    29465

    included

  • [x] Landing (@kaiwalyakoparkar)

    29705

  • [x] kubectl-convert-overview (@ShivamTyagi12345)

    29970

  • [x] kubectl-whats-next (@ShivamTyagi12345)

    29471

  • [x] optional-kubectl-configs-bash-linux (@ashish-jaiswar)

    30569

    30627

  • [x] optional-kubectl-configs-bash-mac (@vedant-kakde, @kranurag7)

    30570

    30607

  • [x] optional-kubectl-configs-zsh (@vedant-kakde)

    29474

  • [x] verify-kubectl (@vedant-kakde)

    29469

    tutorials (content/en/docs/tutorials)

  • [x] Landing (@anubha-v-ardhan)

    29376

  • [x] hello-minikube (@anubha-v-ardhan)

    29396

    kubernetes-basics

  • [x] Landing (@rajatgupta24)

    29391

    create-cluster

    • [x] Landing (@rajatgupta24)

      29392

    • [x] cluster-interactive (@rajatgupta24)

      29392

    • [x] cluster-intro (@rajatgupta24)

      29392

      deploy-app

    • [x] Landing (@rajatgupta24)

      29400

    • [x] deploy-interactive (@rajatgupta24)

      29393

    • [x] deploy-intro (@rajatgupta24)

      29401

      explore

    • [x] Landing (@anubha-v-ardhan)

      29399

    • [x] explore-interactive (@anubha-v-ardhan)

      29403

    • [x] explore-intro (@anubha-v-ardhan)

      29412

      expose

    • [x] Landing (@rajatgupta24)

      29430

    • [x] expose-interactive (@rajatgupta24)

      29405

    • [x] expose-intro (@rajatgupta24)

      29407

      scale

    • [x] Landing (@verma-kunal)

      29421

    • [x] scale-interactive (@verma-kunal)

      29410

    • [x] scale-intro (@verma-kunal)

      29420

      update

    • [x] Landing (@ShivamTyagi12345)

      29971

    • [x] update-interactive (@verma-kunal)

      29432

    • [x] update-intro (@verma-kunal)

      29454

Site strings (data/i8n/hi)

• [x] hi.toml (@prashantpandey9, @Babapool)

  29472

  31013

  31072

[anubha-v-ardhan]

/language hi

[verma-kunal]

Nice work @anubha-v-ardhan !! 👍

[anubha-v-ardhan]

@verma-kunal Please don't assign the issue as this is a collective effort of many people. We want new contributors to see this as an unassigned issue on issues tab /unassign @verma-kunal

[verma-kunal]

alright sure!! Understood 👍

[verma-kunal]

@anubha-v-ardhan , i think it would be good to mention the source folder of all the files as well, that needs to be localized https://github.com/kubernetes/website/tree/main/content/en this would be easier for new folks to navigate!!

[anubha-v-ardhan]

I have added location for the parent directories. For ease of new contributors, The identation of tasks is as per their location in the website repo.

[verma-kunal]

Remember folks, all the changes are needed to be done here: https://github.com/kubernetes/website/tree/main/content/hi. That means, whenever you assign yourself a particular page, after localising that, refer the file structure in the source folder (English one) & create new files/folder according to that in the hi folder (with the Hindi localization)

Feel free to ask any doubts you would have in this 🙂

[verma-kunal]

I'll be working on website/content/en/docs/home/supported-doc-versions.md whenever I'll be getting the time today !! 🙂

[anubha-v-ardhan]

@verma-kunal Please take one file at a time. A whole directory is a lot of work. Hope you understand

[anubha-v-ardhan]

I will be working on website/content/en/docs/_index.md soon

[verma-kunal]

@verma-kunal Please take one file at a time. A whole directory is a lot of work. Hope you understand

oops, wrong location added !! Changing now

[keshavcodex]

I am starting with this folder website/content/en/docs/setup/_index.html to localise it.

[ShivamTyagi12345]

I am working on website\content\en\docs\setup\best-practices\node-conformance.md

[verma-kunal]

@anubha-v-ardhan , how are we keeping the branch names (for us) !! I think we should decide a convention for that what do you think?

[anubha-v-ardhan]

@verma-kunal personal branch names are our own choices, feel free to do it your own way. : )

[verma-kunal]

Working on website/content/en/docs/home/_index.md now!!

[anubha-v-ardhan]

Now working on content/en/docs/setup/best-practices/_index.md

[sftim]

For content/hi/docs/setup you need to localize that page and its direct subheadings. For example:

• https://kubernetes.io/docs/setup/ needed
• https://kubernetes.io/docs/setup/learning-environment/ needed (including the redirect)
• https://kubernetes.io/docs/setup/production-environment/ needed
• https://kubernetes.io/docs/setup/production-environment/tools/ eventually but not for the initial localization
• https://kubernetes.io/docs/setup/best-practices/ needed
• https://kubernetes.io/docs/setup/best-practices/certificates/ eventually but not for the initial localization

• If you're not sure about anything, there's a localization Zoom call once each month. Folks there who have already done this for their localization can help you work out the details.

[sftim]

For tutorials, you only need to localize

• https://kubernetes.io/docs/tutorials/kubernetes-basics/ (the whole tutorial - I recommend splitting this)
• https://kubernetes.io/docs/tutorials/hello-minikube/

as minimum required content.

[sftim]

/triage accepted

[anubha-v-ardhan]

Thank you so much @sftim, Our initial checklist includes the files suggested by you. We will try to attend localization meetings.

[verma-kunal]

Thank you for the info @sftim !! Would follow these as we go ahead 🙂

[verma-kunal]

Hey @anubha-v-ardhan , i've made a draft PR here: https://github.com/kubernetes/website/pull/29372 Can you pls add that to the list above!!

[verma-kunal]

And we had to create a draft PR for now, right? not the normal one

[anubha-v-ardhan]

~I have opened normal ones. I don't think it matters. We will basically change the branch once its available.~

[verma-kunal]

oh, actually @sftim had mentioned this, so thats why I was asking!!

[anubha-v-ardhan]

Oh sorry, my bad. we have to open draft PR's. Thanks for pointing this out :D

[verma-kunal]

Oh sorry, my bad. we have to open draft PR's. Thanks for pointing this out :D

yeah, no worries !!

[ShivamTyagi12345]

would next work oncontent\en\docs\setup\best-practices\enforcing-pod-security-standards.md

[Darshnadas]

Hello I would like to work on this website/content/en/docs/setup/learning-environment/_index.md

[verma-kunal]

Sure, go ahead @Darshnadas !! Welcome 🙂

[verma-kunal]

Hey @anubha-v-ardhan , made a PR for content/en/docs/home/_index.md here: https://github.com/kubernetes/website/pull/29383

[ShivamTyagi12345]

hey @anubha-v-ardhan @verma-kunal ,drafted a PR forwebsite\content\en\docs\setup\best-practices\node-conformance.md check: this

[indrasvat]

Pure Telugu/Hindī suggestions for some core k8s terms (also commented about this in https://github.com/kubernetes/website/pull/29383#issuecomment-898721517):

pod కోశము कोश service ఆయోగము आयोग replica ప్రతికృతి प्रतिकृति deployment వినిమయము विनिमय orchestration సంపృక్తము संपृक्त

Perhaps more such terms can be found.

Source: https://twitter.com/vakibs/status/1426299108596273155

[anubha-v-ardhan]

@kodeninja Thanks for the suggestions but we think the name of Kubernetes objects such as deployment, pod, service etc should be written as डिप्लॉयमेंट, पॉड, सर्विस etc only. The aim of this localization is not to have pure word to word translation of all the terms but to have the docs in Hindi for easy understanding. Hope you understand We would like to hear your views @mittalyashu

[verma-kunal]

@anubha-v-ardhan , would be working on this content/en/docs/setup/best-practices/cluster-large.md now !!

[rajatgupta24]

Hey @anubha-v-ardhan, I'd like to work on content/en/docs/tutorials/kubernetes-basics/_index.html

[rajatgupta24]

Hey @anubha-v-ardhan, now I'm working on content/hi/docs/tutorial/kubernetes-basics/create-cluster/_index.md

[mittalyashu]

@kodeninja Thanks for the suggestions but we think the name of Kubernetes objects such as deployment, pod, service etc should be written as डिप्लॉयमेंट, पॉड, सर्विस etc only. The aim of this localization is not to have pure word to word translation of all the terms but to have the docs in Hindi for easy understanding. Hope you understand We would like to hear your views @mittalyashu

I agree with @anubha-v-ardhan

Can you also add these names to Google spreadsheet?

[anubha-v-ardhan]

Sure @mittalyashu . I will. Thank you : )

[mittalyashu]

I am don't remember how many pages I localised last time and how many of them got updated.

Can we go one file per PR? It will be easy for me to review as well.

[anubha-v-ardhan]

I am don't remember how many pages I localised last time and how many of them got updated.

Can we go one file per PR? It will be easy for me to review as well.

cc @rajatgupta24

[rajatgupta24]

I am don't remember how many pages I localised last time and how many of them got updated. Can we go one file per PR? It will be easy for me to review as well.

cc @rajatgupta24

Sure, ok

[rajatgupta24]

Hey @anubha-v-ardhan, now I'm working on content/hi/docs/tutorial/kubernetes-basics/deploy-app/deploy-interactive.html

[verma-kunal]

adding on to @mittalyashu 's point about PRs, try to follow the naming convention as mentioned in the above note, so that it would be easier to locate & review!! For example: Add content/hi/docs/concepts/architecture/nodes.md Update content/hi/setup/release/building-from-source.md

cc @rajatgupta24

[verma-kunal]

Hey, actually i had a doubt! If we for example take the translation of the word Nodes: originally it is नोड्स, but if we wanna go with the pronunciation as well, then it should be नोड्ज़ (for the English word Nodez). Which one is better to be considered in this situation? & then we can add that to the sheet as well.

[anubha-v-ardhan]

I think नोड्स fit better, Adding this to sheet

[rajatgupta24]

Hey, actually i had a doubt! If we for example take the translation of the word Nodes: originally it is नोड्स, but if we wanna go with the pronunciation as well, then it should be नोड्ज़ (for the English word Nodez). Which one is better to be considered in this situation? & then we can add that to the sheet as well.

I think नोड्ज़, because it's the right pronunciation

[rajatgupta24]

Hey @anubha-v-ardhan, now I'm working on content/hi/docs/tutorial/kubernetes-basics/deploy-app/landing

[rajatgupta24]

Hey @anubha-v-ardhan, now I'm working on content/hi/docs/tutorial/kubernetes-basics/deploy-app/deploy-intro.html