You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ The OpenJS Foundation uses [EasyCLA](https://lfcla.com) to ensure that all contr
8
8
* Contributors may sign as individuals, or their company can sign on their behalf.
9
9
* Companies who sign the CLA can authorize employee usernames individually, add an entire email domain, or specify a GitHub organization containing their employees as members.
10
10
11
-
There is no cost to signing the OpenJS Foundation CLA. Please note that this is different from [membership in the OpenJS Foundation](https://openjsf.org/about/members). If your organization relies upon our projects, [please become a member](https://join.openjsf.org). Membership dues are an essential source of funding, and we rely upon them to support the OpenJS project ecosystem.
11
+
There is no cost to sign the OpenJS Foundation CLA. Please note that this is different from [membership in the OpenJS Foundation](https://openjsf.org/about/members). If your organization relies upon our projects, [please become a member](https://join.openjsf.org). Membership dues are an essential source of funding, and we rely upon them to support the OpenJS project ecosystem.
12
12
13
13
## How to use EasyCLA
14
14
@@ -33,7 +33,7 @@ If you simply want to sign the documents in preparation for future contributions
33
33
34
34
## Sign as an individual
35
35
36
-
If you are working on your own behalf and can make IP commitments about what you produce, you can sign as an individual contributor.
36
+
If you are working on your own behalf and can make IP commitments about what you produce, you can sign as an individual contributor. ([Preview the document](./openjs_foundation_icla-PREVIEW.pdf))
37
37
38
38
1. Open a PR against a repo that uses EasyCLA.
39
39
1. When blocked by the bot, follow the prompts and choose *Individual*.
@@ -46,7 +46,7 @@ That's all there is to it.
46
46
47
47
If you are doing work for someone else (e.g., it's your job), the company might need to sign for you. The advantage here is that they can authorize other employees with a single signature. If your company has already signed the document but you're still blocked, you may just need to request your username be added to the list of authorized contributors. Once this is complete you'll just have to confirm you work for them by clicking through the process one final time.
48
48
49
-
Here are the steps to have your company sign the CLA.
49
+
Here are the steps to have your company sign the CLA. ([Preview the document](./openjs_foundation_ccla-PREVIEW.pdf))
50
50
51
51
### If your company hasn't yet signed the agreement
52
52
@@ -59,7 +59,7 @@ Here are the steps to have your company sign the CLA.
59
59
60
60
### When your company has finished signing the agreement
61
61
62
-
1. Once the agreement is signed, any CLA manager can [log into the EasyCLA site](https://easycla.lfx.linuxfoundation.org/#/) (choose EasyCLA v1) and either:
62
+
1. Once the agreement is signed, any CLA manager can [log into the EasyCLA site](https://easycla.lfx.linuxfoundation.org/#/) (choose EasyCLA v2) and either:
63
63
* Add your GitHub username individually to the list of authorized contributors, or
64
64
* Add your corporate email domain, which authorizes anyone who has that email in their GitHub account, or
65
65
* Add a corporate GitHub Organization, where any member of the org is covered by the CLA.
0 commit comments