Quoting Adrian Custer <[EMAIL PROTECTED]>: > On Fri, 2005-10-07 at 14:59 -0700, Jody Garnett wrote: > > So how about it, would the user list like to lead a documentation charge > :-) > > Jody > > > Are the geotools developers willing to ensure that documentation and > tutorials have staying power?
In a word, yes. But we need to mark down which APIs are stable. I want to run through the library making everthing stable, consistent, and scalable. Depending on the package we sometimes only get one out of three. We also have to know our limitations, part of why geotools is a social success is the habit of using tools (not people) to maintain quality. Hense the first thing I am looking for is a way to make sure the code used for learning, is actually compiled *all* the time. If we cannot figure out how to get code snipits from svn into confluence (I have seen it done from svn) we will have to cut & paste and contain a disclaimer/link to the origional (saying the origional is always authoritive). Jody ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
