Open utkarsh-singh1 opened 9 months ago
This issue is currently awaiting triage.
SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted
label.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
/language hi /sig docs /area localization
Also follow these guidelines for localize content ⇾
/help /good-first-issue
@utkarsh-singh1 Please refrain from labeling issues as "good first issue" until they have been properly triaged as accepted.
/remove-help /remove-good-first-issue
I think the issue's scope is quite broad for contribution and subsequent review. The main requested page for localization seems to be the index page, which is already localized. However, the challenge lies in index page's list content which is pulled from the front matter of other pages in the same directory, which includes a total of five pages that would need to be localized for this issue to be considered completed. To address this effectively, I suggest either narrowing down the scope of the issue or breaking it down into a task list, allowing multiple contributors to pick up different parts of the issue.
/assign @Ayush9026
@dipesh-rawat I think it would be better if we retitle this as an umbrella issue like issue #35600 We can have 5 checkboxes for this issue and individual contributors can work on these checkboxes. By doing so, we can create a structured approach to track and manage the progress.
@utkarsh-singh1 : Could you please reword the description & retitle the whole issue to incorporate this suggestion
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/remove-lifecycle rotten
To address this effectively, I suggest either narrowing down the scope of the issue or breaking it down into a task list, allowing multiple contributors to pick up different parts of the issue.
It's better to have an umbrella issue that will cover the localization of these pages.
/retitle Umbrella issue for localizing /docs/setup/best-practice/ into hindi.
@utkarsh-singh1: Re-titling can only be requested by trusted users, like repository collaborators.
@Ayush9026, Have you made any progress in localizing the pages?
If not please mention the pages you are working with your assign tag.
This is a Feature Request
What would you like to be added Localize docs/setup/best-practices/ in Hindi. As there are 5 pages to localize it will be best to have individual contributors working on each of the following listed pages.
Contributors who will be localizing these pages make sure to mention the pages you are localizing with your assign.
Page - https://kubernetes.io/hi/docs/setup/best-practices/