search

cncf / glossary

The CNCF Cloud Native Glossary Project aims to define cloud native concepts in clear and simple language, making them accessible to anyone — whether they have a technical background or not (https://glossary.cncf.io).
https://glossary.cncf.io/
Apache License 2.0
652 stars 542 forks source link

Tracking Hindi Localization Progress of Glossary #270

Closed Garima-Negi closed 2 years ago

Garima-Negi commented 2 years ago

This issue tracks Hindi localization progress.

Checklist to translate a term

  1. Check that no one else has claimed the page in the comments below.
  2. Comment below the page that you would like to localize, focus on one page per PR, at a time.
  3. Maintainers will add your username and Pull Request next to your selected page in below checklist.
  4. Fork this repo, make your localizations, and submit a pull request following the name convention [hi] [page name from task].
  5. tag/ping a maintainer to make it easier to track progress

Points to remember:

For Volunteers

Volunteers can comment below on this issue with the page-name they are interested in localizing. Please also provide a placeholder PR in your comment. Example: I would like to help with/take up/localize page xyz.md . Here's a placeholder PR for the same.

To create a PR:

For Maintainers

Volunteers will comment below on this issue with the page-name. Maintainers will add their username and PR next to the task. Example : Autoscaling Hindi localization (@contributor-username) #<PR link> Regularly check for PRs merged and subsequently mark the task done in this issue.

Priorities

We need at least 10 terms in Hindi before go live, below are some suggested terms to work:

Minimum 10 terms required:

Additional good to have terms:

sayantani11 commented 2 years ago

I can review the PRs, but will require someone else as well

anubha-v-ardhan commented 2 years ago

@Garima-Negi I believe, we will also need Site strings i.e. i18n/hi.toml as a minimum requirement. Can you add it to the checklist.

anubha-v-ardhan commented 2 years ago

I can review the PRs, but will require someone else as well

I can help with review and approval work too

jayesh-srivastava commented 2 years ago

I would like to assist too.

I can review the PRs, but will require someone else as well

jayesh-srivastava commented 2 years ago

@Garima-Negi Also I think a new language block for Hindi is to be added in config.toml right?

anubha-v-ardhan commented 2 years ago

@jayesh-srivastava yes, we can do all the setup in one PR like the korean team in https://github.com/cncf/glossary/pull/253 once we decide the reviewers and approvers. Please join #glossary-localization-hindion CNCF slack for detailed discussions (if not joined already)

jayesh-srivastava commented 2 years ago

@anubha-v-ardhan I guess one page per PR would be great unlike how the Korean team did because then it would be a difficult process to review such huge PRs.

anubha-v-ardhan commented 2 years ago

@jayesh-srivastava Not exactly like that. I was saying the initilization of new localization can be done in one PR. i.e just configs.toml and CODEOWNERS. Sorry for miscommunication

sayantani11 commented 2 years ago

I can review the PRs, but will require someone else as well

I can help with review and approval work too

Yeah review and approval, sorry was on a break for few days😓

verma-kunal commented 2 years ago

Awesome! I would love to join in as an approver & reviewer from the next month as well, to help out 🙂

ShivamTyagi12345 commented 2 years ago

Thats great @Garima-Negi ! I m making a tutorial video for beginner folks to get on board with this. I hope it's alright if I use this in my video. Also, I would love to be one of the reviewers /approver

anubha-v-ardhan commented 2 years ago

@Garima-Negi I believe we'll also need site strings as minimum requirements, Can we add it to the checklist.

Also, it would be nice if we mention the steps to contribute in more detail (for example mention branch to be used and important things to keep in mind like making branch on your fork from dev-hi and not main etc.)

sayantani11 commented 2 years ago

content/hi/_TEMPLATE.md content/hi/_index.md content/hi/contribute/_index.md i18n/hi.toml Solved in #349

ShivamTyagi12345 commented 2 years ago

I would like to take up content/hi/auto_scaling.md to get started @Garima-Negi

Garima-Negi commented 2 years ago

I would like to take up content/hi/auto_scaling.md to get started @Garima-Negi

Hi Shivam, I have updated your name in the list above. Whenever you're ready with a placeholder PR, do share it here or on slack. Thank you!

Garima-Negi commented 2 years ago

@Garima-Negi I believe we'll also need site strings as minimum requirements, Can we add it to the checklist.

Also, it would be nice if we mention the steps to contribute in more detail (for example mention branch to be used and important things to keep in mind like making branch on your fork from dev-hi and not main etc.)

I have added a new section to the issue : To create a PR with some initial steps. As and when the contributors face blockers, I'll make the instructions more detailed.

Shubh28698 commented 2 years ago

@Garima-Negi I would like to take content/hi/_TEMPLATE.md

anubha-v-ardhan commented 2 years ago

@Shubh28698 content/hi/_TEMPLATE.md content/hi/_index.md content/hi/contribute/_index.md and i18n/hi.toml have been localized by @sayantani11. see https://github.com/cncf/glossary/issues/270#issuecomment-1019583345 You can take any other file than this. Also check recent comments along with the checklist as the checklist maybe lagging a bit as updating it is a manual work.

@Garima-Negi, can you mark all the above pages on checklist

Shubh28698 commented 2 years ago

@Shubh28698 content/hi/_TEMPLATE.md content/hi/_index.md content/hi/contribute/_index.md and i18n/hi.toml have been localized by @sayantani11. see #270 (comment) You can take any other file than this. Also check recent comments along with the checklist as the checklist maybe lagging a bit as updating it is a manual work.

@Garima-Negi, can you mark all the above pages on checklist

Sry @anubha-v-ardhan, @Garima-Negi , Then i will take content/hi/abstraction.md

Garima-Negi commented 2 years ago

Updated the list, sorry for the confusion. Multiple tasks were part of single PR.

anubha-v-ardhan commented 2 years ago

I'll take content/hi/agile_software_development.md

WebShivam commented 2 years ago

Hi @Garima-Negi, I would like to take content/hi/application_programming_interface.md to get started with the localization

Shubh28698 commented 2 years ago

Hi @Garima-Negi , I would like to take content/hi/cloud_computing.md

anubha-v-ardhan commented 2 years ago

@Garima-Negi #349 is closed (ref. https://github.com/cncf/glossary/pull/300#issuecomment-1024894288)

Following pages will be added via #300

PR #300 will test our config for Hindi localization works. Please mark these pages on the checklist as assigned

Please, also update the status of pages assigned by folks in above comments

anubha-v-ardhan commented 2 years ago

@Garima-Negi content/hi/style-guide/_index.md and content/hi/cloud_native_tech.md are written as separate points too while they are being covered by #300. Please remove them from checklist to avoid confusion.

Also add content/hi/_TEMPLATE.md being covered by #300 itself

anubha-v-ardhan commented 2 years ago

Next working on content/hi/devops.md :)

rajatgupta24 commented 2 years ago

Hey everyone, I'll be working on content/hi/cluster.md.

anubha-v-ardhan commented 2 years ago

A small reminder for everyone, please use the label 'lang/hi' with your PR. Thanks!

@jayesh-srivastava Everyone can't edit labels on PRs. We maintainers have the rsponsibility to assign appropriate labels

jayesh-srivastava commented 2 years ago

@anubha-v-ardhan Oh okay! Got it.

verma-kunal commented 2 years ago

Hey all, i would be starting to work on content/hi/containerization.md :)

kranurag7 commented 2 years ago

Hey Everyone, I would be love to work on content/hi/container.md and content/hi/container-image.md

anubha-v-ardhan commented 2 years ago

@kranurag7 Please only take one page at a time. Assigning content/hi/container.md to you

kranurag7 commented 2 years ago

Sure @anubha-v-ardhan I will work on this. Thank you for assigning.

verma-kunal commented 2 years ago

Would be working on content/hi/continuous_delivery.md , next :)

ShivamTyagi12345 commented 2 years ago

will work next on content/hi/_index.md

anubha-v-ardhan commented 2 years ago

will work next on content/hi/_index.md

content/hi/_index.md is already localized with PR #300 as shown in the cheklist above. Please choose something else.

ShivamTyagi12345 commented 2 years ago
  • content/hi/api_gateway.md

Thats on me. Thanks. I will choose content/hi/api_gateway.md

Aayush987 commented 2 years ago

Hi I would love to contribute to this issue.I would like to take content/hi/continuous_integration.md file.If anyone is not working on it please assign it to me.

kranurag7 commented 2 years ago

@Aayush987 Thanks for coming up. The issue will be assigned to you if no one is working on it.

Aayush987 commented 2 years ago

@kranurag7 Thanks

Aayush987 commented 2 years ago

I wanted to ask if i have to do it via cloning on my system or i can simply do it in github on browser?

kranurag7 commented 2 years ago

@Aayush987 You can do it in browser only. Cloning is not required but still if you want to clone then go ahead.

anubha-v-ardhan commented 2 years ago

Thanks @Aayush987. I've assigned the requested page to you. Please also consider joining #glossary-localization and #glossary-localization-hindi on CNCF Slack for discussions or conversations of any kind.

I wanted to ask if i have to do it via cloning on my system or i can simply do it in github on browser?

I's not sure if we can branch from dev-hi on GitHub itself. If yes, I see no harm in doing so. Note that the PR will have to target dev-hi and not main

Aayush987 commented 2 years ago

Thanks @Aayush987. I've assigned the requested page to you. Please also consider joining #glossary-localization and #glossary-localization-hindi on CNCF Slack for discussions or conversations of any kind.

I wanted to ask if i have to do it via cloning on my system or i can simply do it in github on browser?

I's not sure if we can branch from dev-hi on GitHub itself. If yes, I see no harm in doing so. Note that the PR will have to target dev-hi and not main

Ok thanks

verma-kunal commented 2 years ago

Would be working on content/hi/client_server_architecture.md next :)

kranurag7 commented 2 years ago

I would be working on content/hi/cloud_native_security.md.

Aayush987 commented 2 years ago

My previous Pr on content/hi/continuous_integration.md just needs approval , now i would like to work on content/hi/canary_deployment.md.Plz assign it to me

Garima-Negi commented 2 years ago

Updated https://github.com/cncf/glossary/pull/417 in tracking issue

Garima-Negi commented 2 years ago

Hi, @Shubh28698 and @WebShivam!

Thank you for signing up for your respective pages. We would like to get placeholder PRs for the same if you have begun work on the localization already. Please also paste the tracking issue https://github.com/cncf/glossary/issues/270 in your PRs description, this helps us track.

Thank you for your help!

Garima-Negi commented 2 years ago

hi, taking content/hi/contributor-ladder/_index.md next.