sig-node: CONTRIBUTING.md updates

[endocrimes]

/sig node
/kind documentation

The sig-node contributor documentation currently assumes a lot of existing knowledge about how the kubernetes project works. To help foster new contributions from people who don't necessarily have existing upstream contributor knowledge, or people within their organization who can train them we should update this document.

I think we probably need to focus on the following as a first step:

• How do you get the code and build/test a kubelet change
  • e.g you likely need access to a linux machine/vm with containerd or cri-o installed, might not be obvious to a new contrib.
• How do you make a good first contribution
  • How do you find issues?
  • How do you request feedback?

Something to think about in a future community meeting would be talking about how we can help foster these contributions. Reviewer/Approver capacity is low, but we can't fix that without new contributors long term.

[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

[endocrimes]

/remove-lifecycle rotten
/lifecycle frozen

[ibilalkayy]

Hey @endocrimes what do you want to achieve in this issue? I didn't understand. I am new to open source and I just want to help. Can you please guide me? Thank you!