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: CONTRIBUTING.md
+9-3Lines changed: 9 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
-
# Contributing to SLEEF
1
+
# Contributing to our project
2
2
3
-
Thank you for your interest in contributing to SLEEF. We welcome contributions from the community to help improve this project.
3
+
Thank you for your interest in contributing to our project. We welcome contributions from the community to help improve this project.
4
4
5
5
However, to ensure the sustainability of the project and fairness among stakeholders, we have established specific policies for corporate contributors.
6
6
@@ -10,7 +10,11 @@ However, to ensure the sustainability of the project and fairness among stakehol
10
10
11
11
Many corporations routinely require their business partners to agree to similar provisions (such as unlimited liability and complete transfer of intellectual property). In fact, this project has explicitly been asked by corporate users of our products to agree to these exact types of clauses in the past.
12
12
13
-
Therefore, we recognize that agreeing to such clauses is a standard practice in business-to-business transactions and should **pose no obstacle** for corporate users wishing to contribute to this project.
13
+
**This CCLA was created specifically in response to those experiences.** During funding negotiations, corporate partners presented us with agreements containing the very terms listed above. When we expressed concerns about unlimited liability and IP transfer, we were told these were "standard business practices" and non-negotiable.
14
+
15
+
**As stated in our Code of Conduct, we believe corporate participants should treat open source maintainers as equal business partners.** This means not demanding contractual terms from maintainers that the corporation's own legal department would refuse to accept if presented by a counterparty.
16
+
17
+
If your legal team finds the terms in this CCLA unacceptable for your organization, we encourage you to consider why it was deemed acceptable to demand identical terms from this project's maintainers.
14
18
15
19
### Scope of Application
16
20
@@ -42,4 +46,6 @@ We understand that some organizations may prefer not to agree to the terms above
42
46
43
47
Organizations that enter into a separate Maintenance Support Agreement (which includes fair liability caps and mutual respect for IP) with the Project Maintainer are granted an **"Authorized Exemption"** status.
44
48
49
+
If your organization cannot accept the terms in this CCLA (such as unlimited liability or complete IP transfer), then it would be inconsistent to demand that the project maintainer accept those same terms in a Maintenance Support Agreement. Organizations seeking an Authorized Exemption are expected to negotiate under terms they themselves would be willing to accept.
50
+
45
51
For inquiries regarding CCLA exemption, please contact the maintainers.
0 commit comments