Meeting takes place on IRC on the #evergreen channel on Freenode. See the Calendar for specific dates and times.

Held at

• 09:00:00 a.m. Tuesday May 24, 2011 in America/Los_Angeles
• 12:00:00 p.m. Tuesday May 24, 2011 in Canada/Eastern
• 16:00:00 Tuesday May 24, 2011 in UTC

Last meeting: 2011-04-30

• IRC logs
• Minutes will be supplied in this document after the meeting finishes.

• Please fill out Who's who if you want to be identified more readily in the future

1. Determine the taker of minutes: ?
2. Determine meeting leader: ?
3. Review action items
4. Git processes:
   1. How do we go about getting topic branches reviewed before committing them to a main branch? For example, I opened LP 787295 but as it doesn't have a patch, it won't show up in the current "patch review queue" canned LP searches that we have. Perhaps adopt a standard tag like reviewplease that we can then build another canned search against?
   2. Do we want to consider requiring reviewer sign-off before committing to a main branch? It doesn't slow down development, as you can continue to commit to topic branches, and should improve the quality of the main branches.
5. OpenLibrary: Dan Scott met with the OpenLibrary development team for a very positive day in May. Topics discussed included:
   1. rate-limiting of cover images by ISBN (limit has been removed)
   2. design of a Read API; throw multiple identifiers at OpenLibrary and get back JSON responses including everything OpenLibrary knows about matches to those identifiers, including all electronic versions available to your IP address range (including DAISY and borrowable ebooks). Dan plans to implement this new API as a proof of concept in Conifer in the next week or two
   3. longer term integration plans, including the ability to write to OpenLibrary (table of contents, excerpts, cover art) from Evergreen
6. Notice: Conifer is holding TT OPAC development days @ University of Windsor, June 27-29th. If you hack on the TT OPAC and want to join us, get in touch with Dan Scott.

We don't want to let submitted patches rot, here's a list of bugs with attached patches

1. Evergreen release status:
   1. 1.6.1.x (current release = 1.6.1.8)
      1. Bugs targeted to 1.6.1.9
   2. 2.0.x (current release = 2.0.6)
      1. Bugs targeted to 2.0.7
   3. 2.1.x
      1. Status check?
   4. Most recently reported bugs

• On calendar for Tuesday, June 7th at 12:00 EST, 9:00 PST.