[hi] Put together a "welcome package" of information to share with new volunteers on #kubernetes-docs-hi

[rolfedh]

For folks who express an interest in volunteering for /hi localization on #kubernetes-docs-hi and elsewhere, it would be nice to establish ways of:

• Welcoming them.
• Providing the information they need to get started.
• Connect them with an onboarding friend who can answer their questions and show them the way.

The welcoming might be done by agreement among the team.

The information package might include the following:

• A set of links to key documents:
  • General localization topics.
  • /hi-specific localization topics, such as the style guide.

The onboarding friend might be done by enlisting volunteers from the team. Assignments might be done by self-assignment or by a coordinator making round-robin assignments.

[rolfedh]

/language hi

[bishal7679]

/triage accepted

[bishal7679]

@rolfedh Its really a great initiative.
will be glad to be a part of this.

[rolfedh]

/assign @amolmote @bishal7679
Thank you both for volunteering. Let's work together on this together.

[k8s-ci-robot]

@rolfedh: GitHub didn't allow me to assign the following users: amolmote.

Note that only kubernetes members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @amolmote @bishal7679
Thank you both for volunteering. Let's work together on this together.

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]

@bishal7679: GitHub didn't allow me to assign the following users: amolmote.

Note that only kubernetes members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @amolmote

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.

[amolmote]

I think I require to comment on this PR then only command will work

[bishal7679]

/assign @amolmote

[amolmote]

Glad to be the part of this feature 🎉😊

[rolfedh]

@anubha-v-ardhan 's tracker #29353 contains some interesting links for contributors that we should include in a welcome package.

[k8s-triage-robot]

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-triage-robot]

The Kubernetes project currently lacks enough active 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 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 rotten

[rakshitgondwal]

Is this issue still open for grabs? @rolfedh

[rolfedh]

Hi @rakshitgondwal. Thanks for your interest. Please check with @bishal7679 and @amolmote on the #kubernetes-docs-hi channel in Slack.

[divya-mohan0209]

/remove-lifecycle rotten

[divya-mohan0209]

As an active maintainer for the Kubernetes Hindi docs, I will be un-assigning Bishal and Amol since there hasn't been any progress on this issue since a long time.
Please consider re-assigning yourself if you have the bandwidth to work on this.
The expected outcome from this tracking issue would be the following:

• Revamp the slack channel description to point to the current docs for Hindi localization
• Understand from the previous assignees if there was any work done in the form of a formal contribution to the docs.
• If there was, report it on the issue. If there wasn't, work your way thro the checklist provided in the description.