Hi All, During the DIG meeting Dan proposed that the DIG could suggest to the Evergreen community that any new contracted feature development should include docs to be submitted to the DIG as part of the development. I wonder if we could discuss this here and broaden the topic a bit to see if it is possible to get documentation on new features into the official documentation more quickly?
I would like to offer an open-ended question: Is there anything that DIG can do to help get documentation on new features into official documentation as they are developed so all organizations can get the information they need to learn about and use the new features when the install or upgrade Evergreen? It would seem that these new features would have something written somewhere -- even rough notes? Is there an economic or contractual reason why these cannot be shared with the general Evergreen community at an earlier stage by either the developers of the features, users of the new features or trainers for the new features? Robert Robert Soulliere, BA (Hons), MLIS Systems Librarian Mohawk College Library [email protected] Telephone: 905 575 1212 x3936 Fax: 905 575 2011 This E-mail contains privileged and confidential information intended only for the individual or entity named in the message. If the reader of this message is not the intended recipient, or the agent responsible to deliver it to the intended recipient, you are hereby notified that any review, dissemination, distribution or copying of this communication is prohibited. If this communication was received in error, please notify the sender by reply E-mail immediately, and delete and destroy the original message. _______________________________________________ OPEN-ILS-DOCUMENTATION mailing list [email protected] http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation
