[hi] Umbrella issue for translating glossary entries to Hindi

[rolfedh]

This is a Feature Request

What would you like to be added

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

[rolfedh]

/assign rolfedh

[AmanSarraf]

/assign AmanSarraf

[sftim]

/language hi
/retitle [hi] Umbrella issue for translating glossary entries to Hindi

[sftim]

/remove-kind feature

[taniaduggal]

I also want to work on this. May I @rolfedh

[AmanSarraf]

I also want to work on this. May I @rolfedh

yes sure welcome, you can assign this to yourself as /assign

[anubha-v-ardhan]

/triage accepted

Thank you @rolfedh

@AmanSarraf @taniaduggal 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 (#29353) unless we have another method to organize work.

[taniaduggal]

Oky @anubha-v-ardhan

[taniaduggal]

I am working on content/en/docs/reference/glossary/cidr.md
@AmanSarraf @rolfedh

[taniaduggal]

Now , I am working on content/en/docs/reference/glossary/annotation.md @rolfedh

[rolfedh]

That's great, Tania!

…

On Fri, Aug 5, 2022 at 1:05 AM Tania Duggal ***@***.***> wrote: Now , I am working on content/en/docs/reference/glossary/annotation.md @rolfedh <https://github.com/rolfedh> — Reply to this email directly, view it on GitHub <#35600 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACVVOYRPEO7ENR2VV6YGBTVXSOKTANCNFSM55HGC4OA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Rolfe Dlugy-Hegwer (He | Him | His) Senior Technical Writer, US ENG Content Services Cloud Application Development & Services Red Hat North Carolina <https://www.redhat.com/> ***@***.*** M: 910-409-8007 IM: rdlugyhe <https://red.ht/sig>To book a meeting with me, click here. <https://calendly.com/rolfe-at-redhat>

[rolfedh]

Status update

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:

• Update .gitignore to ignore .hugo_build.lock #35749 Has been resolved. .gitignore contains a line that ignores .hugo_build.lock. Some users might need to update older working branches to include this change:

git fetch upstream dev-1.22-hi.1
git rebase upstream/dev-1.22-hi.1

• [hi] Create a language-specific style guide for Hindi #35599 to help contributors avoid common issues, and support reviewers providing feedback. This is under discussion and in progress.
• themes/docsy submodule showing up in PRs #35588, which is in progress.

[rolfedh]

@anubha-v-ardhan For translating glossary entries, should we be guiding contributors to translate the content from main or dev-1.22?

I lean toward working from main because these glossary entries contain have substantial improvements since 1.22. WDYT?

[anubha-v-ardhan]

@rolfedh I'd say main too, I see no harm in having the latest glossary localized.

[rolfedh]

Examples of localized glossary entries:

• Localize content/en/docs/reference/glossary/cidr.md into Hindi #35719
• Localize content/en/docs/reference/glossary/annotation.md into Hindi #35844
• [hi] Localize content/en/docs/reference/glossary/cluster-architect.md  #35867

[k8s-ci-robot]

@bishal7679: Reopened this issue.

In response to this:

/reopen

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/test-infra repository.

[bishal7679]

/reopen

[k8s-ci-robot]

@bishal7679: Reopened this issue.

In response to this:

/reopen

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/test-infra repository.

[anubha-v-ardhan]

/reopen

Folks, this is an umbrella issue. please don't tag individual PRs as fixing this issue.

[k8s-ci-robot]

@anubha-v-ardhan: Reopened this issue.

In response to this:

/reopen

Folks, this is an umbrella issue. please don't tag individual PRs as fixing this issue.

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/test-infra repository.

[anubha-v-ardhan]

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 @bishal7679 @Babapool

[Babapool]

@anubha-v-ardhan I think it is better to review to open PRs and calibrate a fresh efforts especially for tracking the glossary localization.

[bishal7679]

@anubha-v-ardhan Yes it would be better to review all the already opened PRs and merge those
and let this issue be closed as for now!