I have some ideas spinning out the docs discussion of on the user list; and after accosting andrea on the IRC channel have been told to "socialise" them.
Basically: - we would like to publish docs for stable 2.6 - we would like to publish docs for 2.7 - and we can "end" the experimental spike/web/sphinx (it is an experiment of an experiment!) - I really like the source code being *live* for documentation - the wiki is dead (it is a wiki so it is out of date; codehaus security hoops scare off any contributors ...) So what does that look like? That is basically my question ... here is an idea. http://svn.osgeo.org/geotools/web/ <-- contents of the existing sphinx folder minus the docs http://svn.osgeo.org/geotools/trunk/doc <--- welcome docs; gradually growing into user guide http://svn.osgeo.org/geotools/branches/2.6.x/doc <-- welcome docs from stable branch A couple comments: - I kind of thought we should convert the developers guide first (since it is more of a static document) - however it is a static document so there is no motivation - I would like to have a modules/shapefile/doc containing the current "module matrix" page (I was thinking we could collect these with svn:externals - but apparently that is a bad idea for GIT clients) And questions: - How/where do we publish javadocs? - We could publish sphinx docs as PDF given a bit of effort; website is better for search engines however ------------------------------------------------------------------------------ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
