===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/policy.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- www/policy.html	1998/11/17 01:10:30	1.10
+++ www/policy.html	1999/08/07 08:02:28	1.11
@@ -17,16 +17,16 @@
 <h1><font color=#e00000>OpenBSD Copyright Policy</font></h1>
 <p>
 Copyright law is complex, OpenBSD policy is simple - OpenBSD strives to
-maintain the spirit of the original Berkeley unix copyrights.
+maintain the spirit of the original Berkeley Unix copyrights.
 </p>
 <p>
 OpenBSD can exist as it does today because of the example set by the
 Computer Systems Research Group at Berkeley and the battles which they
-and others fought to create a relatively un-encumbered unix source
+and others fought to create a relatively un-encumbered Unix source
 distribution.
 </p>
 <p>
-The ability of a <strong>freely redistributable</strong> "Berkeley" unix
+The ability of a <strong>freely redistributable</strong> "Berkeley" Unix
 to move forward on a competitive basis with other operating systems depends
 on the willingness of the various development groups to exchange code amongst
 themselves and with other projects.
@@ -148,7 +148,7 @@
 included in OpenBSD.
 </p>
 <dt>AT&amp;T<dd><p>
-While AT&amp;T holds the copyrights to much "unix" code and documentation,
+While AT&amp;T holds the copyrights to much "Unix" code and documentation,
 OpenBSD is based largely on Berkeley (BSD) distributions that contain only
 material known to be free of AT&amp;T copyrights, or material to which
 AT&amp;T has abandoned its copyright or included licensing terms similar
@@ -176,6 +176,16 @@
 are still subject to AT&amp;T copyrights, which prevents the general
 distribution of Mach sources.
 </p>
+<dt>Apache<dd><p>
+The Apache copyright is similar to the Berkeley copyright, except
+that it stipulates that products derived from the code may not
+have "Apache" in their name.  The purpose of this clause is to
+avoid a situation in which another party releases a modified version
+of the code named in such a way to make users think that it is the
+"official" version.  This is not an issue with OpenBSD because
+OpenBSD is a <strong>Compilation</strong>, and not a
+<strong>Derived Work</strong>.
+</p>
 <dt>GNU General Public License, GPL, LGPL, copyleft, etc.<dd><p>
 The GNU Public License and licenses modeled on it impose the restriction
 that source code must be distributed or made available for all works that
@@ -207,12 +217,13 @@
 license can generally be included in OpenBSD.
 </p>
 <p>
-The current NetBSD distribution also includes material copyrighted by
-individuals who have imposed license conditions beyond that of the
-general NetBSD license, but granted the NetBSD Foundation license to
-distribute the material.  Such material can not be included in OpenBSD
-as long as the conditions imposed are at odds with the OpenBSD license
-terms or releases from those terms are offered on a discriminatory basis.
+In the past, NetBSD has included material copyrighted by individuals
+who have imposed license conditions beyond that of the general
+NetBSD license, but granted the NetBSD Foundation license to
+distribute the material.  Such material can not be included in
+OpenBSD as long as the conditions imposed are at odds with the
+OpenBSD license terms or releases from those terms are offered on
+a discriminatory basis.
 </p>
 <dt>FreeBSD<dd><p>
 Most of FreeBSD is also based on Berkeley licensed material or includes
@@ -255,7 +266,7 @@
 <hr>
 <a href=index.html><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a> 
 <a href=mailto:www@openbsd.org>www@openbsd.org</a>
-<br><small>$OpenBSD: policy.html,v 1.10 1998/11/17 01:10:30 espie Exp $</small>
+<br><small>$OpenBSD: policy.html,v 1.11 1999/08/07 08:02:28 millert Exp $</small>
 
 </body>
 </html>