From 54431437a78392906910d31ca59cd6591e3ef0ba Mon Sep 17 00:00:00 2001
From: Tim Hudson <tjh@cryptsoft.com>
Date: Fri, 6 Jan 2017 06:06:19 +1000
Subject: [PATCH] update policy based on team vote

see bureau commit 0f7c5c6b1fc37b4418aaf7789ab3548eb37cb9e9
---
 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>
-- 
2.34.1