-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Contributors website docs/guid#sign-the-cla has no link to CNCF's easycla #576
Comments
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: |
@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. |
I've found that the Sign the CLA part of contributors website is misleading since it only states:
It doesn't note the process of signing the actual CLA at easycla part of CNCF website.
But when you do a PR, the bot will reject and complains about signing the CLA.
The text was updated successfully, but these errors were encountered: