As per discussion I did up a proposal with the plan. http://docs.codehaus.org/display/GEOTOOLS/Sphinx+Documentation+Process
-Justin On 10-05-25 5:28 PM, Jody Garnett wrote: > Comments inline; but yes we all agree about the direction. Where we are stuck > is on some of the details. > > On 26/05/2010, at 9:12 AM, Justin Deoliveira wrote: > >> doc/ >> user/ >> devel/ >> web/ > > Agreed. > > trunk/web would be the current website > trunk/devel would be the current developers guide > 2.6.x/user would be the current "stable" users guide > >> 1. Integrate the doc generation into the maven build. > > Sounds fine; the maven hacking is proving a bit tough these days. I have been > unable to build a clean > checkout of trunk on one of my machines due to the cycle involved in build > javadoc. > >> 2. Update the assembly process to create -doc artifacts for the user and >> developer guides. These artifacts would be mostly for release purposes. > > Yep. > >> 3. Add the doc generation to the opengeo hudson build server. This would >> give us continuous builds on docs. On each build we could upload the >> resulting docs to the osgeo box (or wherever we decide to host them). >> >> Thoughts and opinions welcome. I can write up a proposal if need be but >> want to get some initial feedback first. > > I think a very short proposal would be good; no more detail then what has > been provided in email thus far. > -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. ------------------------------------------------------------------------------ _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
