Hi all, Just an FYI that this server is down while we perform some maintenance.
Sincerely, Michael Peters Indiana State Library MIS | Inspire.IN.gov Helpdesk | Evergreen Indiana Helpdesk office - 317.234.2128 email - [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Lebbeous Fogle-Weekley Sent: Wednesday, May 30, 2012 2:14 PM To: [email protected] Subject: Re: [OPEN-ILS-DEV] Evergreen ILS 2.2 (RC1) Community TestServerInformation Hi David, [This is my rapid fire-attempt to parse the documentation contribution guidelines. Anybody stepping in to correct me where I'm wrong would be appreciated.] According to the process outlined here http://open-ils.org/dokuwiki/doku.php?id=adding_documentation , I think you can just email the open-ils-documentation mailing list and CC Roni Shwaish and June Rayner as the Administration/Development Content Coordinators. I don't know whether they might have questions for you about licensing or not. If you want to try to go for a technical/direct route just try sharing a git branch based on Evergreen master with your documentation in AsciiDoc format somewhere appropriate under the docs/ directory, and open a Launchpad bug about it. Thanks, Lebbeous On 05/30/2012 01:25 PM, David Busby wrote: > Lebbeous, > You can feel free to copy any Evergreen content from Edoceo; those > are my "brain dump" style notes and some times are not fit for human > consumption. I've got write access to the Wiki but don't know where I > should place content - pointers? Also, didn't I hear about docs > getting into Evergreen master? I can make a branch in my fork and > pushrequest that bad-boy - but where to start? Basically, how do I > "git" folks to "DIG" it? ;) > -- Lebbeous Fogle-Weekley | Software Developer | Equinox Software, Inc. / Your Library's Guide to Open Source | phone: 1-877-OPEN-ILS (673-6457) | email: [email protected] | web: http://www.esilibrary.com
