Document SIG Docs New Contributor Ambassador Program

[divya-mohan0209]

cc: @RinkiyaKeDad @natalisucks @reylejano @jimangel

We require more documentation around the New Contributor Ambassador role to set off with the formalization of the process. Opening up this issue to track the progress in these potential areas

• Modify README
• Discuss potential for inclusion in Contributor guide for SIG Docs
• If outcome of above discussion is a yes, suitable edits to be made on the Contributor guide.

These are a few places I could think of. Please use this issue as an avenue for discussing any other areas that might benefit from including details about the role.

[RinkiyaKeDad]

/assign

[RinkiyaKeDad]

Thanks for opening the issue to track this @divya-mohan0209! By "Contributor guide" do you mean https://kubernetes.io/docs/contribute/?

[RinkiyaKeDad]

/triage accepted

[divya-mohan0209]

@RinkiyaKeDad : Yes, I don't know if it'd be a good fit given the nature of the contributor guide. But we need to have it documented somewhere as a role like we have the Release Team shadow/role leads under the sig-release repo.

[sftim]

/language en
/sig docs

[RinkiyaKeDad]

Ping to update the checklist :) Readme has been updated, will start a discussion on Slack to see if the Contributor guide needs to be updated next.

[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

[RinkiyaKeDad]

/remove-lifecycle stale

I can get to this next month!

[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

[divya-mohan0209]

/remove-lifecycle rotten

[divya-mohan0209]

@RinkiyaKeDad - gentle reminder on this one. Do you need anything from our side?

[RinkiyaKeDad]

@RinkiyaKeDad - gentle reminder on this one. Do you need anything from our side?

Thanks! This totally fell off radar. I'll get the discussions for this going this week!

[RinkiyaKeDad]

Started discussions here: https://kubernetes.slack.com/archives/C1J0BPD2M/p1666775238623839

[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

[divya-mohan0209]

/remove-lifecycle stale

[divya-mohan0209]

Hello @RinkiyaKeDad , please may I know if you have had a chance to work on this? Please let us know if you need anything from our side.

[RinkiyaKeDad]

Hey @divya-mohan0209, if you see the Slack thread in the comment above, I need someone to confirm if it is okay to proceed with adding the section on that page. LMK if yes, and I will make the PR!

[divya-mohan0209]

@RinkiyaKeDad thank you for clarifying. However the expectation was to timebox the consensus seeking process to a few days/weeks. After which, the PR you submit for amending the page would be put through a formal review by the website approvers & reviewers. So, if there is no dissent/feedback, it'd be okay for us to now have a PR opened to k/website per the initial idea & then figure out the placement/duplication there onwards.

[RinkiyaKeDad]

Hello! I talked with Sreeram on one of our New Contributors Meet and Greet calls, and they expressed an interest in picking this issue up so I'm assigning them for now. I have communicated what needs to be done over the call to them and given them the required context. @sreeram-venkitesh please feel free to ping me if you have more questions and tag me for a review on the PR!

/assign @sreeram-venkitesh

[k8s-ci-robot]

@RinkiyaKeDad: GitHub didn't allow me to assign the following users: sreeram-venkitesh.

Note that only kubernetes members with read permissions, 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:

Hello! I talked with Sreeram on one of our New Contributors Meet and Greet calls, and they expressed an interest in picking this issue up so I'm assigning them for now. I have communicated what needs to be done over the call to them and given them the required context. @sreeram-venkitesh please feel free to ping me if you have more questions and tag me for a review on the PR!

/assign @sreeram-venkitesh

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.

[sreeram-venkitesh]

/assign @sreeram-venkitesh

[divya-mohan0209]

@RinkiyaKeDad @sreeram-venkitesh : Any updates on this? Please can we prioritise work on this?

[sreeram-venkitesh]

Sorry for the delay! Will work on this on priority.

[divya-mohan0209]

@sreeram-venkitesh - Any updates on this, please?

[sreeram-venkitesh]

@divya-mohan0209 I have raised a PR and asked for review from @RinkiyaKeDad . Sorry for the delay in getting this done!

[divya-mohan0209]

All the objectives to track the formalisation of the New Contributor Ambassador have been completed with the merge of #42481 . Hence closing this as completed.
/close

[k8s-ci-robot]

@divya-mohan0209: Closing this issue.

In response to this:

All the objectives to track the formalisation of the New Contributor Ambassador have been completed with the merge of #42481 . Hence closing this as completed.
/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.