22:01:59 #startmeeting Development IRC meeting 15 April 2015 - part 2 22:01:59 Meeting started Wed Apr 15 22:01:59 2015 UTC. The chair is tcohen. Information about MeetBot at http://wiki.debian.org/MeetBot. 22:01:59 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 22:01:59 The meeting name has been set to 'development_irc_meeting_15_april_2015___part_2' 22:02:13 #topic Introductions 22:02:14 #info wahanui, a bot that has become sentient 22:02:38 please introduce yourselves using #info name 22:02:45 just like wahanui did 22:03:00 #info Tomas Cohen Arazi, Universidad Nacional de Córdoba 22:03:27 eythian, wizzyrea, rangi ? 22:03:43 #info Liz Rea, Catalyst IT 22:03:58 no rangi (away) or eythian (yet) 22:04:06 we'll wait then :-D 22:04:21 unless we can count as enough 22:04:25 hah 22:04:34 think it might be just you and me :) 22:05:00 ok 22:05:15 #topic RM 3.20 comments 22:05:21 have you read the logs? 22:05:35 i basically apologize (again) 22:06:18 I hadn't - I will go do now 22:06:21 and i've been (and will keep) using my office hours for RM duties 22:06:32 focused on bugfixes since last week 22:06:41 and enhancements follow 22:06:57 yeah, I think we can all understand and be sympathetic to your situation there 22:07:20 thanks 22:07:37 #info wizzyrea is sympathetic to tcohen 22:07:43 LOL 22:07:44 lol 22:08:01 #info: Freeze for 3.20: What's not passed QA by April 23nd, 9:10 Argentinian time... won't make it in 22:08:30 i set april 22nd as the cut for things to have the chance to get included 22:08:36 sensible 22:09:19 fwiw I have no opinion on moose, the others here might 22:09:21 as i will get to the office to get a screenshot of the pqa list at 9 am (ART) we shift to the next day 22:09:50 #info please let tcohen know if your feature needs attention to make it move, or have his opinion on the odds of it making into 3.20 22:10:21 #topic Bugs 22:10:56 on part 1 I proposed to approach fredericd about moving to Moo 22:11:22 khall asked people to give 13799 a chance to make it into 3.20 22:12:17 during part 1 we also talked about QueryParser 22:12:28 which has issues that need to be addresed 22:13:01 the question was wheter to put bugs that required not using QP on hold or not 22:13:22 and we agreed QueryParser having a bug shouldn't prevent us from having the feature 22:13:45 simply for my information 22:14:04 shoot 22:14:05 is it more desirable to have QueryParser on 22:14:10 generally? 22:14:44 because it could be a bit like the old "put it in bootstrap and backport it to prog" that we did for a while 22:15:27 personally, I feel like we should work on the more advanced framework 22:15:40 #info Robin Sheat, Catalyst IT 22:15:43 and port features back 22:15:44 QueryParser is a really good idea that we should be using more widely 22:15:46 but that's just me 22:15:49 but 22:16:02 people are afraid of getting into it to fix stuff 22:16:18 well then that's the problem that needs addressing, imo 22:16:38 Jonathan basically found a bug on the PQF driver Koha uses 22:16:45 and we need to address that, correctly 22:16:51 you are right 22:17:02 i'll try to 22:17:06 because people won't change to the new hotness if we let them get by wearing the old sweatpants, if you know what I mean 22:17:14 Joubu bets we won't be able to fix it on time 22:17:27 wizzyrea: I agree 22:17:55 much people are conservative about how they use their daily tools 22:18:10 anyway 22:18:24 that may be true, that we won't be able to fix it on time 22:18:36 but we mandated "features in bootstrap, back to prod" before, we could do it here too 22:18:39 just something to think about 22:18:52 we agreed we should push the feature, and fill a bug for QueryParser 22:19:07 QueryParser is off by default, so it is expected that too little people are using it 22:19:16 and that's because there are some outstanding bugs still 22:19:18 yeah, I think this instance is probably fine 22:19:43 does HEA have information about that? 22:19:48 it could be handy this time :-D 22:19:49 if it's a syspref, probably 22:20:18 #info Thomas Dukleth, Agogme, New York City 22:20:23 http://hea.koha-community.org/systempreferences > find in page QueryParser 22:20:32 59 with it enabled? 22:20:34 59 out of 63 have it disabled 22:20:39 0 22:20:49 other way round :) 22:20:50 and the rest: undef :-F 22:20:59 from what I said 22:21:08 that is, you're right 22:21:16 so yeah, nobody who's submitted using that. 22:21:18 :/ 22:21:35 so we are safe probably 22:21:38 yep 22:21:39 My understanding is that QP had some bugs that would make it more or less not work if you turned it on. 22:21:50 * eythian has been thinking about looking into it for ES work. 22:21:57 that's almost true 22:21:58 is it our intention to use it? 22:22:13 things like "right truncation doesn't work as expected" 22:22:22 I have no intention, I just wanted to get a good feel for it to see how useful it is/would be. 22:22:25 not things like "searches don't work" 22:22:37 ah, I thought it was closer to "not work" 22:22:40 tcohen: Are certain that a similar bug does not affect QueryParser in Evergreen? 22:22:59 i couldn't approach gmcharlt_ 22:23:10 but jcamins told me Evergreen has been using it for years 22:23:15 without any problems 22:23:22 so the issues are Koha specific 22:23:31 and related to our PQF driver 22:23:39 which narrows things a lot 22:23:48 to put it clear (my opinion on QP) 22:24:05 ok 22:24:14 our search code is full of ad-hoc stuff noone knows what to expect from it 22:24:24 imean, you read a line and you know what it does 22:24:39 but having the whole picture of all the border cases... difficult 22:24:40 yes, it is. 22:24:46 the idea about queryparser 22:25:05 is that it is an abstract query parser and translation engine 22:25:10 configurable using a yaml file 22:25:17 tcohen: Could the problems have been present but unnoticed by Evergreen users? 22:25:35 which I though would be good to generate ES queries, eventually. 22:25:53 ... or without complaint from Evergreen users even if noticed? 22:25:58 the problem is that parse trees traversal and what to do with it is not trivial as a regular expression 22:26:11 eythian: yes, a ES driver should do the job 22:26:36 thd: the problem jonathan mentioned today is trivial enough to make it clear they dont face it 22:27:40 I see problems everywhere I look but there are too many for me to have time to file bug reports about all of them ;) 22:28:09 thd: are you using QP? 22:28:18 tcohen: No. 22:28:30 heh 22:28:45 this is jonathan's post to koha-devel 22:28:52 explaining the bug http://koha.1045719.n5.nabble.com/QueryParser-does-not-manage-more-than-1-operator-td5823170.html 22:28:53 my only point is that if we have btter tech, we should be looking to use it 22:29:02 wizzyrea: we should 22:29:04 and improve it 22:29:16 and not languish because it's more comfortable. 22:29:31 that's all I'm getting at. 22:29:34 that's the right attitude 22:29:36 wizzyrea++ 22:29:41 wizzyrea++ 22:30:19 unfortunately enforcing that comes from the top :/ 22:30:27 and that's an unpleasant thing. 22:30:50 #info wizzyrea reminded us that the project evolves because of our commitment to do good stuff, not to let ourselves languish in favor of comfort 22:31:21 wizzyrea: but... we don't have a top! 22:32:04 In the early meeting, ColinC reported that he thought that QueryParser would break multiple system preferences as it is. 22:32:38 I am certain that is true, it could be a goal of a future release to tidy all that up perhaps? 22:33:19 there aren't *that many* open bugs for QueryParser 22:33:28 The fault may be in the legacy query code which many people have had difficulty deciphering. 22:33:29 but we definitely need someone to work on that 22:33:32 or (sorry eythian) to make sure that the next iteration of searching in Koha doesn't have the same issues 22:33:33 bug 12742 22:33:34 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12742 enhancement, P5 - low, ---, gmcharlt, NEW , Omnibus: QueryParser 22:33:53 or rather, to learn from our mistakes 22:34:12 tcohen: ColinC was reporting his suspicion for things which may not have been properly discovered and reported. 22:34:15 searching for ES will be pretty easy to replace with something better. 22:35:03 eythian: that's awesome to hear 22:35:06 *read 22:35:47 ok, we need to move on, unless eythian, wizzyrea, thd or rangi (if absent... beware) volunteers to work on QP 22:35:50 at the moment, it's mostly compatibility layers with the C4::Search way anyway. 22:36:41 eythian: on my work for a more reasonable way to filter data, i came with a Koha::Search::Result class (or something like that) 22:36:59 "filter data"? 22:37:07 that only puts some stuff together (bitstream, metadata format, etc) 22:37:32 I think we should make broader use of Koha::RecordProcessor 22:37:39 with Koha::Filter::* 22:38:15 for example, if you need to apply a policy about fields/subfields visibility 22:38:22 then have a filter that does that 22:38:23 ah yep 22:38:52 prepare data for display in results context, have a specific filter that applies the xslt, etc 22:39:20 yeah, build a filter chain 22:39:25 and i wrote that tiny class that encapsulated both the bitstream, and the metadata format of the bitstream, thinking of having JSON data, etc... 22:39:34 eythian: you're damn right 22:40:01 ok, diverted a lot 22:40:32 moving on 22:40:49 22:40:52 22:41:08 i was worried about the patches waiting for QA right now that introduce new fields on the XSLT 22:41:39 and we concluded that adding fields there is not a problem as long as they are not added to the frameworks and/or enabled for visibility 22:42:12 as long as the visibility rules are applying correctly, this is sensible to me. 22:42:12 yeah 22:42:24 (as far as I know they are) 22:42:43 wizzyrea: they aren't, but shhh 22:42:52 hrmpn. 22:43:08 hrmph. 22:43:19 :-P 22:43:26 hmpf 22:43:41 ohh you got a double hmpf. 22:43:44 they are, until someone has a regression test for that 22:43:54 :-P 22:44:23 who's got the double? 22:44:25 me? 22:44:26 hmmm... tcohen is 122 22:45:01 wahanui: tcohen is actually 123 22:45:02 ...but tcohen is obsessed with packages' scripts|122|obsessed with automated testing :)|king of the lab... 22:45:13 ok 22:45:30 you obsess a lot. 22:45:31 :) 22:45:59 i think we agree that if view policy is working, there's no problem adding fields to the xSLTs, right? 22:46:05 yep 22:46:08 great 22:46:25 on part one we mentioned bug 10480 22:46:27 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10480 enhancement, P5 - low, ---, m.de.rooy, Signed Off , Improvements for framework plugins in cataloguing/item editor 22:46:45 that does an interesting job refactoring the cataloguing plugins code 22:46:52 adding wings to them 22:47:15 i mentioned because (1) it looks great and (2) it had been signed by two QA members 22:47:25 so the SO status was strange 22:47:38 but Jonathan said he wanted more eyes on it 22:47:44 and khall volunteered 22:47:47 khall++ 22:48:35 khall++ 22:49:06 #topic Big stuff we are working on 22:49:21 we talked a bit about the REST api implementation 22:49:36 because we needed to catch up 22:49:43 I had a look at that yesterday, the dependencies are awkward and annoying 22:49:58 jonathan mentioned the work on bug 13799 needs signoff 22:49:59 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13799 enhancement, P5 - low, ---, julian.maurice, Needs Signoff , Add base for building RESTful API 22:50:19 it's not near a state for signoff, imo 22:50:28 and khall said he approached julian about some called "Robin"'s comments 22:51:19 eythian: you mean they are not in jessie? 22:51:22 he's a taskmaster, that packaging manager of ours. 22:51:26 they're not in anything 22:51:33 :/ 22:51:51 they're not even in any unreleased version 22:52:20 ^ this seems like perhaps not the best situation ever. 22:52:27 mojolicious and swagger2 22:52:39 older mojolicious is in debian, swagger2 isn't at all. 22:53:12 the next biggest issue is that the code has no documentation. 22:53:33 * tcohen hasn't had the time to take a look yet 22:53:36 http://wiki.koha-community.org/wiki/New_REST_API_RFC 22:53:40 but anyway, it's documented on the bug :) 22:53:57 (rather, my issues are documented on the bug) 22:54:04 but we agreed we don't need the latest mojolicious 22:54:23 tcohen: swagger2 declares that it depends on mojolicious 6.0 22:56:10 * tcohen is stuck 22:56:13 eythian: Which code has no documentation? 22:56:37 i couldn't find that dependency, but i will sure take a look at the office tomorrow 22:56:52 http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=36705&action=diff <-- see for example the perl files here 22:57:34 eythian: ok 22:57:45 i'm worried, but we'll sort it out, for sure 22:57:50 yeah 22:58:24 I'm having a quick go at building mojolicious 6, it might be that it's easy, but if it can't backport to wheezy, then that's simply not an option. 22:59:31 ok, lets keep positive 22:59:42 butterflies! 22:59:42 khall nudged julian about those concerns 22:59:57 eythian: Is jessie not forthcoming at the end of the month? 23:00:00 we'll talk about that before the end of the week for sure 23:00:01 thd: it is 23:01:42 jessie == systemd == unix is dead 23:01:47 23:02:19 ok 23:02:22 anything else? 23:02:29 eythian: about ES' 23:02:29 squeeze is being shot in the head 23:02:38 come 3.20 23:02:39 * thd in no hurry to discover jessie bugs. 23:02:41 ah *that* 23:02:52 * eythian decides unilaterally 23:03:05 on the previous dev meeting we agreed that 3.20 wouldn't support Squeeze 23:03:14 \o/ that was easy. 23:03:27 you did? 23:03:28 eythian: Is squeeze not being maintained until 2016 even if not for Koha? 23:03:32 * eythian can't find it in the logs 23:03:38 thd: it is 23:03:55 thd: but if you want to backport everything that newer koha wants, be my guest :) 23:04:06 * tcohen can't find them ,but is pretty sure 23:04:58 * thd just wants to avoid upgrading some squeeze systems to wheezy too suddenly 23:05:05 is it valid if the RM dreamed about a vote on something? 23:05:38 yes 23:05:52 thd: wheezy was released nearly two years ago, you may need to refine your definition of sudden :) 23:05:55 heh, thanks bag 23:06:17 tcohen: maybe it was in the main meeting 23:06:35 I seem to remember something about it too 23:06:58 or after you closed the meeting. I don't see it in the logs but whatever. 23:07:01 eythian: My definition is not being forced to do by the end of the month something which I should have done two years ago :) 23:07:18 thd: well, you'll only have to do it in order to upgrade to 3.20 anyway 23:07:39 support in 3.18 etc. will remain 23:08:06 eythian: I mean my non-Koha backup systems, etc. 23:08:57 eythian: i'll send a new email about this to koha-devel, I think no one would disagree 23:08:58 ah right. If it's any consolation I have an 8.04 box still running. 23:09:14 * tcohen too 23:09:29 tcohen: I was going to announce it on both lists to make sure everyone knows about it. 23:09:30 ah, no 10.04 23:10:34 go ahead 23:10:39 cool. 23:10:52 you could avoid the "unilateral" speech just in case 23:11:02 something more politically correct maybe? 23:11:05 :-D 23:11:55 oh sure 23:12:04 that's just for you people :) 23:12:19 "Hi, it's not possible or even reasonable to continue supporting squeeze, so we're not going to do it anymore. eom." 23:12:53 the release notes will mention it too 23:13:06 eythian: go ahead 23:13:12 cool 23:13:26 we will blame you if something goes wrong about the announcement anywayu 23:14:05 ok 23:14:10 moving on then 23:14:16 as I said on part 1 23:14:29 cut date -> next wednesday 23:14:38 wfm :) 23:14:41 beta -> next weekend (after the cut) 23:15:10 next dev meeeting probably wednesday week after freeze - april 29 23:15:15 objections? 23:15:34 tcohen: I'd really like to get you to have an eyeball over bug 13979 and put it in, btw. 23:15:35 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13979 major, P1 - high, ---, robin, Signed Off , Packages uninstallable on Debian Jessie 23:15:37 that gives us time to coordinate efforts toward stabilization if needed 23:15:56 tcohen: What happens during Wed. before Wed. has ended? 23:15:57 * tcohen adds it to his pocket 23:16:24 thd: i don't follow you sorry 23:17:02 tcohen: If something passes QA on Wednesday would it have a chance of qualifying? 23:17:09 of course 23:17:34 thursday 9:10 am argentinian timezone is the actual cut 23:18:07 [off] you could try to brive me anyway 23:18:11 :-P 23:18:24 Wow, many hours of UTC time for those who can stay awake doing QA :) 23:18:55 yeah 23:19:10 #info next dev meeeting probably wednesday week after freeze - april 29 23:19:54 any other thing? 23:20:01 to talk about? 23:20:14 ES is moving along. About to start on staff client 23:20:24 otherwsie, nothing to report from me 23:20:25 tcohen: Did we skip some items? 23:20:26 eythian: awesome! 23:20:26 That'll be $1 for the awesome jar, tcohen 23:20:58 yes good news 23:20:59 good news is it looks like it's running properly. 23:20:59 thd: i think we skipped the country of production positions talk 23:21:26 production positions? 23:21:49 the item was 23:21:50 Language and country fixed size field positions: MARC flavour-specific vs. a general approach (Bug 13912) 23:21:51 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13912 enhancement, P5 - low, ---, gmcharlt, Failed QA , System preference for default place of publication (country code) for field 008, range 15-17 23:21:52 tcohen: That is fine, I had an idea about how to keep it with the frameworks without putting it in the frameworks. 23:22:10 *ublication 23:22:23 is it failed? 23:23:03 tcohen: It passed but I toggled the state in ignorance of the correct procedure when adding my comments this morning. 23:23:11 wizzyrea: my question was wheter that kind of sysprefs could be set framework-wise, and in a MARC-dialect agnostic way 23:23:42 aha 23:24:13 Additional problem is having any associated value list translatable. 23:24:32 right 23:25:34 ok, i'll finish the meeting now, i need to leave and you can keep discussing it if you want to 23:25:35 I have the idea of setting a preference per Koha MARC framework without storing the value in the framework itself. 23:25:47 how would you do it? 23:26:32 Maybe as a system preference but called for each bibliographic framework. 23:27:08 thd: i think we should discuss it on a bug or RFC 23:27:21 cait mentioned that YAML for system preferences is being translated. 23:27:44 tcohen: It certainly needs some more careful consideration. 23:28:07 i need to take care of home stuff (i've just arrived and it is 20:30 already) 23:28:14 so 23:28:25 thanks everyone for your time and ideas/opinions 23:28:34 we'll do this more often 23:28:37 again 23:28:38 :-D 23:28:42 later 23:28:47 #endmeeting