I definitely intend to use the docs that are already there. In fact I'm expecting that most of these are written, but I don't want to ask that question until I have a ToC.
What I'm intending to do is to organize the scattered docs into a centralized manual so that people don't have to search as much for information. Plus I can then throw an editor at it and have a PDF version for printing. Hen On 12/2/05, Phil Steitz <[EMAIL PROTECTED]> wrote: > I am +1 (in the sense of will help :-) for anything involving > improving docs. My one request would be that we start with the docs > that already exist and target the main commons web site to house this > stuff, rather than creating ever more scattered and incomplete Wiki > pages. The following items are already covered on the commons and > apache/dev pages: > > * Subversion information. How to check code out. > * Maven information. How to build. > * Site information. How to generate the site. How to upload your changes. > * Releasing. How to release. > > If the existing pages are not complete or clear enough, then we should > start by updating them. > > Phil > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]