18:04:41 #startmeeting General IRC Meeting 18:04:41 Meeting started Wed Sep 11 18:04:41 2013 UTC. The chair is cait. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:04:41 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:04:41 The meeting name has been set to 'general_irc_meeting' 18:04:48 #topic Introductions 18:04:49 #info wahanui, a bot that has become sentient 18:04:52 #info rhcl = Greg Lawson, Rolling Hills Consolidated Library 18:05:04 #info Galen Charlton, Equinox Software, 3.14 RM 18:05:05 please introduce yourself using #info 18:05:10 #info Nicole Engard, ByWater Solutions 18:05:13 #info Katrin Fischer, BSZ Germany 18:05:14 #info Margo Duncan, University of Texas at Tyler 18:05:15 #info 18:05:16 * thd is typing in lower case and yet the caps lock key is down. What causes that? 18:05:19 #info David Nind, Wellington, New Zealand 18:05:20 #info Kyle M Hall, ByWater Solutions 18:05:21 #info D Ruth Bavousett 18:05:23 #info Melissa Lefebvre, ByWater Solutions 18:05:25 #info Tomas Cohen Arazi, Universidad Nacional de Cordoba 18:05:27 #info Bernardo Gonzalez Kriegel, Cordoba, Argentina 18:05:28 #info Mark Tompsett 18:05:29 #info Jane Wagner, LibLime/PTFS 18:05:38 #info Fred King, Washington Hospital Center 18:05:41 Zeno Tajoli, CINECA, Italy 18:05:48 #info Mirko Tietgen, Berlin, Germany 18:05:51 Thomas Dukleth, Agogme, New York City 18:05:52 #info Agenda for today's meeting: http://wiki.koha-community.org/wiki/General_IRC_meeting,_11th_September_2013 18:05:58 tajoli: You forgot the #info. 18:06:01 #info Zeno Tajoli, CINECA, Italy 18:06:03 #info Thomas Dukleth, Agogme, New York City 18:06:10 Nate Curulla: Bywater Solutions 18:06:11 maybe that should have been #link :) 18:06:16 #info Brendan Gallagher ByWater 18:06:56 all done? 18:07:07 yeap 18:07:09 #topic Announcements 18:07:23 *waits* 18:07:53 no announcements? :) 18:08:27 #info David Noe, ByWater Solutions 18:08:28 I like space 18:08:29 "... in other news, the sky is blue today" 18:08:30 ok, is chrish around? 18:08:54 bgkriegel? 18:08:54 bgkriegel is on a signoff spree 18:08:57 :) 18:09:00 #info clintD, Anact, NZ 18:09:02 yes :) 18:09:11 #topic Update on 3.10 18:09:22 all is well, a little behind 18:09:28 but i will catch up 18:09:50 bgkriegel++ 18:10:21 thx for your work :) 18:10:26 iwill move to 3.12 then? 18:10:33 #topic Update on 3.12 18:10:41 tcohen: the stage is yours :) 18:10:57 3.12 is getting mature, no big bugs arise 18:11:09 #info Joy Nelson ByWater Solutions 18:11:14 i plan to cherry-pick dom indexing support for packages 18:11:23 but leaving grs1 as default 18:11:33 (dom-as-default would be a 3.14 feature) 18:11:43 sounds good to me 18:11:56 trying to catch up with master 18:12:01 and that's it :-D 18:12:20 thx tcohen - tcohen++ :) 18:12:36 #topic Update on 3.14 18:12:52 OK 18:12:59 #info Feature slush remains at 2012-09-25 18:13:09 #info Feature freeze remains at 2013-10-03 18:13:18 #info Architectural changes that are still on the table for inclusion in 3.14 are DBIx::Class and some sort of logging module 18:13:51 #info planning a big push, well, push next week after the QA sprint tomorroow 18:14:15 gmcharlt: can you define feature slush a little? want to prevent any misunderstandings if possible :) 18:14:56 #info RM emphasis for this release is reinforcing the QA process -- patches must have sufficient review to be accepted, and I'm heavily pushing for unit tests 18:15:27 gmcharlt++ 18:15:34 gmcharlt++ 18:15:49 cait: feature slush -- any new features that have hit passed QA by that date will be included in 3.14, assuming they don't raise signfiicant QA concerns on my part 18:16:29 thx :) 18:16:33 new features that have /not/ hit passed QA by feature slush are more liable to be left for the next release; if you want something that misses slush to make it in, you'll need to advocate for it 18:16:42 Why does slush have the name slush? 18:16:56 a partial freeze, of course 18:17:05 OK 18:17:37 also, another announcement -- I did not, of course, actually do a tarball of a pre-pre-alpha 18:17:48 instaed, I'll do so shortly after feature freeze 18:17:58 * thd was thinking of other domains in which slush is used. 18:17:59 any questions for me? 18:18:31 What is intended to be logged for a logging feature? 18:18:36 just a thank you for your work gmcharlt++ 18:18:55 The differce beetwenn slush and freeze ? 18:19:02 thd: system events, debug info 18:19:33 essentially, the idea in the patch series for bug 8190, but a version that supports syslog 18:19:34 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8190 enhancement, P5 - low, ---, jonathan.druart, Passed QA , Add a logging module to Koha 18:19:39 which is a sine qua non from my POV 18:19:43 gmcharlt: what's the road block for DBIx::Class currently? 18:20:04 is it just getting the DB foriegn keys worked out... 18:20:11 the current patch series needs some cleanup, and there are some FK to be added 18:20:12 just... :) 18:20:23 #info Owen Leonard, Athens County Public Libraries 18:20:26 also, the current patch series uses an otion that the DBIC maintainer specifically recommends against 18:20:35 ok subtract just from my statement cait :) 18:20:41 but be assured, it /will/ be in 3.14 18:20:44 i think it's doable 18:20:51 ok cool thanks galen 18:21:39 gmcharlt: have you seen tajoli's question? 18:21:48 ah, no, missed it 18:22:04 tajoli: any feature that is passed-qa by feature slush is elegible for 3.14, otherwise it isnt. 18:22:16 I did answer the question about the distinction between slush and freeze, if that's what you're referring to 18:22:23 then I missed it :) 18:22:39 frozen out, verses slushing in. :) 18:22:49 no, looks like tajoli had asked the same question you had asked, cait :) 18:22:50 ^verses^versus^ 18:23:00 if there are no more questions we can move on? 18:23:09 In fact yes, is the same question 18:23:29 #topic QA sprint day 18:23:51 we had a qa team meeting and discussed some ideas on how to get things moving and flowing a bit better 18:23:59 and one of the ideas that came up was a QA sprint day 18:24:04 #link http://wiki.koha-community.org/wiki/2013-09-12_QA_Sprint_day 18:24:19 mtj++ has added a wiki page for it and i hope that lots of QA will be done 18:24:30 but right now I think the needs sign off queue needs some work too... 18:24:32 sounds great, can we non-QA people help? 18:24:49 and for the big features you want to see moved through qa a second sign off would make help 18:24:52 or third.. fourth... 18:25:02 best with some notes what you looked at 18:25:19 there are some pretty big patches in the qa queue right now that take a lot of time testing 18:26:19 so it's not a GBSD - but with 169 bugs in needs signoff... and 51 of that bugs... 18:26:37 please feel free to test test test everything you can get your hands on :) 18:26:55 But will it be coordinated after GBSD's in the future? 18:27:15 it's something new we try out, we will have to see how it goes I think 18:27:18 I have an annucement about sign off 18:27:39 I think it actually might have started already in kiribati or so? 18:28:14 As CINECA we try to sponsor an our internal IT as 'sign offer' 18:28:17 #info if you care about a feature, don't hesitate to give it another good testing and sign off 18:28:40 tajoli++ 18:28:48 * oleonard dispatches the QA team to Kiribati in a black helicopter 18:28:55 heh 18:29:16 this person is working only on bugs in 'Need Sign Off' to test them 18:29:40 tajoli: sounds good 18:29:45 tajoli: you should probably send the person here 18:29:56 i was going to suggest that too :) 18:30:00 if there is no language barrier 18:30:20 Her name is 'Paola Rossi' 18:30:24 oleonard has the helicopter to transport the person. ;) 18:30:35 She speak Italian and English 18:30:59 tajoli: I think I have seen her name on some patches already? 18:31:01 But she doesn't have a big knowldge of Koha 18:31:06 or maybe i confuse her 18:31:42 She stritly follow the plan inside 18:32:09 maybe she can note that - or she can drop on irc and ask if there is something she is not sure about 18:32:16 or just note on the bug :) 18:32:16 she worked heavly on waterfall metodology 18:33:17 so, if you receive an email from her, answer as longer as you can 18:34:02 I think that in some month she could stard to write unit test also 18:34:09 but not now 18:35:14 So if tomorrow you have a simple 'sign off', write me and I send it to her 18:35:17 cineca++ 18:35:24 cineca++ 18:35:25 That all folk 18:35:26 any more questions and notes about this topic? 18:35:47 is there something people would like to see given top priority in QA? 18:35:51 your chance ;) 18:36:05 good qa 18:36:06 :P 18:36:23 drojf: excellent priority :) 18:36:35 cait++ 18:36:36 ok, i see that nancy has left a note on the wiki 18:36:37 drojf++ 18:36:40 packages patches 18:36:40 tajoli++ 18:36:51 tcohen: have been trying, but my vm ... was annoying 18:37:02 i'll be around to help on them if needed 18:37:03 cait, we contributed money towards Bug 2720, so we're anxious to see that pass 18:37:04 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2720 enhancement, P3, ---, kyle, Signed Off , Overdues which debar automatically should undebar automatically when returned 18:37:05 will try again soon, but would be nice if someone beat me to it 18:37:36 oleonard: ok 18:38:11 #topic KohaCon2013 18:39:10 #info news from nancy were sent to the mailinglist and are also noted on the agenda 18:39:19 it looks like we need more people reserving rooms at the hotel 18:39:34 hm 18:39:38 question 18:39:39 question is "What is the meaning of life, the universe and everything?" 18:39:40 so if you are guilty of going to KohaCon but not having done your bookings yet... 18:39:51 yes drojf? 18:39:51 drojf is from Germany and developing Koha on a raspberry pi! 18:40:02 The note does not give a reminder of the required number for meeting the hotel conditions. 18:40:14 i think the email had it 18:40:17 i don't think it is mandatory to sleep in that hotel, is it? so in theory, is it possible that there won't be a conference location if not enough people get rooms? 18:40:35 How many more reservations are needed? 18:40:44 I think they have to pay for the meeting rooms then 18:40:49 that's what i understood 18:41:20 ISTR it was 125, with about 100 registered. 18:41:21 and by they you mean you? 18:41:35 #link http://koha-community.org/koha-community-newsletter-august-2013/#kohacon13 18:41:48 As the hosts I think they would have to pay drojf 18:41:57 We don't have a mechanism set up to charge attendees 18:42:03 ok 18:42:04 or look for more sponsors 18:42:46 iw as a little confused by the calculation of every registration equals a room booked 18:42:52 drogf: The host goal is to break even on expenses. If anything goes wrong, then they loose. 18:43:32 i thnk we can move on? 18:43:35 yup 18:43:43 #topic KohaCon14 18:44:05 as you have probably seen, i have sent out another mail. proposals close 15 september 18:44:16 i set 18 UTC as the time, so there is one 18:44:24 we have two proposals 18:44:28 argentina and nigeria 18:44:58 and i do not expect another one coming up in the next three days, but who knows 18:45:19 i think that's about it 18:45:22 drojf: 2 will be easy for voting i think? 18:45:31 one would have been easy :) 18:45:35 true :) 18:45:38 ok, next topic 18:45:49 voting? 18:45:50 voting is http://ci.openstack.org/meetbot.html 18:45:53 #topic Actions from previous meeting 18:46:02 when will it happen? 18:46:08 tcohen: sorry, was too fast 18:46:13 np 18:46:48 drojf: have we talked about that yet? 18:46:57 we said beginning of october. sow e should probably fix that now 18:47:07 because next meeting will be after that 18:47:22 how long did we do the last times? open polls for a week or something? 18:48:00 maybe 2 18:48:07 Sorry for delay--just found e-mail from Nancy--need 125 rooms booked, didn't say how many had been (as of 28 August) 18:48:49 what about voting from 23september to 6 october? 18:48:55 sounds ok to me 18:48:59 +1 18:49:07 +1 18:49:12 +1 18:49:13 +1 18:49:14 that would be two weeks and cover the beginning of october part, but would not delay things unnecessarily 18:49:21 +1 18:49:25 have we figured out who will set up the vote? 18:49:31 +1 18:49:40 nengard can you? 18:49:41 i can do a limesurvey i guess 18:49:46 cool 18:49:47 drojf++ 18:49:54 oh darn she's out 18:50:45 #agreed the vote for kohacon14 will be open from 23september to 6 october? 18:51:03 hm missed to delete the questionmark 18:51:26 #action drojf will set up a limesurvey 18:51:29 ;) 18:51:43 ok, as there are actually no actions left from last meeting it seems 18:51:46 0/ 18:51:51 Also back under KohaCon related issues, my Filipino colleague is dreaming of how to make a 2015 proposal work. But no promises. :) 18:51:56 i think we can move on and decide a time and date for the next :) 18:52:29 isn't next meeting essentially KohaCon? 18:52:30 roughly in a month... before kohacon? 18:52:39 #topic Set time for next meeting 18:52:53 Do we want to set a time after the votes on KohaCon14 have been tallied? 18:52:54 Brooke: not everyone is going there - so i think having one before wouldn't hurt 18:52:59 and we are getting closer and closer to release 18:53:03 and deadlines 18:53:23 what about... october 12th? 18:53:29 drojf: which time is next? 18:53:46 why not just after kohacon14 voting end? 18:53:54 October 12 is a Saturday 18:54:06 oh sory, was looking at the wrong month 18:54:11 Wed. 9 October? 18:54:23 +1 18:54:26 +1 # 9 Oct 18:54:30 +1 18:54:39 What hour is next? 18:54:41 Where are we in the time rotation? What's next? 18:54:46 +1 9 October 18:54:47 That works without interfering with the travelling of those going to KohaCon. 18:54:50 +1 18:54:50 +1 10/9 18:54:53 i asked drojf - didn't work :) 18:55:07 10:00 UTC 18:55:25 sounds about right 18:55:26 ok 18:55:40 +1 October 9. 18:55:47 #info next meeting will be on 9th October, 10 UTC 18:56:02 thank you all for attending :) 18:56:10 cait++ 18:56:11 go testing patches! 18:56:13 thanks for chairing. *sucker* ;) 18:56:16 cait++ # thanks for chairing the meeting. 18:56:16 sorry, was in the kitchen :) 18:56:17 cait++ 18:56:18 cait++ 18:56:19 cait++ 18:56:19 #endmeeting