Change:
This is a Feature Request What would you like to be We plan to hold a "team localization jam" for translating glossary entries to Hindi. Why is this needed Glossary entries provide building blocks of content that many topics include. Translating these first is a strategic priority. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
/assign rolfedh
/assign AmanSarraf
/language hi /retitle [hi] Umbrella issue for translating glossary entries to Hindi
/remove-kind feature
I also want to work on this. May I
yes sure welcome, you can assign this to yourself as /assign <your username
/triage accepted Thank you and others, this being an umbrella issue, my suggestion would be to not assign ourselves since GitHub has a limit of 10 assigneed and we can easily have more than 10 contributors on this issue. Also, addition of a checklist in issue description would make tracking the work easier, just like we did localizing the content intiitally () unless we have another method to organize work.
Oky
I am working on
Now , I am working on
That's great, Tania! Tania Duggal (He His) Senior Technical Writer, US ENG Content Services Cloud Application Development & Services Red Hat North Carolina * M: 910-409-8007 IM: rdlugyhe book a meeting with me, click here.
Based on some initial experiences I've seen contributors encounter, I've been working on a several issues to clear a smoother path for contributors: Has been resolved. contains a line that ignores . Some users might need to update older working branches to include this change: to help contributors avoid common issues, and support reviewers providing feedback. This is under discussion and in progress. , which is in progress.
For translating glossary entries, should we be guiding contributors to translate the content from or ? I lean toward working from because these glossary entries contain have substantial improvements since 1.22. WDYT?
I'd say too, I see no harm in having the latest glossary localized.
Examples of localized glossary entries:
Here is the first set of proposed issues for this glossary localization guide. I'd like to get your suggestions on any improvements that might help new contributors with these issues. This set of issues is oriented toward contributors who are familiar with Git and GitHub operations.
Here's a different set of proposed issues. These already have PRs to make getting started VERY easy for newcomers (Zero setup, no git skills required, no CNCF Contributor License Agreement):
I would also like to work with you
Have you reviewed the prs?
Now, I am working on content/en/docs/reference/glossary/application-
hi , I would like to work with you all
Status update: Right now, I'm communicating with the /hi branch owners/reviewers to get the review and merge processes moving forward. I expect to merge the current raft of PRs and close their associated issues and conducting a retrospective before I open a new set of issues. I encourage you to forge ahead without me: Localizing glossary entries and other content from the branch to the branch. Self organizing, communicating with each other about your efforts, mentoring newcomers.
I opened an issue on JUL 22 Can We add this issue with this localization efforts??
Thanks, ! It's great that you've gone ahead and created this issue. I expect you or someone will create a PR to fix it, too! It can stand on its own and doesn't need to be part of this issue, which is focused on glossary entries. I'm here to support you any time, as are all the other contributors!
somewhere you also add English title with Hindi and somewhere not. What guidelines you follow to do like this. Please let me know:)
Now, I am working on :)
Thanks for reminding me I forgot to add english with hindi as well
Now, I am working on :)
I am working on
Now, I am working on
Now, I am working on
Now, I am working on content/en/docs/reference/glossary/helm-
[ ] (Assigned) [x] (Assigned) [ ] (Assigned) [ ] (Assigned) [x] (Assigned) [x] (Assigned) [x] (Assigned) [ ] (Assigned) [ ] (Assigned) [ ] (Assigned)
great work , some folks are facing checks failing issue. i have checked the build logs. but i am not able to understand what is the actual issue. . do you know anything about this.
Sorry for being late! I think this issue may be occured for using in the commit message in which is not allowed so for fixing this the PR raiser has to push an empty commit with proper commit message!
Reopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/reopen
Reopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/reopen Folks, this is an umbrella issue. please don't tag individual PRs as fixing this issue.
Reopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Are we still using this issue to coordinate our efforts on localizing glossary or should we close this issue, review open PRs and again calibrate our efforts fresh? cc
I think it is better to review to open PRs and calibrate a fresh efforts especially for tracking the glossary localization.
Yes it would be better to review all the already opened PRs and merge those and let this issue be closed as for now!

Discussion:
<ins> --- title: etcd id: etcd date: 2018-04-12 full_link: /docs/tasks/administer-cluster/configure-upgrade-etcd/ short_description: > सभी क्लस्टर डेटा के लिए कुबेरनेट्स के बैकिंग स्टोर के रूप में उपयोग किया जाने वाला सुसंगत और उच्च उपलब्धता की-वैल्यू स्टोर। aka: tags: - architecture - storage --- सभी क्लस्टर डेटा के लिए कुबेरनेट्स के बैकिंग स्टोर के रूप में उपयोग किया जाने वाला सुसंगत और उच्च उपलब्धता की-वैल्यू स्टोर। <!--more--> यदि आपका कुबेरनेट्स क्लस्टर बैकिंग स्टोर के रूप में etcd का उपयोग करता है, तो सुनिश्चित करें कि आपके पास उन डेटा के लिए एक [बैकअप](/docs/tasks/administer-cluster/configure-upgrade-etcd/#backing-up-an-etcd-cluster) योजना है। आप आधिकारिक [प्रलेखन](https://etcd.io/docs/) में etcd के बारे में गहन जानकारी प्राप्त कर सकते हैं। </ins>