02:00:25 #startmeeting 02:00:25 if there is a meeting then Brooke must want me 02:00:25 Meeting started Wed Nov 7 02:00:25 2012 UTC. The chair is rangi. Information about MeetBot at http://wiki.debian.org/MeetBot. 02:00:25 Useful Commands: #action #agreed #help #info #idea #link #topic. 02:00:34 #topic Introductions 02:00:35 #info wahanui, a bot that has become sentient 02:00:44 #info Owen Leonard, Athens County Public Libraries 02:00:48 #info Elliott Davis, ByWater Solutions 02:00:55 #info Chris Cormack, Catalyst IT, Rmaint 3.8.x and 3.10.x 02:01:10 #info Bob Birchall, Calyx information essentials 02:01:11 #info Chris Hall, Catalyst IT 02:01:11 #info NancyK Reno 02:01:12 #info rhcl = Greg - Rolling Hills Consolidated Library 02:01:14 #info Jane Wagner, LibLime/PTFS 02:01:19 #info Jared Camins-Esakov, C & P Bibliography Services, Release Manager for 3.12 and RMaint emeritus for 3.6.x 02:01:24 #info Robin Sheat, Catalyst IT 02:01:27 aww I forgot to add that I am QAA 3.12 02:01:28 shoot 02:01:30 #info Clint Deckard, Anact 02:01:45 2#info Joanne Dillon (JD), Te Takere 02:01:56 in blue even 02:02:13 anyone else? 02:02:13 2Felt like being colourful :-) 02:02:17 #info Mason James, NZ 02:03:04 #topic Announcements 02:03:07 #info Kathryn Tyree, Catalyst IT NZ 02:03:08 #infor David Nind, NZ 02:03:25 #info Liz Rea 02:03:31 anyone have any announcements ? 02:04:02 wizzyrea starts work at catalyst on monday 02:04:07 thats the only one i have 02:04:08 \o/ 02:04:13 I've starting working on automated testing 02:04:22 with WWW::Mech 02:04:29 libsysguy++ 02:04:30 cool 02:04:32 ill publish the repo soon 02:04:48 #action libsysguy to publish repo of his mechanized testing suite 02:05:07 anything else before we move on? 02:05:11 #info We now have a repository for a version of git-bz customized for Koha at http://git.koha-community.org/gitweb/?p=git-bz.git;a=summary 02:05:16 #info i've just eaten waaay too many samosas :/ 02:05:16 That's it from me. 02:05:21 oooo 02:05:27 to both 02:05:30 git-bz++ 02:05:40 git-bz++ 02:05:43 ^^ what he said 02:05:46 #topic update on 3.8 02:06:05 3.8 is coming along nicely, on schedule for 3.8.7 release on time 02:06:18 awesome 02:06:23 is it going to include the hourly fixes? 02:06:30 for use with the calendar 02:06:34 if they are pushed to master then yes 02:06:39 hehe 02:06:42 fair enough 02:06:53 ie signed off, passed qa, and pushed, then ill cherry pick them to 3.8.x 02:07:19 #topic update on 3.10 02:07:38 we have no paul, but i think reading the newsletter is a good idea 02:07:45 paul_p isn't here, so I'll give what information I have. 02:08:12 #link http://koha-community.org/koha-release-manager-newsletter-11-12-2012-10/ 02:08:27 Now that 3.10.x has been branched and I am pushing to master we have an additional set of eyes looking over code before it gets into 3.10.x. 02:08:37 excellent 02:08:46 Paul is cherry-picking bugfixes that do not include string changes. 02:09:09 [off] twitter: @nzkoha: "@ranginui is chairing the #kohails IRC meeting like a boss" 02:09:13 Any code that either of us is uncomfortable with will probably not go into master until after 3.10.x is released. 02:09:30 *3.10.0 02:09:59 ("probably" because there is always the possibility -- however slight -- of an error) 02:10:10 oops I forgot about tweetbot sorry for the interruption, my jokes always backfire... 02:10:11 sounds good to me 02:10:13 As far as I know, 3.10.0 is on-schedule 02:10:19 I will address 3.12 when we get there. 02:10:31 anyone have anything else for 3.10? 02:10:40 Oh, one more thing. 02:10:49 TEST BUGFIXES!!!! 02:10:59 oh yes 02:11:23 #action everyone test bug fixes 02:11:29 #topic 3.12 02:11:31 #action Test and sign off on the bugfixes that are already in Bugzilla, and test 3.10.x/master and fix any bugs you find. 02:11:38 Oh, rangi beat me. 02:11:40 heh 02:11:47 you again jcamins 02:11:52 sorry I am late # Irma CALYX information essentials - Sydney 02:12:04 hi all 02:12:18 The master branch will be 3.11 once 3.10.0 is released. 02:12:35 Right now I am only pushing 3.10-safe fixes to that branch. 02:12:43 cool 02:13:00 However, as non-3.10 patches pass QA I am applying them to an integration branch on my local machine. 02:13:18 This brings up an important point. 02:13:53 One of the bugs that was marked "Passed QA" was marked that BY ITS AUTHOR, without ANY member of the QA team approving it. 02:14:06 Attached to that bug were no fewer than *three* patches that had not been tested by anyone. 02:14:09 down with that kind of thing 02:14:20 ew yea not acceptable. 02:14:22 That is not, and never has been acceptable. 02:14:45 The change in release manager does not mean a relaxation of QA standards. 02:15:08 I will, in fact, be requesting additional signoffs from members of the QA team whenever they QA patches. 02:15:17 shall i do an info point only qa team can mark things passed-qa ? 02:15:23 Yes, good idea. 02:15:36 I think bugzilla can manage that sort of thing or no? 02:15:40 with permissions 02:15:51 bugzilla can do some crazy awesome things. 02:15:52 wizzyrea: I'm not sure. But if it can, that might be good. 02:15:52 yeah can we fix that kind of thing with perms 02:16:05 #info only qa team should mark patches passed qa, unless there are some crazy circumstances like security and everyone is on holiday in tahiti or something 02:16:06 wewt 02:16:17 #action Find out if we can set Bugzilla permissions so that only the QA team can mark things "Passed QA" 02:16:18 tahiti_holiday++ 02:16:29 Let's see, what else? 02:16:35 although if a patch is 'passed qa' and then goes 'in discussion' it would require a qa team member to put it back to 'passed qa', is this desired? 02:16:43 cjh: I'm leaning towards "yes." 02:16:56 yea, I tend to agree with hat 02:16:58 that* 02:16:59 same 02:17:03 i think we have a big team now 02:17:06 that should be ok 02:17:07 The bug report that I'm referring to was set to "Passed QA" by the author several times. 02:17:14 eek 02:17:15 !! 02:17:18 oy 02:17:31 jcamins++ # for bringing it up 02:17:57 Other than that, I expect a nice tight six-month release cycle, and I'll be preparing monthly "previews." 02:18:02 a general reinforcement of the rules would be good 02:18:19 I like your style. 02:18:24 I've seen a patch by company X that was signed off by someone associated with X, and then the QA signoff was also from X. 02:18:34 And it broke things for other people. 02:18:40 yeah, now the team is big too, its easy to stop that 02:18:41 Yes. That's a good point. 02:19:06 i think cait will be great at managing those things 02:19:23 During the 3.12 cycle I'll be leaning on cait a lot to deal with delegation. 02:19:49 cait will rule with an iron fist 02:20:46 :) 02:20:47 #info During the 3.12 release cycle, the RM will assign the QAM as QA contact to bugs where he is concerned about a conflict of interest, and the QAM can delegate as appropriate. 02:21:01 I think that's pretty much it from me. 02:21:08 thanks jcamins 02:21:11 Oh, one more thing. 02:21:24 * rangi pauses 02:21:55 #info The RM will prepare a "roadmap" for 3.12 after 3.10.0 is released, but since the focus is on "stability," don't expect a detailed plan for exactly what we're going to be working on at any given point. 02:22:00 That's it. 02:22:07 jcamins++ 02:22:11 Is there a date for the next Global Bug Squashing Day? 02:22:18 jcamins++ 02:22:23 #topic kohacon13 02:22:30 jcamins++ i like roadmaps 02:22:38 heh 02:22:40 Irma: can you ask that again when we get to miscallaneous please 02:22:49 ok 02:22:51 but spelt right ;) 02:23:12 nancyk: did you have any information about kohacon13 ? 02:23:15 almost finished touring hotels, have it narrowed down to 3 02:23:20 oh cool 02:23:29 looks like mid odtober 02:23:40 rats bad spelling 02:23:59 cool 02:24:12 #info kohacon13 dates are looking like mid october 02:24:20 nancyk ++ 02:24:28 We will get info on the web site and wiki as soon as we know which hotel 02:24:42 Excited!!!! 02:24:49 nancyk I require a beautyrest in my hotel :p 02:24:51 Could you put a link to the KohaCon13 website and wiki pages in the minutes? 02:24:55 nancyk++ 02:24:58 lol. 02:25:11 What's the weather like in October? 02:25:11 well you are our "hottest developer" so there's that. 02:25:14 nancyk++ 02:25:17 #link http://wiki.koha-community.org/wiki/KohaCon13_Summary 02:25:23 I do have to keep up my beauty :p 02:25:26 and 02:25:29 70s and sometimes 80s sunny 02:25:30 * wizzyrea giggles 02:25:37 #link http://koha-community.org/kohacon/kohacon13-2/ 02:25:37 sounds pretty perfect ;) 02:25:38 Swank. 02:25:41 #info Thomas Dukleth, Agogme , New York City, survived the blackout and heatout 02:25:52 good to see you safe and sound thd 02:25:54 yes! thd made it through sandy! 02:26:06 thd: nor'easter coming, right 02:26:10 ? 02:26:13 does anyone else have anything else about kohacon13 ? 02:26:22 no 02:26:36 70 F = 21 degrees C 02:27:10 #topic actions from the last meeting 02:27:32 i don tthink we had any actions? 02:27:41 I don't see any. 02:27:48 moving on 02:27:55 #topic Miscellaneous 02:28:09 spelt right, too 02:28:11 Irma: you had a question? :) 02:28:52 it was about Global Bug Squashing Day, is there a date? 02:29:07 http://wiki.koha-community.org/wiki/2012-09-14_Global_bug_squashing_day Next date? 02:29:18 snap 02:29:19 ah, magnus usually organises that 02:29:30 id suggest an email to the koha-devel list 02:29:35 he's sleeping :) 02:29:40 of course, we could just pick a date ;) 02:29:55 itd be good to do one before 3.10.0 02:29:59 It's usually the second Friday. 02:30:05 *nod* 02:30:12 which is tomorrow 02:30:13 Stefan is in Sydney until 3/12 so before then would be good 02:30:20 in nz 02:30:38 Which would be... 9 November 02:30:49 I'd love to see people try to lead testing on patches they have written which have languished in the needs-signoff queue for a long time. 02:30:58 or 16th nov, the friday after that? 02:31:06 i think the 9th is good 02:31:23 15th is string freeze for 3.8.x 02:31:46 adn we dont want a pile of patches the week before 3.10.0 02:31:52 yeah, so 16th not so good 02:31:53 I'm fine with the 16th, but keep in mind that I _am_ a stickler, and we have two people pushing code to get it into 3.10.x, so some patches would probably get deferred for 3.10.1 02:31:59 yeah 02:32:15 And by "probably" I mean "I am absolutely certain." 02:32:22 #idea bug squashing day on the 9th of november 02:32:36 if people want it to happen then, they just need to make a wiki page 02:32:39 and send out emails 02:32:54 any one want to volunteer to do that ? 02:33:45 hrm think it'll actually get any traction? does it have to be a friday? 02:33:55 nope 02:34:14 make it monday and ill make it your job to test patches *grin* 02:34:26 ^.^ 02:34:58 Friday 9th Nov or Mon 12th Nov ok for CALYX 02:35:05 well i think the secret with it, like pretty much everything in koha, is someone needs to organise/do it 02:35:18 and magnuse is conferencing 02:35:24 and so is cait 02:35:27 and they usually do it 02:35:32 so someone else will need to step up 02:35:46 I can to the wiki and the emails if we can settle on a date 02:35:57 im trying to work out how to use a 'Template:Globsquad' template to make a new GSBD page 02:36:06 +1 9th nov 02:36:47 + 9th nov 02:37:09 +1 9th nov 02:37:16 Will magnus and cait still be conferencing Friday? Monday? 02:37:28 cait will be make on friday 02:37:35 +1 12 Nov. 02:37:50 +1 9th nov 02:38:03 What about GBSW? - Global Bug Squashing Weekend 02:38:20 We're approaching 3.10. 02:38:24 true 02:38:30 Now is a good time to really focus on testing. 02:38:32 yup 02:38:35 * oleonard can bug-squash at work but too many obligations at home 02:38:50 oleonard: right, that's why it's Friday-Monday. 02:39:01 *College* weekend. 02:39:02 I see 02:39:05 Not real person weekend. :P 02:39:15 I feel 2 days is a bit short notice, hopefully we can get enough people 02:39:30 Right, so we also have 5 days notice for Monday. 02:39:41 We'll call it a sprint, or a storm, or whatever's cool in project management. 02:39:47 heh 02:39:52 storm :) 02:40:26 #action jcamins will mark candidates for 3.10 that are in "Needs signoff" assuming he has power this week. 02:40:28 i love the bugs squash weekend idea 02:40:34 scrum storm sprint 02:40:40 a bug squash weekend sounds cool. 02:40:41 dont kick the ball 02:40:42 pass it 02:40:46 Anyone object to GBSW? 02:40:50 not me 02:40:51 What about starting on Friday and letting it run until Monday? Is that the suggestion? 02:40:56 This will make it easier for people to prioritize for the bug squashers. 02:40:57 thats the one BobB 02:41:00 BobB: exactly. :) 02:41:06 cool 02:41:09 koha bitzkrieg 02:41:38 O.o 02:42:15 So, let's vote? 02:42:16 'Shock and Awe!' 02:42:17 +1 02:42:20 +1 02:42:21 +1 02:42:33 +1 02:42:41 +1 02:42:56 +1 02:43:05 +1 02:43:14 +1 all weekend although I am otherwise committed 02:43:24 +1 02:43:41 +1 on friday 02:43:46 +1 02:44:09 #agreed Global bug squashing weekend starting november 9th 02:44:56 ok, anything else before we move on to the date for the next meeting? 02:45:29 Not from me. 02:45:42 ok 02:45:48 RDA and getting Koha ready for it ... 02:45:59 heh, thats more of a wiki page i think 02:46:02 ..that's a big one! 02:46:25 first they need to decide which rda :) 02:46:37 but yeah, can we move that one to the list? 02:46:42 and/or wiki? 02:46:49 http://wiki.koha-community.org/wiki/RDA 02:46:52 The MARC framewarks are years out of date. Funding disappeared for that work. 02:47:13 Yeah, I'd say the wiki is the place for that discussion. 02:47:54 Should we enter it as an agenda item for the next meetings though? 02:48:25 I'm not sure that would be productive before a list/wiki discussion has started 02:48:26 Prolly need to get more momentum first, via the wiki. 02:48:35 yeah 02:48:38 ^^ 02:48:41 So that we can briefly discuss progress and necessary actions? 02:48:44 then organise a meeting of ppl interested in it 02:48:49 speaking of which, we need to get the license upgrade conversation started again too 02:48:51 not really a general topic i dont think 02:48:52 Yeah, wiki and/or list, then when there's an action, discuss it in a general meeting. 02:49:17 We should be trying to push it so that people can at least have full RDA records from copy cataloguing when those start becoming widely available. 02:49:19 I feel like I need to know what exactly needs to be done? "RDA support" is pretty nebulous for me 02:49:34 the wiki page makes a few starting points 02:49:37 yep, those are all opinions 02:49:44 and ripe for putting on a wiki page :) 02:49:52 * rangi moves on 02:49:57 I am well informed about RDA and paid for some expensive classes. 02:49:59 #topic date for next meeting 02:50:14 (i warned you about letting me chair, i have an awards thingy to go to later) 02:50:43 the next time is 18:00 UTC 02:50:48 +1 02:50:49 I like the pace :) 02:51:05 so who has a date in mind? 02:51:25 early in the month please 02:51:34 5 Dec? 02:51:39 5/12? 02:51:39 0.416666666666667 02:51:40 5 dec 02:51:45 5 December - first Wednesday of the MOnth? 02:51:48 that's the first Wednesday in Dec 02:51:49 sounds good 02:51:50 sounds good. 02:51:53 lets vote 02:51:56 +1 02:51:57 +1 02:51:58 +1 02:51:58 +1 02:52:00 +1 02:52:01 +1 02:52:02 +1 02:52:05 +1 02:52:06 +1 02:52:14 +1 02:52:17 +1 02:52:21 +1 02:52:28 obama wins! 02:52:40 we can hope ;) 02:52:46 heh 02:52:47 Great voting! If only US elections were this simple ;-) 02:53:08 #agreed Next meeting is Decmber 5 18:00 UTC 02:53:28 ok, see y'all next 5 dec 02:53:29 December too 02:53:34 decememememeber 02:53:43 #endmeeting