Propchange: any23/site/js/jquery-ui-1.10.4.custom.js
------------------------------------------------------------------------------
svn:executable = *
Added: any23/site/js/jquery-ui-1.10.4.custom.min.js
URL:
http://svn.apache.org/viewvc/any23/site/js/jquery-ui-1.10.4.custom.min.js?rev=1595073&view=auto
==============================================================================
--- any23/site/js/jquery-ui-1.10.4.custom.min.js (added)
+++ any23/site/js/jquery-ui-1.10.4.custom.min.js Thu May 15 23:25:50 2014
@@ -0,0 +1,7 @@
+/*! jQuery UI - v1.10.4 - 2014-05-12
+* http://jqueryui.com
+* Includes: jquery.ui.core.js, jquery.ui.widget.js, jquery.ui.mouse.js,
jquery.ui.position.js, jquery.ui.draggable.js, jquery.ui.droppable.js,
jquery.ui.resizable.js, jquery.ui.selectable.js, jquery.ui.sortable.js,
jquery.ui.accordion.js, jquery.ui.autocomplete.js, jquery.ui.button.js,
jquery.ui.datepicker.js, jquery.ui.dialog.js, jquery.ui.menu.js,
jquery.ui.progressbar.js, jquery.ui.slider.js, jquery.ui.spinner.js,
jquery.ui.tabs.js, jquery.ui.tooltip.js, jquery.ui.effect.js,
jquery.ui.effect-blind.js, jquery.ui.effect-bounce.js,
jquery.ui.effect-clip.js, jquery.ui.effect-drop.js,
jquery.ui.effect-explode.js, jquery.ui.effect-fade.js,
jquery.ui.effect-fold.js, jquery.ui.effect-highlight.js,
jquery.ui.effect-pulsate.js, jquery.ui.effect-scale.js,
jquery.ui.effect-shake.js, jquery.ui.effect-slide.js,
jquery.ui.effect-transfer.js
+* Copyright 2014 jQuery Foundation and other contributors; Licensed MIT */
+
[... 4 lines stripped ...]
Propchange: any23/site/js/jquery-ui-1.10.4.custom.min.js
------------------------------------------------------------------------------
svn:executable = *
Modified: any23/site/poweredby.html
URL:
http://svn.apache.org/viewvc/any23/site/poweredby.html?rev=1595073&r1=1595072&r2=1595073&view=diff
==============================================================================
--- any23/site/poweredby.html (original)
+++ any23/site/poweredby.html Thu May 15 23:25:50 2014
@@ -218,9 +218,16 @@
<h2>PoweredBy<a name="PoweredBy"></a></h2>
<p>This page collects a set of project and web initiatives which use <i>Apache
Any23</i>.</p><img src="./images/logo-sindice-90x30.png" alt="" />
<p><a class="externalLink" href="http://sindice.com/";>Sindice</a></p>
-<p>Sindice is a platform to build applications on top of this data. Sindice
collects Web Data in many ways, following existing web standards, and offers
Search and Querying across this data, updated live every few minutes.</p><img
src="./images/fu-logo-90x25.png" alt="[./images/kit-logo-90x40.png]" />
+<p>Sindice is a platform to build applications on top of this data. Sindice
collects Web Data in many ways, following existing web standards, and offers
Search and Querying across this data, updated live every few minutes.</p>
+
+<img src="./images/fu-logo-90x25.png" alt="[./images/kit-logo-90x40.png]" />
<p><a class="externalLink"
href="http://webdatacommons.org/";>WebDataCommons</a></p>
-<p>Extracting Structured Data from the Common Web Crawl. More and more
websites have started to embed structured data describing products, people,
organizations, places, events into their HTML pages. The Web Data Commons
project extracts this data from several billion web pages and provides the
extracted data for download. Web Data Commons thus enables you to use the data
without needing to crawl the Web yourself.</p></div>
+<p>Extracting Structured Data from the Common Web Crawl. More and more
websites have started to embed structured data describing products, people,
organizations, places, events into their HTML pages. The Web Data Commons
project extracts this data from several billion web pages and provides the
extracted data for download. Web Data Commons thus enables you to use the data
without needing to crawl the Web yourself.</p>
+
+<img src="http://nutch.apache.org/images/nutch_logo_tm.gif";
alt="http://nutch.apache.org/images/nutch_logo_tm.gif"; />
+<p><a class="externalLink" href="http://nutch.apache.org/";>Apache Nutch</a></p>
+<p>Apache Nutch is a highly extensible and scalable open source web crawler
software project. </br>
+A <a href="https://issues.apache.org/jira/browse/NUTCH-1129";>number of
tickets</a> address Any23 integration in the form of a plugin for extracting
implicit structure from WebPages.</p></div>
</div>
</div>
</div>
Modified: any23/site/release-howto.html
URL:
http://svn.apache.org/viewvc/any23/site/release-howto.html?rev=1595073&r1=1595072&r2=1595073&view=diff
==============================================================================
--- any23/site/release-howto.html (original)
+++ any23/site/release-howto.html Thu May 15 23:25:50 2014
@@ -315,16 +315,16 @@
<li>Install Apache Maven 2.2.1 or higher. 2.2.0 has a bug that will produce
invalid checksums; we strongly
- encourage our committers to install Apache Maven 3.0.4.</li>
+ encourage our committers to install <b>the latest</b> Apache Maven</li>
</ul>
</div>
<div class="section">
-<h2>Configuration<a name="Configuration"></a></h2>
+<h2>Configuration</h2>
<div class="section">
-<h3>Apache Maven<a name="Apache_Maven"></a></h3>
+<h3>Apache Maven</h3>
<p>As of Maven 2.1.0 you can now encrypt your servers passwords. We highly
recommend that you follow this
<a class="externalLink"
href="http://maven.apache.org/guides/mini/guide-encryption.html";>guide</a> to
set your master password and
@@ -333,10 +333,10 @@
<div class="section">
-<h3>ASF settings<a name="ASF_settings"></a></h3>
+<h3>ASF settings</h3>
<p>Using the instructions from the previous step encrypt your Sonatype
password and add the following servers to
- your <tt>~/.m2/settings.xml</tt> file. You may already have other
servers in this file. If not just create
+ your <code>~/.m2/settings.xml</code> file. You may already have other
servers in this file. If not just create
the file.</p>
@@ -375,8 +375,8 @@
</settings></pre></div>
-<p>You can find a <a class="externalLink"
href="https://svn.apache.org/repos/asf/any23/committers/maven/settings.xml";><tt>settings.xml</tt></a>
- template in our SVN committers space</p>
+<p>You can find a <a class="externalLink"
href="https://git-wip-us.apache.org/repos/asf?p=any23-committers.git;a=blob_plain;f=maven/settings.xml;hb=HEAD";><code>settings.xml</code></a>
+ template in our Git committers space. Please see <a
href="./source-repository.html">here</a> for access to the committers space.</p>
</div>
</div>
@@ -397,13 +397,26 @@
<ol style="list-style-type: decimal">
-<li>Update the <tt>CHANGES</tt> based on the Text release reports from
JIRA.</li>
+<li>Update the <code>CHANGES</code> based on the Text release reports from
JIRA.</li>
-<li>Review and update <tt>README</tt> if needed.</li>
+<li>Review and update <code>README</code> if needed.</li>
+
+<li>Review and update <code>NOTICE</code> year number if needed. The same goes
for all <b>plugins</b> and <b>service</b> NOTICE as well.</li>
+
+<li>Edit the following properties in <code>pom.xml</code> to reflect the
<b>proposed release</b> versions of the respective artifacts.</li>
+<div class="source">
+<pre><project...>
+ ...
+ <properties>
+ <latest.stable.released>1.X</latest.stable.released>
+
+</properties></pre></div>
-<li>Commit any changes back to svn:
+<li>Commit any changes back to Git origin master branch:
<div>
-<pre>svn commit -m "updating files for release"</pre></div>.</li>
+<pre>svn add ...</pre>
+<pre>git commit -m "updating files for release"</pre>
+<pre>git push origin master</pre></div>.</li>
</ol>
</li>
@@ -414,7 +427,7 @@
</div>
-<div class="section">
+<!-- div class="section">
<h3>Get source tree<a name="Get_source_tree"></a></h3>
<ol style="list-style-type: decimal">
@@ -437,7 +450,7 @@
<div>
<pre>svn checkout https://svn.apache.org/repos/asf/any23/trunk/
release</pre></div></li>
</ol>
- </div>
+ </div-->
<div class="section">
@@ -445,41 +458,44 @@
<ol style="list-style-type: decimal">
-<li>Do a dry run of the <tt>release:prepare</tt> step.
+<li>Do a dry run of the <code>release:prepare</code> step.
<div>
<pre>mvn release:prepare -DdryRun=true</pre></div>
- The dry run will not commit any changes back to SVN and gives you
the opportunity to verify that the
+ The dry run will not commit any changes back to Git and gives you
the opportunity to verify that the
release process will complete as expected.
-<p><i>If you cancel a <tt>release:prepare</tt> before it updates the pom.xml
versions, then use the
- <tt>release:clean</tt> goal to just remove the extra files that were
created.</i></p></li>
+<p><i>If you cancel a <code>release:prepare</code> before it updates the
pom.xml versions, then use the
+ <code>release:clean</code> goal to just remove the extra files that
were created.</i></p></li>
<li>Verify that the release process completed as expected:
<ol style="list-style-type: decimal">
-<li>The release plugin will create <tt>pom.xml.tag</tt> files which contain
the changes that would
- have been committed to SVN. The only differences between
<tt>pom.xml.tag</tt> and its corresponding
- <tt>pom.xml</tt> file should be the version
+<li>The release plugin will create <code>pom.xml.tag</code> files which
contain the changes that would
+ have been committed to Git. The only differences between
<code>pom.xml.tag</code> and its corresponding
+ <code>pom.xml</code> file should be the version
number.</li>
-<li>If other formatting changes have been made you should review the changes
and then commit them:
+<li>If other formatting changes have been made you should review the changes
and then commit them back to Git origin master branch:
<div>
-<pre>svn commit -m "fixing formatting for release"</pre></div></li>
+<pre>svn add ...</pre>
+<pre>git commit -m "updating files for release"</pre>
+<pre>git push origin master</pre></div></li>
+
-<li>Assuming the <tt>.tag</tt> files look OK you may proceed and do any other
validation you feel
+<li>Assuming the <code>.tag</code> files look OK you may proceed and do any
other validation you feel
necessary. The following list may be helpful:
<ol style="list-style-type: decimal">
-<li>Check <tt>release.properties</tt> and make sure that the scm properties
have the right version.
+<li>Check <code>release.properties</code> and make sure that the scm
properties have the right version.
Sometimes the scm location can be the previous version not
the next version.</li>
@@ -509,7 +525,7 @@ gpg: Signature made ...</pre></div>
</li>
-<li>Run the <tt>release:prepare</tt> step for real this time. You'll be
prompted for the same version
+<li>Run the <code>release:prepare</code> step for real this time. You'll be
prompted for the same version
information and optionally your GPG passphrase again.
<div>
<pre>mvn release:prepare</pre></div>
@@ -524,7 +540,7 @@ gpg: Signature made ...</pre></div>
<ol style="list-style-type: decimal">
<li>
- From the directory where you have launched
<tt>release:prepare</tt> execute (this step will create a maven staging
repository):
+ From the directory where you have launched
<code>release:prepare</code> execute (this step will create a maven staging
repository):
<div class="source">
<pre>mvn release:perform [-Duser.name=<your_apache_uid>]</pre></div>
@@ -533,7 +549,7 @@ gpg: Signature made ...</pre></div>
<p>
<i>If your local OS userid doesn't match your Apache userid,
then you'll have to also override the value
provided by the OS to Maven for the site-deploy step to work.
This is known to work for Linux,
- but not for Mac and unknown for Windows.
+ and Mac OSX 10.9.2 but unknown for Windows.
</i>
</p>
@@ -551,15 +567,15 @@ gpg: Signature made ...</pre></div>
<li><b>Staging tab --> Name column --> org.apache.any23</b></li>
<li>Navigate through the artifact tree and make sure that all binary,
- <tt>javadoc</tt>,
- <tt>sources</tt>, and
- <tt>tests</tt> jars, as well as
- <tt>pom</tt>s, ... have
- <tt>.asc</tt> (GPG signature) and checksum files (see
+ <code>javadoc</code>,
+ <code>sources</code>, and
+ <code>tests</code> jars, as well as
+ <code>pom</code>s, ... have
+ <code>.asc</code> (GPG signature) and checksum files (see
<a class="externalLink"
href="http://people.apache.org/~henkp/repo/faq.html";>Repository FAQ</a> and
<a class="externalLink"
href="http://www.apache.org/dev/release-signing.html#openpgp-ascii-detach-sig";>Detached
Signatures</a>).
- The <tt>any23-sources-dist-X.Y.tar.gz</tt> and
- <tt>any23-sources-dist-X.Y.zip</tt> files shall likewise
have signature and checksum files.
+ The <code>any23-sources-dist-X.Y.tar.gz</code> and
+ <code>any23-sources-dist-X.Y.zip</code> files shall
likewise have signature and checksum files.
</li>
</ol>
</li>
@@ -575,18 +591,17 @@ gpg: Signature made ...</pre></div>
<li><b>Staging tab --> Name column --> org.apache.any23</b></li>
-<li>Right click on the open <tt>org.apache.any23-XXX</tt> staging repo and
select
+<li>Right click on the open <code>org.apache.any23-XXX</code> staging repo and
select
<b>Close</b>.</li>
</ol>
</li>
-<li>Add the distribution artifacts to the build area (the <a
class="externalLink"
href="https://svn.apache.org/repos/asf/any23/committers/scripts/grab-binaries.sh";>grab-binaries.sh</a>
- script is versioned under the committer space of Any23 SVN).
+<li>Add the distribution artifacts to the build area (the <a
class="externalLink"
href="https://git-wip-us.apache.org/repos/asf?p=any23-committers.git;a=blob_plain;f=scripts/grab-binaries.sh;hb=HEAD";>grab-binaries.sh</a>
+ script is versioned under the Any23 Git committers space).
<div class="source">
-<pre>ssh [email protected]
-cd /x1/builds/any23
+<pre>
sh grab-binaries.sh REPO_ID ANY23_VERSION CRAWLER_VERSION HTML_SCRAPER_VERSION
OFFICE_SCRAPER_VERSION</pre></div>
</li>
@@ -594,8 +609,8 @@ sh grab-binaries.sh REPO_ID ANY23_VERSIO
</li>
-<li>
- This step will create the staging site: From the directory where
you have launched <tt>release:perform</tt> execute:
+<!-- li>
+ This step will create the staging site: From the directory where
you have launched <code>release:perform</code> execute:
<div class="source">
<pre>cd target/checkout
@@ -604,7 +619,7 @@ mvn -P site site-deploy -Dsite.deploymen
cd staging-site
svn add <version>
svn commit -m "staging site for release"</pre></div>
- </li>
+ </li-->
</ol>
</div>
@@ -614,11 +629,11 @@ svn commit -m "staging site for rel
<ol style="list-style-type: decimal">
-<li>Create a <tt>VOTE</tt> email thread on <a class="externalLink"
href="mailto:[email protected]";>any23-dev</a>
+<li>Create a <code>VOTE</code> email thread on <a
href="./mail-lists.html">any23-dev</a>
to record votes as replies, e.g.:
<div>
-<pre>To: "Apache Any23 Developers List" <[email protected]>
+<pre>To: "Apache Any23 Developers List" <dev [at]
any23.apache.org>
Subject: [VOTE] Release Apache Any23 X.Y
Hi,
@@ -629,17 +644,14 @@ http://issues.apache.org/jira/secure/Rel
There are still a couple of issues left in JIRA:
http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12312323&status=1
-SVN source tag (r9999999):
-https://svn.apache.org/repos/asf/any23/tags/X.Y/
+Git source tag signature (xyz....):
+https://git-wip-us.apache.org/repos/asf/any23.git......
Staging repo:
https://repository.apache.org/content/repositories/orgapacheany23-[YOUR
REPOSITORY ID]/
Staging binaries:
-http://people.apache.org/builds/any23/
-
-Staging site:
-http://any23.apache.org/X.Y/
+https://dist.apache.org/repos/dist/dev/any23/X.Y/
PGP release keys (signed using ABCDEFG):
http://any23.apache.org/dist/KEYS
@@ -652,13 +664,13 @@ Vote will be open for 72 hours.
</li>
-<li>Create a <tt>DISCUSS</tt> email thread on <tt>any23-dev@</tt> for any vote
questions, e.g.:
+<li>Create a <code>DISCUSS</code> email thread on <code>any23-dev@</code> for
any vote questions, e.g.:
<div>
-<pre>To: "Apache Any23 Developers List" <[email protected]>
+<pre>To: "Apache Any23 Developers List" <dev [at]
any23.apache.org>
Subject: [DISCUSS] Apache Any23 X.Y
-Discussion thread for vote on &lt;version&gt; release candidate, with
SVN source tag (r9999999).
+Discussion thread for vote on &lt;version&gt; release candidate, with
Git source tag (xyz.....).
For more information on the release process, check out
http://www.apache.org/dev/release.html
@@ -676,18 +688,18 @@ Some of the things to check before votin
<a class="externalLink"
href="http://www.apache.org/dev/release.html";>http://www.apache.org/dev/release.html</a>.</li>
-<li>A <tt>-1</tt> vote does not necessarily mean that the vote must be redone,
however it is usually a
- good idea to rollback the release if a <tt>-1</tt> vote is received
+<li>A <code>-1</code> vote does not necessarily mean that the vote must be
redone, however it is usually a
+ good idea to rollback the release if a <code>-1</code> vote is
received
(see "Recovering from a vetoed release" below).</li>
<li>After the vote has been open for at least 72 hours, has at least three +1
PMC votes and no -1 votes, then
- post the results to the vote thread, replying to the initial email
prepending <tt>[RESULT]</tt> to the
- original subject and include a list of every binding <tt>+1</tt>,
<tt>0</tt> and <tt>-1</tt> vote.
+ post the results to the vote thread, replying to the initial email
prepending <code>[RESULT]</code> to the
+ original subject and include a list of every binding
<code>+1</code>, <code>0</code> and <code>-1</code> vote.
<div>
-<pre>To: "Apache Any23 Developers List" <[email protected]>
-CC: "Apache Any23 PMC List" <[email protected]>
+<pre>To: "Apache Any23 Developers List" <dev [at]
any23.apache.org>
+CC: "Apache Any23 PMC List" <private [at] any23.apache.org>
Subject: [RESULT] [VOTE] Release Apache Any23 X.Y
Hi,
@@ -734,12 +746,12 @@ I will promote the artifacts to the cent
<li>Add the distribution artifacts to the distribution area
-<div class="source">
+<!-- div class="source">
<pre>ssh [email protected]
cd /x1/www/www.apache.org/dist/any23/
mv /x1/builds/any23/sources/* sources/
-mv /x1/builds/any23/binaries/* binaries/</pre></div>
+mv /x1/builds/any23/binaries/* binaries/</pre></div-->
</li>
@@ -754,18 +766,35 @@ mv /x1/builds/any23/binaries/* binaries/
<div class="section">
<h3>Announce the Release<a name="Announce_the_Release"></a></h3>
-<p>Make an announcement about the release on the
- <a class="externalLink"
href="mailto:[email protected]";>any23-user</a>,
- <a class="externalLink"
href="mailto:[email protected]";>any23-dev</a>, and
- <a class="externalLink"
href="mailto:[email protected]";>[email protected]</a> lists as per
- <a class="externalLink"
href="http://www.apache.org/foundation/mailinglists.html#foundation-announce]";>the
Apache Announcement Mailing Lists page</a>
- </p>
+<p>Make an announcement about the release on the follwoing lists:</p>
+ <ol>
+ <li>user [at] any23.apache.org</li>
+ <li>dev [at] any23.apache.org</li>
+ <li>announce [at] apache.org: lists as per <a class="externalLink"
href="http://www.apache.org/foundation/mailinglists.html#foundation-announce]";>the
Apache Announcement Mailing Lists page</a></li>
+ <li>public-geosemweb [at] w3.org: lists as found <a
class="externalLink"
href="http://lists.w3.org/Archives/Public/public-geosemweb/";>here</a></li>
+ <li>public-lod [at] w3.org: lists as found <a class="externalLink"
href="http://lists.w3.org/Archives/Public/public-lod/";>here</a></li>
+ <li>public-ogsw [at] w3.org: lists as found <a class="externalLink"
href="http://lists.w3.org/Archives/Public/public-ogsw/";>here</a></li>
+ <li>public-owl-wg [at] w3.org: lists as found <a class="externalLink"
href="http://lists.w3.org/Archives/Public/public-owl-wg/";>here</a></li>
+ <li>public-rdfa [at] w3.org: lists as found <a class="externalLink"
href="http://lists.w3.org/Archives/Public/public-rdfa/";>here</a></li>
+ <li>public-semnews [at] w3.org: lists as found <a class="externalLink"
href="http://lists.w3.org/Archives/Public/public-semnews/";>here</a></li>
+ <li>public-semstats [at] w3.org: lists as found <a
class="externalLink"
href="http://lists.w3.org/Archives/Public/public-semstats/";>here</a></li>
+ <li>public-semweb-lifesci [at] w3.org: lists as found <a
class="externalLink"
href="http://lists.w3.org/Archives/Public/public-semweb-lifesci/";>here</a></li>
+ <li>public-semweb-ui [at] w3.org : lists as found <a
class="externalLink"
href="http://lists.w3.org/Archives/Public/public-semweb-ui/";>here</a></li>
+ <li>public-semwebprog [at] w3.org: lists as found <a
class="externalLink"
href="http://lists.w3.org/Archives/Public/public-semwebprog/";>here</a></li>
+ <li>public-sodata [at] w3.org: lists as found <a class="externalLink"
href="http://lists.w3.org/Archives/Public/public-sodata/";>here</a></li>
+ <li>public-ssn-cg [at] w3.org: lists as found <a class="externalLink"
href="http://lists.w3.org/Archives/Public/public-ssn-cg/";>here</a></li>
+ <li>public-sweo-ig [at] w3.org: lists as found <a class="externalLink"
href="http://lists.w3.org/Archives/Public/public-sweo-ig/";>here</a></li>
+ <li>public-swim [at] w3.org: lists as found <a class="externalLink"
href="http://lists.w3.org/Archives/Public/public-swim/";>here</a></li>
+ <li>public-swisig [at] w3.org: lists as found <a class="externalLink"
href="http://lists.w3.org/Archives/Public/public-swisig/";>here</a></li>
+ <li>public-ws-semann [at] w3.org: lists as found <a
class="externalLink"
href="http://lists.w3.org/Archives/Public/public-ws-semann/";>here</a></li>
+ <li>semantic-web [at] w3.org: lists as found <a class="externalLink"
href="http://lists.w3.org/Archives/Public/semantic-web/";>here</a></li>
+ </ol>
<div>
<pre>From: [email protected]
-To: "ASF Announcements" <[email protected]>, "Apache
Any23 Users List" <[email protected]>
-CC: "Apache Any23 Developers List" <[email protected]>
+To: "ASF Announcements" <announce [at] apache.org>,
"Apache Any23 Users List" <user [at] any23.apache.org>
+CC: "Apache Any23 Developers List" <adev [at]
any23.apache.org> .....
Subject: [ANNOUNCE] Apache Any23 X.Y
The Apache Any23 Team is pleased to announce the release of Apache Any23 X.Y.
@@ -788,7 +817,7 @@ Have Fun,
<ol style="list-style-type: decimal">
-<li>Reply to the initial vote email prepending <tt>[CANCELED]</tt> to the
original subject.</li>
+<li>Reply to the initial vote email prepending <code>[CANCELED]</code> to the
original subject.</li>
<li>Rollback the version upgrades in trunk by <i>either</i>:
@@ -802,10 +831,12 @@ Have Fun,
</li>
-<li>Delete the svn tag created by the <tt>release:perform</tt> step:
+<li>Delete the svn tag created by the <code>release:perform</code> step:
<div>
-<pre>svn rm https://svn.apache.org/repos/asf/any23/tags/X.Y -m "deleting
tag from rolled back release"</pre></div></li>
+<pre>$ git push origin --delete ${branchName}</pre>
+<pre>$ git branch -d the_local_branch</pre>
+</div></li>
<li>Drop the Nexus staging repo:
Modified: any23/site/source-repository.html
URL:
http://svn.apache.org/viewvc/any23/site/source-repository.html?rev=1595073&r1=1595072&r2=1595073&view=diff
==============================================================================
--- any23/site/source-repository.html (original)
+++ any23/site/source-repository.html Thu May 15 23:25:50 2014
@@ -3,7 +3,7 @@
| Generated by Apache Maven Doxia at 2013-11-03
| Rendered using Apache Maven Fluido Skin 1.3.0
-->
-<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml"; lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
@@ -265,41 +265,38 @@
<div id="bodyColumn" class="span9" >
<div class="section">
-<h2>Overview<a name="Overview"></a></h2><a name="Overview"></a>
-<p>This project uses <a class="externalLink"
href="http://subversion.apache.org/";>Subversion</a> to manage its source code.
Instructions on Subversion use can be found at <a class="externalLink"
href="http://svnbook.red-bean.com/";>http://svnbook.red-bean.com/</a>.</p></div>
+<h2>Overview</h2>
+<p>Any23 uses <a class="externalLink" href="http://git.apache.org/";>Git</a> as
it's primary SCM. Instructions on Git use ata Apache can be found at <a
class="externalLink"
href="http://www.apache.org/dev/git.html";>here</a>.</p></div>
<div class="section">
-<h2>Web Access<a name="Web_Access"></a></h2><a name="Web_Access"></a>
+<h2>Web Access</h2>
<p>The following is a link to the online source repository.</p>
<div class="source">
-<pre><a class="externalLink"
href="http://svn.apache.org/viewvc/any23/trunk";>http://svn.apache.org/viewvc/any23/trunk</a></pre></div></div>
+<pre><a class="externalLink"
href="https://github.com/apache/any23";>https://github.com/apache/any23</a></pre>
+<p>Please ensure you are browsing within the <b>master branch</b></div></div>
<div class="section">
-<h2>Anonymous access<a name="Anonymous_access"></a></h2><a
name="Anonymous_access"></a>
-<p>The source can be checked out anonymously from SVN with this command:</p>
+<h2>Anonymous access</h2>
+<p>The source can be checked out anonymously from Git via http or git
protocols:</p>
<div class="source">
-<pre>$ svn checkout http://svn.apache.org/repos/asf/any23/trunk
apache-any23</pre></div></div>
+<pre>$ git clone http://git.apache.org/any23.git</pre>
+<p>or</p>
+<pre>$ git clone git://git.apache.org/any23.git</pre></div></div>
<div class="section">
-<h2>Developer access<a name="Developer_access"></a></h2><a
name="Developer_access"></a>
-<p>Everyone can access the Subversion repository via HTTP, but Committers must
checkout the Subversion repository via HTTPS.</p>
+<h2>Developer access</h2>
+<p>Everyone can access the Git repository via HTTP, but Committers must
checkout the Subversion repository via HTTPS in order to push code changes.</p>
<div class="source">
-<pre>$ svn checkout https://svn.apache.org/repos/asf/any23/trunk
apache-any23</pre></div>
-<p>To commit changes to the repository, execute the following command to
commit your changes (svn will prompt you for your password)</p>
-<div class="source">
-<pre>$ svn commit --username your-username -m "A
message"</pre></div></div>
+<pre>$ git clone https://git-wip-us.apache.org/repos/asf/any23.git</pre></div>
+<p>There is also an Any23 committers area which hosts committer specific
resources which as <code>KEYS</code> files, etc.</p>
+<pre>$ git clone
https://git-wip-us.apache.org/repos/asf/any23-committers.git</pre>
+</div>
+<p>Apache Infrastructure provide a bunch of information on Git at Apache for
Committers <a href="https://git-wip-us.apache.org/";>here</a>.</p>
<div class="section">
-<h2>Access from behind a firewall<a
name="Access_from_behind_a_firewall"></a></h2><a
name="Access_from_behind_a_firewall"></a>
-<p>For those users who are stuck behind a corporate firewall which is blocking
HTTP access to the Subversion repository, you can try to access it via the
developer connection:</p>
+<h2>Access from behind a firewall</h2>
+<p>For those users who are stuck behind a corporate firewall which is blocking
HTTP access to the Git repository, you can try to access it via the developer
connection:</p>
<div class="source">
-<pre>$ svn checkout https://svn.apache.org/repos/asf/any23/trunk
apache-any23</pre></div></div>
+<pre>$ git clone
https://git-wip-us.apache.org/repos/asf/any23.git</pre></div></div>
<div class="section">
-<h2>Access through a proxy<a name="Access_through_a_proxy"></a></h2><a
name="Access_through_a_proxy"></a>
-<p>The Subversion client can go through a proxy, if you configure it to do so.
First, edit your "servers" configuration file to indicate which proxy
to use. The file's location depends on your operating system. On Linux or Unix
it is located in the directory "~/.subversion". On Windows it is in
"%APPDATA%\Subversion". (Try "echo %APPDATA%", note this is
a hidden directory.)</p>
-<p>There are comments in the file explaining what to do. If you don't have
that file, get the latest Subversion client and run any command; this will
cause the configuration directory and template files to be created.</p>
-<p>Example: Edit the 'servers' file and add something like:</p>
-<div class="source">
-<pre>[global]
-http-proxy-host = your.proxy.name
-http-proxy-port = 3128
-</pre></div></div>
+<h2>Access through a proxy</h2>
+<p>Committers should consulte the <a
href="http://git-scm.com/docs/git-config";>git-config</a> manual for proxy
specific settings within their Git client.</div>
</div>
</div>
</div>
Modified: any23/site/team-list.html
URL:
http://svn.apache.org/viewvc/any23/site/team-list.html?rev=1595073&r1=1595072&r2=1595073&view=diff
==============================================================================
--- any23/site/team-list.html (original)
+++ any23/site/team-list.html Thu May 15 23:25:50 2014
@@ -281,65 +281,78 @@
<td><a name="ansell"></a>ansell</td>
<td>Peter Ansell</td>
<td>ansell[at]apache[dot]org</td>
-<td>Committer, PPMC Member</td></tr>
+<td>Committer, PMC Member</td></tr>
<tr class="a">
<td><a name="dpalmisano"></a>dpalmisano</td>
<td>Davide Palmisano</td>
<td>dpalmisano[at]apache[dot]org</td>
-<td>Committer, PPMC Member</td></tr>
+<td>Committer, PMC Member</td></tr>
<tr class="b">
<td><a name="giovanni"></a>giovanni</td>
<td>Giovanni Tummarello</td>
<td>giovanni[at]apache[dot]org</td>
-<td>Committer, PPMC Member</td></tr>
+<td>Committer, PMC Member</td></tr>
<tr class="a">
<td><a name="lewismc"></a>lewismc</td>
<td>Lewis John McGibbney</td>
<td>lewismc[at]apache[dot]org</td>
-<td>Committer, PPMC Member</td></tr>
+<td>Committer, PMC Member, Project Chair</td></tr>
<tr class="b">
<td><a name="mattmann"></a>mattmann</td>
<td>Chris Mattmann</td>
<td>mattmann[at]apache[dot]org</td>
-<td>Champion, Committer, PPMC Member, Mentor</td></tr>
+<td>Champion, Committer, PMC Member, Mentor</td></tr>
<tr class="a">
<td><a name="mostarda"></a>mostarda</td>
<td>Michele Mostarda</td>
<td>mostarda[at]apache[dot]org</td>
-<td>Committer, PPMC Member</td></tr>
+<td>Committer, PMC Member</td></tr>
<tr class="b">
-<td><a name="niq"></a>niq</td>
-<td>Nick Kew</td>
-<td>niq[at]apache[dot]org</td>
-<td>Committer, PPMC Member, Mentor</td></tr>
-<tr class="a">
<td><a name="pramirez"></a>pramirez</td>
<td>Paul Michael Ramirez</td>
<td>pramirez[at]apache[dot]org</td>
-<td>Committer, PPMC Member, Mentor</td></tr>
-<tr class="b">
+<td>Committer, PMC Member, Mentor</td></tr>
+<tr class="a">
<td><a name="reto"></a>reto</td>
<td>Reto Bachmann-Gmür</td>
<td>reto[at]apache[dot]org</td>
-<td>Committer, PPMC Member</td></tr>
-<tr class="a">
+<td>Committer, PMC Member</td></tr>
+<tr class="b">
<td><a name="simonetripodi"></a>simonetripodi</td>
<td>Simone Tripodi</td>
<td>simonetripodi[at]apache[dot]org</td>
-<td>Committer, PPMC Member, Mentor</td></tr>
-<tr class="b">
+<td>Committer, PMC Member, Mentor</td></tr>
+<tr class="a">
<td><a name="szydan"></a>szydan</td>
<td>Szymon Danielczyk</td>
<td>szydan[at]apache[dot]org</td>
-<td>Committer, PPMC Member</td></tr>
+<td>Committer, PMC Member</td></tr>
+</table></div>
+
+<div class="section">
+<h3>Emeritus Members<a name="Members"></a></h3><a name="Members"></a>
+<p>The following is a list of Emeritus developers and friends with commit
privileges that have directly contributed to the project in one way or another
in the past.</p>
+<table border="0" class="table table-striped">
+<tr class="a">
+<th>Id</th>
+<th>Name</th>
+<th>Email</th>
+<th>Roles</th></tr>
+<tr class="b">
+<td><a name="niq"></a>niq</td>
+<td>Nick Kew</td>
+<td>niq[at]apache[dot]org</td>
+<td>Committer, PMC Member, Mentor</td></tr>
<tr class="a">
<td><a name="tommaso"></a>tommaso</td>
<td>Tommaso Teofili</td>
<td>tommaso[at]apache[dot]org</td>
-<td>Committer, PPMC Member, Mentor</td></tr></table></div>
+<td>Committer, PMC Member, Mentor</td></tr></table></div>
+
<div class="section">
<h3>Contributors<a name="Contributors"></a></h3><a name="Contributors"></a>
-<p>There are no contributors listed for this project. Please check back again
later.</p><script type="text/javascript">
+<p>There are a number of community contributions to Any23. The best way to
track them is to join the <a href="./mail-lists.html">mailing lists</a></p>
+<script type="text/javascript">
function offsetDate(id, offset) {
var now = new Date();
var nowTime = now.getTime();
![http://nutch.apache.org/images/nutch_logo_tm.gif"](http://nutch.apache.org/images/nutch_logo_tm.gif"){kind=link}