And so I did. Thanks, Robert, for the suggestion. I hope the Evergreen project proposal is accepted.
Aleksey On Oct 24, 2012, at 11:27 , Soulliere, Robert wrote: > Hi, Aleksey, > > I already submitted the project proposal last weekend with a full 5 member > team. However, the Doc Sprint Summit allows for individuals to also apply to > attend. The deadline is Oct. 26. I strongly encourage you to apply as an > individual. > > I encourage others in the Evergreen documentation community to apply as well. > Individuals will be added to selected projects at the summit. I am not sure > how individuals are added to each project though (draft, lottery, etc...). > Also note that there is the possibility that our project is not selected but > individuals are accepted. I am not sure about the odds of a proposal being > accepted or how many proposals have been submitted. > > Here is the registration form URL: > https://sites.google.com/site/docsprintsummitv2/home/registration-form > > Thanks, > Robert > > Robert Soulliere, BA (Hons), MLIS > Digital Systems Librarian > Mohawk College Library > robert.soulli...@mohawkcollege.ca > Telephone: 905 575 1212 x3936 > Fax: 905 575 2011 > > ________________________________________ > From: open-ils-documentation-boun...@list.georgialibraries.org > [open-ils-documentation-boun...@list.georgialibraries.org] On Behalf Of > Lazar, Alexey Vladimirovich [alexey.la...@mnsu.edu] > Sent: October 24, 2012 10:10 AM > To: Documentation discussion for Evergreen software > Subject: Re: [OPEN-ILS-DOCUMENTATION] Fwd: [Announce] Call for Proposals for > Doc Sprint Summit v2.0 > > Well, in that case and if it's not too late, is there room for one more? As a > relatively new person to Evergreen, I think many of the questions I've had to > answer to get going are still fresh in my mind. I've also been working with > libraries interested in Evergreen and talking to our current libraries, so I > know some of their perspectives and concerns. Also, I have some sysadmin > documentation written - at this point for our local needs, but I am planning > to submit it to the community and perhaps it could be of some use for this > project as well. > > Thanks. > Aleksey > > On Oct 22, 2012, at 08:15 , Soulliere, Robert wrote: > >> Lori is exactly correct about the main audience and purpose for the getting >> started guide as far as I see it. It seems we get quite a few questions from >> people about how to get started with implementing Evergreen, or if Evergreen >> is right for them in the fist place. It would be great to be able to provide >> them with a concise guide to help them answer these questions and plan for a >> migration to Evergreen with a few walk-throughs of the basic steps to >> installation and configuration to help get them off the ground. >> >> Robert >> >> Robert Soulliere, BA (Hons), MLIS >> Digital Systems Librarian >> Mohawk College Library >> robert.soulli...@mohawkcollege.ca >> Telephone: 905 575 1212 x3936 >> Fax: 905 575 2011 >> >> ________________________________________ >> From: open-ils-documentation-boun...@list.georgialibraries.org >> [open-ils-documentation-boun...@list.georgialibraries.org] On Behalf Of Lori >> Bowen Ayre [lori.a...@galecia.com] >> Sent: October 20, 2012 1:31 PM >> To: Documentation discussion for Evergreen software >> Subject: Re: [OPEN-ILS-DOCUMENTATION] Fwd: [Announce] Call for Proposals for >> Doc Sprint Summit v2.0 >> >> My belief is that there are some libraries out there that would consider >> moving to Evergreen on their own if there was just a bit more documentation >> for them to rely upon, especially to get started. >> >> So, the target audience is the library with a sharp SysAdmin type person who >> is thinking about Evergreen but who doesn't have a ton of time to spend >> figuring out how to get started. But if he or she could get started more >> easily, would quickly learn that Evergreen is a very viable alternative for >> their library and will eventually take the ball and run with it at their >> organization. Meaning they will set up a demo for their libraries to show >> them what can be done with Evergreen and start talking to them about options >> for migrating off their system to Evergreen (going it along, contracting >> with someone, etc). >> >> Lori >> >> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-= >> Lori Bowen Ayre // >> Library Technology Consultant / The Galecia Group >> Oversight Board & Communications Committee / Evergreen >> (707) 763-6869 // lori.a...@galecia.com<mailto:lori.a...@galecia.com> >> Availability: http://doodle.com/loriayre >> >> <mailto:lori.a...@galecia.com>Specializing in open source ILS solutions, >> RFID, filtering, >> workflow optimization, and materials handling >> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= >> >> >> >> On Fri, Oct 19, 2012 at 11:56 AM, Lazar, Alexey Vladimirovich >> <alexey.la...@mnsu.edu<mailto:alexey.la...@mnsu.edu>> wrote: >> >> On Oct 18, 2012, at 15:17 , Dan Scott wrote: >> >>> In that vein, Robert's suggestion for a getting started guide would be >>> an appropriately-sized standalone project that would also be able to be >>> integrated into our existing documentation after the fact. I think that >>> would have particular value if there was also a focus on the "Getting >>> started with a production system" section; in the IRC channel we've >>> noted that there are all kinds of knobs to tweak and tune that new sites >>> trip over. It would be a real win to come away with a book that closes >>> that gap. >> >> Who would be the target audience for this guide? >> >> Alexey Lazar >> PALS >> Information System Developer and Integrator >> 507-389-2907<tel:507-389-2907> >> http://www.mnpals.org/ >> >> _______________________________________________ >> OPEN-ILS-DOCUMENTATION mailing list >> OPEN-ILS-DOCUMENTATION@list.georgialibraries.org<mailto:OPEN-ILS-DOCUMENTATION@list.georgialibraries.org> >> http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation >> >> >> 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 >> OPEN-ILS-DOCUMENTATION@list.georgialibraries.org >> http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation > > > Alexey Lazar > PALS > Information System Developer and Integrator > 507-389-2907 > http://www.mnpals.org/ > > _______________________________________________ > OPEN-ILS-DOCUMENTATION mailing list > OPEN-ILS-DOCUMENTATION@list.georgialibraries.org > http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation > > 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 > OPEN-ILS-DOCUMENTATION@list.georgialibraries.org > http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation Alexey Lazar PALS Information System Developer and Integrator 507-389-2907 http://www.mnpals.org/ _______________________________________________ OPEN-ILS-DOCUMENTATION mailing list OPEN-ILS-DOCUMENTATION@list.georgialibraries.org http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation
