> From: "Chris K Chew" <[EMAIL PROTECTED]> Much of what you are suggesting in this post is already covered by the documentation that is produced by maven. > > *How To Build Turbine From Source Turbine uses maven and thus the build process has been standardised across all turbine projects. A specific document for turbine-2 does not currently exist, but we could easily create something based on the Torque document: http://jakarta.apache.org/turbine/torque/developer-guide.html > > *How To Submit Bugs http://jakarta.apache.org/turbine/turbine-2/project-info.html > > *How To Request Features http://jakarta.apache.org/turbine/turbine-2/project-info.html > > *Source Xreference http://jakarta.apache.org/turbine/turbine-2/xref/index.html > > *How To Submit Patches http://jakarta.apache.org/turbine/turbine-2/project-info.html > > *ToDo List This is an existing document that can be patched like any other: http://jakarta.apache.org/turbine/turbine-2/todo.html IMHO it would be best if all items on the ToDo list had Scarab issue identifiers associated with them (i.e. what needs to be done is recorded in Scarab but selected items of significance are echoed on the ToDo list). > > *Contributors http://jakarta.apache.org/turbine/turbine-2/team-list.html
See also: http://jakarta.apache.org/turbine/common/documentation.html I have also noticed that the "Development Process" links under "Project Documentation" are currently broken. I will look into this. Cheers, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au -- To unsubscribe, e-mail: <mailto:turbine-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:turbine-user-help@;jakarta.apache.org>
