Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[hi] Tracking Hindi localization progress #29353

Closed
52 tasks done
anubha-v-ardhan opened this issue Aug 13, 2021 · 169 comments
Closed
52 tasks done

[hi] Tracking Hindi localization progress #29353

anubha-v-ardhan opened this issue Aug 13, 2021 · 169 comments
Labels
area/localization General issues or PRs related to localization kind/feature Categorizes issue or PR as related to a new feature. language/hi Issues or PRs related to Hindi language triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@anubha-v-ardhan
Copy link
Member

anubha-v-ardhan commented Aug 13, 2021 •
edited
Loading

Summary of progress till now: #29353 (comment)

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:

Reviewers:

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)

releases (content/en/releases)

includes (content/en/includes)

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

Docs (content/en/docs)

concepts (content/en/docs/concepts)

overview

contribute (content/en/docs/contribute)

reference (content/en/docs/reference)

glossary

home (content/en/docs/home)

setup (content/en/docs/setup)

best-practices

learning-environment

production-environment

windows

tasks (content/en/docs/tasks)

tools

included

tutorials (content/en/docs/tutorials)

kubernetes-basics

create-cluster

deploy-app

explore

expose

scale

update

Site strings (data/i8n/hi)
@anubha-v-ardhan anubha-v-ardhan added the kind/feature Categorizes issue or PR as related to a new feature. label Aug 13, 2021
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Aug 13, 2021
@anubha-v-ardhan
Copy link
Member Author

/language hi

@k8s-ci-robot k8s-ci-robot added the language/hi Issues or PRs related to Hindi language label Aug 13, 2021
@verma-kunal
Copy link
Contributor

Nice work @anubha-v-ardhan !! 👍

@anubha-v-ardhan anubha-v-ardhan mentioned this issue Aug 13, 2021
Closed
65 tasks
@anubha-v-ardhan
Copy link
Member Author

@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
Copy link
Contributor

alright sure!! Understood 👍

@verma-kunal
Copy link
Contributor

verma-kunal commented Aug 13, 2021 •
edited
Loading

@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
Copy link
Member Author

anubha-v-ardhan commented Aug 13, 2021 •
edited
Loading

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
Copy link
Contributor

verma-kunal commented Aug 13, 2021 •
edited
Loading

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
Copy link
Contributor

verma-kunal commented Aug 13, 2021 •
edited
Loading

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
Copy link
Member Author

anubha-v-ardhan commented Aug 13, 2021 •
edited
Loading

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

@anubha-v-ardhan
Copy link
Member Author

anubha-v-ardhan commented Aug 13, 2021 •
edited
Loading

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

@verma-kunal
Copy link
Contributor

@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
Copy link
Contributor

keshavcodex commented Aug 13, 2021 •
edited
Loading

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

@ShivamTyagi12345
Copy link
Member

ShivamTyagi12345 commented Aug 13, 2021 •
edited
Loading

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

@verma-kunal
Copy link
Contributor

@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
Copy link
Member Author

anubha-v-ardhan commented Aug 13, 2021 •
edited
Loading

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

This was referenced Aug 13, 2021
Closed
Closed
Closed
Closed
@verma-kunal
Copy link
Contributor

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

@anubha-v-ardhan anubha-v-ardhan mentioned this issue Aug 13, 2021
Closed
@anubha-v-ardhan anubha-v-ardhan changed the title Tracking Hindi localisation progress [hi] Tracking Hindi localisation progress Aug 13, 2021
@anubha-v-ardhan
Copy link
Member Author

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

@anubha-v-ardhan anubha-v-ardhan mentioned this issue Aug 13, 2021
Closed
@sftim
Copy link
Contributor

sftim commented Mar 1, 2022

I'm guessing that #31987 is the last piece before launch - have I got that right?

@anubha-v-ardhan
Copy link
Member Author

I'm guessing that #31987 is the last piece before launch - have I got that right?

Yes @sftim !!

@sftim
Copy link
Contributor

sftim commented May 9, 2022

In #29679 I can see an error logged. That will need fixing before we can merge the changes.

@anubha-v-ardhan anubha-v-ardhan mentioned this issue Aug 1, 2022
Closed
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 7, 2022
@anubha-v-ardhan
Copy link
Member Author

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 7, 2022
@anubha-v-ardhan
Copy link
Member Author

Closing this issue
Hindi localization is live now with merge of #29679
Great work everyone!

@sftim
Copy link
Contributor

sftim commented Aug 31, 2022

It's OK (and a good idea) to open a new tracking issue to cover future work on Hindi.

Is it OK to delete the branch dev-1.22-hi.1 now?

@verma-kunal
Copy link
Contributor

It's OK (and a good idea) to open a new tracking issue to cover future work on Hindi.

I totally agree with this!

Is it OK to delete the branch dev-1.22-hi.1 now?

I believe if we'll directly be making PRs to the main branch, then we could delete.
There was a conversation about making PRs from dev-1.22-hi.1 branch in batches of 5-10 localised pages to the main branch!
Was any decision made on what approach we'll be following?!

@anubha-v-ardhan
Copy link
Member Author

Let's discuss on Slack

@anubha-v-ardhan
Copy link
Member Author

It's OK (and a good idea) to open a new tracking issue to cover future work on Hindi.

Good idea @sftim but looks like folks have already started working under umbrella issues such as #36455 and #35600 making separate issues for each page.

@rolfedh rolfedh mentioned this issue Sep 2, 2022
Open
@sftim
Copy link
Contributor

sftim commented Mar 17, 2023

/reopen

This is the overall umbrella issue for the Hindi work.

@k8s-ci-robot
Copy link
Contributor

@sftim: Reopened this issue.

In response to this:

/reopen

This is the overall umbrella issue for the Hindi work.

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.

@k8s-ci-robot k8s-ci-robot reopened this Mar 17, 2023
@sftim sftim mentioned this issue Mar 17, 2023
Closed
@Kanika637
Copy link

As I opened the issue #40095, may I proceed with the specified work? @sftim

@sftim
Copy link
Contributor

sftim commented Mar 17, 2023

I recommend either closing #40095, or reshaping it to clearly track specific improvements.

This is open source. Anyone willing to honor our values and abide by the code of conduct is welcome to contribute. You don't need permission! You - and everyone else - are welcome to open a pull request.

See https://www.k8s.dev/docs/guide/ for more tips.

This was referenced Aug 16, 2023
Closed
Closed
@sftim
Copy link
Contributor

sftim commented Aug 20, 2023

Also see #42653

@divya-mohan0209
Copy link
Contributor

Hello @sftim , I don't think tracking progress on this issue is feasible any longer. As a cleanup measure, what I propose we do is:

  • Close this issue.
  • Open two fresh tracking issues - one for updating the documentation & one for introducing new documentation.
  • Invite people to work off these two issues individually.

Does that sound okay by you? I ask, because you reopened this issue recently.

@sftim
Copy link
Contributor

sftim commented Jan 4, 2024

/area localization

I've no objection to this issue getting closed.

@k8s-ci-robot k8s-ci-robot added the area/localization General issues or PRs related to localization label Jan 4, 2024
@seokho-son
Copy link
Member

Hi folks! From the discussions in #29353 (comment) and #29353 (comment), it seems we've reached a general consensus on closing this issue. Considering that SIG-Docs is endeavoring to manage the quantity of open issues, I'll go ahead and close this issue.

/close

@k8s-ci-robot
Copy link
Contributor

@seokho-son: Closing this issue.

In response to this:

Hi folks! From the discussions in #29353 (comment) and #29353 (comment), it seems we've reached a general consensus on closing this issue. Considering that SIG-Docs is endeavoring to manage the quantity of open issues, I'll go ahead and close this issue.

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/localization General issues or PRs related to localization kind/feature Categorizes issue or PR as related to a new feature. language/hi Issues or PRs related to Hindi language triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests