I second the thoughts about not reinventing the wheel, and "it'll get done faster if we help out".
Another positive would be raising the profile of Evergreen within the larger open source community. Finally, even if a larger open source community style guide isn't done for awhile, it doesn't stop us from doing our initial content audits, and developing a plan of attack. While not ideal, we could start writing, and then edit to the style guide later. Cheers, Tara On Tue, Jun 16, 2009 at 12:54 AM, Karen Schneider <[email protected]>wrote: > See idea below -- comments to this list (Paul and I will consolidate) > or to http://writingopensource.com -- > > cheers, > > -- > -- > | 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 >
_______________________________________________ OPEN-ILS-DOCUMENTATION mailing list [email protected] http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation
