linking-to-sections diff

Previous Topic Next Topic
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

linking-to-sections diff


Would you consider accepting the below diff?

The purpose of its addition of id parameters in a bunch of places is
enabling savvy visitors to link directly to subsections of the page.
E.g. a user could then send someone a link to , i.e. specifically to the part
of the page that's about the ISC license, etc.

Alternatively, the same ends could be accomplished in a more generally
user-visible way with the addition of clickable anchor tags, and I'd
be happy to whip up another diff in case the latter turned out to be


diff -u policy.html.orig policy.html
--- policy.html.orig    2014-03-06 17:22:40.000000000 +0100
+++ policy.html    2014-03-06 17:39:32.000000000 +0100
@@ -19,7 +19,7 @@

-<li><h3><font color="#e00000">Goal</font></h3><p>
+<li><h3 id="goal"><font color="#e00000">Goal</font></h3><p>

 Copyright law is complex, OpenBSD policy is simple - OpenBSD strives to
 maintain the spirit of the original Berkeley Unix copyrights.
@@ -41,7 +41,7 @@
 cooperation of the people involved.

-<li><h3><font color="#e00000">The Berkeley Copyright</font></h3><p>
+<li><h3 id="berkeley"><font color="#e00000">The Berkeley

 The Berkeley copyright poses no restrictions on private or commercial
 use of the software and imposes only simple and uniform requirements
@@ -100,7 +100,7 @@
 components may not be.

-<li><h3><font color="#e00000">Copyright Law</font></h3><p>
+<li><h3 id="law"><font color="#e00000">Copyright Law</font></h3><p>
 While the overall subject of copyright law is far beyond the scope of
 this document, some basics are in order.  Under the current copyright law,
 copyrights are implicit in the creation of a new work and reside with
@@ -137,7 +137,7 @@
 with respect to liability surrounding use of the material.

-<li><h3><font color="#e00000">Permissions - the flip side</font></h3><p>
+<li><h3 id="permissions"><font color="#e00000">Permissions - the flip

 Because copyrights arise from the creation of a work, rather than through
 a registration process, there needs to be a practical way to extend
@@ -184,14 +184,14 @@
 more restrictive permissions in his future distributions of that work.

-<li><h3><font color="#e00000">Specific Cases</font></h3><p>
+<li><h3 id="licenses"><font color="#e00000">Specific Cases</font></h3><p>

 This section attempts to summarize the position of OpenBSD relative to
 some commonly encountered copyrights.

+<dt id="berkeley-redux">Berkeley<dd><p>
 The Berkeley copyright is the model for the OpenBSD copyright.  It retains
 the rights of the copyright holder, while imposing minimal conditions on
 the use of the copyrighted material.  Material with Berkeley copyrights,
@@ -199,7 +199,7 @@
 included in OpenBSD.

+<dt id="att">AT&amp;T<dd><p>
 As part of its settlement with AT&amp;T, Berkeley included an
 AT&amp;T copyright notice on some of the files in 4.4BSD lite and lite2.
 The terms of this license are identical to the standard Berkeley license.
@@ -209,7 +209,7 @@
 <a href="">awk</a>.

+<dt id="caldera">Caldera<dd><p>
 Caldera (now known as the SCO group) is the current owner of the Unix
 code copyrights.  On 23 January 2002, the original Unix code (versions 1
 through seven, including 32V) was freed by Caldera.  This code is now
@@ -220,7 +220,7 @@
 to bring it up to date).

-<dt>DEC, Sun, other manufacturers/software houses.<dd><p>
+<dt id="dec">DEC, Sun, other manufacturers/software houses.<dd><p>
 In general OpenBSD does not include material copyrighted by manufacturers
 or software houses.  Material may be included where the copyright owner has
 granted general permission for reuse without conditions, with terms similar
@@ -229,7 +229,7 @@
 rights they might have to the work.

-<dt>Carnegie-Mellon (CMU, Mach)<dd><p>
+<dt id="cmu">Carnegie-Mellon (CMU, Mach)<dd><p>
 The Carnegie-Mellon copyright is similar to the Berkeley copyright, except
 that it requests that derivative works be made available to Carnegie-Mellon.
 Because this is only a request and not a condition, such material can still
@@ -238,7 +238,7 @@
 distribution of Mach sources.

+<dt id="apache">Apache<dd><p>
 The original 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
@@ -253,7 +253,7 @@
 version includes many enhancements and bugfixes.

+<dt id="isc">ISC<dd><p>
 The ISC copyright is functionally equivalent to a two-term BSD
 copyright with language removed that is made unnecessary by the
 Berne convention.  This is the preferred license for new code
@@ -263,7 +263,7 @@

-<dt>GNU General Public License, GPL, LGPL, copyleft, etc.<dd><p>
+<dt id="gpl">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
 are derivatives of the GNU copyrighted code.
@@ -285,7 +285,7 @@
 GPL terms.

+<dt id="netbsd">NetBSD<dd><p>
 Much of OpenBSD is originally based on and evolved from NetBSD, since some
 of the OpenBSD developers were involved in the NetBSD project.  The general
 NetBSD license terms are compatible with the Berkeley license and permit
@@ -302,7 +302,7 @@
 a discriminatory basis.

+<dt id="freebsd">FreeBSD<dd><p>
 Most of FreeBSD is also based on Berkeley licensed material or includes
 copyright notices based on the Berkeley model.  Such material can be
 included in OpenBSD, while those parts that are subject to GPL or
@@ -310,7 +310,7 @@
 can not be included in OpenBSD.

+<dt id="linux">Linux<dd><p>
 Most of Linux is subject to GPL style licensing terms and therefore
 can not be included in OpenBSD.  Individual components may be eligible,
 subject to the terms of the originator's copyright notices.  Note that
@@ -319,14 +319,14 @@
 included that is not part of the Linux core.

-<dt>X, XFree86, X.Org<dd><p>
+<dt id="x">X, XFree86, X.Org<dd><p>
 X, X.Org or XFree86 are not parts of OpenBSD, rather X.Org and parts of
 XFree86 3.3.6 are distributed
 with many OpenBSD ports as a convenience to the user, subject to applicable
 license terms.

-<dt>Shareware, Charityware, Freeware, etc.<dd><p>
+<dt id="sw">Shareware, Charityware, Freeware, etc.<dd><p>
 Most "shareware" copyright notices impose conditions for redistribution,
 use or visibility that are at conflict with the OpenBSD project goals.
 Review on a case-by-case basis is required as to whether the wording
@@ -335,7 +335,7 @@
 goals of the OpenBSD project.

-<dt>Public Domain<dd><p>
+<dt id="pd">Public Domain<dd><p>
 While material that is truly entered into the "Public Domain" can be
 included in OpenBSD, review is required on a case by case basis.
 Frequently the "public domain" assertion is made by someone who does