> > EG documentation project might have a similar structure, with a steering > committee deciding on the general project road map, the executive (with > a rotating membership if necessary) being responsible for a single > release (or chunk) of documentation and the technical team doing > implementation, testing and releasing different formats of the > documentation. >
That seems like a productive model that could be a good fit for EG. Apropos of this, the Fedora documentation group meets every week by irc, same time. I wouldn't skimp on the "project road map" -- actually figuring out a working production model (format, tools, etc.) will be key for long-term sustainability. -- -- | Karen G. Schneider | Community Librarian | Equinox Software Inc. "The Evergreen Experts" | Toll-free: 1.877.Open.ILS (1.877.673.6457) x712 | [email protected] | Web: http://www.esilibrary.com | Be a part of the Evergreen International Conference, May 20-22, 2009! | http://www.lyrasis.org/evergreen
_______________________________________________ OPEN-ILS-DOCUMENTATION mailing list [email protected] http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation
