[Evergreen-web-team] 2012-08-16 EG Web Team meeting notes
Lazar, Alexey Vladimirovich
alexey.lazar at mnsu.edu
Wed Aug 29 10:17:22 EDT 2012
Evergreen Web Team meeting notes
Date: 2012-08-16
Type: conference call
Next meeting: 2012-08-30 at 14:30 ET | 13:30 CT | 12:30 MT | 11:30 PT (USA)
Attendees:
* Anoop Atre <aatre at esilibrary.com>
* Lori Bowen Ayre <lori.ayre at galecia.com>
* Jim Craner <jim at galecia.com>
* Alexey Lazar <alexey.lazar at mnsu.edu> (notetaker)
* Benjamin Shum <bshum at biblio.org>
* Stephen Wills <swills at beyond-print.com>
Done:
* Jim: http://evergreen.galecia.com/ticketmaster is set it up and people are free to use it as needed (project management)
* Jim: Evergreen logo and footer added to the prototype website (content)
* Ben: talk to Kathy and Yamil to figure out who is doing calendaring currently, will update the current who-is-who wiki page with the information (calendar)
Topics that were discussed:
* Review past todo items, mark as done, plan next steps
* "Content owner": decided to go with Galen's suggestion of Content Editor for this role
* Blogs
* Calendars
* Evergreen map and directory functionality
* "Web publishing policy": a document that would outline the publishing process for Evergreen web infrastructure. Web Team could work on this if the Oversight Board gives us a charge.
* Conference website: any changes/standardization for how the Evergreen conference content is managed would not be implemented until the 2014 conference, at the earliest.
Working draft of Content Editor volunteer responsibilities:
* Actively seek out and/or add content for their sections
* Assist folks who want to contribute
* Keep an eye on any updates to their section and, as needed, improve any updates supplied by another contributor
* Handle any periodic or time-sensitive updates (for example, the person or persons who edit the downloads section would be on point whenever a release is cut)
Old to-do items:
* Jim: create a new role called blogger (blog)
* Jim: will create an editor field on each page to identify who is responsible for what part of content (content management)
* Alexey: start working on Web Team content (content migration)
* Jim: will look at options for adding a left-menu
New to-do items:
* Alexey: send out a call for anyone interested to get involved in prototyping of blog, calendar and maps/directory functionality
On the radar (these topics were mentioned):
* Discuss Drupal calendar features/options with current calendar owners. Identify potential candidates for Drupal role of Event manager(s).
* Discuss/review blogging feature with current bloggers.
* Review current official and unofficial pages for content migration needs
* Future conference website (2014)
More information about the Evergreen-web-team
mailing list