Hi folks.  By my estimate, the last time we had a true documentation push was 
prior to the release of 2.0.0, about three years ago.  I think it may be time 
to do another one.

I was reminded of this recently as I found a tutorial page [1] that mentioned 
how the www/ directory would allow you to serve even "a full installation of 
MapBuilder".  MapBuilder, if I'm not mistaken, was retired in 2008.  :)

A trivial example, mind you, but there are still screenshots from the 1.7.x 
series [2], documentation on extensions that no longer exist [3], and other 
small bummers that come from a general lack of curation.

With this in mind, is there any interest in a documentation sprint, possibly 
hosted in the OpenGeo (NYC) office?  The goal would be to clean up, update, 
curate, reorganize, fill gaps, and perform other tasks that aren't covered by 
our day-to-day operation.

We've come a long way, and I think we should be proud of what we have.  That 
said, I think we can still strive for improvement.  Spending a little bit of 
time directly addressing our documentation will pay dividends over the long 
term, and make what we have easier to maintain.

Interested?  Thoughts?


[1] http://docs.geoserver.org/2.2.0/user/tutorials/staticfiles.html
[2] http://docs.geoserver.org/2.2.0/user/googleearth/tutorials/time/time.html
[3] http://docs.geoserver.org/2.2.0/user/extensions/styler.html

  
Thanks,
Mike Pumphrey
OpenGeo - http://opengeo.org


------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to