Mike Pumphrey wrote: > I don't think the idea was abandoned, but I also don't think it was adopted > as dogma.
While I agree that it is very good to have an overall coordinator and editor (maintainer) for docs, I believe that module maintainers should take principal responsibility for providing the documentation for their particular components. We cannot expect Mike to be in a position to provide technical content for modules with which he may not be familiar, nor to provide the content. I encourage Mike to exercise editorial and subeditorial control over the documentation as a whole, and respect his authority to edit, move, or remove any content that is unacceptable to him. For global cross-module content, we should indeed defer to Mike on the content, but I think module-specific detail can be delegated. As a user, I would rather have rough documentation in the manual than no documentation for a component. It may be useful to have a pending manual for features for components that have never been in a release, and users cannot access. Once a component has been released, the documentation should be released as well. This should be a precondition of release. Trunk, by definition, is a work in progress. Kind regards, -- Ben Caradoc-Davies <[email protected]> Software Engineer, CSIRO Exploration and Mining Australian Resources Research Centre 26 Dick Perry Ave, Kensington WA 6151, Australia ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
