You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by se...@apache.org on 2008/04/23 13:14:44 UTC
svn commit: r650828 - in /infrastructure/site/trunk/docs:
legal/src-headers.html licenses/exports/index.html licenses/index.html
licenses/proposed/index.html
Author: sebb
Date: Wed Apr 23 04:14:32 2008
New Revision: 650828
URL: http://svn.apache.org/viewvc?rev=650828&view=rev
Log:
Regenerate site:
Replace <a name="anchor"> with <h5/6 id="anchor">
Modified:
infrastructure/site/trunk/docs/legal/src-headers.html
infrastructure/site/trunk/docs/licenses/exports/index.html
infrastructure/site/trunk/docs/licenses/index.html
infrastructure/site/trunk/docs/licenses/proposed/index.html
Modified: infrastructure/site/trunk/docs/legal/src-headers.html
URL: http://svn.apache.org/viewvc/infrastructure/site/trunk/docs/legal/src-headers.html?rev=650828&r1=650827&r2=650828&view=diff
==============================================================================
--- infrastructure/site/trunk/docs/legal/src-headers.html (original)
+++ infrastructure/site/trunk/docs/legal/src-headers.html Wed Apr 23 04:14:32 2008
@@ -192,15 +192,15 @@
</h4>
<div class="section-content">
-<h5>
- <a name="faq-when">When must Apache projects comply with this policy?</a>
+<h5 id="faq-when">
+ When must Apache projects comply with this policy?
</h5>
<div class="section-content">
<p>All releases created and distributed after November 1, 2006 must comply with this policy.</p>
</div>
-<h5>
- <a name="faq-why">Why is this change required?</a>
+<h5 id="faq-why">
+ Why is this change required?
</h5>
<div class="section-content">
<p>Since contributors maintain their copyright ownership in the works they submit, it is misleading to place the ASF
@@ -209,17 +209,17 @@
we are placing all copyright notices in a single file and leaving only the licensing information within each source file.
</p>
-<h6>
- <a name="faq-branches">Is it sufficient just to change the headers on files in trunk and active branches?</a>
-</h6>
+<h6 id="faq-branches">
+ Is it sufficient just to change the headers on files in trunk and active branches?
+</h6>
<div class="section-content">
<p>Yes. Only active branches from which releases are cut need to be updated.</p>
</div>
-<h6>
- <a name="faq-moveothercopyright">Should a project move non-ASF copyright notices from Apache source files
-to the NOTICE file?</a>
-</h6>
+<h6 id="faq-moveothercopyright">
+ Should a project move non-ASF copyright notices from Apache source files
+to the NOTICE file?
+</h6>
<div class="section-content">
<p>No. If the copyright owner is still involved with the project, they should move the notice themselves or permit us to do so.
If the owner cannot be found, the copyright notice should be left as is, but the new licensing header should be added or
@@ -227,8 +227,8 @@
</div>
</div>
-<h5>
- <a name="faq-update-scripts">What scripts are available to update existing source headers?</a>
+<h5 id="faq-update-scripts">
+ What scripts are available to update existing source headers?
</h5>
<div class="section-content">
<p>See <a href="https://svn.apache.org/repos/private/committers/">https://svn.apache.org/repos/private/committers/</a>
@@ -242,23 +242,23 @@
post on legal-discuss</a> on this topic.</p>
</div>
-<h5>
- <a name="faq-examplenotice">Where can I find an example of the NOTICE file that is required to be included
-in every ASF release?</a>
+<h5 id="faq-examplenotice">
+ Where can I find an example of the NOTICE file that is required to be included
+in every ASF release?
</h5>
<div class="section-content">
<p>See the <a href="/licenses/example-NOTICE.txt">httpd project NOTICE example</a>.</p>
</div>
-<h5>
- <a name="faq-docs">Does this policy apply to documentation files included in a release?</a>
+<h5 id="faq-docs">
+ Does this policy apply to documentation files included in a release?
</h5>
<div class="section-content">
<p>Yes.</p>
</div>
-<h5>
- <a name="faq-webpages">Does this policy also apply to content displayed on our web sites?</a>
+<h5 id="faq-webpages">
+ Does this policy also apply to content displayed on our web sites?
</h5>
<div class="section-content">
<p>No. Our web sites do not have an associated NOTICE file. Instead we may soon be making the terms of such content
@@ -266,8 +266,8 @@
required for Apache web sites.</p>
</div>
-<h5>
- <a name="faq-siteindocs">What if my project includes its web site within a product distribution?</a>
+<h5 id="faq-siteindocs">
+ What if my project includes its web site within a product distribution?
</h5>
<div class="section-content">
<p>With <a href="#faq-exceptions">few exceptions</a>, all human-readable Apache-developed files that are included within a distribution must
@@ -276,8 +276,8 @@
appearing in the visible documentation.</p>
</div>
-<h5>
- <a name="faq-exceptions">What files in an Apache release do not require a license header?</a>
+<h5 id="faq-exceptions">
+ What files in an Apache release do not require a license header?
</h5>
<div class="section-content">
<p>A file without any degree of creativity in either its literal elements or its structure is not protected by
@@ -286,8 +286,8 @@
</p>
</div>
-<h5>
- <a name="faq-binaries">Does the policy apply to binary/object files, such as executables or JAR files?</a>
+<h5 id="faq-binaries">
+ Does the policy apply to binary/object files, such as executables or JAR files?
</h5>
<div class="section-content">
<p>
@@ -297,8 +297,8 @@
unless they are installers and include the LICENSE and NOTICE files in their installation.</p>
</div>
-<h5>
- <a name="faq-3partybinaries">Does this policy apply to third-party binary/object files included within an ASF release?</a>
+<h5 id="faq-3partybinaries">
+ Does this policy apply to third-party binary/object files included within an ASF release?
</h5>
<div class="section-content">
<p>
@@ -307,8 +307,8 @@
</p>
</div>
-<h5>
- <a name="faq-media">Do images or other media require a copyright line in the NOTICE file?</a>
+<h5 id="faq-media">
+ Do images or other media require a copyright line in the NOTICE file?
</h5>
<div class="section-content">
<p>If the media was contributed directly to an ASF project, the contributor has the option to insert their copyright notice
@@ -318,8 +318,8 @@
</p>
</div>
-<h5>
- <a name="faq-whyheader">Why is a licensing header necessary?</a>
+<h5 id="faq-whyheader">
+ Why is a licensing header necessary?
</h5>
<div class="section-content">
<p>License headers allow someone examining the file to know the terms for the work, even when it is distributed without
@@ -328,8 +328,8 @@
</p>
</div>
-<h5>
- <a name="faq-nonasf">Does this policy apply to projects outside the ASF that use the Apache License?</a>
+<h5 id="faq-nonasf">
+ Does this policy apply to projects outside the ASF that use the Apache License?
</h5>
<div class="section-content">
<p>No. This is strictly an ASF policy. Other projects using the Apache License should still refer to the
Modified: infrastructure/site/trunk/docs/licenses/exports/index.html
URL: http://svn.apache.org/viewvc/infrastructure/site/trunk/docs/licenses/exports/index.html?rev=650828&r1=650827&r2=650828&view=diff
==============================================================================
--- infrastructure/site/trunk/docs/licenses/exports/index.html (original)
+++ infrastructure/site/trunk/docs/licenses/exports/index.html Wed Apr 23 04:14:32 2008
@@ -108,8 +108,8 @@
seek the source code for ASF products. All export classification information
contained in the matrix is subject to change without notice.</p>
-<h5>
- <a name="embargoed">Embargoed Destinations</a>
+<h5 id="embargoed">
+ Embargoed Destinations
</h5>
<div class="section-content">
<p>ASF software and/or technical data may NOT be exported/reexported, either
@@ -124,9 +124,9 @@
regulations</a>.</p>
</div>
-<h6>
- <a name="denied">Denied Parties List</a>
-</h6>
+<h6 id="denied">
+ Denied Parties List
+</h6>
<div class="section-content">
<p>U.S. export regulations require that all international and domestic
transactions be screened against the U.S. Government listing of prohibited
Modified: infrastructure/site/trunk/docs/licenses/index.html
URL: http://svn.apache.org/viewvc/infrastructure/site/trunk/docs/licenses/index.html?rev=650828&r1=650827&r2=650828&view=diff
==============================================================================
--- infrastructure/site/trunk/docs/licenses/index.html (original)
+++ infrastructure/site/trunk/docs/licenses/index.html Wed Apr 23 04:14:32 2008
@@ -99,8 +99,8 @@
</p>
-<h5>
- <a name="2.0">Apache License, Version 2.0 (current)</a>
+<h5 id="2.0">
+ Apache License, Version 2.0 (current)
</h5>
<div class="section-content">
<p><a href="LICENSE-2.0">http://www.apache.org/licenses/LICENSE-2.0</a>
@@ -132,9 +132,9 @@
<p>See the <a href="../foundation/licence-FAQ.html">Licence FAQ</a>.</p>
</div>
-<h6>
- <a name="1.1">Apache License, Version 1.1 (historic)</a>
-</h6>
+<h6 id="1.1">
+ Apache License, Version 1.1 (historic)
+</h6>
<div class="section-content">
<p><a href="LICENSE-1.1">http://www.apache.org/licenses/LICENSE-1.1</a></p>
<p>The 1.1 version of the Apache License was approved
@@ -147,9 +147,9 @@
but the binding terms were all the same.</p>
</div>
-<h6>
- <a name="1.0">Apache License, Version 1.0 (historic)</a>
-</h6>
+<h6 id="1.0">
+ Apache License, Version 1.0 (historic)
+</h6>
<div class="section-content">
<p><a href="LICENSE-1.0">http://www.apache.org/licenses/LICENSE-1.0</a></p>
<p>This is the original Apache License which applies only to older
Modified: infrastructure/site/trunk/docs/licenses/proposed/index.html
URL: http://svn.apache.org/viewvc/infrastructure/site/trunk/docs/licenses/proposed/index.html?rev=650828&r1=650827&r2=650828&view=diff
==============================================================================
--- infrastructure/site/trunk/docs/licenses/proposed/index.html (original)
+++ infrastructure/site/trunk/docs/licenses/proposed/index.html Wed Apr 23 04:14:32 2008
@@ -174,8 +174,8 @@
</ol>
</p>
-<h5>
- <a name="2.0">Apache License, version 2.0</a>
+<h5 id="2.0">
+ Apache License, version 2.0
</h5>
<div class="section-content">
<p>
@@ -189,9 +189,9 @@
</p>
</div>
-<h6>
- <a name="JSR">Apache JSR License, version 2.0 (proposed)</a>
-</h6>
+<h6 id="JSR">
+ Apache JSR License, version 2.0 (proposed)
+</h6>
<div class="section-content">
<p>
<a href="JSR-LICENSE-2.0.txt">http://www.apache.org/licenses/proposed/JSR-LICENSE-2.0.txt</a>
@@ -211,9 +211,9 @@
</p>
</div>
-<h6>
- <a name="TCK">Apache TCK License, version 2.0 (proposed)</a>
-</h6>
+<h6 id="TCK">
+ Apache TCK License, version 2.0 (proposed)
+</h6>
<div class="section-content">
<p>
<a href="TCK-LICENSE-2.0.txt">http://www.apache.org/licenses/proposed/TCK-LICENSE-2.0.txt</a>
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org