Clarify copyright transfer when you don't own the copyright of

the contributed code.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@51329 91177308-0d34-0410-b5e6-96231b3b80d8

1 files changed, 9 insertions, 2 deletions

diff --git a/docs/DeveloperPolicy.html b/docs/DeveloperPolicy.html
index 18c1ff34ac..ab985b565b 100644
--- a/docs/DeveloperPolicy.html
+++ b/docs/DeveloperPolicy.html
@@ -458,7 +458,7 @@ Changes</a></div>
   
   <p>
   Although UIUC may eventually reassign the copyright of the software to another
-  entity (e.g. a dedicated non-profit "LLVM Organization", or something)
+  entity (e.g. a dedicated non-profit "LLVM Organization")
   the intent for the project is to always have a single entity hold the
   copyrights to LLVM at any given time.</p>
   
@@ -467,6 +467,12 @@ Changes</a></div>
   reduces the managerial burden for any kind of administrative or technical 
   decisions about LLVM.  The goal of the LLVM project is to always keep the code
   open and <a href="#license">licensed under a very liberal license</a>.</p>
+
+  <p>When contributing code, you also affirm that you are legally entitled to 
+  grant this copyright, personally or on behalf of your employer.  If the code
+  belongs to some other entity, please raise this issue with the oversight
+  group before the code is committed.</p>
+
 </div>
 
 <!-- _______________________________________________________________________ -->
@@ -480,7 +486,8 @@ Changes</a></div>
   <ul>
     <li>You can freely distribute LLVM.</li>
     <li>You must retain the copyright notice if you redistribute LLVM.</li>
-    <li>Binaries derived from LLVM must reproduce the copyright notice.</li>
+    <li>Binaries derived from LLVM must reproduce the copyright notice (e.g. 
+        in an included readme file).</li>
     <li>You can't use our names to promote your LLVM derived products.</li>
     <li>There's no warranty on LLVM at all.</li>
   </ul>