struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From hus...@apache.org
Subject svn commit: r376838 [4/6] - in /struts/site/trunk/xdocs: announce.xml bylaws.xml download.xml downloads.xml faqs.xml helping.xml index.xml javadoc.xml kickstart.xml mail.xml navigation.xml release-checklist.xml releases.xml struts.css volunteers.xml
Date Fri, 10 Feb 2006 20:58:36 GMT
Modified: struts/site/trunk/xdocs/kickstart.xml
URL: http://svn.apache.org/viewcvs/struts/site/trunk/xdocs/kickstart.xml?rev=376838&r1=376837&r2=376838&view=diff
==============================================================================
--- struts/site/trunk/xdocs/kickstart.xml (original)
+++ struts/site/trunk/xdocs/kickstart.xml Fri Feb 10 12:58:33 2006
@@ -16,305 +16,560 @@
 <!--
 // ======================================================================== 78
 -->
-<document><properties>
-<title>Kickstart FAQ</title>
-</properties>
-<body>
-<a name="faq"/>
-<section name="Kickstart FAQ">
-
-<a name="contents"/>
-<subsection name="Index">
-
-<p>
-Here are answers to the some of the usual Apache Struts getting-started questions. 
-</p>
-  <ul>
-    <li><a href="#shale">Why are you offering both Struts Shale and Struts Action Framework? Don't they compete for new development?</a></li>
-    <li><a href="#2x">Is Shale likely to become Struts 2.x?</a></li>
-    <li><a href="#fork">Is Struts Shale a fork?</a></li>
-    <li><a href="#struts">If Shale is a new product, why is it called Struts?</a></li>
-  <li><a href="#ti">What about Ti? What about WebWork?</a></li>
-    <li><a href="#ti2">Does Ti mean there will be three frameworks?</a></li>
-    <li><a href="#overdrive">What about OverDrive or Struts Nexus?</a></li>    
-    <li><a href="#classic">What's the difference between Struts Action Framework and Struts Classic</a></li>
-  </ul>
-  <ul>
-    <li><a href="#struts">Why is the project called Struts?</a></li>
-    <li><a href="#license">How is Apache Struts licensed?</a></li>
-    <li><a href="#usage">Can Apache Struts be used in a commercial application?</a></li>
-    <li><a href="#credits">Do I have to credit Apache Struts on my own website?</a></li>
-  </ul><ul>
-    <li><a href="#requests">If a product doesn't do what I want, can I request that a feature be added?</a></li>
-    <li><a href="#help">Where can I get help with Apache Struts?</a></li>
-    <li><a href="#support">Is commercial support available for Apache Struts?</a></li>
-    <li><a href="#providers">Are there ISPs that will host my Apache Struts application?</a></li>
-    <li><a href="#ide">Is there a particularly good IDE to use with Struts Action Framework?</a></li>
-  </ul><ul>
-    <li><a href="#digest">Is there a digest for the Apache Struts User list?</a></li>
-    <li><a href="#newsgroup">Is there a Apache Struts Newsgroup?</a></li>
-    <li><a href="#mailbounce">Why didn't my posting show up on the user list?"</a></li>
-    <li><a href="#unsubscribe">How do I unsubscribe from the mailing list?</a></li>
-  </ul>
-
-<p>
-For other FAQs, see the documentation for each subproject.
-</p>
-
-</subsection>
-
-<a name="shale"/>
-<subsection name="Why are you offering both Struts Shale and Struts Action Framework? Don't they compete for new development?">
-<p>We do offer Apache Struts developers a choice, but, hey, choice is good. :)</p>
-<p>People who want to create and maintain the <a href="announce.html#a20051214.4">Struts Action Framework</a> are welcome to do so.</p>
-<p>People who want to create and maintain the <a href="announce.html#a20051214.2">Struts Shale Framework</a> are equally welcome.</p>
-<p>As a volunteer organization, we are not constrained by the economics of competition. All we need are volunteers who are ready, willing, and able to do the work. So long as we have volunteers, we have work for them to do.</p>
-<p>Right now, we have volunteers who want to leverage the new JavaServer Faces framework by using Struts Shale for new development. We also have volunteers who prefer to leverage their existing investment in Struts Action Framework. All are welcome.</p>
-<p>For more about volunteering, visit our <a href="http://struts.apache.org/faqs/helping.html">how to help page</a>.</p>
-</subsection>
-
-<a name="fork"/>
-<subsection name="Is Struts Shale a fork?">
-<p>No. It's an entirely new product with its own architecture. Struts Shale is an MVC framework for web applications, like Struts Action Framework, but it's a fresh start. Struts Shale is the best choice for developers eager to leverage the latest technologies, like JavaServer Faces.</p>
-<p>Both frameworks will have a home here so long as there are volunteers ready to contribute.</p>
-<p>We encourage you to choose the framework that works best for you. (Even if it is not one of ours!)</p>
-</subsection>
-
-<a name="struts"/>
-<subsection name="If Shale is a new product, why is it called Struts?">
-<p>
-Apache Struts embraces standards, and JavaServer Faces (JSF) is a new standard. 
-JSF is not the first standard that Struts has assimilated (and, undoubtedly, it will not be the last). 
-</p>
-<p>
-For example, many of the original Struts taglibs overlap with the JavaServer Pages Standard Tag Library (JSTL). 
-Some of us want to continue using the original tags. 
-Others want to be able to use JSTL as much as possible. 
-As a result, David Karr created the Struts EL taglibs. 
-The Struts EL subproject provides JSTL versions of only the Struts tags that do not overlap with JSTL. 
-Meanwhile, the original taglibs are available and maintained for those that choose to use them. 
-</p>
-<p>
-Likewise, some of us want to use JSF as much as possible. 
-Others want to continue using the original Action framework. 
-As a result, Craig McClanahan created the Struts Shale framework. 
-Shale provides the same utility as the Action framework by building on the JSF feature set.
-Since Shale does for JSF what Action does for JSP, we consider Shale to be another Struts framework. 
-</p>
-</subsection>
-
-<a name="2x"/>
-<subsection name="Is Shale likely to become Struts 2.x?">
-<p>
-Struts Shale has its own identity and its own release cycle. 
-Struts Action Framework is one subproject, and the Struts Shale framework is another. 
-So, no, it is not likely that Struts Shale will become Struts Action 2.x.
-</p>
-</subsection>
-
-<a name="ti"/>
-<subsection name="What about Ti? What about WebWork?">
-<p>
-<a href="http://wiki.apache.org/struts/StrutsTi">Struts Ti</a> 
-(short for Titanium) is a proposal for a Struts Action Framework 2.x candidate. 
-In late November 2005, the Ti proposal was amended to include a merger with 
-<a href="http://www.opensymphony.com/webwork/">Open Symphony WebWork</a>. 
-Under this plan, the next stable release of WebWork would be donated to Apache Struts, 
-and the lead WebWork committers would join the Struts community. 
-</p>
-<p>
-WebWork started as a <a href="http://incubator.apache.org/learn/rules-for-revolutionaries.html">Struts Revolution</a>. 
-Over the years, it has evolved into a superb action-based framework that retains many Struts 1.x paradigms. 
-</p>
-<p>
-People who have worked with both Struts 1.x and WebWork 2.x tend to agree that it is a logical candidate for Struts Action Framework 2.x.
-If you look the Struts Action 1.x roadmap and the WebWork 2.x feature set, 
-you'll see that WebWork has already does most of what we wanted Struts Action to do. 
-If we finished the roadmap ourselves, Struts Action would end up as a WebWork workalike. 
-Rather than reinvent the wheel, 
-Ti has become a proposal to put the WebWork wheel back on the Struts axle.
-</p>
-<p>
-Of course, many of us have significant Struts Action 1.x applications in production. 
-Being able to migrate both applications and developer skill sets is a telling point of the proposal.
-Both a migration layer and migration documentation are under active development.
-</p>
-</subsection>
-
-<a name="ti2" />
-<subsection name="Does Ti mean there will be three frameworks?">
-<p>
-Probably not. 
-Like many projects, we start by giving proposed subprojects a codename. 
-Sun's "Tiger" and Microsoft's "Vista" are two examples. 
-"Ti" is a codename like "Tiger" and "Vista. 
-If Struts Ti is accepted as Struts Action Framework 2.x, the codename would fall into disuse. 
-</p>
-</subsection>
-
-<a name="overdrive" />
-<subsection name="What about OverDrive or Struts Nexus?">
-<p>
-<a href="http://wiki.apache.org/struts/StrutsOverDrive">OverDrive</a> 
-is a working proposal to use a set of case-study applications 
-to drive the design and creation of a business layer framework. 
-The codename for the business layer framework under development is "Nexus". 
-Like Action and Shale, the Nexus internals are based on the Chain of Responsibility pattern.
-</p>
-<p>
-OverDrive and Nexus do not complete with frameworks like Action and Shale. 
-Nexus begins where these frameworks end. 
-Nexus is the "rest of the stack". 
-</p>
-<p>
-The codebase underlying the proposal is being coded in C#, but a version for Java is expected in due course. 
-</p>
-</subsection>
-
-<a name="action"/>
-<subsection name="What's the difference between Struts Action Framework and Struts Classic?">
-<p>For the Struts Action Framework 1.3.x series, we subdivided the monolithic Struts 1.2.x distribution into several discrete subprojects. Struts Classic is a codename for the work we needed to do to create and release the new subprojects. </p>
-<p>For a time, we considered bundling those seven products together and calling the bundle "Struts Classic". Instead, we are bundling Struts Action Framework and any compatible projects into a distribution called "Struts Action Framework Library". This bundle includes the original "seven dwarfs" and new subprojects, like Struts Scripting.</p>
-</subsection>
-
-<a name="struts"/>
-<subsection name="Why is the project called Struts?">
-<p>It's a reference to struts in the architectural sense, a reminder of the nearly invisible pieces that hold up buildings, houses, and bridges.</p>
-</subsection>
-
-<a name="license"/>
-<subsection name="How is Apache Struts licensed?">
-<p>All Apache Struts products are copyrighted software available under the <a href="http://www.apache.org/licenses">Apache License</a>, a &quot;free-to-use, business-friendly license&quot;.</p>
-</subsection>
-
-<a name="usage"/>
-<subsection name="Can Apache Struts be used in a commercial product?">
-<p>Yes. The only requirements you must meet are those listed in the <a href="http://www.apache.org/licenses">Apache License</a>.</p>
-</subsection>
-
-<a name="credits"/>
-<subsection name="Do I have to credit Apache Struts on my own website?">
-<p>You need to credit Apache Struts if you <strong>redistribute your own framework</strong> based on our products
-for other people to use. (See the <a href="http://www.apache.org/LICENSE">Apache License</a> for details.)
-But you do <strong>not</strong> need to credit Apache Struts just because your web application utilizes one of our products.
-It's the same situation as using the Apache HTTPD server or Tomcat. Not required if its just running your web site.
-Required if you've used the source code to create your own server that you are redistributing to other people.</p>
-</subsection>
-
-<a name="requests"/>
-<subsection name="If a product doesn't do what I want, can I request that a feature be added?">
-<p>
-First, it's important to remember that Apache Struts is an all-volunteer project.
-We don't charge anyone anything to use Apache Struts products.
-Committers and other developers work on Apache Struts products because they need to use it with their own applications.
-If others can use it too, that's "icing on the cake".
-If you <a href="../helping.html">submit a patch</a> for a feature that a Committer finds useful, then that Committer may choose to volunteer his or her time to apply the patch.
-If you just submit an idea without a patch, it is much less likely to be added (since first someone else has to volunteer their time to write the patch).
-</p>
-<p>
-We are grateful for any patches, and we welcome new ideas, but the best way to see that something gets added to the framework is to do as much of the work as you can, rather than rely on the "kindness of strangers". Worst case, you can apply the patch to your copy of Struts and still use the feature in your own application. (Which is what open source is ~really~ all about.)
-</p>
-</subsection>
-
-<a name="help"/>
-<subsection name="Where can I get help with Apache Struts?">
-<p>Struts Action Framework comes complete with a
-<a href="../userGuide/index.html">Users Guide</a> to
-introduce people to the framework and its underlying technologies. Various components
-also have their own in-depth Developers Guide, to cover more advanced topics. Comprehensive
-<a href="../api/index.html">Javadocs</a> are included
-along with the <strong>full source code</strong>.
-</p>
-<p>
-The
-<a href="http://struts.apache.org/mail.html">Struts user mailing list</a> is also
-very active, and welcomes posts from new users. Before posting a new question, be
-sure to consult the
-<a href="http://struts.apache.org/mail.html#Archives">
-<strong>MAILING LIST ARCHIVE</strong></a> and the very excellent
-<a href="http://www.catb.org/~esr/faqs/smart-questions.html">
-How To Ask Questions The Smart Way</a> by Eric Raymond. Please do be sure
-to <a href="http://expita.com/nomime.html">turn off HTML</a> in your
-email client before posting.
-</p>
-</subsection>
-
-<a name="support"/>
-<subsection name="Is commercial support available?">
-<p>The Apache Software Foundation does not provide commercial support for any of our software products, including Apache Struts products. 
-However, third parties may offer different degrees of support. </p>
-</subsection>
-
-<a name="providers"/>
-<subsection name="Are there ISPs that will host my Struts application?">
-<p>For a listing of some Java and Struts Action Framework ISPs, visit the <a href="http://struts.sf.net/community/index.html">Struts Community Resources</a> area on SourceForge.</p>
-</subsection>
-
-<a name="ide"/>
-<subsection name="Is there a particularly good IDE to use with Struts Action Framework">
-<p>
-Struts should work well with any development environment that you would like to use, as well as with any programmers editor.
-The members of the Struts development team each use their own tools such as
-<a href="http://www.gnu.org/software/emacs/emacs.html">Emacs</a>,
-<a href="http://www.intellij.com/idea/">IDEA</a>,
-<a href="http://www.eclipse.org/">Eclipse</a>,
-and <a href="http://www.netbeans.org/">NetBeans</a>.
-</p>
-<p>
-See the <a href="../faqs/index.html">Howto Guides</a> for more about configuring IDEs to work with Struts.
-</p>
-</subsection>
-
-<a name="digest"/>
-<subsection name="Is there a digest for the User list?">
-<p>
-Yes. <a href="mailto:user-digest-subscribe@struts.apache.org">send a blank message</a> to &lt; <a href="mailto:user-digest-subscribe@struts.apache.org">user-digest-subscribe@struts.apache.org</a>&gt;.
-</p>
-<p>
-If you are subscribed to the digest, you can also post to the list.
-Just be sure to send your post to the
-<a href="mailto:user@struts.apache.org">user list</a> rather than trying to reply to the digest.
-</p>
-</subsection>
-
-<a name="newsgroup"/>
-<subsection name="Is there an Apache Struts newsgroup?">
-<p>
-Not a usenet group, but the Struts User list can be accessed with your
-favorite newsgroup reader from the
-<a href="http://news.gmane.org/">GMane News Site</a>.  Subscribe to groups
-<code>gmane.comp.jakarta.struts.devel</code> for the developer list, or
-<code>gmane.comp.jakarta.struts.user</code> for the user list.
-</p>
-</subsection>
-
-<a name="mailbounce"/>
-<subsection name="Why didn't my posting show up on the user list?">
-<p>
-You must be subscribed to the <a href="mailto:user-subscribe@struts.apache.org">user list</a>
-or <a href="mailto:user-digest-subscribe@struts.apache.org">user digest</a> before posting
-(or use the <a href="http://news.gmane.org">GMane Newsgroups</a> instead).
-</p>
-</subsection>
-
-<a name="unsubscribe"/>
-<subsection name="How do I unsubscribe from the mailing list?">
-<p>
-<strong>From the email account used to subscribe to the list,</strong> <a href="mailto:user-unsubscribe@struts.apache.org">send a blank message</a> to &lt; <a href="mailto:user-unsubscribe@struts.apache.org">user-unsubscribe@struts.apache.org</a>&gt;.
-</p>
-<p>
-If you are receiving the digest, you must send a blank email to
-&lt;<a href="mailto:user-digest-unsubscribe@struts.apache.org">user-unsubscribe@struts.apache.org</a>&gt;
-instead.
-</p>
-</subsection>
-
-</section>
-
-    <section>
-       <p class="right">
-	<strong>Next:</strong> <a href="helping.html">How to Help FAQ</a>
-       </p>
-    </section>
+<document>
+    <properties>
+        <title>Kickstart FAQ</title>
+    </properties>
+    <body>
+        <a name="faq"/>
+        <section name="Kickstart FAQ">
+
+            <a name="contents"/>
+            <subsection name="Index">
+
+                <p>
+                    Here are answers to the some of the usual Apache Struts
+                    getting-started questions.
+                </p>
+                <ul>
+                    <li>
+                        <a href="#shale">Why are you offering both Struts
+                            Shale and Struts Action Framework? Don't they
+                            compete for new development?</a>
+                    </li>
+                    <li>
+                        <a href="#2x">Is Shale likely to become Struts
+                            2.x?</a>
+                    </li>
+                    <li>
+                        <a href="#fork">Is Struts Shale a fork?</a>
+                    </li>
+                    <li>
+                        <a href="#struts">If Shale is a new product, why is it
+                            called Struts?</a>
+                    </li>
+                    <li>
+                        <a href="#ti">What about Ti? What about WebWork?</a>
+                    </li>
+                    <li>
+                        <a href="#ti2">Does Ti mean there will be three
+                            frameworks?</a>
+                    </li>
+                    <li>
+                        <a href="#overdrive">What about OverDrive or Struts
+                            Nexus?</a>
+                    </li>
+                    <li>
+                        <a href="#classic">What's the difference between
+                            Struts Action Framework and Struts Classic</a>
+                    </li>
+                </ul>
+                <ul>
+                    <li>
+                        <a href="#struts">Why is the project called
+                            Struts?</a>
+                    </li>
+                    <li>
+                        <a href="#license">How is Apache Struts licensed?</a>
+                    </li>
+                    <li>
+                        <a href="#usage">Can Apache Struts be used in a
+                            commercial application?</a>
+                    </li>
+                    <li>
+                        <a href="#credits">Do I have to credit Apache Struts
+                            on my own website?</a>
+                    </li>
+                </ul>
+                <ul>
+                    <li>
+                        <a href="#requests">If a product doesn't do what I
+                            want, can I request that a feature be added?</a>
+                    </li>
+                    <li>
+                        <a href="#help">Where can I get help with Apache
+                            Struts?</a>
+                    </li>
+                    <li>
+                        <a href="#support">Is commercial support available for
+                            Apache Struts?</a>
+                    </li>
+                    <li>
+                        <a href="#providers">Are there ISPs that will host my
+                            Apache Struts application?</a>
+                    </li>
+                    <li>
+                        <a href="#ide">Is there a particularly good IDE to use
+                            with Struts Action Framework?</a>
+                    </li>
+                </ul>
+                <ul>
+                    <li>
+                        <a href="#digest">Is there a digest for the Apache
+                            Struts User list?</a>
+                    </li>
+                    <li>
+                        <a href="#newsgroup">Is there a Apache Struts
+                            Newsgroup?</a>
+                    </li>
+                    <li>
+                        <a href="#mailbounce">Why didn't my posting show up on
+                            the user list?"</a>
+                    </li>
+                    <li>
+                        <a href="#unsubscribe">How do I unsubscribe from the
+                            mailing list?</a>
+                    </li>
+                </ul>
+
+                <p>
+                    For other FAQs, see the documentation for each subproject.
+                </p>
+
+            </subsection>
+
+            <a name="shale"/>
+            <subsection
+                    name="Why are you offering both Struts Shale and Struts Action Framework? Don't they compete for new development?">
+                <p>We do offer Apache Struts developers a choice, but, hey,
+                    choice is good. :)</p>
+                <p>People who want to create and maintain the
+                    <a href="announce.html#a20051214.4">Struts Action
+                        Framework</a>
+                    are welcome to do so.
+                </p>
+                <p>People who want to create and maintain the
+                    <a href="announce.html#a20051214.2">Struts Shale
+                        Framework</a>
+                    are equally welcome.
+                </p>
+                <p>As a volunteer organization, we are not constrained by the
+                    economics of competition. All we need are volunteers who
+                    are ready, willing, and able to do the work. So long as we
+                    have volunteers, we have work for them to do.</p>
+                <p>Right now, we have volunteers who want to leverage the new
+                    JavaServer Faces framework by using Struts Shale for new
+                    development. We also have volunteers who prefer to
+                    leverage their existing investment in Struts Action
+                    Framework. All are welcome.</p>
+                <p>For more about volunteering, visit our
+                    <a href="http://struts.apache.org/faqs/helping.html">how
+                        to help page</a>
+                    .
+                </p>
+            </subsection>
+
+            <a name="fork"/>
+            <subsection name="Is Struts Shale a fork?">
+                <p>No. It's an entirely new product with its own architecture.
+                    Struts Shale is an MVC framework for web applications,
+                    like Struts Action Framework, but it's a fresh start.
+                    Struts Shale is the best choice for developers eager to
+                    leverage the latest technologies, like JavaServer
+                    Faces.</p>
+                <p>Both frameworks will have a home here so long as there are
+                    volunteers ready to contribute.</p>
+                <p>We encourage you to choose the framework that works best
+                    for you. (Even if it is not one of ours!)</p>
+            </subsection>
+
+            <a name="struts"/>
+            <subsection
+                    name="If Shale is a new product, why is it called Struts?">
+                <p>
+                    Apache Struts embraces standards, and JavaServer Faces
+                    (JSF) is a new standard.
+                    JSF is not the first standard that Struts has assimilated
+                    (and, undoubtedly, it will not be the last).
+                </p>
+                <p>
+                    For example, many of the original Struts taglibs overlap
+                    with the JavaServer Pages Standard Tag Library (JSTL).
+                    Some of us want to continue using the original tags.
+                    Others want to be able to use JSTL as much as possible.
+                    As a result, David Karr created the Struts EL taglibs.
+                    The Struts EL subproject provides JSTL versions of only
+                    the Struts tags that do not overlap with JSTL.
+                    Meanwhile, the original taglibs are available and
+                    maintained for those that choose to use them.
+                </p>
+                <p>
+                    Likewise, some of us want to use JSF as much as possible.
+                    Others want to continue using the original Action
+                    framework.
+                    As a result, Craig McClanahan created the Struts Shale
+                    framework.
+                    Shale provides the same utility as the Action framework by
+                    building on the JSF feature set.
+                    Since Shale does for JSF what Action does for JSP, we
+                    consider Shale to be another Struts framework.
+                </p>
+            </subsection>
+
+            <a name="2x"/>
+            <subsection name="Is Shale likely to become Struts 2.x?">
+                <p>
+                    Struts Shale has its own identity and its own release
+                    cycle.
+                    Struts Action Framework is one subproject, and the Struts
+                    Shale framework is another.
+                    So, no, it is not likely that Struts Shale will become
+                    Struts Action 2.x.
+                </p>
+            </subsection>
+
+            <a name="ti"/>
+            <subsection name="What about Ti? What about WebWork?">
+                <p>
+                    <a href="http://wiki.apache.org/struts/StrutsTi">Struts
+                        Ti</a>
+                    (short for Titanium) is a proposal for a Struts Action
+                    Framework 2.x candidate.
+                    In late November 2005, the Ti proposal was amended to
+                    include a merger with
+                    <a href="http://www.opensymphony.com/webwork/">Open
+                        Symphony WebWork</a>
+                    .
+                    Under this plan, the next stable release of WebWork would
+                    be donated to Apache Struts,
+                    and the lead WebWork committers would join the Struts
+                    community.
+                </p>
+                <p>
+                    WebWork started as a
+                    <a href="http://incubator.apache.org/learn/rules-for-revolutionaries.html">
+                        Struts Revolution</a>
+                    .
+                    Over the years, it has evolved into a superb action-based
+                    framework that retains many Struts 1.x paradigms.
+                </p>
+                <p>
+                    People who have worked with both Struts 1.x and WebWork
+                    2.x tend to agree that it is a logical candidate for
+                    Struts Action Framework 2.x.
+                    If you look the Struts Action 1.x roadmap and the WebWork
+                    2.x feature set,
+                    you'll see that WebWork has already does most of what we
+                    wanted Struts Action to do.
+                    If we finished the roadmap ourselves, Struts Action would
+                    end up as a WebWork workalike.
+                    Rather than reinvent the wheel,
+                    Ti has become a proposal to put the WebWork wheel back on
+                    the Struts axle.
+                </p>
+                <p>
+                    Of course, many of us have significant Struts Action 1.x
+                    applications in production.
+                    Being able to migrate both applications and developer
+                    skill sets is a telling point of the proposal.
+                    Both a migration layer and migration documentation are
+                    under active development.
+                </p>
+            </subsection>
+
+            <a name="ti2"/>
+            <subsection name="Does Ti mean there will be three frameworks?">
+                <p>
+                    Probably not.
+                    Like many projects, we start by giving proposed
+                    subprojects a codename.
+                    Sun's "Tiger" and Microsoft's "Vista" are two examples.
+                    "Ti" is a codename like "Tiger" and "Vista.
+                    If Struts Ti is accepted as Struts Action Framework 2.x,
+                    the codename would fall into disuse.
+                </p>
+            </subsection>
+
+            <a name="overdrive"/>
+            <subsection name="What about OverDrive or Struts Nexus?">
+                <p>
+                    <a href="http://wiki.apache.org/struts/StrutsOverDrive">
+                        OverDrive</a>
+                    is a working proposal to use a set of case-study
+                    applications
+                    to drive the design and creation of a business layer
+                    framework.
+                    The codename for the business layer framework under
+                    development is "Nexus".
+                    Like Action and Shale, the Nexus internals are based on
+                    the Chain of Responsibility pattern.
+                </p>
+                <p>
+                    OverDrive and Nexus do not complete with frameworks like
+                    Action and Shale.
+                    Nexus begins where these frameworks end.
+                    Nexus is the "rest of the stack".
+                </p>
+                <p>
+                    The codebase underlying the proposal is being coded in C#,
+                    but a version for Java is expected in due course.
+                </p>
+            </subsection>
+
+            <a name="action"/>
+            <subsection
+                    name="What's the difference between Struts Action Framework and Struts Classic?">
+                <p>For the Struts Action Framework 1.3.x series, we subdivided
+                    the monolithic Struts 1.2.x distribution into several
+                    discrete subprojects. Struts Classic is a codename for the
+                    work we needed to do to create and release the new
+                    subprojects.</p>
+                <p>For a time, we considered bundling those seven products
+                    together and calling the bundle "Struts Classic". Instead,
+                    we are bundling Struts Action Framework and any compatible
+                    projects into a distribution called "Struts Action
+                    Framework Library". This bundle includes the original
+                    "seven dwarfs" and new subprojects, like Struts
+                    Scripting.</p>
+            </subsection>
+
+            <a name="struts"/>
+            <subsection name="Why is the project called Struts?">
+                <p>It's a reference to struts in the architectural sense, a
+                    reminder of the nearly invisible pieces that hold up
+                    buildings, houses, and bridges.</p>
+            </subsection>
+
+            <a name="license"/>
+            <subsection name="How is Apache Struts licensed?">
+                <p>All Apache Struts products are copyrighted software
+                    available under the
+                    <a href="http://www.apache.org/licenses">Apache
+                        License</a>
+                    , a &quot;free-to-use, business-friendly license&quot;.
+                </p>
+            </subsection>
+
+            <a name="usage"/>
+            <subsection
+                    name="Can Apache Struts be used in a commercial product?">
+                <p>Yes. The only requirements you must meet are those listed
+                    in the
+                    <a href="http://www.apache.org/licenses">Apache
+                        License</a>
+                    .
+                </p>
+            </subsection>
+
+            <a name="credits"/>
+            <subsection
+                    name="Do I have to credit Apache Struts on my own website?">
+                <p>You need to credit Apache Struts if you
+                    <strong>redistribute your own framework</strong>
+                    based on our products
+                    for other people to use. (See the
+                    <a href="http://www.apache.org/LICENSE">Apache License</a>
+                    for details.)
+                    But you do
+                    <strong>not</strong>
+                    need to credit Apache Struts just because your web
+                    application utilizes one of our products.
+                    It's the same situation as using the Apache HTTPD server
+                    or Tomcat. Not required if its just running your web site.
+                    Required if you've used the source code to create your own
+                    server that you are redistributing to other people.
+                </p>
+            </subsection>
+
+            <a name="requests"/>
+            <subsection
+                    name="If a product doesn't do what I want, can I request that a feature be added?">
+                <p>
+                    First, it's important to remember that Apache Struts is an
+                    all-volunteer project.
+                    We don't charge anyone anything to use Apache Struts
+                    products.
+                    Committers and other developers work on Apache Struts
+                    products because they need to use it with their own
+                    applications.
+                    If others can use it too, that's "icing on the cake".
+                    If you
+                    <a href="../helping.html">submit a patch</a>
+                    for a feature that a Committer finds useful, then that
+                    Committer may choose to volunteer his or her time to apply
+                    the patch.
+                    If you just submit an idea without a patch, it is much
+                    less likely to be added (since first someone else has to
+                    volunteer their time to write the patch).
+                </p>
+                <p>
+                    We are grateful for any patches, and we welcome new ideas,
+                    but the best way to see that something gets added to the
+                    framework is to do as much of the work as you can, rather
+                    than rely on the "kindness of strangers". Worst case, you
+                    can apply the patch to your copy of Struts and still use
+                    the feature in your own application. (Which is what open
+                    source is ~really~ all about.)
+                </p>
+            </subsection>
+
+            <a name="help"/>
+            <subsection name="Where can I get help with Apache Struts?">
+                <p>Struts Action Framework comes complete with a
+                    <a href="../userGuide/index.html">Users Guide</a>
+                    to
+                    introduce people to the framework and its underlying
+                    technologies. Various components
+                    also have their own in-depth Developers Guide, to cover
+                    more advanced topics. Comprehensive
+                    <a href="../api/index.html">Javadocs</a>
+                    are included
+                    along with the
+                    <strong>full source code</strong>
+                    .
+                </p>
+                <p>
+                    The
+                    <a href="http://struts.apache.org/mail.html">Struts user
+                        mailing list</a>
+                    is also
+                    very active, and welcomes posts from new users. Before
+                    posting a new question, be
+                    sure to consult the
+                    <a href="http://struts.apache.org/mail.html#Archives">
+                        <strong>MAILING LIST ARCHIVE</strong>
+                    </a>
+                    and the very excellent
+                    <a href="http://www.catb.org/~esr/faqs/smart-questions.html">
+                        How To Ask Questions The Smart Way</a>
+                    by Eric Raymond. Please do be sure
+                    to
+                    <a href="http://expita.com/nomime.html">turn off HTML</a>
+                    in your
+                    email client before posting.
+                </p>
+            </subsection>
+
+            <a name="support"/>
+            <subsection name="Is commercial support available?">
+                <p>The Apache Software Foundation does not provide commercial
+                    support for any of our software products, including Apache
+                    Struts products.
+                    However, third parties may offer different degrees of
+                    support.</p>
+            </subsection>
+
+            <a name="providers"/>
+            <subsection
+                    name="Are there ISPs that will host my Struts application?">
+                <p>For a listing of some Java and Struts Action Framework
+                    ISPs, visit the
+                    <a href="http://struts.sf.net/community/index.html">Struts
+                        Community Resources</a>
+                    area on SourceForge.
+                </p>
+            </subsection>
+
+            <a name="ide"/>
+            <subsection
+                    name="Is there a particularly good IDE to use with Struts Action Framework">
+                <p>
+                    Struts should work well with any development environment
+                    that you would like to use, as well as with any
+                    programmers editor.
+                    The members of the Struts development team each use their
+                    own tools such as
+                    <a href="http://www.gnu.org/software/emacs/emacs.html">
+                        Emacs</a>
+                    ,
+                    <a href="http://www.intellij.com/idea/">IDEA</a>
+                    ,
+                    <a href="http://www.eclipse.org/">Eclipse</a>
+                    ,
+                    and
+                    <a href="http://www.netbeans.org/">NetBeans</a>
+                    .
+                </p>
+                <p>
+                    See the
+                    <a href="../faqs/index.html">Howto Guides</a>
+                    for more about configuring IDEs to work with Struts.
+                </p>
+            </subsection>
+
+            <a name="digest"/>
+            <subsection name="Is there a digest for the User list?">
+                <p>
+                    Yes.
+                    <a href="mailto:user-digest-subscribe@struts.apache.org">
+                        send a blank message</a>
+                    to &lt;
+                    <a href="mailto:user-digest-subscribe@struts.apache.org">
+                        user-digest-subscribe@struts.apache.org</a>
+                    &gt;.
+                </p>
+                <p>
+                    If you are subscribed to the digest, you can also post to
+                    the list.
+                    Just be sure to send your post to the
+                    <a href="mailto:user@struts.apache.org">user list</a>
+                    rather than trying to reply to the digest.
+                </p>
+            </subsection>
+
+            <a name="newsgroup"/>
+            <subsection name="Is there an Apache Struts newsgroup?">
+                <p>
+                    Not a usenet group, but the Struts User list can be
+                    accessed with your
+                    favorite newsgroup reader from the
+                    <a href="http://news.gmane.org/">GMane News Site</a>
+                    . Subscribe to groups
+                    <code>gmane.comp.jakarta.struts.devel</code>
+                    for the developer list, or
+                    <code>gmane.comp.jakarta.struts.user</code>
+                    for the user list.
+                </p>
+            </subsection>
+
+            <a name="mailbounce"/>
+            <subsection
+                    name="Why didn't my posting show up on the user list?">
+                <p>
+                    You must be subscribed to the
+                    <a href="mailto:user-subscribe@struts.apache.org">user
+                        list</a>
+                    or
+                    <a href="mailto:user-digest-subscribe@struts.apache.org">
+                        user digest</a>
+                    before posting
+                    (or use the
+                    <a href="http://news.gmane.org">GMane Newsgroups</a>
+                    instead).
+                </p>
+            </subsection>
+
+            <a name="unsubscribe"/>
+            <subsection name="How do I unsubscribe from the mailing list?">
+                <p>
+                    <strong>From the email account used to subscribe to the
+                        list,</strong>
+                    <a href="mailto:user-unsubscribe@struts.apache.org">send a
+                        blank message</a>
+                    to &lt;
+                    <a href="mailto:user-unsubscribe@struts.apache.org">
+                        user-unsubscribe@struts.apache.org</a>
+                    &gt;.
+                </p>
+                <p>
+                    If you are receiving the digest, you must send a blank
+                    email to
+                    &lt;
+                    <a href="mailto:user-digest-unsubscribe@struts.apache.org">
+                        user-unsubscribe@struts.apache.org</a>
+                    &gt;
+                    instead.
+                </p>
+            </subsection>
+
+        </section>
+
+        <section>
+            <p class="right">
+                <strong>Next:</strong>
+                <a href="helping.html">How to Help FAQ</a>
+            </p>
+        </section>
 
-</body></document>
+    </body>
+</document>

Modified: struts/site/trunk/xdocs/mail.xml
URL: http://svn.apache.org/viewcvs/struts/site/trunk/xdocs/mail.xml?rev=376838&r1=376837&r2=376838&view=diff
==============================================================================
--- struts/site/trunk/xdocs/mail.xml (original)
+++ struts/site/trunk/xdocs/mail.xml Fri Feb 10 12:58:33 2006
@@ -18,234 +18,388 @@
 -->
 <document>
 
-  <properties>
-    <title>Mailing List Guidelines</title>
-  </properties>
-
-<body>
-
-<section name="Mailing Lists - Guidelines">
-<a name="Guidelines"/>
-
-<p>
-    A mailing list is an electronic discussion forum that anyone can
-    subscribe to. When someone sends an email message to the mailing list,
-    a copy of that message is broadcast to everyone who is subscribed to
-    that mailing list. Mailing lists are the primary means of communication
-    for people working within the Apache Struts Project.
-</p>
-
-<subsection name="Mailing Lists - Guidelines">
-
-<p>
-    Mailing lists provide a simple and effective communication mechanism.
-    With potentially thousands of subscribers, there is a common set of
-    etiquette guidelines that you should observe. Please keep on reading.
-</p>
-
-<p>
-<strong>
-      Respect the mailing list type
-</strong>
-</p>
-
-<ul>
-    <li>
-    The "User" list is where you can send questions and comments about
-    configuration, setup, usage and other "user" types of questions.
-    </li>
-    <li>
-    The "Developer" (or "Dev") list is where you can send questions and
-    comments about the actual software source code and general
-    "development" types of questions.
-    </li>
-</ul>
-
-<p>Some questions are appropriate for posting on both the "user" and
-the "developer" lists. In this case, pick one and only one. Do not
-cross post.</p>
-
-<p>Asking a configuration question on the developers list is frowned
-upon because developers' time is as precious as yours. By contacting
-them directly instead of the user base you are abusing resources. In
-fact, it is unlikely that you will get a quicker answer, if at
-all.</p>
-
-<p>
-<strong>
-      Join the lists that are appropriate for your discussion.
-</strong><br />
-Please make sure that you are joining the list that is appropriate for the 
-topic or product that you would like to discuss. For example, 
-please do not join the Struts mailing list and ask questions about Tomcat. 
-Instead, you should join the Tomcat User list and ask your questions
-there. 
-</p>
-
-<p>
-<strong>
-    Ask smart questions.
-</strong><br />
-Every volunteer project obtains its strength from the people involved
-in it. You are welcome to join any of our mailing lists.  You can
-choose to lurk, or actively participate; it's up to you.  The level of
-community responsiveness to specific questions is generally directly
-proportional to the amount of effort you spend formulating your
-question. Eric Raymond and Rick Moen have even written an essay entitled <a
-href="http://www.catb.org/~esr/faqs/smart-questions.html">"<b>Asking
-Smart Questions</b>"</a> precisely on this topic.
-</p>
-
-<p>
-<strong>
-    Keep your email short and to the point.
-</strong><br />
-If your email is more than about a page of text, chances are that it
-won't get read by very many people. It is much better to try to pack a
-lot of informative information (see above about asking smart questions)
-into as small of an email as possible. If you are replying to a previous
-email, it is a good idea to only quote the parts that you are replying
-to and to remove the unnecessary bits. This makes it easier for people
-to follow a thread as well as making the email archives easier to search
-and read.
-</p>
-
-<p>
-<strong>
-    Do your best to ensure that you are not sending HTML or
-    "Stylelized" email to the list.
-</strong><br />
-If you are using Outlook or Outlook Express or Eudora, chances are that
-you are sending HTML email by default. There is usually a setting that
-will allow you to send "Plain Text" email. If you are using Microsoft
-products to send email, there are several bugs in the software that
-prevent you from turning off the sending of HTML email. Please read this
-<a href="./micromail.html">page</a> as well...
-</p>
-
-<p>
-<strong>
-    Do not cross post messages.
-</strong><br />
-In other words, pick a mailing list and send your messages to that mailing 
-list only. Do not send your messages to multiple mailing lists. The reason is 
-that people may be subscribed to one list and not to the other. Therefore, 
-some people will only see part of the conversation.
-</p>
-
-<p>
-<strong>Watch where you are sending email.</strong>.
-The majority of our mailing lists have set the Reply-To to go back to the
-list. That means that when you Reply to a message, it will go to the list
-and not to the original author directly. The reason is because it helps
-facilitate discussion on the list for everyone to benefit from. Be careful
-of this as sometimes you may intend to reply to a message directly to someone
-instead of the entire list.
-The appropriate contents of the Reply-To header is an age-old debate that
-should not be brought up on the mailing lists.  You can
-examine opposing points of view
-<a href="http://www.unicom.com/pw/reply-to-harmful.html">condemning</a> our convention and
-<a href="http://www.metasystema.org/essays/reply-to-useful.mhtml">condoning</a>
-it. Bringing this up for debate on a mailing list will add nothing
-new and is considered off-topic.
-</p>
-
-</subsection>
-
-<subsection name="Archives">
-<p>Archives Carrying Struts Lists</p>
-<ul>
-<li><a href="http://mail-archives.apache.org/">ASF Mail Archives</a></li>
-<li>Mail-Archive</li>
-   <ul>
-      <li><a href="http://www.mail-archive.com/user%40struts.apache.org/">User list</a></li>
-      <li><a href="http://www.mail-archive.com/dev%40struts.apache.org/">Dev. list</a></li>
-   </ul>
-<li>Gmane</li>
-   <ul>
-      <li><a href="http://news.gmane.org/gmane.comp.jakarta.struts.user/">User List</a></li>
-      <li><a href="http://news.gmane.org/gmane.comp.jakarta.struts.devel/">Dev. List</a></li>
-   </ul>
-<li>Mailing list ARChives</li>
-   <ul>
-      <li><a href="http://marc.theaimsgroup.com/?l=struts-user&amp;r=1&amp;w=2">User List</a></li>
-      <li><a href="http://marc.theaimsgroup.com/?l=struts-dev&amp;r=1&amp;w=2">Dev. List</a></li>
-   </ul>
-<li><a href="http://www.servlets.com/archive/servlet/SummarizeList?listName=struts-user">Servlets.com servlet and JSP list archives</a></li>
-</ul>
-</subsection>
-
-<subsection name="Subscribing">
-<p>
-Now that you've read the guidelines (you <em>have</em> read the rest of the page, haven't you?), please subscribe to
-whichever Struts lists are of interest. 
-</p>
-
-    <ul>
-        
-    <li>
-      <strong>STRUTS-ANNOUNCEMENTS Mailing List</strong> - Subscribe to this list
-      to receiving only major announcements regarding Struts. This is a low-volume, 
-      read-only list.<br />
-      [<a href="mailto:announcements-subscribe@struts.apache.org">Subscribe</a>]<br />
-      [<a href="mailto:announcements-unsubscribe@struts.apache.org">Unsubscribe</a>]
-    </li>
-      
-    <li>
-      <strong>STRUTS-USER Mailing List</strong> - Subscribe to this list
-      to communicate with other developers that are using
-      Struts for their own applications, including questions about the
-      installation of Struts, and the usage of particular Struts features.<br />
-      [<a href="mailto:user-subscribe@struts.apache.org">Subscribe</a>]<br />
-      [<a href="mailto:user-unsubscribe@struts.apache.org">Unsubscribe</a>]
-    </li>
-      
-    <li>
-      <strong>STRUTS-DEV Mailing List</strong> - Subscribe to this mailing 
-      list to communicate with other developers interested in expanding and 
-      improving the functionality supported by Struts itself.<br />
-      [<a href="mailto:dev-subscribe@struts.apache.org">Subscribe</a>]<br />
-      [<a href="mailto:dev-unsubscribe@struts.apache.org">Unsubscribe</a>]
-    </li>
-    
-    <li>
-      <strong>STRUTS-USER Digest</strong> - Subscribe to this list to receive 
-      a daily digest of the Struts USER list.<br />
-      [<a href="mailto:user-digest-subscribe@struts.apache.org">Subscribe</a>]<br />
-      [<a href="mailto:user-digest-unsubscribe@struts.apache.org">Unsubscribe</a>]<br />
-      If you subscribe to the Digest, you can also post to the User list. 
-      (Just don't quote the entire Digest mailing in a reply!)
-    </li>
-    
-    <li>
-      <strong>STRUTS-USER Newsgroup</strong> - The User list is also mirrored online,
-      so that you can participate <strong>without</strong> subscribing to the regular mailing
-      list.<br />
-      [<a href="http://struts_user.roomity.com">Struts User on Roomity</a>]<br />
-      This is another way to post to the User list without subscribing to the 
-      regular list. <br/>
-      </li>
-    </ul>
-
-    <p>
-        Please note that the Struts User list enjoys a "casual friday" policy.
-        More off-topic  messages are tolerated on Fridays so long as the
-        message is prefixed with the token [FRIDAY].
-        If you'd rather not be troubled by these postings, please set your
-        mail filter accordingly.
-        Posting [FRIDAY] articles on any other weekday is <strong>strongly
-        discouraged</strong>.
-        We thank you for your cooperation.
-    </p>
-
-</subsection>
-</section>
-
-<section>
-    <p class="right">
-      <strong>Next:</strong> <a href="volunteers.html">Who we are</a>
-    </p>
-</section>
+    <properties>
+        <title>Mailing List Guidelines</title>
+    </properties>
+
+    <body>
+
+        <section name="Mailing Lists - Guidelines">
+            <a name="Guidelines"/>
+
+            <p>
+                A mailing list is an electronic discussion forum that anyone
+                can
+                subscribe to. When someone sends an email message to the
+                mailing list,
+                a copy of that message is broadcast to everyone who is
+                subscribed to
+                that mailing list. Mailing lists are the primary means of
+                communication
+                for people working within the Apache Struts Project.
+            </p>
+
+            <subsection name="Mailing Lists - Guidelines">
+
+                <p>
+                    Mailing lists provide a simple and effective communication
+                    mechanism.
+                    With potentially thousands of subscribers, there is a
+                    common set of
+                    etiquette guidelines that you should observe. Please keep
+                    on reading.
+                </p>
+
+                <p>
+                    <strong>
+                        Respect the mailing list type
+                    </strong>
+                </p>
+
+                <ul>
+                    <li>
+                        The "User" list is where you can send questions and
+                        comments about
+                        configuration, setup, usage and other "user" types of
+                        questions.
+                    </li>
+                    <li>
+                        The "Developer" (or "Dev") list is where you can send
+                        questions and
+                        comments about the actual software source code and
+                        general
+                        "development" types of questions.
+                    </li>
+                </ul>
+
+                <p>Some questions are appropriate for posting on both the
+                    "user" and
+                    the "developer" lists. In this case, pick one and only
+                    one. Do not
+                    cross post.</p>
+
+                <p>Asking a configuration question on the developers list is
+                    frowned
+                    upon because developers' time is as precious as yours. By
+                    contacting
+                    them directly instead of the user base you are abusing
+                    resources. In
+                    fact, it is unlikely that you will get a quicker answer,
+                    if at
+                    all.</p>
+
+                <p>
+                    <strong>
+                        Join the lists that are appropriate for your
+                        discussion.
+                    </strong>
+                    <br/>
+                    Please make sure that you are joining the list that is
+                    appropriate for the
+                    topic or product that you would like to discuss. For
+                    example,
+                    please do not join the Struts mailing list and ask
+                    questions about Tomcat.
+                    Instead, you should join the Tomcat User list and ask your
+                    questions
+                    there.
+                </p>
+
+                <p>
+                    <strong>
+                        Ask smart questions.
+                    </strong>
+                    <br/>
+                    Every volunteer project obtains its strength from the
+                    people involved
+                    in it. You are welcome to join any of our mailing lists.
+                    You can
+                    choose to lurk, or actively participate; it's up to you.
+                    The level of
+                    community responsiveness to specific questions is
+                    generally directly
+                    proportional to the amount of effort you spend formulating
+                    your
+                    question. Eric Raymond and Rick Moen have even written an
+                    essay entitled
+                    <a
+                            href="http://www.catb.org/~esr/faqs/smart-questions.html">
+                        "
+                        <b>Asking
+                            Smart Questions</b>
+                        "
+                    </a>
+                    precisely on this topic.
+                </p>
+
+                <p>
+                    <strong>
+                        Keep your email short and to the point.
+                    </strong>
+                    <br/>
+                    If your email is more than about a page of text, chances
+                    are that it
+                    won't get read by very many people. It is much better to
+                    try to pack a
+                    lot of informative information (see above about asking
+                    smart questions)
+                    into as small of an email as possible. If you are replying
+                    to a previous
+                    email, it is a good idea to only quote the parts that you
+                    are replying
+                    to and to remove the unnecessary bits. This makes it
+                    easier for people
+                    to follow a thread as well as making the email archives
+                    easier to search
+                    and read.
+                </p>
+
+                <p>
+                    <strong>
+                        Do your best to ensure that you are not sending HTML
+                        or
+                        "Stylelized" email to the list.
+                    </strong>
+                    <br/>
+                    If you are using Outlook or Outlook Express or Eudora,
+                    chances are that
+                    you are sending HTML email by default. There is usually a
+                    setting that
+                    will allow you to send "Plain Text" email. If you are
+                    using Microsoft
+                    products to send email, there are several bugs in the
+                    software that
+                    prevent you from turning off the sending of HTML email.
+                    Please read this
+                    <a href="./micromail.html">page</a>
+                    as well...
+                </p>
+
+                <p>
+                    <strong>
+                        Do not cross post messages.
+                    </strong>
+                    <br/>
+                    In other words, pick a mailing list and send your messages
+                    to that mailing
+                    list only. Do not send your messages to multiple mailing
+                    lists. The reason is
+                    that people may be subscribed to one list and not to the
+                    other. Therefore,
+                    some people will only see part of the conversation.
+                </p>
+
+                <p>
+                    <strong>Watch where you are sending email.</strong>
+                    .
+                    The majority of our mailing lists have set the Reply-To to
+                    go back to the
+                    list. That means that when you Reply to a message, it will
+                    go to the list
+                    and not to the original author directly. The reason is
+                    because it helps
+                    facilitate discussion on the list for everyone to benefit
+                    from. Be careful
+                    of this as sometimes you may intend to reply to a message
+                    directly to someone
+                    instead of the entire list.
+                    The appropriate contents of the Reply-To header is an
+                    age-old debate that
+                    should not be brought up on the mailing lists. You can
+                    examine opposing points of view
+                    <a href="http://www.unicom.com/pw/reply-to-harmful.html">
+                        condemning</a>
+                    our convention and
+                    <a href="http://www.metasystema.org/essays/reply-to-useful.mhtml">
+                        condoning</a>
+                    it. Bringing this up for debate on a mailing list will add
+                    nothing
+                    new and is considered off-topic.
+                </p>
+
+            </subsection>
+
+            <subsection name="Archives">
+                <p>Archives Carrying Struts Lists</p>
+                <ul>
+                    <li>
+                        <a href="http://mail-archives.apache.org/">ASF Mail
+                            Archives</a>
+                    </li>
+                    <li>Mail-Archive</li>
+                    <ul>
+                        <li>
+                            <a href="http://www.mail-archive.com/user%40struts.apache.org/">
+                                User list</a>
+                        </li>
+                        <li>
+                            <a href="http://www.mail-archive.com/dev%40struts.apache.org/">
+                                Dev. list</a>
+                        </li>
+                    </ul>
+                    <li>Gmane</li>
+                    <ul>
+                        <li>
+                            <a href="http://news.gmane.org/gmane.comp.jakarta.struts.user/">
+                                User List</a>
+                        </li>
+                        <li>
+                            <a href="http://news.gmane.org/gmane.comp.jakarta.struts.devel/">
+                                Dev. List</a>
+                        </li>
+                    </ul>
+                    <li>Mailing list ARChives</li>
+                    <ul>
+                        <li>
+                            <a href="http://marc.theaimsgroup.com/?l=struts-user&amp;r=1&amp;w=2">
+                                User List</a>
+                        </li>
+                        <li>
+                            <a href="http://marc.theaimsgroup.com/?l=struts-dev&amp;r=1&amp;w=2">
+                                Dev. List</a>
+                        </li>
+                    </ul>
+                    <li>
+                        <a href="http://www.servlets.com/archive/servlet/SummarizeList?listName=struts-user">
+                            Servlets.com servlet and JSP list archives</a>
+                    </li>
+                </ul>
+            </subsection>
+
+            <subsection name="Subscribing">
+                <p>
+                    Now that you've read the guidelines (you
+                    <em>have</em>
+                    read the rest of the page, haven't you?), please subscribe
+                    to
+                    whichever Struts lists are of interest.
+                </p>
+
+                <ul>
+
+                    <li>
+                        <strong>STRUTS-ANNOUNCEMENTS Mailing List</strong>
+                        - Subscribe to this list
+                        to receiving only major announcements regarding
+                        Struts. This is a low-volume,
+                        read-only list.
+                        <br/>
+                        [
+                        <a href="mailto:announcements-subscribe@struts.apache.org">
+                            Subscribe</a>
+                        ]
+                        <br/>
+                        [
+                        <a href="mailto:announcements-unsubscribe@struts.apache.org">
+                            Unsubscribe</a>
+                        ]
+                    </li>
+
+                    <li>
+                        <strong>STRUTS-USER Mailing List</strong>
+                        - Subscribe to this list
+                        to communicate with other developers that are using
+                        Struts for their own applications, including questions
+                        about the
+                        installation of Struts, and the usage of particular
+                        Struts features.
+                        <br/>
+                        [
+                        <a href="mailto:user-subscribe@struts.apache.org">
+                            Subscribe</a>
+                        ]
+                        <br/>
+                        [
+                        <a href="mailto:user-unsubscribe@struts.apache.org">
+                            Unsubscribe</a>
+                        ]
+                    </li>
+
+                    <li>
+                        <strong>STRUTS-DEV Mailing List</strong>
+                        - Subscribe to this mailing
+                        list to communicate with other developers interested
+                        in expanding and
+                        improving the functionality supported by Struts
+                        itself.
+                        <br/>
+                        [
+                        <a href="mailto:dev-subscribe@struts.apache.org">
+                            Subscribe</a>
+                        ]
+                        <br/>
+                        [
+                        <a href="mailto:dev-unsubscribe@struts.apache.org">
+                            Unsubscribe</a>
+                        ]
+                    </li>
+
+                    <li>
+                        <strong>STRUTS-USER Digest</strong>
+                        - Subscribe to this list to receive
+                        a daily digest of the Struts USER list.
+                        <br/>
+                        [
+                        <a href="mailto:user-digest-subscribe@struts.apache.org">
+                            Subscribe</a>
+                        ]
+                        <br/>
+                        [
+                        <a href="mailto:user-digest-unsubscribe@struts.apache.org">
+                            Unsubscribe</a>
+                        ]
+                        <br/>
+                        If you subscribe to the Digest, you can also post to
+                        the User list.
+                        (Just don't quote the entire Digest mailing in a
+                        reply!)
+                    </li>
+
+                    <li>
+                        <strong>STRUTS-USER Newsgroup</strong>
+                        - The User list is also mirrored online,
+                        so that you can participate
+                        <strong>without</strong>
+                        subscribing to the regular mailing
+                        list.
+                        <br/>
+                        [
+                        <a href="http://struts_user.roomity.com">Struts User
+                            on Roomity</a>
+                        ]
+                        <br/>
+                        This is another way to post to the User list without
+                        subscribing to the
+                        regular list.
+                        <br/>
+                    </li>
+                </ul>
+
+                <p>
+                    Please note that the Struts User list enjoys a "casual
+                    friday" policy.
+                    More off-topic messages are tolerated on Fridays so long
+                    as the
+                    message is prefixed with the token [FRIDAY].
+                    If you'd rather not be troubled by these postings, please
+                    set your
+                    mail filter accordingly.
+                    Posting [FRIDAY] articles on any other weekday is
+                    <strong>strongly
+                        discouraged</strong>
+                    .
+                    We thank you for your cooperation.
+                </p>
+
+            </subsection>
+        </section>
+
+        <section>
+            <p class="right">
+                <strong>Next:</strong>
+                <a href="volunteers.html">Who we are</a>
+            </p>
+        </section>
 
-</body>
+    </body>
 </document>

Modified: struts/site/trunk/xdocs/navigation.xml
URL: http://svn.apache.org/viewcvs/struts/site/trunk/xdocs/navigation.xml?rev=376838&r1=376837&r2=376838&view=diff
==============================================================================
--- struts/site/trunk/xdocs/navigation.xml (original)
+++ struts/site/trunk/xdocs/navigation.xml Fri Feb 10 12:58:33 2006
@@ -1,193 +1,194 @@
 <?xml version="1.0" encoding="ISO-8859-1"?>
 <project name="Struts Site">
-<title>Apache Struts Project</title>
-  <body>
-    <menu name="Apache Struts Project">
-        <item 
-            name="Welcome"
-            href="index.html"
-            />
-        <item
-            name="Announcements"
-            href="announce.html"
-            />
-        <item
-           name="FAQs"
-            href="faqs.html"
-            />
-        <item
-            name="Who We Are"
-            href="volunteers.html"
-            />
-    </menu>
-
-    <menu name="Community">
-        <item
-            name="Mailing Lists"            
-            href="mail.html"
-            />
-        <item
-            name="Resource Directory"
-            href="http://wiki.apache.org/struts/StrutsResources"
-            />
-        <item
-            name="Wiki Pages"
-            href="http://wiki.apache.org/struts"
-            />
-        <item
-            name="Issue Tracker (Bugzilla)"
-            href="http://issues.apache.org/bugzilla"
-            />
-    </menu>
-
-    <menu name="Download">
-        <item
-            name="Binaries"                
-            href="downloads.html"
-            />
-        <item 
-            name="Source Code"             
-            href="downloads.html#Source_Code"
-            />
-        <item
-            name="Development Releases"
-            href="http://svn.apache.org/dist/struts/"
-            />
-    </menu>
-
-    <menu name="Frameworks">
-        <item name="Action Framework" href="/struts-action/index.html"/>
-        <item name="Shale Framework" href="/struts-shale/index.html" />
-    </menu>
- 
-    <menu name="Extensions">
-        <item name="EL" href="/struts-el/index.html"/>
-        <item name="Extras" href="/struts-extras/index.html"/>
-        <item name="Flow" href="/struts-flow/index.html"/>
-        <item name="JSF Integration" href="/struts-faces/index.html"/>
-        <item name="JSP Taglib" href="/struts-taglib/index.html"/>
-        <item name="Scripting" href="/struts-scripting/index.html"/>
-        <item name="Tiles" href="/struts-tiles/index.html"/>
-        <item name="Other Extensions" href="http://wiki.apache.org/struts/StrutsExtensions"/>
-    </menu>
-
-    <menu name="Subprojects">
-        <item name="Applications" href="/struts-apps/index.html"/>
-        <item name="Sandbox" href="/struts-sandbox/index.html"/>
-    </menu>
-
-    <menu name="Development">
-        <item
-            name="Charter"
-            href="bylaws.html"
-            />
-        <item
-            name="Release Guidelines"
-            href="releases.html"
-            />
-        <item
-            name="Javadoc Index"
-            href="javadoc.html"
-            />
-        <item
-            name="Source Repository"
-            href="http://svn.apache.org/viewcvs.cgi/struts/"
-            />
-        <item
-            name="Issue Tracker (Bugzilla)"
-            href="http://issues.apache.org/bugzilla"
-            />
-     </menu>
-    
-     <menu name="Site Archive">    
-            <item
-                name="Struts 1.2.x"
-                href="http://struts.apache.org/struts-doc-1.2.x/index.html"
-                />
-            <item
-                name="Struts 1.2.8"
-                href="http://struts.apache.org//struts-doc-1.2.8/index.html"
-                />
-            <item
-                name="Struts 1.2.7"
-                href="http://struts.apache.org//struts-doc-1.2.7/index.html"
-                />
-            <item
-                name="Struts 1.2.4"
-                href="http://struts.apache.org//struts-doc-1.2.4/index.html"
-                />
-            <item
-                name="Struts 1.1"
-                href="http://struts.apache.org//struts-doc-1.1/index.html"
-                />
-            <item
-                name="Struts 1.0.2"
-                href="http://struts.apache.org//struts-doc-1.0.2/index.html"
-                />
-      </menu>
-
-     <menu name="Related Projects">    
-            <item
-                name="Apache Beehive"
-                href="http://beehive.apache.org/"
-                />
-            <item
-                name="Apache Bookstore"
-                href="http://apachebookstore.com/"
-                />
-            <item
-                name="Jakarta Commons"
-                href="http://jakarta.apache.org/commons/"
-                />
-            <item
-                name="Apache MyFaces"
-                href="http://myfaces.apache.org/"
-                />
-            <item
-                name="Struts SourceForge"
-                href="http://struts.sourceforge.net/"
-                />
-            <item
-                name="Apache Tomcat"
-                href="http://tomcat.apache.org/"
-                />
-            <item
-                name="Struts University"
-                href="http://opensource2.atlassian.com/confluence/oss/display/STRUTS/Home"
-                />
-            <item
-                name="Velocity Struts"
-                href="http://jakarta.apache.org/velocity/tools/struts/"
-                />
-     </menu>
-
-     <menu name="Similar Projects">    
-            <item
-                name="Apache Cocoon"
-                href="http://cocoon.apache.org/"
-                />
-            <item
-                name="AppFuse"
-                href="http://appfuse.dev.java.net/"
-                />
-            <item
-                name="Jakarta Tapestry"
-                href="http://jakarta.apache.org/tapestry/"
-                />
-            <item
-                name="Jakarta Turbine"
-                href="http://jakarta.apache.org/turbine/"
-                />
-            <item
-                name="OS WebWork"
-                href="http://www.opensymphony.com/webwork/"
-                />
-            <item
-                name="Spring MVC"
-                href="http://www.springframework.org/docs/reference/mvc.html"
-                />
-     </menu>
+    <title>Apache Struts Project</title>
+    <body>
+        <menu name="Apache Struts Project">
+            <item
+                    name="Welcome"
+                    href="index.html"
+                    />
+            <item
+                    name="Announcements"
+                    href="announce.html"
+                    />
+            <item
+                    name="FAQs"
+                    href="faqs.html"
+                    />
+            <item
+                    name="Who We Are"
+                    href="volunteers.html"
+                    />
+        </menu>
+
+        <menu name="Community">
+            <item
+                    name="Mailing Lists"
+                    href="mail.html"
+                    />
+            <item
+                    name="Resource Directory"
+                    href="http://wiki.apache.org/struts/StrutsResources"
+                    />
+            <item
+                    name="Wiki Pages"
+                    href="http://wiki.apache.org/struts"
+                    />
+            <item
+                    name="Issue Tracker (Bugzilla)"
+                    href="http://issues.apache.org/bugzilla"
+                    />
+        </menu>
+
+        <menu name="Download">
+            <item
+                    name="Binaries"
+                    href="downloads.html"
+                    />
+            <item
+                    name="Source Code"
+                    href="downloads.html#Source_Code"
+                    />
+            <item
+                    name="Development Releases"
+                    href="http://svn.apache.org/dist/struts/"
+                    />
+        </menu>
+
+        <menu name="Frameworks">
+            <item name="Action Framework" href="/struts-action/index.html"/>
+            <item name="Shale Framework" href="/struts-shale/index.html"/>
+        </menu>
+
+        <menu name="Extensions">
+            <item name="EL" href="/struts-el/index.html"/>
+            <item name="Extras" href="/struts-extras/index.html"/>
+            <item name="Flow" href="/struts-flow/index.html"/>
+            <item name="JSF Integration" href="/struts-faces/index.html"/>
+            <item name="JSP Taglib" href="/struts-taglib/index.html"/>
+            <item name="Scripting" href="/struts-scripting/index.html"/>
+            <item name="Tiles" href="/struts-tiles/index.html"/>
+            <item name="Other Extensions"
+                  href="http://wiki.apache.org/struts/StrutsExtensions"/>
+        </menu>
+
+        <menu name="Subprojects">
+            <item name="Applications" href="/struts-apps/index.html"/>
+            <item name="Sandbox" href="/struts-sandbox/index.html"/>
+        </menu>
+
+        <menu name="Development">
+            <item
+                    name="Charter"
+                    href="bylaws.html"
+                    />
+            <item
+                    name="Release Guidelines"
+                    href="releases.html"
+                    />
+            <item
+                    name="Javadoc Index"
+                    href="javadoc.html"
+                    />
+            <item
+                    name="Source Repository"
+                    href="http://svn.apache.org/viewcvs.cgi/struts/"
+                    />
+            <item
+                    name="Issue Tracker (Bugzilla)"
+                    href="http://issues.apache.org/bugzilla"
+                    />
+        </menu>
+
+        <menu name="Site Archive">
+            <item
+                    name="Struts 1.2.x"
+                    href="http://struts.apache.org/struts-doc-1.2.x/index.html"
+                    />
+            <item
+                    name="Struts 1.2.8"
+                    href="http://struts.apache.org//struts-doc-1.2.8/index.html"
+                    />
+            <item
+                    name="Struts 1.2.7"
+                    href="http://struts.apache.org//struts-doc-1.2.7/index.html"
+                    />
+            <item
+                    name="Struts 1.2.4"
+                    href="http://struts.apache.org//struts-doc-1.2.4/index.html"
+                    />
+            <item
+                    name="Struts 1.1"
+                    href="http://struts.apache.org//struts-doc-1.1/index.html"
+                    />
+            <item
+                    name="Struts 1.0.2"
+                    href="http://struts.apache.org//struts-doc-1.0.2/index.html"
+                    />
+        </menu>
+
+        <menu name="Related Projects">
+            <item
+                    name="Apache Beehive"
+                    href="http://beehive.apache.org/"
+                    />
+            <item
+                    name="Apache Bookstore"
+                    href="http://apachebookstore.com/"
+                    />
+            <item
+                    name="Jakarta Commons"
+                    href="http://jakarta.apache.org/commons/"
+                    />
+            <item
+                    name="Apache MyFaces"
+                    href="http://myfaces.apache.org/"
+                    />
+            <item
+                    name="Struts SourceForge"
+                    href="http://struts.sourceforge.net/"
+                    />
+            <item
+                    name="Apache Tomcat"
+                    href="http://tomcat.apache.org/"
+                    />
+            <item
+                    name="Struts University"
+                    href="http://opensource2.atlassian.com/confluence/oss/display/STRUTS/Home"
+                    />
+            <item
+                    name="Velocity Struts"
+                    href="http://jakarta.apache.org/velocity/tools/struts/"
+                    />
+        </menu>
+
+        <menu name="Similar Projects">
+            <item
+                    name="Apache Cocoon"
+                    href="http://cocoon.apache.org/"
+                    />
+            <item
+                    name="AppFuse"
+                    href="http://appfuse.dev.java.net/"
+                    />
+            <item
+                    name="Jakarta Tapestry"
+                    href="http://jakarta.apache.org/tapestry/"
+                    />
+            <item
+                    name="Jakarta Turbine"
+                    href="http://jakarta.apache.org/turbine/"
+                    />
+            <item
+                    name="OS WebWork"
+                    href="http://www.opensymphony.com/webwork/"
+                    />
+            <item
+                    name="Spring MVC"
+                    href="http://www.springframework.org/docs/reference/mvc.html"
+                    />
+        </menu>
 
 
-  </body>
+    </body>
 </project>



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Mime
View raw message