[Evergreen-web-team] What should the EG Website Team do next?

Thu Sep 15 19:29:06 EDT 2011

Excellent Anoop!  Good idea to get all that posted. Thanks!

Lori

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=
Lori Bowen Ayre //
Library Technology Consultant / The Galecia Group
Oversight Board & Communications Committee / Evergreen
(707) 763-6869 // Lori.Ayre at galecia.com

<Lori.Ayre at galecia.com>Specializing in open source ILS solutions, RFID,
filtering,
workflow optimization, and materials handling
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

On Thu, Sep 15, 2011 at 4:25 PM, Anoop Atre <anoop.atre at mnsu.edu> wrote:

> ++1 everything Kate said especially "June's list is fantastic!"
>
> Here is the list of things to get done one the website -
> http://evergreen-ils.org/**dokuwiki/doku.php?id=webteam:**
> website_recommendations<http://evergreen-ils.org/dokuwiki/doku.php?id=webteam:website_recommendations>
>
> I hope all the folk on the web team have wiki accounts right? : )
>
> Cheers
>
>
> On 09/14/2011 03:55 PM, Kate Sheehan wrote:
>
>> June's list is fantastic!
>>
>> I like the idea of adopt a page and agree that we should solicit help from
>> the lists. Is the web team officially in charge of the site? If we
>> christen
>> someone keeper of a page, does that hold any weight? It seems like a nice,
>> decentralized way to manage a site without putting onerous processes into
>> place to approve content, but I want to make sure when someone adopts a
>> page, they're really adopting it.
>>
>> Talk to you all tomorrow,
>> kate
>>
>> -----Original Message-----
>> From: evergreen-web-team-bounces@**list.evergreen-ils.org<evergreen-web-team-bounces at list.evergreen-ils.org>
>> [mailto:evergreen-web-team-**bounces at list.evergreen-ils.org<evergreen-web-team-bounces at list.evergreen-ils.org>
>> **] On Behalf Of Amy
>> Terlaga
>> Sent: Wednesday, September 14, 2011 3:40 PM
>> To: 'Evergreen Community Web Team Email List'
>> Subject: Re: [Evergreen-web-team] What should the EG Website Team do next?
>>
>> I don't have anything meaningful to add to June's suggestions.  I agree
>> with
>> her approach.
>>
>> I would add that under the "adopt a page" maintenance suggestion, we
>> solicit
>> help via the lists.
>>
>> Looking forward to using her suggestions as a springboard for discussion
>> tomorrow.
>>
>> Amy
>>
>> +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=**+=+=+
>> Amy Terlaga
>> Assistant Director, User Services
>> Bibliomation, Inc.
>> 32 Crest Road
>> Middlebury, CT  06762
>> www.biblio.org
>>
>>
>> -----Original Message-----
>> From: evergreen-web-team-bounces@**list.evergreen-ils.org<evergreen-web-team-bounces at list.evergreen-ils.org>
>> [mailto:evergreen-web-team-**bounces at list.evergreen-ils.org<evergreen-web-team-bounces at list.evergreen-ils.org>
>> **] On Behalf Of Jim
>> Craner
>> Sent: Monday, September 12, 2011 3:57 PM
>> To: evergreen-web-team at list.**evergreen-ils.org<evergreen-web-team at list.evergreen-ils.org>
>> Subject: Re: [Evergreen-web-team] What should the EG Website Team do next?
>>
>> Thanks, June - great stuff!  (And thanks for going first! :-)
>>
>> Hopefully everyone else is working on their contributions but in the
>> meantime, I'll throw in a couple of small points inline to your
>> suggestions:
>>
>> On 09/08/2011 12:20 PM, Rayner, June wrote:
>>
>>  1.  Technical / Platform changes.   Based on the recommendations that
>>> we have put forth, what technical or platform changes do we need to
>>> make to implement those recommendations?    What resources are
>>> required to do this?     If the resources required are more than what
>>> the current web team can provide, who could potentially provide those
>>> resources and how can we approach them?    For example, if we were
>>> going to implement an idea percolator, is there an existing tool that
>>> does this (like IdeaTorrent that Sitka was using)?    Where can it
>>> run?   What's needed to install it?   What costs are involved?
>>>
>>
>> Lori has been discussing IdeaTorrent with some folks from Sitka and we
>> have
>> a separate instance to use.  She will give us more info at our meeting on
>> Thursday.
>>
>>  2.  Ongoing maintenance.   The current EG web site SWAT team has
>>> pioneered the process of doing relatively small changes.    Maybe to
>>> split the work up, we can ask individuals if they can "adopt a page"
>>> for ongoing maintenance, with the overall plan and guidelines in mind.
>>>
>>> 3.  New Content.    If we've identified new content that we want to
>>> add to the site, and assuming there are no technical barriers from #1,
>>> have a "content wanted" page and ask people if they have existing
>>> content that could be adapted or if they would work on creating the
>>> new content.
>>>
>>> 4.  Major site overhauls.    If someone has a large block of time to
>>> work on a major overhaul, that's great.   But probably not realistic.
>>> This might be tackled in an Evergreen website hackfest, possibly as
>>> part of the Evergreen conference.
>>>
>>
>> 2, 3, and 4 are all great ideas and definitely achievable given the team's
>> resources.
>>
>> Other folks have thoughts to share?
>>
>> Thanks again, June!
>> -Jim
>>
>>
>>> Best regards,
>>>
>>> June
>>>
>>> -----Original Message----- From:
>>> evergreen-web-team-bounces@**list.evergreen-ils.org<evergreen-web-team-bounces at list.evergreen-ils.org>
>>> [mailto:evergreen-web-team-**bounces at list.evergreen-ils.org<evergreen-web-team-bounces at list.evergreen-ils.org>
>>> **] On Behalf
>>> Of Jim Craner Sent: Wednesday, September 07, 2011 5:20 PM To:
>>> evergreen-web-team at list.**evergreen-ils.org<evergreen-web-team at list.evergreen-ils.org>Subject:
>>> [Evergreen-web-team] What should the EG Website Team do next?
>>>
>>> Hi everyone,
>>>
>>> As promised, this is your mid-week/post-holiday reminder of your EG
>>> Web Team homework.
>>>
>>> *** Homework: write a 1-4 paragraph narrative of what you see the Web
>>> Team's structure, processes/policies, and activities look like going
>>> forward.  Submit this to the Web Team list for discussion and comment
>>> on everyone else's narrative so that a rough consensus is arrived at
>>> before our next meeting.
>>>
>>> Who wants to go first?  :-)
>>>
>>> Thanks! Jim
>>>
>>> On 09/01/2011 02:14 PM, Jim Craner wrote:
>>>
>>>> Hi everyone,
>>>>
>>>> We had a great discussion today about the future of the Web Team and
>>>> what that may look like.  Please review these (brief) notes and do
>>>> the homework assignment listed at the end -- our goal is to have a
>>>> very active conversation on the Web Team mailing list over the next
>>>> two weeks about this.
>>>>
>>>> Thanks! Jim
>>>>
>>>> Attending: John, June, Jim, Kathy, Roni, Amy, Steve, Kate
>>>>
>>>> ** Importance of "Creation of formal website team" recommendation
>>>>
>>>> * Who can change/edit?  Authority? * Promote people
>>>> changing/editing/adding content * Who is vetting changes?  Little
>>>> technical errors get fixed via wiki/commenting mechanisms.  Big
>>>> changes are arrived at via Web Team consensus with community input
>>>> where appropriate.
>>>>
>>>> * Going forward: loosey-goosey or formal team?  Formal team is
>>>> requirement for the Big changes (implementing centralized
>>>> platform) but policies/efforts can be formalized
>>>>
>>>> * Count the changes Anoop made based on input from the Existing Site
>>>> Improvement Committee as a big success for our efforts!
>>>>
>>>> * Oversight Board?  Governance Committee?  Answer: oversight entities
>>>> are deliberately going hands-off so don't expect top-down strategy.
>>>>
>>>> * Hackfest at annual conference -- Web team spends the year figuring
>>>> out what could be done by a team in a concerted effort at an annual
>>>> Website Hackfest and what stuff they can just do as small chunks
>>>> throughout the year themselves.
>>>>
>>>> * Management spectrum: gatekeepers vs. cheerleaders/facilitators
>>>>
>>>> *** Homework: write a 1-4 paragraph narrative of what you see the Web
>>>> Team's structure, processes/policies, and activities look like going
>>>> forward.  Submit this to the Web Team list for discussion and comment
>>>> on everyone else's narrative so that a rough consensus is arrived at
>>>> before our next meeting.
>>>>
>>>> *** Next meeting (tentative pending Anoop's ability to attend) is
>>>> Thursday, September 15th, same time (1100pdt / 1200mdt / 1300cdt /
>>>> 1400edt).
>>>>
>>>> Thanks, Jim
>>>>
>>>>  -------Original Message------- From: Jim Craner<jim at chicagotech.org>
>>>>> To:
>>>>> evergreen-web-team at list.**evergreen-ils.org<evergreen-web-team at list.evergreen-ils.org>
>>>>> <evergreen-**web-team at list.ev
>>>>> ergreen-ils.org>
>>>>>
>>>>>
>>>>>  Subject: [Evergreen-web-team] Today's meeting - agenda and info
>>
>>> Sent: 01 Sep '11 11:24
>>>>>
>>>>> Hi everyone,
>>>>>
>>>>> We're having our "welcome back" EG Website planning meeting in a
>>>>> couple of hours.  Info and draft agenda below!
>>>>>
>>>>> 2:00pm EST /11:00am PST Conference call number 866-365-4406 /
>>>>> 3693433#
>>>>>
>>>>> Webteam Wiki page:
>>>>> http://www.evergreen-ils.org/**dokuwiki/doku.php?id=webteam<http://www.evergreen-ils.org/dokuwiki/doku.php?id=webteam>
>>>>>
>>>>> Webteam Draft "Big Web Plan Doc" page:
>>>>>
>>>>> http://www.evergreen-ils.org/**dokuwiki/doku.php?id=webteam:**
>>>>> webplan:20<http://www.evergreen-ils.org/dokuwiki/doku.php?id=webteam:webplan:20>
>>>>> 1
>>>>>
>>>>>
>>>>>  1
>>
>>>
>>>>> Webteam's Recommendations page:
>>>>>
>>>>> http://www.evergreen-ils.org/**dokuwiki/doku.php?id=webteam:**
>>>>> webplan:20<http://www.evergreen-ils.org/dokuwiki/doku.php?id=webteam:webplan:20>
>>>>> 1
>>>>>
>>>>>
>>>>>  1:section6_recommendations
>>
>>>
>>>>> (Note: there are two sections on the Recommendations page that
>>>>> we'll discuss - "People&    Process" and "Website")
>>>>>
>>>>> Newest Visual Aids for the "Website Recommendations" section are
>>>>> here:
>>>>>
>>>>> http://www.evergreen-ils.org/**dokuwiki/doku.php?id=webteam:**
>>>>> webplan:20<http://www.evergreen-ils.org/dokuwiki/doku.php?id=webteam:webplan:20>
>>>>> 1
>>>>>
>>>>>
>>>>>  1:section6_recommendations&#**files
>>
>>>
>>>>> Talk to you soon! Thanks, Jim
>>>>> ______________________________**_________________
>>>>> Evergreen-web-team mailing list
>>>>> Evergreen-web-team at list.**evergreen-ils.org<Evergreen-web-team at list.evergreen-ils.org>
>>>>>
>>>>> http://list.evergreen-ils.org/**cgi-bin/mailman/listinfo/**
>>>>> evergreen-web<http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web>
>>>>> -
>>>>>
>>>>>
>>>>>  team
>>
>>>
>>>>>  ______________________________**_________________ Evergreen-web-team
>>>> mailing list Evergreen-web-team at list.**evergreen-ils.org<Evergreen-web-team at list.evergreen-ils.org>
>>>> http://list.evergreen-ils.org/**cgi-bin/mailman/listinfo/**
>>>> evergreen-web-<http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web->
>>>> t
>>>>
>>>>
>>>>  eam
>>
>>> ______________________________**_________________ Evergreen-web-team
>>> mailing list Evergreen-web-team at list.**evergreen-ils.org<Evergreen-web-team at list.evergreen-ils.org>
>>> http://list.evergreen-ils.org/**cgi-bin/mailman/listinfo/**
>>> evergreen-web-t<http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-t>
>>> eam
>>>
>>>
>>>  ______________________________**_________________
>>
>>> Evergreen-web-team mailing list
>>> Evergreen-web-team at list.**evergreen-ils.org<Evergreen-web-team at list.evergreen-ils.org>
>>> http://list.evergreen-ils.org/**cgi-bin/mailman/listinfo/**
>>> evergreen-web-t<http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-t>
>>> eam
>>>
>> ______________________________**_________________
>> Evergreen-web-team mailing list
>> Evergreen-web-team at list.**evergreen-ils.org<Evergreen-web-team at list.evergreen-ils.org>
>> http://list.evergreen-ils.org/**cgi-bin/mailman/listinfo/**
>> evergreen-web-team<http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team>
>>
>> ______________________________**_________________
>> Evergreen-web-team mailing list
>> Evergreen-web-team at list.**evergreen-ils.org<Evergreen-web-team at list.evergreen-ils.org>
>> http://list.evergreen-ils.org/**cgi-bin/mailman/listinfo/**
>> evergreen-web-team<http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team>
>>
>> ______________________________**_________________
>> Evergreen-web-team mailing list
>> Evergreen-web-team at list.**evergreen-ils.org<Evergreen-web-team at list.evergreen-ils.org>
>> http://list.evergreen-ils.org/**cgi-bin/mailman/listinfo/**
>> evergreen-web-team<http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team>
>>
>
>
> --
>
> Anoop Atre
> IS Developer & Integrator, MnPALS
> PH: 507.389.5060
> OF: 3022 Memorial Library (Office-ML 3022)
> --
> "Mit der Dummheit kämpfen Götter selbst vergebens"
>  ~ Johann Christoph Friedrich von Schiller
>
> ______________________________**_________________
> Evergreen-web-team mailing list
> Evergreen-web-team at list.**evergreen-ils.org<Evergreen-web-team at list.evergreen-ils.org>
> http://list.evergreen-ils.org/**cgi-bin/mailman/listinfo/**
> evergreen-web-team<http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-web-team/attachments/20110915/80227e62/attachment-0001.html>