Galen,<div><br></div><div>We have prepared four or five blocks of text we plan to paste in so it really depends on how much people want to talk about the site. But I think 15 minutes is probably sufficient.</div><div><br>
</div><div>Lori<br clear="all"><div><div><br></div><div>=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=</div><div><div>Lori Bowen Ayre // </div><div>Library Technology Consultant / The Galecia Group</div><div>Oversight Board & Communications Committee / Evergreen</div>
<div>(707) 763-6869 // <a href="mailto:Lori.Ayre@galecia.com" target="_blank">Lori.Ayre@galecia.com</a></div><div>Availability: <a href="http://tungle.me/lori.ayre" target="_blank">http://<span style="font-family:Verdana,Arial,sans-serif;line-height:20px;background-color:rgb(255,255,255)">tungle.me/lori.ayre</span></a><span> </span></div>
<div><br></div><div><a href="mailto:Lori.Ayre@galecia.com" target="_blank"></a>Specializing in open source ILS solutions, RFID, filtering, </div><div>workflow optimization, and materials handling <br><div>=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=</div>
</div></div></div><br>
<br><br><div class="gmail_quote">On Fri, Sep 14, 2012 at 6:56 AM, Galen Charlton <span dir="ltr"><<a href="mailto:gmc@esilibrary.com" target="_blank">gmc@esilibrary.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi folks,<br>
<br>
There's quite a lot on the overall agenda for the community meeting,<br>
so we'll need to stick to some time limits. Do you feel 15 minutes is<br>
sufficient for your presentation and allowing time for initial<br>
commentary.<br>
<br>
Regards,<br>
<br>
Galen<br>
<div class="HOEnZb"><div class="h5"><br>
On Thu, Sep 13, 2012 at 5:47 PM, Lori Bowen Ayre <<a href="mailto:lori.ayre@galecia.com">lori.ayre@galecia.com</a>> wrote:<br>
> Alexey,<br>
><br>
> This is mostly great! I do find the last part about the Phase 1 tasks,<br>
> features and pages confusing. You say:<br>
><br>
> Following is an approximate list of tasks, features and pages for the Phase<br>
> 1 rollout:<br>
> * Design: colors, graphics, typography, layout. What you see on the current<br>
> prototype is just a pre-canned template that ships with Drupal, not our<br>
> recommendation. Alexey Lazar agreed to be primary on that, will work closely<br>
> Jim Craner fro Drupal-specific needs.<br>
> * Features: news/blog, possibly the calendar and maybe site search.<br>
> * Content: main landing page, about, downloads, documentation (just top<br>
> level), FAQ, community/communicate/contribute.<br>
><br>
> Can I suggest we say instead:<br>
><br>
> For our Phase 1 rollout (hopefully in time for the conference), we are<br>
> shooting for having the following areas ready: :<br>
><br>
> * Design: colors, graphics, typography, layout. What you see on the current<br>
> prototype is just a pre-canned template that ships with Drupal, not our<br>
> recommendation. Alexey Lazar agreed to be primary on that, will work closely<br>
> Jim Craner fro Drupal-specific needs.<br>
> * Content: all the basic landing pages and any sub-pages that have content<br>
> already written on the current site. In other words, no new content.<br>
> * Features: news/blog aggregator, possibly the calendar, site search.<br>
><br>
><br>
><br>
> On Thu, Sep 13, 2012 at 2:11 PM, Lazar, Alexey Vladimirovich<br>
> <<a href="mailto:alexey.lazar@mnsu.edu">alexey.lazar@mnsu.edu</a>> wrote:<br>
>><br>
>> Web team and others, please review the draft for the web prototype report<br>
>> for the community meeting tomorrow. I added a couple of sections to Jim's<br>
>> draft:<br>
>><br>
>> For the past two years, members of the Evergreen Community Web Team have<br>
>> been working on planning for the future of the Evergreen website. We've<br>
>> conducted community surveys, analyzed the existing website's usage<br>
>> statistics, consulted with key community groups such as developers and<br>
>> oversight board members, and issued requests for feedback, comments, and<br>
>> volunteer assistance.<br>
>><br>
>> ---<br>
>> You can learn more about the work that we've done, as well as see the<br>
>> results of our surveys and documentation efforts, at the Evergreen Web Team<br>
>> page:<br>
>><br>
>> <a href="http://www.evergreen-ils.org/dokuwiki/doku.php?id=webteam" target="_blank">http://www.evergreen-ils.org/dokuwiki/doku.php?id=webteam</a><br>
>><br>
>> ---<br>
>> Most recently, we've been working on a prototype website, located at<br>
>> <a href="http://drupal.evergreen-ils.org/" target="_blank">http://drupal.evergreen-ils.org/</a>, which we'll use as a foundation for<br>
>> building the future Evergreen website. This prototype is based on the very<br>
>> popular Drupal content management system, chosen because of its broad<br>
>> feature set, widespread support, and existing Drupal skill set in the Web<br>
>> Team.<br>
>><br>
>> ---<br>
>> Right now, we're building a website that will help community members find<br>
>> the information they need easily. On the back end, we're building a system<br>
>> that will allow as many community members as possible to become active<br>
>> contributors and easily keep Evergreen info up-to-date. We're also<br>
>> exploring systems that will allow community members to communicate and<br>
>> collaborate with each other via the website.<br>
>><br>
>> ---<br>
>> In the past few months, we discussed some of the issues with the current<br>
>> Evergreen web presence, and how we might want to start addressing those<br>
>> issues with the new site. For example, we want to eliminate orphaned content<br>
>> and make sure that content is updated and maintained in a timely way. To<br>
>> help achieve that, we agreed to create the role of "Content Editor" to:<br>
>> * Actively seek out and/or add content for their sections<br>
>> * Assist folks who want to contribute<br>
>> * Keep an eye on any updates to their section and, as needed, improve any<br>
>> updates supplied by another contributor<br>
>> * Handle any periodic or time-sensitive updates (for example, the person<br>
>> or persons who edit the downloads section would be on point whenever a<br>
>> release is cut)<br>
>> (Galen, thanks for formulating the role)<br>
>><br>
>> We also agreed that any new features will be dependent on availability of<br>
>> volunteers to maintain those features.<br>
>><br>
>> ---<br>
>> Our next step is to firm up a roll-out date for the initial (we are<br>
>> calling it "Phase 1") release of the new site and recruit some volunteers to<br>
>> help with migrating content and other work. What we can deliver in the end<br>
>> will depend on how many volunteers we get and what we can reasonably<br>
>> accomplish within the time period. We think that it is feasible to populate<br>
>> the new site with content from the current site, review and update that<br>
>> content (with some exceptions) and have the new site go live in April of<br>
>> 2013.<br>
>><br>
>> ---<br>
>> Following is an approximate list of tasks, features and pages for the<br>
>> Phase 1 rollout:<br>
>> * Design: colors, graphics, typography, layout. What you see on the<br>
>> current prototype is just a pre-canned template that ships with Drupal, not<br>
>> our recommendation. Alexey Lazar agreed to be primary on that, will work<br>
>> closely Jim Craner fro Drupal-specific needs.<br>
>> * Features: news/blog, possibly the calendar and maybe site search.<br>
>> * Content: main landing page, about, downloads, documentation (just top<br>
>> level), FAQ, community/communicate/contribute.<br>
>><br>
>> ---<br>
>> We need your help! If you are currently responsible for maintaining any<br>
>> of the areas we want to tackle for Phase 1, or are new and want to get<br>
>> involved, or just have some wishes or ideas, use the Web Team mailing list<br>
>> to let us know how/where you would like to help:<br>
>><br>
>> <a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team</a><br>
>><br>
>> ---<br>
>> Questions? Thoughts? Suggestions? Concerns?<br>
>><br>
>> ---<br>
>><br>
>> Alexey<br>
>><br>
>><br>
>> On Sep 13, 2012, at 15:53 , Lori Bowen Ayre wrote:<br>
>><br>
>> > Thanks, Kathy! Will you be at the IRC meeting tomorrow?<br>
>> ><br>
>> > Also, if you (or any other Web Team folks!) get a chance to edit any of<br>
>> > the pages on <a href="http://drupal.evergreen-ils.org" target="_blank">drupal.evergreen-ils.org</a> with an explanation of what will go<br>
>> > there....that would be useful. I think it will help people understand where<br>
>> > we're are trying to go with the site.<br>
>> ><br>
>> > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=<br>
>> > Lori Bowen Ayre //<br>
>> > Library Technology Consultant / The Galecia Group<br>
>> > Oversight Board & Communications Committee / Evergreen<br>
>> > <a href="tel:%28707%29%20763-6869" value="+17077636869">(707) 763-6869</a> // <a href="mailto:Lori.Ayre@galecia.com">Lori.Ayre@galecia.com</a><br>
>> > Availability: <a href="http://tungle.me/lori.ayre" target="_blank">http://tungle.me/lori.ayre</a><br>
>> ><br>
>> > Specializing in open source ILS solutions, RFID, filtering,<br>
>> > workflow optimization, and materials handling<br>
>> > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=<br>
>> ><br>
>> ><br>
>> ><br>
>> > On Thu, Sep 13, 2012 at 12:09 PM, Kathy Lussier <<a href="mailto:klussier@masslnc.org">klussier@masslnc.org</a>><br>
>> > wrote:<br>
>> > Hi Jim,<br>
>> ><br>
>> > I'm not in on the meeting, but just wanted to mention you'll need to<br>
>> > correct the <a href="http://drupal.evergreen-ils.com" target="_blank">http://drupal.evergreen-ils.com</a> URL.<br>
>> ><br>
>> > Kathy<br>
>> > Kathy Lussier<br>
>> > Project Coordinator<br>
>> > Massachusetts Library Network Cooperative<br>
>> ><br>
>> > <a href="tel:%28508%29%20343-0128" value="+15083430128">(508) 343-0128</a><br>
>> > <a href="mailto:klussier@masslnc.org">klussier@masslnc.org</a><br>
>> ><br>
>> > Twitter:<br>
>> > <a href="http://www.twitter.com/kmlussier" target="_blank">http://www.twitter.com/kmlussier</a><br>
>> > On 9/13/2012 3:00 PM, Jim Craner wrote:<br>
>> >> For the past two years, members of the Evergreen Community Web Team<br>
>> >> have been working on planning for the future of the Evergreen website.<br>
>> >> We've conducted community surveys, analyzed the existing website's usage<br>
>> >> statistics, consulted with key community groups such as developers and<br>
>> >> oversight board members, and issued repeated requests for feedback,<br>
>> >> comments, and volunteer assistance.<br>
>> >> ---<br>
>> >> You can learn more about the work that we've done, as well as see the<br>
>> >> results of our surveys and documentation efforts, at the Evergreen Web Team<br>
>> >> page:<br>
>> >><br>
>> >> <a href="http://www.evergreen-ils.org/dokuwiki/doku.php?id=webteam" target="_blank">http://www.evergreen-ils.org/dokuwiki/doku.php?id=webteam</a><br>
>> >> ---<br>
>> >> Most recently, we've been working on a prototype website, located at<br>
>> >> <a href="http://drupal.evergreen-ils.com" target="_blank">http://drupal.evergreen-ils.com</a>, which we'll use as a foundation for<br>
>> >> building the future Evergreen website. This prototype is based on the very<br>
>> >> popular Drupal content management system, chosen because of its broad<br>
>> >> feature set, widespread support, and existing Drupal skill set in the Web<br>
>> >> Team.<br>
>> >> ---<br>
>> >> Right now, we're building a website that will help community members<br>
>> >> find the information they need easily. On the back end, we're building a<br>
>> >> system that will allow as many community members as possible to become<br>
>> >> active contributors and easily keep Evergreen info up-to-date. We're also<br>
>> >> exploring systems that will allow community members to communicate and<br>
>> >> collaborate with each other via the website.<br>
>> >> ---<br>
>> >> And we need your help! We're working on making the first phase of our<br>
>> >> new website live this winter and the website is fairly large. If you'd like<br>
>> >> to help us work on building a great new website for this community, just<br>
>> >> join the Evergreen Web Team mailing list here and introduce yourself:<br>
>> >><br>
>> >><br>
>> >> <a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team</a><br>
>> >> ---<br>
>> >> Questions? Thoughts? Concerns?<br>
>> >><br>
>> >><br>
>> >><br>
>> >><br>
>> >><br>
>> >><br>
>> >> On 09/12/2012 05:21 PM, Lori Bowen Ayre wrote:<br>
>> >>> Jim and Alexey,<br>
>> >>><br>
>> >>> Do you have a plan for the IRC meeting on Friday? I'd like to make<br>
>> >>> sure we have some blocks of text ready to deliver so the meeting goes<br>
>> >>> quickly.<br>
>> >>><br>
>> >>> And FYI, at the Oversight Board meeting there was a general feeling<br>
>> >>> that we should move this project along quickly. Meaning...there isn't<br>
>> >>> really any doubt about people wanting this to be the future of the Evergreen<br>
>> >>> website. So we probably need to think strategically about how we can most<br>
>> >>> effectively move forward, get the bones of this website as close to ready as<br>
>> >>> can, involve more people as much as possible, and start moving content. The<br>
>> >>> sooner this can be the face of Evergreen, the better....that's my<br>
>> >>> impression.<br>
>> >>><br>
>> >>> Given that....what do we want to say, ask for, promise at the meeting?<br>
>> >>><br>
>> >>> Lori<br>
>> >>><br>
>> >>> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=<br>
>> >>> Lori Bowen Ayre //<br>
>> >>> Library Technology Consultant / The Galecia Group<br>
>> >>> Oversight Board & Communications Committee / Evergreen<br>
>> >>> <a href="tel:%28707%29%20763-6869" value="+17077636869">(707) 763-6869</a> // <a href="mailto:Lori.Ayre@galecia.com">Lori.Ayre@galecia.com</a><br>
>> >>> Availability: <a href="http://tungle.me/lori.ayre" target="_blank">http://tungle.me/lori.ayre</a><br>
>> >>><br>
>> >>> Specializing in open source ILS solutions, RFID, filtering,<br>
>> >>> workflow optimization, and materials handling<br>
>> >>> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=<br>
>> >>><br>
>> >>><br>
>> >>> _______________________________________________<br>
>> >>> Evergreen-web-team mailing list<br>
>> >>><br>
>> >>> <a href="mailto:Evergreen-web-team@list.evergreen-ils.org">Evergreen-web-team@list.evergreen-ils.org</a><br>
>> >>><br>
>> >>> <a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team</a><br>
>> >><br>
>> >><br>
>> >><br>
>> >> _______________________________________________<br>
>> >> Evergreen-web-team mailing list<br>
>> >><br>
>> >> <a href="mailto:Evergreen-web-team@list.evergreen-ils.org">Evergreen-web-team@list.evergreen-ils.org</a><br>
>> >><br>
>> >> <a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team</a><br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > Evergreen-web-team mailing list<br>
>> > <a href="mailto:Evergreen-web-team@list.evergreen-ils.org">Evergreen-web-team@list.evergreen-ils.org</a><br>
>> ><br>
>> > <a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team</a><br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > Evergreen-web-team mailing list<br>
>> > <a href="mailto:Evergreen-web-team@list.evergreen-ils.org">Evergreen-web-team@list.evergreen-ils.org</a><br>
>> ><br>
>> > <a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team</a><br>
>><br>
>><br>
>> Alexey Lazar<br>
>> PALS<br>
>> Information System Developer and Integrator<br>
>> <a href="tel:507-389-2907" value="+15073892907">507-389-2907</a><br>
>> <a href="http://www.mnpals.org/" target="_blank">http://www.mnpals.org/</a><br>
>><br>
>> _______________________________________________<br>
>> Evergreen-web-team mailing list<br>
>> <a href="mailto:Evergreen-web-team@list.evergreen-ils.org">Evergreen-web-team@list.evergreen-ils.org</a><br>
>> <a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Evergreen-web-team mailing list<br>
> <a href="mailto:Evergreen-web-team@list.evergreen-ils.org">Evergreen-web-team@list.evergreen-ils.org</a><br>
> <a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team</a><br>
><br>
<br>
<br>
<br>
</div></div><span class="HOEnZb"><font color="#888888">--<br>
Galen Charlton<br>
Director of Implementation<br>
Equinox Software, Inc. / The Open Source Experts<br>
email: <a href="mailto:gmc@esilibrary.com">gmc@esilibrary.com</a><br>
direct: <a href="tel:%2B1%20770-709-5581" value="+17707095581">+1 770-709-5581</a><br>
cell: <a href="tel:%2B1%20404-984-4366" value="+14049844366">+1 404-984-4366</a><br>
skype: gmcharlt<br>
web: <a href="http://www.esilibrary.com/" target="_blank">http://www.esilibrary.com/</a><br>
Supporting Koha and Evergreen: <a href="http://koha-community.org" target="_blank">http://koha-community.org</a> &<br>
<a href="http://evergreen-ils.org" target="_blank">http://evergreen-ils.org</a><br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
Evergreen-web-team mailing list<br>
<a href="mailto:Evergreen-web-team@list.evergreen-ils.org">Evergreen-web-team@list.evergreen-ils.org</a><br>
<a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team</a><br>
</div></div></blockquote></div><br></div>