incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1437745 - /incubator/public/branches/license_howto/licensing_howto.mdtext
Date Wed, 23 Jan 2013 21:26:50 GMT
Author: marvin
Date: Wed Jan 23 21:26:50 2013
New Revision: 1437745

Add anchors to subheadings.


Modified: incubator/public/branches/license_howto/licensing_howto.mdtext
--- incubator/public/branches/license_howto/licensing_howto.mdtext (original)
+++ incubator/public/branches/license_howto/licensing_howto.mdtext Wed Jan 23 21:26:50 2013
@@ -5,14 +5,12 @@ Title: Assembling LICENSE and NOTICE.
 Assembling LICENSE and NOTICE
-Intended Audience
+## Intended Audience ## {#audience}
 This document is a "how to" guide aimed at Apache Committers assembling
 `LICENSE` and `NOTICE` files for an Apache product.
-Overview of the `LICENSE` and `NOTICE` files
+## Overview of the `LICENSE` and `NOTICE` files ## {#overview-of-files}
 The `LICENSE` file communicates the licensing of all content in an Apache
 product distribution.  It always contains the text of the Apache License, and
@@ -26,16 +24,14 @@ policy](
 The complete requirements for `LICENSE` and `NOTICE` are described
-Location Within the Source Tree
+## Location Within the Source Tree ## {#source-tree-location}
 `LICENSE` and `NOTICE` belong at the [top level of the source
 tree](  They may
 be named `LICENSE.txt` and `NOTICE.txt`, but the [bare names are
-The Simple Case -- No Bundled Dependencies
+## The Simple Case -- No Bundled Dependencies ## {#simple}
 For a source tree which consists entirely of code licensed to the ASF by the
 copyright holders and which has no bundled dependencies, `LICENSE` should
@@ -52,8 +48,7 @@ product's name and copyright dates:
     This product includes software developed at
     The Apache Software Foundation (
-Bundling Permissively-Licensed Dependencies
+# Bundling Permissively-Licensed Dependencies # {#permissive-deps}
 Bundling a dependency which is issued under one of the following licenses is
 straightforward, assuming that said license applies uniformly to all files
@@ -76,8 +71,7 @@ by the ASF Legal Affairs Committee.  Som
 `NOTICE` -- if in doubt,
-Bundling an Apache-2.0-licensed Dependency
+## Bundling an Apache-2.0-licensed Dependency ## {#alv2-dep}
 Assuming once again that that the dependency subtree contains no bundled
 subcomponents under other licenses and thus the ALv2 applies uniformly to all
@@ -93,8 +87,7 @@ developed at the Apache Software Foundat
 and any other portions of `NOTICE` must be considered for propagation.
-Modifications to NOTICE
+# Modifications to NOTICE # {#mod-notice}
 Aside from Apache-licensed dependencies which supply `NOTICE` files of their
 own, it is uncommon for a dependency to require additions to `NOTICE`.  `NOTICE`
@@ -111,16 +104,14 @@ addition places a burden on downstream c
 `NOTICE` which is not legally required._
-Non-bundled Dependencies
+# Non-bundled Dependencies # {#non-bundled-deps}
 Dependencies which are not included within the distribution MUST NOT be added
 to `LICENSE` and `NOTICE`.  As far as `LICENSE` and `NOTICE` are concerned,
 _only bundled bits matter._
-Dependencies of Dependencies
+# Dependencies of Dependencies # {#deps-of-deps}
 Dependencies of dependencies (including so-called "transitive dependencies")
 are no different from first-order dependencies for the purposes of assembling

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message