You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sis.apache.org by bu...@apache.org on 2013/07/25 13:16:14 UTC
svn commit: r871136 - in /websites/staging/sis/trunk/content: ./
code-patterns.html downloads.html mailinglists.html
release-management-setup.html release-management.html site-management.html
team.html
Author: buildbot
Date: Thu Jul 25 11:16:14 2013
New Revision: 871136
Log:
Staging update by buildbot for sis
Modified:
websites/staging/sis/trunk/content/ (props changed)
websites/staging/sis/trunk/content/code-patterns.html
websites/staging/sis/trunk/content/downloads.html
websites/staging/sis/trunk/content/mailinglists.html
websites/staging/sis/trunk/content/release-management-setup.html
websites/staging/sis/trunk/content/release-management.html
websites/staging/sis/trunk/content/site-management.html
websites/staging/sis/trunk/content/team.html
Propchange: websites/staging/sis/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Jul 25 11:16:14 2013
@@ -1 +1 @@
-1506882
+1506887
Modified: websites/staging/sis/trunk/content/code-patterns.html
==============================================================================
--- websites/staging/sis/trunk/content/code-patterns.html (original)
+++ websites/staging/sis/trunk/content/code-patterns.html Thu Jul 25 11:16:14 2013
@@ -139,16 +139,7 @@ so <code>"Foo bar"</code> is sorted befo
Some "characters" are actually represented using two consecutive <code>char</code> elements.
Those "characters" are called <cite>code points</cite>.
Consequently, when iterating over characters in a string, the following pattern shall be used:</p>
-<p>Do not use:</p>
-<div class="codehilite"><pre><span class="k">for</span> <span class="o">(</span><span class="kt">int</span> <span class="n">i</span><span class="o">=</span><span class="mi">0</span><span class="o">;</span> <span class="n">i</span><span class="o">&</span><span class="n">lt</span><span class="o">;</span><span class="n">string</span><span class="o">.</span><span class="na">length</span><span class="o">();</span> <span class="n">i</span><span class="o">++)</span> <span class="o">{</span>
- <span class="kt">char</span> <span class="n">c</span> <span class="o">=</span> <span class="n">string</span><span class="o">.</span><span class="na">charAt</span><span class="o">(</span><span class="n">i</span><span class="o">);</span>
- <span class="c1">// ... do some stuff ...</span>
-<span class="o">}</span>
-</pre></div>
-
-
-<p>Use instead:</p>
-<div class="codehilite"><pre><span class="k">for</span> <span class="o">(</span><span class="kt">int</span> <span class="n">i</span><span class="o">=</span><span class="mi">0</span><span class="o">;</span> <span class="n">i</span><span class="o">&</span><span class="n">lt</span><span class="o">;</span><span class="n">string</span><span class="o">.</span><span class="na">length</span><span class="o">();)</span> <span class="o">{</span>
+<div class="codehilite"><pre><span class="k">for</span> <span class="o">(</span><span class="kt">int</span> <span class="n">i</span><span class="o">=</span><span class="mi">0</span><span class="o">;</span> <span class="n">i</span><span class="o"><</span><span class="n">string</span><span class="o">.</span><span class="na">length</span><span class="o">();)</span> <span class="o">{</span>
<span class="kd">final</span> <span class="kt">int</span> <span class="n">c</span> <span class="o">=</span> <span class="n">string</span><span class="o">.</span><span class="na">codePointAt</span><span class="o">(</span><span class="n">i</span><span class="o">);</span>
<span class="c1">// ... do some stuff ...</span>
<span class="n">i</span> <span class="o">+=</span> <span class="n">Character</span><span class="o">.</span><span class="na">charCount</span><span class="o">(</span><span class="n">c</span><span class="o">);</span>
Modified: websites/staging/sis/trunk/content/downloads.html
==============================================================================
--- websites/staging/sis/trunk/content/downloads.html (original)
+++ websites/staging/sis/trunk/content/downloads.html Thu Jul 25 11:16:14 2013
@@ -81,18 +81,18 @@
See the <code>NOTICE</code> file contained in each release artifact for applicable copyright attribution notices.</p>
<div class="toc">
<ul>
-<li><a href="#download-zipgz-files">Download ZIP/GZ files</a><ul>
+<li><a href="#bundles">Download ZIP/GZ files</a><ul>
<li><a href="#release-notes">Release notes</a></li>
</ul>
</li>
-<li><a href="#download-as-a-maven-dependency">Download as a Maven dependency</a><ul>
-<li><a href="#using-sis-releases">Using SIS releases</a></li>
-<li><a href="#using-sis-development-snapshots">Using SIS development snapshots</a></li>
+<li><a href="#maven">Download as a Maven dependency</a><ul>
+<li><a href="#maven-release">Using SIS releases</a></li>
+<li><a href="#maven-snapshot">Using SIS development snapshots</a></li>
</ul>
</li>
</ul>
</div>
-<h1 id="download-zipgz-files">Download ZIP/GZ files</h1>
+<h1 id="bundles">Download ZIP/GZ files</h1>
<p>Apache SIS 0.2-incubating is now available.
See the <code>CHANGES</code> file for more information on the list of updates in this initial release.</p>
<ul>
@@ -125,11 +125,11 @@ pgpv apache-sis-X.Y.Z.tar.gz.asc
<h2 id="release-notes">Release notes</h2>
<p>See the <a href="release-notes/0.2.html">release notes</a> for a list of changes since the previous version.</p>
-<h1 id="download-as-a-maven-dependency">Download as a Maven dependency</h1>
+<h1 id="maven">Download as a Maven dependency</h1>
<p>An easy approach to integrate SIS into a Java project uses the <a href="http://maven.apache.org">Apache Maven</a>
dependency management tool to automatically obtain the required Java Archives (JAR) files from the network.
Below are examples of declarations in a <code>pom.xml</code> file for building a project with the SIS core module:</p>
-<h2 id="using-sis-releases">Using SIS releases</h2>
+<h2 id="maven-release">Using SIS releases</h2>
<div class="codehilite"><pre><span class="nt"><properties></span>
<span class="nt"><sis.version></span>0.2-incubating<span class="nt"></sis.version></span>
<span class="nt"></properties></span>
@@ -144,7 +144,7 @@ Below are examples of declarations in a
</pre></div>
-<h2 id="using-sis-development-snapshots">Using SIS development snapshots</h2>
+<h2 id="maven-snapshot">Using SIS development snapshots</h2>
<div class="codehilite"><pre><span class="nt"><properties></span>
<span class="nt"><sis.version></span>0.4-SNAPSHOT<span class="nt"></sis.version></span>
<span class="nt"></properties></span>
Modified: websites/staging/sis/trunk/content/mailinglists.html
==============================================================================
--- websites/staging/sis/trunk/content/mailinglists.html (original)
+++ websites/staging/sis/trunk/content/mailinglists.html Thu Jul 25 11:16:14 2013
@@ -1,7 +1,7 @@
<!DOCTYPE html>
<html lang="en">
<head>
- <title></title>
+ <title>Mailing lists</title>
<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
<link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
<link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
@@ -10,7 +10,7 @@
-
+ <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at . http://www.apache.org/licenses/LICENSE-2.0 . Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. -->
</head>
<body>
@@ -75,10 +75,10 @@
<div class="span10">
<section id="content" class="row">
<article class="span12">
- <p class="page-title"></p>
+ <p class="page-title">Mailing lists</p>
<p>We welcome you to join mailing lists and let us know about your thoughts or ideas about Apache SIS.</p>
-<h3 id="apache-sis-developer-mailing-list">Apache SIS Developer Mailing List</h3>
-<p>This is where the community hangs out and SIS development happens. </p>
+<h3 id="developer">Apache SIS Developer Mailing List</h3>
+<p>This is where the community hangs out and SIS development happens.</p>
<ul>
<li>Subscribe: <a href="mailto://dev-subscribe@sis.apache.org">dev-subscribe@sis.apache.org</a></li>
<li>Post (after subscription): <a href="mailto://dev@sis.apache.org">dev@sis.apache.org</a></li>
@@ -89,8 +89,8 @@
</ul>
</li>
</ul>
-<h3 id="apache-sis-commit-mailing-list">Apache SIS Commit Mailing List</h3>
-<p>This is where the community receives automated notifications of
+<h3 id="commit">Apache SIS Commit Mailing List</h3>
+<p>This is where the community receives automated notifications of
any changes to the sis code and documentation.</p>
<ul>
<li>Subscribe: <a href="mailto:commits-subscribe@sis.apache.org">commits-subscribe@sis.apache.org</a></li>
Modified: websites/staging/sis/trunk/content/release-management-setup.html
==============================================================================
--- websites/staging/sis/trunk/content/release-management-setup.html (original)
+++ websites/staging/sis/trunk/content/release-management-setup.html Thu Jul 25 11:16:14 2013
@@ -82,12 +82,12 @@ If those steps have already been done, j
<div class="toc">
<ul>
<li><a href="#directory-layout">Directory layout</a></li>
-<li><a href="#shell-configuration">Shell configuration</a></li>
-<li><a href="#generate-gpg-key">Generate GPG key</a><ul>
-<li><a href="#web-of-trust">Web of trust</a></li>
+<li><a href="#shell">Shell configuration</a></li>
+<li><a href="#generate-key">Generate GPG key</a><ul>
+<li><a href="#trust">Web of trust</a></li>
</ul>
</li>
-<li><a href="#maven-configuration-nexus-setup">Maven Configuration & Nexus Setup</a></li>
+<li><a href="#maven">Maven Configuration & Nexus Setup</a></li>
</ul>
</div>
<h1 id="directory-layout">Directory layout</h1>
@@ -110,14 +110,14 @@ mkdir tags
</pre></div>
-<h1 id="shell-configuration">Shell configuration</h1>
+<h1 id="shell">Shell configuration</h1>
<p>It is better for Unix shells to contain the following line in their initialization file
(typically <code>~/.bashrc</code> or <code>~/.profile</code>, where <code>~</code> stands for the user's home directory):</p>
<div class="codehilite"><pre><span class="nb">export </span><span class="nv">GPG_TTY</span><span class="o">=</span><span class="k">$(</span>tty<span class="k">)</span>
</pre></div>
-<h1 id="generate-gpg-key">Generate GPG key</h1>
+<h1 id="generate-key">Generate GPG key</h1>
<p>The releases have to be signed by public key cryptography signatures.
Detailed instructions about why releases have to be signed are provided on the <a href="http://www.apache.org/dev/release-signing.html">Release Signing</a> page.
The standard used is OpenPGP (<em>Open Pretty Good Privacy</em>), and a popular software implementation of that standard is GPG (<em>GNU Privacy Guard</em>).
@@ -178,7 +178,7 @@ preferably on a removable device.</p>
</pre></div>
-<h2 id="web-of-trust">Web of trust</h2>
+<h2 id="trust">Web of trust</h2>
<p>Have the key signed by at least three Apache commiters. This can be done by executing the following commands on
the machine of the other Apache commiter, where <code><key_to_use></code> is the identifier of the other commiter's key.
Those operation should preferably be done in some event where the commiters can meet face-to-face.
@@ -193,7 +193,7 @@ gpg --send-key <key_id>
<p>The above-cited <em>Release Signing</em> page provides more instructions.
Then, the signed public key shall be appended to the <code>KEYS</code> file on the <a href="https://svn.apache.org/repos/asf/sis/trunk/">SIS source code repository</a>,
then copied to the <a href="http://dist.apache.org/repos/dist/release/sis/">SIS distribution directory</a>.</p>
-<h1 id="maven-configuration-nexus-setup">Maven Configuration & Nexus Setup</h1>
+<h1 id="maven">Maven Configuration & Nexus Setup</h1>
<p>Detailed instructions are at <a href="http://www.apache.org/dev/publishing-maven-artifacts.html">Publishing Maven Artifacts</a>.
In summary, the developer needs to specify his Apache username and password (<strong>not</strong> the PGP passphrase)
in his local <code>~/.m2</code> directory, and the GPG key identifier.
Modified: websites/staging/sis/trunk/content/release-management.html
==============================================================================
--- websites/staging/sis/trunk/content/release-management.html (original)
+++ websites/staging/sis/trunk/content/release-management.html Thu Jul 25 11:16:14 2013
@@ -87,27 +87,27 @@ The intended audiences are SIS release m
</ul>
</li>
<li><a href="#prepare-documentation">Prepare documentation</a><ul>
-<li><a href="#web-site">Web site</a></li>
+<li><a href="#prepare-website">Web site</a></li>
</ul>
</li>
-<li><a href="#create-branch">Create branch</a><ul>
-<li><a href="#verify-content">Verify content</a></li>
+<li><a href="#branch">Create branch</a><ul>
+<li><a href="#branch-verify">Verify content</a></li>
</ul>
</li>
-<li><a href="#create-tag">Create tag</a></li>
-<li><a href="#deploy-maven-artifacts">Deploy Maven artifacts</a><ul>
-<li><a href="#verify-and-close-the-nexus-release-artifacts">Verify and close the Nexus release artifacts</a></li>
+<li><a href="#tag">Create tag</a></li>
+<li><a href="#maven-deploy">Deploy Maven artifacts</a><ul>
+<li><a href="#nexus-close">Verify and close the Nexus release artifacts</a></li>
</ul>
</li>
-<li><a href="#stage-the-source-binary-and-javadoc-artifacts">Stage the source, binary and javadoc artifacts</a></li>
-<li><a href="#put-the-release-candidate-up-for-a-vote">Put the release candidate up for a vote</a></li>
-<li><a href="#finalize-the-release">Finalize the release</a><ul>
-<li><a href="#announce-the-release">Announce the release</a></li>
+<li><a href="#stage">Stage the source, binary and javadoc artifacts</a></li>
+<li><a href="#vote">Put the release candidate up for a vote</a></li>
+<li><a href="#finalize">Finalize the release</a><ul>
+<li><a href="#announce">Announce the release</a></li>
</ul>
</li>
-<li><a href="#recovering-from-a-vetoed-release">Recovering from a vetoed release</a></li>
-<li><a href="#verify-release-signatures">Verify release signatures</a></li>
-<li><a href="#updating-trunk">Updating trunk</a></li>
+<li><a href="#veto">Recovering from a vetoed release</a></li>
+<li><a href="#verify">Verify release signatures</a></li>
+<li><a href="#next-release">Updating trunk</a></li>
</ul>
</div>
<h1 id="requirements">Requirements</h1>
@@ -162,7 +162,7 @@ in this page shall be adjusted according
<li>Review and update the <code>README</code> file on the <code>trunk</code> source code repository.</li>
<li>Commit any changes back to SVN.</li>
</ul>
-<h2 id="web-site">Web site</h2>
+<h2 id="prepare-website">Web site</h2>
<p>Update the version numbers from <code>$NEW_VERSION</code> to the next version in the following files.</p>
<ul>
<li><code>content/index.mdtext</code></li>
@@ -176,7 +176,7 @@ svn commit --message <span class="s2">&q
<p>The new web site will be published in the <a href="http://sis.staging.apache.org">staging area</a>.
It will not yet be published on <code>http://sis.apache.org</code>.</p>
-<h1 id="create-branch">Create branch</h1>
+<h1 id="branch">Create branch</h1>
<p>Execute the following command:</p>
<div class="codehilite"><pre>svn copy https://svn.apache.org/repos/asf/sis/trunk <span class="se">\</span>
https://svn.apache.org/repos/asf/sis/branches/<span class="nv">$NEW_VERSION</span> <span class="se">\</span>
@@ -212,7 +212,7 @@ the <code>ENABLED</code> flag to <code>f
</pre></div>
-<h2 id="verify-content">Verify content</h2>
+<h2 id="branch-verify">Verify content</h2>
<p>Starts the GPG agent if not already done.
This is for avoiding to be prompted many time for the passphrase in every modules to be built by Maven.
Note that MacOS users can skip this step if their passphrase is stored in the OS keychain,</p>
@@ -236,7 +236,7 @@ the changes that would have been committ
</pre></div>
-<h1 id="create-tag">Create tag</h1>
+<h1 id="tag">Create tag</h1>
<p>In theory, the next commands would be a real (non-dry) run of <code>mvn release:prepare</code>, followed by <code>mvn release:perform</code>.
However we perform those steps manually rather than relying on Maven for the following reasons:</p>
<ul>
@@ -286,7 +286,7 @@ mvn clean
</pre></div>
-<h1 id="deploy-maven-artifacts">Deploy Maven artifacts</h1>
+<h1 id="maven-deploy">Deploy Maven artifacts</h1>
<p>Ensure that the current directory is <code>tags/$NEW_VERSION</code>.
Execute an <code>install</code> phase first (required for our custom <code>sis-build-helper</code> plugin), then deploy.
Note that the <code>site</code> phase need to be specified even if we will not deploy the site,
@@ -296,7 +296,7 @@ mvn site deploy --activate-profiles apac
</pre></div>
-<h2 id="verify-and-close-the-nexus-release-artifacts">Verify and close the Nexus release artifacts</h2>
+<h2 id="nexus-close">Verify and close the Nexus release artifacts</h2>
<p>Verify the staged artifacts in the <a href="https://repository.apache.org/index.html">Nexus repository</a>.
The artifacts can be found under <em>Build Promotion</em> â <em>Staging repositories</em>, and searching for <code>org.apache.sis</code> in the <em>Repository</em> column.
Navigate through the artifact tree and make sure that all javadoc, source, test and jar files have <code>.asc</code> (GPG signature) and <code>.md5</code> files.</p>
@@ -312,7 +312,7 @@ In the description field, enter <code>SI
This will not be done automatically since this field box is not our bash shell!).</p>
<p>Click on the <code>org.apache.sis-<id></code> link in order to get the URL to the temporary Maven repository created by Nexus.
Announce on the <code>dev@</code> mailing list the availability of this temporary repository for testing purpose.</p>
-<h1 id="stage-the-source-binary-and-javadoc-artifacts">Stage the source, binary and javadoc artifacts</h1>
+<h1 id="stage">Stage the source, binary and javadoc artifacts</h1>
<p>Create the directory for the new version and release candidate within the distribution directory.
The <code>RC</code> number shall correspond to the current release attempt.</p>
<div class="codehilite"><pre>mkdir ../../distribution/<span class="nv">$NEW_VERSION</span>
@@ -362,7 +362,7 @@ svn commit --message <span class="s2">&q
<p>Verify that the files are downloadable from the
[http://dist.apache.org/repos/dist/dev/sis/][http://dist.apache.org/repos/dist/dev/sis/] sub-directory.</p>
-<h1 id="put-the-release-candidate-up-for-a-vote">Put the release candidate up for a vote</h1>
+<h1 id="vote">Put the release candidate up for a vote</h1>
<ul>
<li>Create a VOTE email thread on <code>dev@</code> to record votes as replies.
A template is available [here][release-vote.txt].</li>
@@ -376,7 +376,7 @@ svn commit --message <span class="s2">&q
<li>Reply to the initial email and prepend to the original subject "[RESULT]"</li>
<li>Include a list of everyone who voted +1, 0 or -1.</li>
</ul>
-<h1 id="finalize-the-release">Finalize the release</h1>
+<h1 id="finalize">Finalize the release</h1>
<p>The artificats in the repository are not yet mirrored and available for Maven to download.
Promote the staged Nexus artifacts, by releasing them.</p>
<ul>
@@ -419,7 +419,7 @@ Then prepare for the next release:</p>
<li>Make a new release entry in JIRA for the next release.</li>
<li>Update the <a href="https://cwiki.apache.org/confluence/display/SIS/Roadmap">Roadmap</a> wiki page.</li>
</ul>
-<h2 id="announce-the-release">Announce the release</h2>
+<h2 id="announce">Announce the release</h2>
<ul>
<li>Make a news announcement on the SIS home page.</li>
<li>Make an announcement about the release on the <code>dev@</code>, <code>users@</code>, and <code>announce@</code> mailing lists.<ul>
@@ -427,7 +427,7 @@ Then prepare for the next release:</p>
</ul>
</li>
</ul>
-<h1 id="recovering-from-a-vetoed-release">Recovering from a vetoed release</h1>
+<h1 id="veto">Recovering from a vetoed release</h1>
<p>Reply to the initial vote email and prepend to the original subject:</p>
<div class="codehilite"><pre>[CANCELED]
</pre></div>
@@ -444,14 +444,14 @@ Then prepare for the next release:</p>
<li>Right click on the closed staging repositories (<code>org.apache.sis-<id></code>) and select <em>Drop</em>.</li>
</ul>
<p>Make the required updates that caused the vote to be canceled during the release cycle.</p>
-<h1 id="verify-release-signatures">Verify release signatures</h1>
+<h1 id="verify">Verify release signatures</h1>
<p>Download all source and binary artifacts into a new directory, then execute in that directory:</p>
<div class="codehilite"><pre>find . -name <span class="s2">"*.asc"</span> -exec gpg --verify <span class="s1">'{}'</span> <span class="se">\;</span>
</pre></div>
<p>The output shall report only good signatures.</p>
-<h1 id="updating-trunk">Updating trunk</h1>
+<h1 id="next-release">Updating trunk</h1>
<p>Update the version numbers in the <code>pom.xml</code> files on trunk with the following command:</p>
<div class="codehilite"><pre>mvn release:update-versions
</pre></div>
Modified: websites/staging/sis/trunk/content/site-management.html
==============================================================================
--- websites/staging/sis/trunk/content/site-management.html (original)
+++ websites/staging/sis/trunk/content/site-management.html Thu Jul 25 11:16:14 2013
@@ -86,7 +86,7 @@ The remaining of this page is specific t
<li><a href="#directory-layout">Directory layout</a></li>
<li><a href="#content">Content</a></li>
<li><a href="#style-sheets">Style sheets</a><ul>
-<li><a href="#updating-bootstrap">Updating bootstrap</a></li>
+<li><a href="#bootstrap">Updating bootstrap</a></li>
</ul>
</li>
</ul>
@@ -180,7 +180,7 @@ They are rather located together with th
</tr>
</tbody>
</table>
-<h2 id="updating-bootstrap">Updating bootstrap</h2>
+<h2 id="bootstrap">Updating bootstrap</h2>
<p>If the <code>bootstrap.min.css</code> file needs to be updated, then visit the <a href="http://twitter.github.io/bootstrap/customize.html">Bootstrap</a> web site
and select the following options:</p>
<ul>
Modified: websites/staging/sis/trunk/content/team.html
==============================================================================
--- websites/staging/sis/trunk/content/team.html (original)
+++ websites/staging/sis/trunk/content/team.html Thu Jul 25 11:16:14 2013
@@ -1,7 +1,7 @@
<!DOCTYPE html>
<html lang="en">
<head>
- <title></title>
+ <title>Team</title>
<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
<link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css">
<link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
@@ -10,7 +10,7 @@
-
+ <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at . http://www.apache.org/licenses/LICENSE-2.0 . Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. -->
</head>
<body>
@@ -75,8 +75,8 @@
<div class="span10">
<section id="content" class="row">
<article class="span12">
- <p class="page-title"></p>
- <p><strong>Project Management Committee / Committers:</strong></p>
+ <p class="page-title">Team</p>
+ <h2 id="pmc">Project Management Committee / Committers</h2>
<ul>
<li>Adam Estrada</li>
<li>Andrew Hart</li>
@@ -96,7 +96,7 @@
<li><a href="http://people.apache.org/~smarru/">Suresh Marru</a></li>
<li>Travis Pinney</li>
</ul>
-<p><strong>Contributors:</strong></p>
+<h2 id="contributors">Contributors</h2>
<ul>
<li>None at this time</li>
</ul>