See comments below. > And currently when you update documentation, you could have > 2 or 3 branchs to updates (TC 3.2, 3.3, 4.0). > > But there is many common areas (realms, connectors) and > we should avoid such duplication effort... > > What about starting a jakarta-tomcat-doc sub-project, where > some redactors could have commit access, maybe even without > commit access to developpers projects like tomcat, j-t-c, jasper... > > A quick proposal of tree could be : > > jakarta-tomcat-doc + +- jserv > | | > +- connectors -+- jk > | | > | +- webapp > | > +- jasper (3.2/3.3) > | > +- realms (JDBC/JNDI/LDAP) > | > +- tomcat 3.x > | > +- tomcat 4.x > I would like to have another suggestion. The jakarta-tomcat-doc repository should only contains a complete handbook for various tomcat servers (3.2, 3.3 & 4.0). The handbook should covers sections like Installation, System Adminstration, Webapp development and Performance Tuning. (uh, I copy it from FreeBSD handbook). Also, a separate developer handbook can be written as needed. For specifications and technical notes (for example WARP spec), because it documents the developer mind and serves as an effective commuication for developers, I still suggest leaving them in the original repository. For how-tos (JDBC/Realms, connectors), I think we just have to compile an index for it. Just my 2 cents. Punky
