[llvm-commits] CVS: llvm/docs/DeveloperPolicy.html

Reid Spencer reid at x10sys.com
Wed Feb 14 14:55:57 PST 2007



Changes in directory llvm/docs:

DeveloperPolicy.html updated: 1.16 -> 1.17
---
Log message:

Add feedback from Vikram Adve.


---
Diffs of the changes:  (+17 -3)

 DeveloperPolicy.html |   20 +++++++++++++++++---
 1 files changed, 17 insertions(+), 3 deletions(-)


Index: llvm/docs/DeveloperPolicy.html
diff -u llvm/docs/DeveloperPolicy.html:1.16 llvm/docs/DeveloperPolicy.html:1.17
--- llvm/docs/DeveloperPolicy.html:1.16	Wed Feb 14 11:24:04 2007
+++ llvm/docs/DeveloperPolicy.html	Wed Feb 14 16:55:40 2007
@@ -55,6 +55,13 @@
   might arise from the distributed nature of LLVM's development.  By stating 
   the policy in clear terms, we hope each developer can know ahead of time
   what to expect when making LLVM contributions.</p>
+  <p>This policy is also designed to accomplish the following objectives:</p>
+  <ol>
+    <li>Attract both users and developers to the LLVM project.</li>
+    <li>Make life as simple and easy for contributors as possible.</li>
+    <li>Indicate that LLVM is a mature project with a thriving community and
+    sensible policies directing its ongoing development.</li>
+  </ol>
 </div>
 
 <!--=========================================================================-->
@@ -217,6 +224,9 @@
     <li>Patches should not include differences in generated code such as the
     code generated by <tt>flex</tt>, <tt>bison</tt> or <tt>tblgen</tt>. The
     <tt>utils/mkpatch</tt> utility takes care of this for you.</li>
+    <li>Patches must not include any patent violations. To the best of our
+    knowledge, LLVM is free of any existing patent violations and it is our 
+    intent to keep it that way. </li>
   </ol>
 </div>
 <!-- _______________________________________________________________________ -->
@@ -405,8 +415,8 @@
   </ul>
   <p>We believe this fosters the widest adoption of LLVM because it allows 
   commercial products to be derived from LLVM with few restrictions and
-  without a requirement for making any derived works also open source. We
-  suggest that you read the 
+  without a requirement for making any derived works also open source (i.e. 
+  LLVM' license is not a <i>copyleft</i> license). We suggest that you read the 
   <a href="http://www.opensource.org/licenses/UoI-NCSA.php">License</a> if
   further clarification is needed.</p>
 </div>
@@ -436,6 +446,10 @@
     <dt><a name="t_commit">Commit</a><dt>
     <dd>A <a href="t_change">change</a> submitted directly to LLVM software
     repository via the <tt>cvs commit</tt> command.</dd>
+    <dt><a name="t_copleft">Copyleft</a></dt>
+    <dd>A licensing policy that requires the licensee to adopt the terms of the
+    license for <i>derived</i> works. LLVM does not subscribe to this
+    policy.</dd>
     <dt><a name="t_developer">Developer</a></dt>
     <dd>Anyone who submits a <a href="#t_change">change</a> to LLVM.</dd>
     <dt><a name="t_inrement">Increment</a></dt>
@@ -478,7 +492,7 @@
   Written By: the 
   <a href="mailto:llvm-oversight at cs.uiuc.edu">LLVM Oversight Group</a><br>
   <a href="http://llvm.org">The LLVM Compiler Infrastructure</a><br>
-  Last modified: $Date: 2007/02/14 17:24:04 $
+  Last modified: $Date: 2007/02/14 22:55:40 $
 </address>
 </body>
 </html>






More information about the llvm-commits mailing list