====== Developer meeting: May 23, 2012 ======

Meeting takes place on [[http://evergreen-ils.org/chat.php|IRC]] on the #evergreen channel on Freenode. See the [[http://evergreen-ils.org/calendar|Calendar]] for specific dates and times.

Held at
  * 11:00:00 a.m. Wednesday, May 23, 2012 in America/Los_Angeles
  * 2:00:00 p.m. Wednesday, May 23, 2012 in Canada/Eastern
  * 18:00:00 Wednesday, May 23, 2012 in UTC

Last meeting: 
  * [[dev:meetings:2012-04-02|2012-04-02]]

===== Logs and minutes =====

Links will be added after the MeetBot gives us links:

  * Minutes: http://evergreen-ils.org/meetings/evergreen/2012/evergreen.2012-05-23-14.11.html
  * Minutes (text): http://evergreen-ils.org/meetings/evergreen/2012/evergreen.2012-05-23-14.11.txt
  * Meeting Log: http://evergreen-ils.org/meetings/evergreen/2012/evergreen.2012-05-23-14.11.log.html

===== Agenda =====

  - Determine the taker of minutes: MeetBot
  - Determine meeting leader: 
  - Start MeetBot recording: #startmeeting 2012-05-23 - Developer Meeting
  - New business
    - Documentation in the code repository
      * dbs has put together a proof-of-concept branch merging the documentation repository with the code repository at user/dbs/doc_consolidation_master in working
      * The goal is to enable DIG members to commit directly to anything under the docs/ subdirectory of Evergreen. Release notes and install instructions will be located there, with INSTALL && README now being simple symlinks to the actual install docs.
      * Any objections / questions? Shall we make it so?
    - Release notes entries
      * We're putting these in a "RELEASE_NOTES_NEXT" directory or something like that now (clarification appreciated)
      * Is the process that, when the branch gets merged, the release notes entry will get pulled into the release notes file at that time and the RELEASE_NOTES_NEXT directory gets deleted?
    - Github pull requests
      * I imagine we're going to get more pull requests from github users. More contribution == goodness, but we also need to maintain sign-offs and quality commit logs (see [[https://github.com/torvalds/linux/pull/17#issuecomment-5654674|fun Linus rant about github pull requests]]), and there seems to be a common pattern in github pull requests that suggests people aren't reading our "contributing" wiki doc, or our dev:git wiki page.
      * Maybe we could edit the HACKING doc to the root of the git directory / tarball to make it contain the simplest possible info about requirements (good commit logs, sign-offs, pointer to http://bugs.launchpad.net)?
    - Any thoughts on https://bugs.launchpad.net/evergreen/+bug/925776 (OU-targeted URI's and scoping with staff searches) I told Beth (from the ticket) that I'd bring it up and see what folks thought.
      * dbs added a comment, following a similar complaint from rjackson-isl in IRC this morning, trying to describe the use case for the behaviour. It's working as designed, but it sounds like there's a non-trivial number of staff who would prefer it to be designed differently.
    - **GSoC project updates**: Ideally from the students themselves, if they're in attendance.
      * Please note any bottlenecks / barriers that you might be running into; the community wants to help.
    - Comments on [[http://libmail.georgialibraries.org/pipermail/open-ils-dev/2012-May/008263.html|Proposed 2.3 Release Schedule]]
  - Releases
    - OpenSRF
      - OpenSRF release 2.1.0
        * dbs is close to cutting the final pre-release tarball; if there are any further bug fixes to get in, flag them in Launchpad now!
          * (berick: dbs is looking at you and your only-ever-mentioned-in-IRC JS monkeypatch branch) 
        * Thanks to Galen for assistance on testing a few outstanding patches!
        * Also, [[https://bugs.launchpad.net/opensrf/+bug/1003223|dropping support for RHEL 5 / CentOS 5 / Debian Lenny / Ubuntu Hardy]] from README and Makefile.install in user/dbs/README_distros_2_1 branch
          * dbs has tested with a clean Debian Squeeze install, will test with clean Ubuntu Precise and Fedora installs before pushing rel_2_1 / master
      - OpenSRF master:
        * dbs will apply [[https://bugs.launchpad.net/opensrf/+bug/1002509|Remove ChopChop]] as soon as 2.1.0 is cut
        * dbs would like more eyeballs on [[https://bugs.launchpad.net/opensrf/+bug/1002028|Cross Origin Resource Sharing (CORS) Support]]
          * There's some good info in the write-up in the pull request itself, but the commits need to be cleaned up with improved comments and DCO sign-offs. Would anyone be willing to work with Bennett to help guide him through our process?
          * Update: Bennett took another stab at a cleaned-up commit, per the bug; still need eyeballs & braiiinz
  - Evergreen
    - Evergreen release 2.0.11
    - Evergreen release 2.1.2
      * Once OpenSRF 2.1.0 is cut, dbs will focus on a 2.1.2 release
    - Evergreen release 2.2.0
    - Evergreen 2.3?
  - Announcements?
  - End MeetBot recording: #endmeeting