Update CONTRIBUTING.md

[jeremyrickard]

The CONTRIBUTING.md file in this repository is a fairly generic template. One of the questions in the 2022 annual report asked:

Does your [CONTRIBUTING.md] help new contributors engage with your group specifically by pointing to activities or programs that provide useful context or allow easy participation?

I believe we have this information in other places, but it would be beneficial to contributors to pull this into a the CONTRIBUTING.md file in order to make it more discoverable.

[matglas]

Here are a few ideas looking at other CONTRIBUTING docs.

• Different sections

  • Getting started (seen multiple times)
  • Mentorship
  • Before you begin
  • Your first contribution (seen multiple times)
  • Workflow
  • Issue triaging
  • Use of mentions (seen multiple times)
  • Getting in touch
  • Code reviews
  • Community guidelines

• The kubernetes/sig-release/CONTRIBUTING.md is much more expanded. Maybe its good to reference a 'central' sig-release contributing md and expand into specific for each repo. This could help build easier context for new comers. Like me 😉

• Interesting on SIG-cli (here) a "Pick your track". Guiding the user for different ways of CONTRIBUTING.

• SIG-cli has more interesting subsections that help the contributor.

• The community/sig-release is missing a CONTRIBUTING.md. This might be the place where people go when they are first interested in the SIG.

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[vaibhav2107]

/remove-lifecycle stale

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[xmudrii]

/remove-lifecycle stale

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[xmudrii]

/lifecycle frozen