You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by cr...@apache.org on 2002/12/24 03:04:23 UTC
cvs commit: xml-forrest/src/documentation/content/xdocs forrest-contract.xml forrestbot.xml libre-intro.xml primer.xml who.xml your-project.xml
crossley 2002/12/23 18:04:23
Modified: . status.xml
src/resources/skins/common/xslt/html document2html.xsl
src/documentation/content/xdocs forrest-contract.xml
forrestbot.xml libre-intro.xml primer.xml who.xml
your-project.xml
Log:
Obfuscate email addresses.
Revision Changes Path
1.80 +5 -5 xml-forrest/status.xml
Index: status.xml
===================================================================
RCS file: /home/cvs/xml-forrest/status.xml,v
retrieving revision 1.79
retrieving revision 1.80
diff -u -r1.79 -r1.80
--- status.xml 11 Dec 2002 08:28:10 -0000 1.79
+++ status.xml 24 Dec 2002 02:04:22 -0000 1.80
@@ -33,7 +33,7 @@
</action>
<action dev="NKB" type="update" context="skins">
Now even the selected tab retains a link, to be able to easily select
- the main page of that tab even if it's "current".
+ the main page of that tab even if it is "current".
</action>
<action dev="JT" type="fix" context="skins" due-to="Nick Chalko"
due-to-email="nick@chalko.com">
@@ -58,8 +58,8 @@
before it was just reporting [broken link].
</action>
<action dev="NKB" type="update" context="code">
- Updated latest Cocoon jars: chain metamodule name set to "forrest", and it's
- used instead of teh default one.
+ Updated latest Cocoon jars: chain metamodule name set to "forrest",
+ and it is used instead of the default one.
</action>
<action dev="JT" type="fix" context="skins">
Fixed a bug where multiple menu entries are highlighted if the filenames
@@ -418,7 +418,7 @@
</action>
<action context="code" dev="NKB">
Finalise the project-definition DTDs, like status.xml and module.xml;
- try to come up with a common format with others on community@apache.org.
+ try to come up with a common format with others on community.at.apache.org.
</action>
<action context="code" dev="open">
The document-v11 DTD needs to rationalise the use of link|jump|fork
@@ -436,7 +436,7 @@
especially to define sections and titles.
</action>
<action context="code" dev="NKB">
- Add the PATCHQUEUE system to Forrest, as used by cocoon-dev@xml.apache.org
+ Add the PATCHQUEUE system to Forrest, as used by cocoon-dev.at.xml.apache.org
</action>
<action context="code" dev="open">
Define a simple mechanism for staging.
1.2 +15 -4 xml-forrest/src/resources/skins/common/xslt/html/document2html.xsl
Index: document2html.xsl
===================================================================
RCS file: /home/cvs/xml-forrest/src/resources/skins/common/xslt/html/document2html.xsl,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- document2html.xsl 16 Nov 2002 20:58:12 -0000 1.1
+++ document2html.xsl 24 Dec 2002 02:04:22 -0000 1.2
@@ -164,9 +164,20 @@
<xsl:template match="link">
<xsl:apply-templates select="@id"/>
- <a href="{@href}">
- <xsl:apply-templates/>
- </a>
+ <xsl:choose>
+ <xsl:when test="starts-with(@href, 'mailto:') and contains(@href, '@')">
+ <xsl:variable name="mailto-1" select="substring-before(@href,'@')"/>
+ <xsl:variable name="mailto-2" select="substring-after(@href,'@')"/>
+ <a href="{$mailto-1}.at.{$mailto-2}">
+ <xsl:apply-templates/>
+ </a>
+ </xsl:when>
+ <xsl:otherwise>
+ <a href="{@href}">
+ <xsl:apply-templates/>
+ </a>
+ </xsl:otherwise>
+ </xsl:choose>
</xsl:template>
<xsl:template match="jump">
1.5 +5 -3 xml-forrest/src/documentation/content/xdocs/forrest-contract.xml
Index: forrest-contract.xml
===================================================================
RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/forrest-contract.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- forrest-contract.xml 11 Oct 2002 15:42:26 -0000 1.4
+++ forrest-contract.xml 24 Dec 2002 02:04:22 -0000 1.5
@@ -6,8 +6,9 @@
<notice>The legal tone of this document is just a gimmick, this is not a
legal document in any sense. At all times: since this is open source: the real
contract is described in the implementation details of the full distribution.
- This tries to list (not explain) what the ins and outs of using forrest is
- about. Please let <link href="mailto:forrest-dev@apache.org">us</link> know if
+ This tries to list (not explain) what the ins and outs of using Forrest is
+ about. Please let the forrest-dev
+ <link href="mail-lists.html">mail list</link> know if
any of the bullets listed here are out of sync with the real
implementation.</notice>
<abstract>This document describes in a very techy bullet-style way how to use Forrest.</abstract>
@@ -20,7 +21,8 @@
<title>Forrest will:</title>
<ul>
<li>provide DTDs, skins, cocoon-pipelines, and a willing team of
- supporting developers at <link href="mailto:forrest-dev@apache.org">forrest-dev@apache.org</link></li>
+ supporting developers at the forrest-dev
+ <link href="mail-lists.html">mail list</link></li>
<li>use Cocoon to generate the HTML documentation for TheProject</li>
</ul>
</section>
1.4 +5 -3 xml-forrest/src/documentation/content/xdocs/forrestbot.xml
Index: forrestbot.xml
===================================================================
RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/forrestbot.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- forrestbot.xml 18 Aug 2002 07:44:56 -0000 1.3
+++ forrestbot.xml 24 Dec 2002 02:04:22 -0000 1.4
@@ -212,7 +212,8 @@
<note>Once you understand all of this you might decide NOT to run your
own centralized service but rather ask your project to be taken up in the
centralized service of the project team itself: just send a mail to
- forrest-dev@apache.org listing the required parameters to be taken up in the
+ forrest-dev <link href="mail-lists.html">mail list</link>
+ defining the required parameters to be taken up in the
process.</note>
<section>
<title>Checking logs and getting them by mail</title>
@@ -228,8 +229,9 @@
<section><title>Current supported workstages and types.</title><section><title><code><prepare></code></title><p>No specific type versions. (don't use type-attribute)</p><p>Template arguments:</p><ul><li><code><skin></code> @name holds the name of the skin to use.</li></ul></section><section><title><code><get-src ...></code></title><section><title><code><get-src type="cvs"></code></title><p>Template arguments:</p><ul><li><code><host></code> @name holds the ipaddress or dns name of the cvs serving host</li><li><code><root></code> @name holds the cvs-root directory on that host</li><li><code><user></code> @name holds the username to use on the cvs repository </li><li><code><passwd></code> @name holds the password to use on the cvs repository</li><li><code><module></code> @name holds the module name that holds the </li><li><code><dir></code> @name holds the relative path to the {docroot} directory. (This is the dir that is holding the ./content/xdocs as specified in t. </li></ul></section><section><title><code><get-src type="local-copy"></code></title><p>Template arguments:</p><ul><li><code><content-dir/></code> @name holds the path pointing to the {docroot} directory. (See the <link href="forrest-contract.html">contract</link> to understand what should be there.)</li><li><code><project-dir/></code> @name holds the path pointing to the {projecthome} directory where the xml project descriptors reside.</li></ul></section></section><section><title><code><generate></code></title><p>No specific type versions. (don't use type-attribute)</p><p>Template arguments:</p><ul><li><code><debuglevel></code> @name holds the threshold-level for showing debug statements in the cocoon generation process.</li></ul></section><section><title><code><deploy ...></code></title><section><title><code><deploy type="scp"></code></title><p>Template arguments:</p><ul><li><code><host></code> @name holds the remote host where the file will be copied to.</li><li><code><user></code> @name holds the username to be used when logging onto the remote host.</li><li><code><root></code> @name holds the prefix part of where the content needs to be published.</li><li><code><dir></code> @name holds the suffix part of where the content needs to be published.</li></ul><warning>Using this approach requires that the public key of the user executing the bot target is present in the authorized key file (<code>~/.ssh/authorized_keys2</code>) of the remote user (on the remote host).</warning><note>Might be interesting to understand that the full process actually is bundling all files to copy in a *.tar.gz that is un-tar.gzipped on the remote host using ssh. </note></section><section><title><code><deploy type="local-copy"></code></title><p>Template arguments:</p><ul><li><code><destination></code> @name holds the path where the generated content needs to be copied to.</li></ul></section><section><title><code><deploy type="ftp"></code></title><p>Template arguments:</p><ul><li><code><host></code> @name holds the hostname of the ftp server to publish to.</li><li><code><user></code> @name holds the username to use for loging onto the ftp server.</li><li><code><passwd></code> @name holds the password to use.</li><li><code><destination></code> @name holds the path to the directory on the remote host where the generated content needs to be published. The process is using the <code>ftp cd</code> command to get there. This means this directory has to exist.</li></ul></section><warning>Currently the ant distribution that is included in forrest cvs is not offering the required NetComponents.jar to actually support this type of deployment. If you want to use it anyway you should use get the required jar from <link href="http://www.savarese.org/oro/downloads/index.html#NetComponents">http://www.savarese.org/oro/downloads</link> and drop that into your <code>{forrest-sandbox}/tools/antipede/lib</code> directory. </warning></section><section><title><code><cleanup></code></title><p>No specific type versions. (don't use type-attribute)</p><p>Template arguments: None.</p></section></section><section>
<title>ForrestBot design</title>
<p>Most of us will just like things to work, and will be happy enough
- just using it, maybe even letting <link href="mailto:forrest-dev@apache.org">us</link> know if we could improve this or
- the other. Some however might be drawn to the
+ just using it, maybe even letting the forrest-dev
+ <link href="mail-lists.html">mail list</link> know if we could improve
+ this or the other. Some however might be drawn to the
<link href="http://www.howstuffworks.com/">how stuff works</link> of things.
For them is this section as a start in the rest of their own pursuit.</p>
<section>
1.4 +2 -3 xml-forrest/src/documentation/content/xdocs/libre-intro.xml
Index: libre-intro.xml
===================================================================
RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/libre-intro.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- libre-intro.xml 8 Jul 2002 15:19:14 -0000 1.3
+++ libre-intro.xml 24 Dec 2002 02:04:22 -0000 1.4
@@ -357,9 +357,8 @@
<section>
<title>Next Libre (0.1)</title>
<note>Next libre is in fact largely in your hands... just drop
- <link
- href="mailto:forrest-dev@xml.apache.org">forrest-dev@xml.apache.org</link> a
- line, and see what happens...</note>
+ the forrest-dev <link href="mail-lists.html">mail list</link>
+ a line, and see what happens...</note>
<section>
<title>Itches</title>
<p>There is quite a number of fast code patches that can/need to
1.18 +7 -7 xml-forrest/src/documentation/content/xdocs/primer.xml
Index: primer.xml
===================================================================
RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/primer.xml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- primer.xml 12 Nov 2002 12:47:39 -0000 1.17
+++ primer.xml 24 Dec 2002 02:04:22 -0000 1.18
@@ -19,8 +19,7 @@
actual progress of the Forrest project. As such, the primer will be enhanced,
restructured and edited to provide an accessible entry point for new
Forresteers. Please send all comments, patches and suggestions to
- <link href="mailto:forrest-dev@xml.apache.org">the Forrest
- developers</link>.</note>
+ the forrest-dev <link href="mail-lists.html">mail list</link>.</note>
<section>
<title>History</title>
<p>Forrest has come into existence because of the abysmal state of the
@@ -519,8 +518,9 @@
<li>Ant wizards able to compete with Nicola and Stefan</li>
<li>Unix shell scripting / CVS / cron gurus, preferably bearded</li>
</ul>
- <p>Just drop us a line at <link
- href="mailto:forrest-dev@xml.apache.org">forrest-dev@xml.apache.org</link>.</p>
+ <p>Just drop us a line at
+ the forrest-dev <link href="mail-lists.html">mail list</link>.
+ </p>
</section>
<p>That is all, folks.</p>
@@ -531,16 +531,16 @@
</tr>
<tr>
<td>2002-05-22</td>
- <td>Initial version, Steven Noels, stevenn@apache.org</td>
+ <td>Initial version, Steven Noels, stevenn.at.apache.org</td>
</tr>
<tr>
<td>2002-05-23</td>
<td>Various rephrasings and clarifications thanks to Ross Gardler,
- ross@saafe.org</td>
+ ross.at.saafe.org</td>
</tr>
<tr>
<td>2002-09-23</td>
- <td>Updated the directory outline (jefft@apache.org)</td>
+ <td>Updated the directory outline (jefft.at.apache.org)</td>
</tr>
</table>
</body>
1.12 +10 -10 xml-forrest/src/documentation/content/xdocs/who.xml
Index: who.xml
===================================================================
RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/who.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- who.xml 13 Nov 2002 05:20:40 -0000 1.11
+++ who.xml 24 Dec 2002 02:04:22 -0000 1.12
@@ -23,16 +23,16 @@
<section>
<title>Committers</title>
<ul>
- <li>[NKB] - Nicola Ken Barozzi (nicolaken@apache.org)</li>
- <li>[DC] - David Crossley (crossley@apache.org)</li>
- <li>[SM] - Stefano Mazzocchi (stefano@apache.org)</li>
- <li>[JM] - John Morrison (morrijr@apache.org)</li>
- <li>[SN] - Steven Noels (stevenn@apache.org)</li>
- <li>[KP] - Konstantin Piroumian (kpiroumian@apache.org)</li>
- <li>[MP] - Marc Portier (mpo@apache.org)</li>
- <li>[SR] - Sam Ruby (rubys@apache.org)</li>
- <li>[JT] - Jeff Turner (jefft@apache.org)</li>
- <li>[BK] - Bert Van Kets (bert@apache.org)</li>
+ <li>[NKB] - Nicola Ken Barozzi (nicolaken.at.apache.org)</li>
+ <li>[DC] - David Crossley (crossley.at.apache.org)</li>
+ <li>[SM] - Stefano Mazzocchi (stefano.at.apache.org)</li>
+ <li>[JM] - John Morrison (morrijr.at.apache.org)</li>
+ <li>[SN] - Steven Noels (stevenn.at.apache.org)</li>
+ <li>[KP] - Konstantin Piroumian (kpiroumian.at.apache.org)</li>
+ <li>[MP] - Marc Portier (mpo.at.apache.org)</li>
+ <li>[SR] - Sam Ruby (rubys.at.apache.org)</li>
+ <li>[JT] - Jeff Turner (jefft.at.apache.org)</li>
+ <li>[BK] - Bert Van Kets (bert.at.apache.org)</li>
</ul>
</section>
</body>
1.18 +4 -4 xml-forrest/src/documentation/content/xdocs/your-project.xml
Index: your-project.xml
===================================================================
RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/your-project.xml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- your-project.xml 23 Nov 2002 02:58:24 -0000 1.17
+++ your-project.xml 24 Dec 2002 02:04:22 -0000 1.18
@@ -869,9 +869,9 @@
<em>in-place</em> content, eliminating the step of copying everything
into the <code>build/</code> directory. There are also suggestions for making
webapp-based content generation the primary technique. Future
- directions like these are debated on <link
- href="mailto:forrest-dev@xml.apache.org">forrest-dev</link>; please
- join if you have any suggestions.
+ directions like these are debated on
+ the forrest-dev <link href="mail-lists.html">mail list</link>.
+ Please join if you have any suggestions.
</note>
</section>
</section>