14:01:58 <yboston> #startmeeting 2012-06-07 - DIG Monthly Meeting
14:01:58 <pinesol_green> Meeting started Thu Jun  7 14:01:58 2012 US/Eastern.  The chair is yboston. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:58 <pinesol_green> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:02:27 <yboston> #topic Introductions
14:02:40 * jenny1 is Jenny Turner, PALS
14:02:44 * rsoulliere is Robert Soulliere, Mohawk College
14:02:47 <yboston> please introduce yourselves :)
14:02:53 <raynerj> raynerj is June Rayner eiNetwork
14:02:54 * fortin is Sally Fortin, Equinox Software
14:03:03 * csharp is Chris Sharp, Georgia Public Library Service/PINES
14:03:06 * denials is Dan Scott, Laurentian University
14:03:08 <yboston> BTW, I want to try using Meetbot today
14:03:25 <bshum> yboston++  :)
14:03:30 <yboston> Just participate as normal, but don't be thrown off by my use of the special Meetbot "#command" syntax.  More information here:http://www.open-ils.org/dokuwiki/doku.php?id=community:using-meetbot&s[]=meetb
14:03:30 * bshum is Ben Shum, Bibliomation
14:04:23 <yboston> I will like to ask for a volunteer to take minutes as a back up in case I don't use Meetbot properly
14:04:43 <raynerj> I'll do it :)
14:04:44 <yboston> hopefully the last time we need a minutes taker
14:04:50 <yboston> thank you!!!
14:04:57 <raynerj> yboston+++
14:05:15 <yboston> #topic Updates from Content Coordinators
14:05:15 <jenny1> raynerj++
14:05:28 <yboston> Btw, I want to experiment with having the content corrdinators try out the #topic Meetbot command for their reportsSo content coordinators, please start your reports with #info like this
14:05:44 <yboston> #this is a test report
14:05:48 <yboston> sorry
14:05:54 <yboston> #info this is a test report
14:06:09 <yboston> who would like to report first?
14:07:03 <raynerj> I can go from administration
14:07:10 <yboston> ok
14:07:17 <raynerj> #info Adminstration
14:07:32 <raynerj> I have a chunk of 2.1 doc ready to merge, I think
14:07:56 <raynerj> I can then convert it for 2.2
14:08:18 <raynerj> That's it for me.
14:08:38 <yboston> thanks, who would like to go next?
14:08:53 <yboston> don't forget #info :)
14:09:06 <rsoulliere> I can go
14:09:12 <rsoulliere> #info Conversion Coordinator Report
14:09:14 <yboston> go ahead
14:09:25 <rsoulliere> First,  I think I need to change the name of my role from "DocBook Conversion Coordinator" to "Conversion Coordinator" or something else.
14:09:57 <rsoulliere> I will think about that and get back to you...
14:10:03 <rsoulliere> Changed the PDF download image to Dan's generic "PDF" image icon for fear of lawsuits.
14:10:31 <rsoulliere> denials migrated the docs repo to the official code repository.
14:10:45 <rsoulliere> Currently, we are in testing mode for this and we are still pulling the docs from the old documentation repository at this time.
14:11:05 <rsoulliere> I am not sure when I will get a chance to sort out all the details and make the official switch because of other current priorities at my day job.
14:11:31 <rsoulliere> Please bear with me. ;-)
14:11:42 <rsoulliere> That is all I have for now.
14:11:44 <yboston> rsoulliere++++++
14:12:00 <yboston> I just wanted to quickly mention
14:12:13 <yboston> that I am glad to have seen the process of dealing with the PDF icon
14:12:27 <yboston> out in the open to appreciate the software conservancy
14:12:54 <yboston> and the work so many other put in to be compliant with the law, etc
14:13:12 <yboston> (end of rant)
14:13:18 <yboston> who would like to go next?
14:13:24 <jenny1> i can go
14:13:29 <yboston> go ahead
14:13:34 <denials> rsoulliere++
14:13:41 <jenny1> #info Reports Coordinator Report
14:13:59 <jenny1> I am slowly making my way through reports documentation from past versions to make sure it can be brought forward into 2.2.
14:14:05 <jenny1> Otherwise the Reports Taskforce is meeting in 2 weeks for the first time since Conference (scheduling challenges).  Hopefully I'll get an update on other documentation at that time.
14:14:34 <jenny1> I'm in the same boat as rsoulliere with day job priorities, so bear with me, too!
14:14:46 <yboston> jenny1++
14:14:49 <jenny1> and that's all
14:14:54 <denials> raynerj++ jenny1++
14:15:02 <yboston> thanks!
14:15:12 <yboston> any other reports?
14:15:35 <yboston> including non-content coordinators?
14:16:05 <jenny1> I have an unofficial report, too, I guess
14:16:20 <yboston> go ahead
14:16:38 <jenny1> #info Acq Documentation
14:17:32 <jenny1> we're going through the acq documentation here and my coworker has a few clarifications to suggest.  She sent a message to the list as an intro, so watch for her suggestions!
14:18:36 <jenny1> just wanted to mention it - that's all
14:18:49 <yboston> thanks, looking forward to it
14:19:19 <yboston> lets move on to new business
14:19:38 <yboston> #topic Discuss what DIG thinks the role of the DIG release coordinator should be (suggested by Tim Spindler)
14:19:49 <yboston> not sure if Tim is here?
14:20:21 <yboston> we can shelve it for next week?
14:20:31 <yboston> (month)
14:20:50 <yboston> moving on?
14:21:00 <jenny1> sounds good to me.
14:21:15 <yboston> #topic DIG recap of Evergreen conference
14:21:22 <yboston> I can start this
14:21:51 <yboston> I facilitated the DIG meeting during the "hackfest" day
14:22:26 <yboston> I gave an introduction on how to join and participate in DIG, and a quick introduction to AsciiDoc
14:23:03 <yboston> Regretfully, this year we had less people than the year before, but I was glad to meet several of you for the first time face to face
14:23:31 <yboston> Finally at the two "lightening talk" sessions
14:23:52 <yboston> June, Roni, and I put together a pitch for more DIG volunteers
14:23:59 <yboston> that is all for me
14:24:29 <denials> yboston++ # did a great job!
14:25:00 <jenny1> yboston++
14:25:01 <yboston> thanks
14:25:12 <yboston> any other other DIG related reports from the conference?
14:26:09 <yboston> I will move on
14:26:32 <yboston> #topic Brainstorm ideas for next conference (proposed by Yamil Suarez)
14:27:19 <yboston> I definitely want to present a DIG pitch at the lightening talks next year, assuming there is space
14:28:02 <yboston> I also would like to more formally plan a documentation hackfest while the developers hack away
14:28:09 <yboston> any other thoughts?
14:29:08 <raynerj> That all sounds good
14:29:34 <yboston> thanks, we can move on
14:29:56 <yboston> #topic Documentation merged with the code repository: what that means! (proposed by Dan Scott)
14:29:56 * denials would be willing to do a "basics of git" for DIG hackfest if there's interest
14:30:09 <denials> (that kind of flows into this topic, heh)
14:30:13 <yboston> denials+++++++
14:30:33 <jenny1> denials++
14:31:08 <alexlazar> denials++
14:31:18 <raynerj> denials++++
14:31:25 <yboston> denials: do you want to start us off on this agenda item?
14:31:26 * denials blushes
14:31:36 <denials> so, "what that means"
14:32:01 <denials> I think I've laid out the biggest bits in the agenda
14:32:58 <denials> What I'm most excited about is the potential for people to 1) find the help they need in the docs in the source itself and 2) for those same people to contribute patches back based on what they find (or find missing) in the docs in the source
14:33:10 <yboston> #link here it is again http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:dig_meeting_20120607-agenda
14:33:43 <denials> And further to rsoulliere's point about building the docs & needing to cut over, we should be able to be in a good position to get the buildbot at testing.evergreen-ils.org to automatically test & build the docs
14:35:16 <denials> In terms of the details of the merge: we made the "INSTALL" and "README" files in the source directory symbolic links to the docs/installation/server_installation.txt file
14:35:30 <denials> and similarly for the release notes...
14:35:53 <denials> Does anyone have any questions around the merge?
14:37:01 <rsoulliere> I have a few technical questions but I think might be more suited for the list.
14:37:23 <bshum> Other than rsoulliere and yboston, do others from DIG have commit access?
14:37:52 <denials> bshum: you might have to ask the gitadmin@evergreen-ils.org folk (gmcharlt and tsbere) that
14:37:53 <tsbere> anyone who had access to the dig repo should have access to the main one in the docs folder
14:38:02 * tsbere resumes lurkish behavior
14:38:04 <yboston> For the record
14:38:11 <bshum> Right.
14:38:22 <yboston> I had made a Github fork of Robert Github mirror of the docs
14:38:26 <bshum> Just figuring out who to pester ;)
14:38:43 <denials> we might also have to ask who had access to the DIG repo to answer bshum's question then :)
14:38:45 <yboston> but I should eventually retire that
14:38:48 <yboston> fork
14:39:17 <yboston> and I had Roni and June pushing to my fork
14:39:46 <tsbere> "rsoulliere ysuarez@berklee.edu hce@epix.net dbs" are the keys with access.
14:39:49 <denials> Nothing wrong with forks, but it would be nice to maintain the Author: and Signed-off-by: bits so we can credit people appropriately
14:40:02 <denials> tsbere++
14:40:06 <yboston> tsbere: I was about to ask
14:40:17 <yboston> tsbere: you read my mind
14:40:33 <parser> dbs: re Evergreen 2.1.2-rc1 testing -- which upgrade script "2.1.1-2.1.2-rc1-upgrade-db.sql" OR "2.1.1-2.1.2-upgrade-db.sql" ??  I presume the former, but they're quite different in size
14:40:58 <yboston> denials: I agree, this is going to be a fresh start for me, Roni, and June once we get going
14:41:04 <rsoulliere> Process seems more complicated but much better for tracking.
14:41:35 <yboston> and branching and merging...
14:42:52 * denials will be happy to help with git workflows for DIG
14:42:55 <yboston> please correct me if I am wrong, but most DIG contributors can continue to just email their submissions to the list. For now it is those that have the Git access that have to do the hard work
14:43:11 <yboston> (but well worth it)
14:44:29 <jenny1> would be great to keep it that way - lowers the barriers to participation
14:44:36 <alexlazar> yboston: hopefully yes.
14:44:43 <denials> yboston: right. git committers can use 'git  commit --author "Foo Bar <foo@example.com>"' to retain original author credits, for example
14:45:05 <denials> but for sure, we want to encourage the ability to contribute without having to master git or asciidoc
14:45:19 <denials> (one step at a time, we shall draw people in... heh heh)
14:47:13 <yboston> Any other key thoughts that we should bring up on this topic for now until next time?
14:47:27 <yboston> (next meeting)
14:48:52 <rsoulliere> denials++
14:48:58 <yboston> denials++
14:49:38 <raynerj> denials++
14:50:01 <yboston> we are past the 45 minute mark, and all we have is one "old business" agenda item. we can stay on the the DIG Git topic or move on
14:50:08 <denials> DIG++
14:51:32 <rsoulliere> shoud we ask git related question on DIG list DEV list or both?
14:52:33 <yboston> I would do Dev since we are still dealing with really technical Git issues at this time
14:53:01 <yboston> but once we are dealing with more general DIG workflow issues we can add the DIG list
14:54:20 <denials> +1
14:56:24 <yboston> we are almost at the 1 hour mark. I would suggest that we shelve the last "old agenda item" and open up the floor to any general DIG related questions
14:56:36 <yboston> specially form those that have not spoken much yet
14:58:46 <yboston> Perhaps it is best to end the meeting at this point?
14:59:37 <yboston> BTW, assuming we continue on this meeting schedule, we will next meet on July 5th
14:59:41 <fortin> yboston: you've done a great job. thanks for leading the meeting
14:59:48 <denials> yboston++
14:59:51 <yboston> gracias
14:59:52 <jenny1> yboston+++++
14:59:55 <rsoulliere> yboston++
15:00:19 <yboston> thank you everybody for coming, until next time
15:00:28 <yboston> #endmeeting