Yes, we should probably have links there. Do you feel like trying your hand at a simple PR?

Yes of course, I was looking into it and would be happy to work on a PR.

/assign

I've found the Contributor Cheatsheet document, which links to kubernetes/community/CLA.md. This document describes the CLA process more clearly. However, I'm unsure why the Contributor Cheatsheet differs from the one I linked in this issue.

Should we update the contributors website to also point to kubernetes/community/CLA.md?

Or even use the same content in both documents:

https://www.kubernetes.dev/docs/contributor-cheatsheet/#submitting-a-contribution:

https://www.kubernetes.dev/docs/guide/#sign-the-cla:

@jberkus Could you please clarify the next steps? I'd like to move it forward.

I think we should probably link out to the other document. The page is intentionally brief on all topics, and I think having a lot of detail on the CLA in the Getting Started page itself isn't ideal.

Also, the CLA signing process has changed a couple times over the years, and will probably change again in the future. So for the detailed explaination, we want it in only one place.

So, recommended cleanup for this page is: note that the bot will supply links to sign the CLA if you submit a PR, and that the contributor can find more information at CLA.md.

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