The best approach is to submit patches to the Turbine-2 Documentation module in Scarab. Issues that are raised in Scarab are reported to this list so that the committers are aware of them and can act upon them.
Cheers, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au > From: "Chris K Chew" <[EMAIL PROTECTED]> > Reply-To: "Turbine Developers List" <[EMAIL PROTECTED]> > Date: Tue, 12 Nov 2002 15:52:03 -0700 > To: <[EMAIL PROTECTED]> > Subject: Suggestions For The 2.x Documentation Initiative > > Hello. > > Over on the Turbine User's list we have tentatively decided to create a FAQ, > Tutorial, User's Guide, and Developer's Guide for Turbine 2.x. I have a > small site containing the work-in-progress of what will become the outline > for the docs at http://www.fenetics.com/turbine/index.html. > > These outlines will need to be turned into xdocs, filled in with content, > and injected into the existing site documentation. I am happy to act as the > xdoc compiler/arranger for the initiative, but I need to know what you want > me to do with it once created. I figure I will either send somebody the > updates, or you may offer me a committer's account so that I don't have to > bother anybody. > > Also, if anybody feels they can do a better job, or the initiative is going > in the wrong direction, I encourage them to speak up. > > Thanks for the help, > > Chris > > > -- > To unsubscribe, e-mail: <mailto:turbine-dev-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: <mailto:turbine-dev-help@;jakarta.apache.org> > -- To unsubscribe, e-mail: <mailto:turbine-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:turbine-dev-help@;jakarta.apache.org>
