[openssl-commits] [web] master update
Tim Hudson
tjh at openssl.org
Thu Jan 5 20:07:02 UTC 2017
The branch master has been updated
via 54431437a78392906910d31ca59cd6591e3ef0ba (commit)
from 34b6c6f1701d8f583479ac56614c8241d98efb67 (commit)
- Log -----------------------------------------------------------------
commit 54431437a78392906910d31ca59cd6591e3ef0ba
Author: Tim Hudson <tjh at cryptsoft.com>
Date: Fri Jan 6 06:06:19 2017 +1000
update policy based on team vote
see bureau commit 0f7c5c6b1fc37b4418aaf7789ab3548eb37cb9e9
-----------------------------------------------------------------------
Summary of changes:
policies/cla.html | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/policies/cla.html b/policies/cla.html
index b79f550..f234dde 100644
--- a/policies/cla.html
+++ b/policies/cla.html
@@ -15,15 +15,15 @@
Every non-trival contribution to be
covered by a signed
Contributor License Agreement (CLA).
- We are mostly following the practice of
+ We have modelled our policy based on the practice of
<a href="https://www.apache.org">the Apache Software Foundation</a>.
You can see their CLA policy
<a href="https://www.apache.org/licenses/#clas">here</a>.
- Or, you can just read the following paragraphs :)
+ Our policy is:
</p>
<p>
- OpenSSL desires that all contributors of ideas, code, or
+ OpenSSL requires that all non-trivial contributors of ideas, code, or
documentation complete, sign, and submit (via postal mail, fax
or email) an Individual CLA [<a href="openssl_icla.pdf">PDF</a>].
The purpose of this agreement is to clearly define
@@ -44,8 +44,8 @@
is available for contributing intellectual property via
the corporation, that may have been assigned as part of an
employment agreement. Note that a Corporate CLA does not
- cover any individual contributions which are not owned by the
- corporation signing the CCLA.
+ remove the need for every developer to sign their own ICLA as
+ an individual.
</p>
<p>
More information about the openssl-commits
mailing list