husted 2002/10/17 05:00:48
Modified: doc helping.xml project.xml volunteers.xml
Added: doc status.xml
Log:
Add development roadmap (status.xml) so Steve has something to patch :0)
Add "How my company can help" FAQ.
Revision Changes Path
1.2 +23 -0 jakarta-struts/doc/helping.xml
Index: helping.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/helping.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- helping.xml 12 Oct 2002 16:51:26 -0000 1.1
+++ helping.xml 17 Oct 2002 12:00:47 -0000 1.2
@@ -10,12 +10,35 @@
<section href="contents" name="How to Help FAQ">
<ul>
+ <li><a href="#corp">What can my company do to help support Struts?</a></li>
<li><a href="#bugs">How can I report bugs or make feature requests?</a></li>
<li><a href="#contribute">How can I contribute to Struts source code?</a></li>
<li><a href="#documentation">How can I contribute to the documentation?</a></li>
<li><a href="#release">So when is the next release coming out?</a></li>
<li><a href="#release_help">How can I help the next release along?</a></li>
</ul>
+</section>
+
+
+<section href="corp" name="What can my company do to help support Struts?">
+<p>Struts is an all volunteer product. Our customers are the volunteers who donate
+their time and energy to supporting the product. If you want to support Struts, and
+become one of our customers, then you need to
+<a href="http://jakarta.apache.org/site/getinvolved.html";>get involved</a> and
become a volunteer.</p>
+<p>Our challenge to any team using Struts is to donate the time of one team member
one
+afternoon a week (or more if you can spare the resources). Have your team member
browse Bugzilla for any
+issues without a <a href="#code">patch</a> or <a href="#tests">unit test</a>, and
add the patch or test.
+If the patch is written on company time, and you want to give your company an
author's credit, that's
+fine with us. </p>
+<p>If Struts doesn't do what <i>you</i> want, it's up to <b>you</b> to step up and
propose the patch.
+If Struts doesn't ship as often as you would like, it's up to you to step up with
the tests and fixes that
+get a release out the door. </p>
+<p>If Struts does do what you want, help others become involved by turning your war
stories into FAQs and
+how-tos that we can make part of the <a ahref="documentation">documentation</a>.
The mailing list is very
+active and trundling through the archives is no picnic. We can always use people
who can reduce the best
+threads to coherent articles that we can put in the User Guide.</p>
+<p>We don't sell Struts for money, but anyone who wants to be our customer can pay
us back by donating
+the time and energy that money represents.</p>
</section>
<section href="bugs" name="How can I report bugs or make feature requests?">
1.27 +3 -4 jakarta-struts/doc/project.xml
Index: project.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/project.xml,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- project.xml 12 Oct 2002 16:51:26 -0000 1.26
+++ project.xml 17 Oct 2002 12:00:47 -0000 1.27
@@ -12,6 +12,7 @@
<item name="Resources" href="resources/index.html"/>
<item name="Who We Are" href="volunteers.html"/>
<item name="How to Help" href="helping.html"/>
+ <item name="List Archive"
href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=42"/>
</menu>
<menu name="Downloads">
@@ -49,10 +50,8 @@
href="userGuide/release-notes.html"/>
<item name="Installation"
href="userGuide/installation.html"/>
- <item name="Workflow Proposal"
- href="proposals/workflow.html"/>
- <item name="Wish List"
- href="proposals/todo-1.1.html"/>
+ <item name="Development Roadmap"
+ href="status.html"/>
</menu>
</project>
1.12 +1 -1 jakarta-struts/doc/volunteers.xml
Index: volunteers.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/volunteers.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- volunteers.xml 12 Oct 2002 16:51:26 -0000 1.11
+++ volunteers.xml 17 Oct 2002 12:00:47 -0000 1.12
@@ -91,7 +91,7 @@
<li><b>Arron Bates</b> (arron at apache.org)</li>
<li><b>James Holmes</b> (jholmes at apache.org)</li>
<li><b>David M. Karr</b> (dmkarr at apache.org)</li>
-
+<li><b>Eddie Bush</b> (ekbush at apache.org)</li>
</ul>
</section>
1.1 jakarta-struts/doc/status.xml
Index: status.xml
===================================================================
<?xml version="1.0"?>
<document url="./status.xml">
<properties>
<author>Craig R. McClanahan</author>
<title>The Struts User's Guide - Development Roadmap</title>
</properties>
<body>
<chapter href="status" name="Development Roadmap">
<section href="status" name="Development Roadmap">
<p><font size="-2">$Id: status.xml,v 1.1 2002/10/17 12:00:47 husted Exp $</font></p>
<p>
This document outlines some of changes we expect to
see in future releases of Struts.
</p>
<p>
This document is provided for discussion purposes only.
All releases and changes to the codebase are subject to
<a href="http://jakarta.apache.org/site/decisions.html";>a vote</a> of the
<a href="volunteers.html#committers">Struts Committers</a>.
</p>
</section>
<section href="struts_1_1" name="Struts 1.1">
<p>
Struts 1.1 provides a number of functional enhancements, including
support for application modules. Other enhancments include
action-based authentification, declarative exception
handling, Plug-In Actions, and a pluggable request processor.
Several extensions are now bundled with the Struts distribution,
including the Nested taglib, Tiles, and the Commons Validator.
Backward-compatiblity with Struts 1.0.x is a primary goal.
</p>
<p>
Remaining tasks:
</p>
<ul>
<li>Refactor Tiles to be 1.1 compliant</li>
<li>Other routine changes per
<a
href="http://issues.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=Struts&version=Unknown&version=1.0.1+Final&version=1.0+Final&version=1.0+Beta+3&version=1.0+Beta+2&version=1.0+Beta+1&version=0.5+Final&version=1.0.2+Final&version=1.1+Beta+1&version=1.1+Beta+2&version=Nightly+Build&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&order=Bug+Number";>Bugzilla</a>
and <a href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=41";>Dev
list</a></li>
</ul>
</section>
<section href="struts_1_2" name="Struts 1.2.x">
<p>
Struts 1.2.x will include additional functional enhancements
along the same lines as Struts 1.1. The platform requirements
will remain the same (Servlet 2.2 / JSP 1.1). The
release will focus on refactoring of existing functionality,
with a continued emphasis on backwards compatibility.
</p>
<p>
The Struts 1.2.x series is expected to incorporate several
incremental releases (in contrast to Stuts 1.1).
</p>
</section>
<section href="struts_2_0" name="Struts 2.0.x">
<p>
Struts 2.0.x will include broader enhancements.
The implementation will expect a minimum platform of
Servlet 2.3 / JSP 1.2 and refactorings may include
the use of Filters. It is expected that Struts 2.0.x
will rely on JSTL and JavaServer Faces as supporting
technologies.
</p>
</section>
<section href="proposals" name="Relevant Proposals">
<ul>
<li><a href="proposals/release-plan-1.1b2.html">Release Plan 1.1-b2</a></li>
<li><a href="proposals/workflow.html">Workflow Proposal</a></li>
</ul>
</section>
</chapter></body></document>
--
To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>
