summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAnirudh <ramanathana@google.com>2016-11-22 12:17:29 -0800
committerAnirudh <ramanathana@google.com>2016-11-22 12:17:29 -0800
commit3a73c0f9f125a7ff76d1d16abb1d1f80922a9128 (patch)
tree3f0f494ee470e877671c36569a2a566a7fafe7da
parentd7cebb3b12a340ba9dc63648ac789e7df053e25c (diff)
Adding CLA-FAQ.
-rw-r--r--CLA.md29
1 files changed, 29 insertions, 0 deletions
diff --git a/CLA.md b/CLA.md
new file mode 100644
index 00000000..1464e2bb
--- /dev/null
+++ b/CLA.md
@@ -0,0 +1,29 @@
+### How do I sign the CNCF CLA?
+
+* To sign up as an individual or as an employee of a signed organization, go to https://identity.linuxfoundation.org/projects/cncf
+* To sign up as an organization, go to https://identity.linuxfoundation.org/node/285/organization-signup
+
+***
+
+### After you select one of the options above, please follow the instructions below:
+
+**Step 1**: You must sign in with GitHub.
+
+**Step 2**: If you are signing up as an employee, you must use your official person@organization.domain email address in the CNCF account registration page.
+
+
+**Step 3**: The email you use on your commits (https://help.github.com/articles/setting-your-email-in-git/) must match the email address you use when signing up for the CNCF account.
+
+![CNCFCLA](http://i.imgur.com/tEk2x3j.png)
+![CNCFCLA2](http://i.imgur.com/t3WAtrz.png)
+
+
+**Step 4**: Once the CLA sent to your email address is signed (or your email address is verified in case your organization has signed the CLA), you should be able to check that you are authorized in any new PR you create.
+
+![CNCFCLA3](http://i.imgur.com/C5ZsNN6.png)
+
+**Step 5**: The status on your old PRs will be updated when any new comment is made on it.
+
+### I’m having issues with signing the CLA.
+
+If you’re facing difficulty with signing the CNCF CLA, please explain your case on https://github.com/kubernetes/kubernetes/issues/27796 and we (@sarahnovotny and @foxish), along with the CNCF will help sort it out.