19:03:34 #startmeeting Development IRC meeting 27 February 2019 19:03:34 Meeting started Wed Feb 27 19:03:34 2019 UTC. The chair is kidclamp. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:03:34 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:03:34 The meeting name has been set to 'development_irc_meeting_27_february_2019' 19:03:35 kidclamp: Joubu? 19:03:35 Joubu is, like, kidding, right ;) 19:03:43 #chair Joubu 19:03:43 Current chairs: Joubu kidclamp 19:03:47 #chair cait 19:03:47 Current chairs: Joubu cait kidclamp 19:03:49 cait: The API nomenclature is already very close and we may have already deviated from the GUI in one place for clarity which might mean adjusting the GUI. 19:03:54 #topic Introductions 19:03:59 #info Tomas Cohen Arazi, Theke Solutions 19:04:05 #info Nick Clemens, BYWater solutions 19:04:16 I will have to leave ~30 mins 19:04:27 #chair tcohen 19:04:27 Current chairs: Joubu cait kidclamp tcohen 19:04:31 #info Thomas Dukleth, Agogme, New York City 19:04:35 #info Michal Denar, JohaCZ 19:04:40 #info Jonathan Druart 19:05:13 #info David Nind, Wellington, New Zealand 19:05:23 KohaCZ, damn phone keyboard 19:05:30 #info Katrin Fischer, BSZ, Germany 19:05:42 #info Josef Moravec, Municipal Library Ústí nad Orlicí, Czech Republic 19:07:50 #link https://wiki.koha-community.org/wiki/Development_IRC_meeting_27_February_2019 19:08:10 #topic Announcements 19:08:14 Anyone have something? 19:08:59 sounds like a no 19:09:01 #topic Update from the Release Manager (19.05) 19:09:16 kidclamp: your turn 19:09:24 Hi All! 19:09:31 Trying to catch up with the queue 19:09:37 Some failures on Jenkins 19:10:03 that's wrong, I have just attached a follow-up to fix them :) 19:10:07 Looking at Mana we need some fixes, the searchign is bad' 19:10:14 Joubu++ 19:10:22 Joubu++ 19:10:25 ES, going to push 19575 - I talked with Ere and things seem okay now 19:10:27 Joubu++ 19:10:28 QA is unhappy about that, please fix 19:10:36 (Mana) 19:10:37 in another meeting, so a bit scattered, but things are going well 19:10:51 bug 19575 19:10:51 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19575 major, P5 - low, ---, glasklas, Passed QA , Use canonical field names and resolve aliased fields 19:10:58 thank you all for hard work and keep them copming :-) 19:11:00 #info Mana has known bugs that must be fixed as soon as possible 19:11:34 #topic Updates from the Release Maintainers 19:11:36 rmaints? 19:11:36 rmaints is ashimema and fridolin are the rmaints 19:11:46 lukeg jessem 19:11:51 lukeG1: 19:11:58 Hi 19:11:58 bidet, JesseM_ 19:12:21 #info Martin Renvoize , PTFS Europe 19:12:32 Things are going very well! Just trying to keep up wiht ashimema 19:12:34 ;P 19:12:36 Sorry I'm late... Bedtime duties 19:12:44 #info Jesse Maseto. BWS 19:12:53 rmaints is ashimema (18.11), lukeG and JesseM (18.05), and fridolin (17.11) 19:12:58 Snap only it's trying to keep up with kidclamp 19:13:14 nope, things are not well, critical bug (data lost) is in latest 18.05 and 17.11 19:13:29 #info 18.11.03 was released on schedule end of last week 19:13:31 bug 22395 is the one 19:13:31 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22395 critical, P5 - low, ---, koha-bugs, ASSIGNED , Data in 245 field (subfield a or b) will be deleted if it has Quotation Marks 19:13:39 it must be reverted to be fixed in the next releases 19:14:00 as well as, I think, advertised in the general mailing list 19:14:28 #info code is being pushed fast for the next release.. lots of small bugfixes, nothing revolutionary. 19:14:29 or new release including only this patch? 19:15:09 we need to release a patch version 19:16:18 coordination? 19:17:03 Yes we'll revert 21986 in 18.05.x 19:17:14 #info critical bug (22395) in latest 18.05 and 17.11 - Rmaints coordination would be great (new release and mails to the general ML) 19:17:40 Sorry I didn't spot that and send a warning down whilst I was pushing to on my branch guys 19:17:52 Easy miss 19:18:35 moving on then? 19:18:43 #topic Updates from the QA team 19:18:47 qa_team? 19:18:47 rumour has it qa_team is cait alex_a jajm khall josef_moravec ashimema Joubu marcelr tcohen rangi 19:18:53 you are qa team :) 19:19:04 😀 19:19:05 numbers have been going down - quite happy about that 19:19:28 I am slowly back, too many things I would prefer to not touch in the NQA queue 19:19:30 currently 37 in the queue, some older things, but mostly ILL related 19:19:42 we are working through the ILL 'graph' at the moment, so they will move at some point 19:19:44 Joubu's been on form the last few days.. catching lots.. thanks Joubu 19:20:16 ashimema: Joubu - something to add? 19:20:20 some of them are blocked by bug 20750 19:20:20 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20750 enhancement, P5 - low, ---, andrew.isherwood, Failed QA , Allow timestamped auditing of ILL request events 19:21:01 #info QA queue is under control, currently at 37, oldest bugs are mostly ILL, ILL dependency tree is worked on 19:21:16 yes, that is the next we need to resolve 19:21:20 Nothing to add from me.. I'm slowing down on QA a but these next few days.. building up motivation to look at some of the more challenging ones again soon 19:21:34 12 majors waiting for SO 19:21:56 #topic General development discussion (trends, ideas, ...) 19:22:16 #topic API - Holds suspension endpoint 19:22:16 * ashimema will tackle a few on that list soon hopefully 19:22:25 #link https://wiki.koha-community.org/wiki/Holds_suspension_endpoint_RFC 19:22:36 Are we ready to vote? 19:23:02 yes 19:23:03 yeah, NSO queue is bad (needs devs to look at a lot of them) 19:23:04 there are disagreements 19:23:10 tcohen here 19:23:13 Yes 19:23:33 I should abstain 19:23:34 he 19:24:18 what about the discussion? 19:24:41 There's some more detail in the minutes of the last meeting I think 19:24:46 tcohen: Was retun_date intended to be distinct from checkin_date? 19:25:02 thd: this is the other endpoint 19:25:06 But basically it boils down to the date field names 19:25:09 our API is resource-ooriented 19:25:23 thd: we are looking at the hold suspension currently 19:25:26 so we are talking about a 'hold suspension' 19:25:27 oops, sorry 19:25:39 i thin we had n agreement last meeting 19:25:44 or almost 19:25:45 in the context of a 'hold suspension', 'expiration_date' seems more appropriate 19:25:49 i won't insist on renaming it :) 19:25:50 * thd read too quickly 19:26:09 tcohen: could you edit the wiki page and then we vote? 19:26:20 in the meanwhile we are moving to the next one? 19:26:23 I'd actually go to far as to say I'd like it even more generalised 19:26:33 ashimema: shoot 19:26:44 end_date? 19:26:46 start_date and end_date where it makes sense 19:26:56 I like it too 19:27:13 That way you can practically guess the fields for your context sensitive endpoint 19:27:25 seems good for me too 19:27:27 i like it as well, but do we have a start date? 19:27:37 we don't, just an end_date 19:27:38 Devs are lazy.. having to refer to the docs to get that obscurely named field name right is just annoying.. hehe 19:27:52 ok, vote on end_date 19:27:56 worry about start date later? ) 19:27:57 yes 19:28:01 Awesome 19:28:19 +1 19:28:22 wiki adjusted 19:28:31 Awesome 19:28:50 Shall we vote then.. sounds like a consensus to me 19:28:53 sounds weird to me, but fine 19:29:06 the #vote syntax? 19:29:10 * ashimema is struggling to type fast on his phone whilst also attempting to read a bedtime story 19:29:26 #vote do you agree with the "Holds suspension endpoint RFC" Y/N? 19:29:29 gotta run 19:29:33 #vote Y 19:29:34 #vote yes 19:29:39 #vote yes 19:29:51 #vote yes 19:29:52 #vote yes 19:29:59 #vote yes 19:30:00 you need to vote the options he gave 19:30:03 yes won't work 19:30:04 #vote yes 19:30:11 #vote Y 19:30:17 #vote Y 19:30:19 #vote Y 19:30:21 #vote Y 19:30:32 #vote Y 19:30:34 sorry 19:30:40 #endvote 19:30:41 #vote Y 19:30:56 #info "Holds suspension endpoint RFC" agreed! 19:31:15 Woopie 19:31:20 #topic API - Checkouts endpoint 19:31:28 #link https://wiki.koha-community.org/wiki/Checkouts_endpoint_RFC 19:31:35 it didn#t summarize 19:31:43 not sure, maybe need to phrase it a little different? 19:32:10 wiki correction checked_out_date => checkout_date? 19:32:25 or use "startvote" command ;) 19:32:25 * ashimema hasn't fully read that one yet.. my bad 19:32:42 tcohen: Was retun_date intended to be distinct from checkin_date? 19:33:00 oh yes, and comma separated :) 19:33:26 I am ok with checkout_date 19:33:27 thd: what do you mean? 19:33:27 i guess do you mean is reserves.tt the only place where a hold gets placed? 19:33:56 I've had some suggestions 19:34:06 return_date > checkin_date - or removing it 19:34:11 it only has a role in old_issues 19:34:24 so would be needed for the checkin api, but not for checkouts actually 19:34:40 and simplify checked_out_date to checkout_date 19:34:46 cait: we would like to extend the endpoint to be able to return checked in checkouts in the future somehow 19:34:59 once the tables are merged 19:35:01 In the widest context returning an item via post, dropbox, etc. is different activity from checking an item back into the system after the item has been collected. 19:35:03 return checked in checkouts? ;) 19:35:13 would that not be a separate endpoint? 19:35:32 cait: that's what we need to discuss here 19:35:38 ah ok 19:35:41 are we planning on merging the tables? 19:36:12 updated wiki to checkout_date and checkin_date 19:36:16 IIRC we decided to merge the old_ deleted_ tables, so yes 19:36:54 koha doesn#t differentiate at the moment 19:37:09 in action logs, do we want to have interface api ? 19:37:36 i'd not make the api dependent on the merge 19:38:37 "403 is valid response code if you try to renew a non-renewable loan, but error codes should not be used to indicate a status. So the renewability check should rather return 200 and an actual response telling if renewal is possible." 19:38:38 cait: bug 18205 19:38:38 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18205 enhancement, P5 - low, ---, lari.taskula, Signed Off , REST interface to Koha::Logger 19:38:41 this has not been addressed 19:39:03 josef_moravec++ 19:40:01 Joubu: right, current implementation even does return 200 and true or false 19:40:32 josef_moravec: it needs to be addressed on the RFC 19:40:55 RFC changed now 19:40:57 * thd prefers caits suggestion of allows_checkout instead of renewability as an extensible nomenclature. 19:42:12 hm, true or false on renewability endpoint i not enough maybe... 19:42:14 ... hence also allows_renewability 19:42:37 should also say how many renewals are available from limit 19:42:43 there is also " Maybe instead of renewability... loanability... we should do something like: allows_renewal, allows_checkout ... and it would be more clear. " 19:42:59 what thd said, I am too slow 19:43:53 I am not against such a change 19:43:58 * thd restating prefers cait's suggestion of allows_renewability, and allows_checkout instead of renewability as an extensible nomenclature. 19:44:05 allows_checkout, allows_renewal... allows_hold? allows_article_request? i wonder if checkouts is the right spot 19:44:15 it sounds more like... an item status 19:44:17 * ashimema has had to dissapear.. sorry 19:44:52 * tcohen has to pick up wife for a doctor check 19:44:56 Do we postpone the vote to the next dev meeting? 19:44:56 hm is on hold 19:45:02 maybe needs some more fleshing out 19:45:07 tcohen, what do you think? 19:45:13 * ashimema will read later.. but trusts you guys 19:45:17 i am fine with what's in the checkouts table and mapped, i am nto sure about the status things 19:45:24 cait: We have https://wiki.koha-community.org/wiki/Availability_endpoints_RFC . 19:46:05 thd: not ready for vote yet 19:46:23 #info vote about "Checkouts endpoint RFC" postponed to the next meeting, some adjustements are needed. 19:46:45 #topic Bug 22407 - Use DBIC relations for fetching related object 19:46:45 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22407 enhancement, P5 - low, ---, koha-bugs, NEW , OMNIBUS: Use DBIC relations to fetch related object rather than searching for the object 19:46:54 However, as cait points out we are voting on something which includes parts which might be better placed in availability 19:47:28 ... which cait characterised as item status. 19:49:18 Bug 22407 - there was a discussion about how we should access the related objects, from our Koha::Object 19:49:30 It seems that there is no guidelines ready yet to be voted. 19:49:54 I invite you to read and continue the discussion on the bug, we may be ready for the next meeting 19:50:32 #info Bug 22407 is going to state on how we should access the related objects, from our Koha::Object (see comment 3 for examples) 19:51:08 #topic Bug 22417 - Give a try to RabbitMQ (background jobs rewrite) - POC! 19:51:08 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417 enhancement, P5 - low, ---, jonathan.druart, In Discussion , Delegate background jobs execution 19:51:45 last minute topic, I have sent an email to the list. Please read the comments on the bug report. You can also test the patch if you want to see them moving forward 19:51:59 I like that Joubu 19:52:16 I am going to try it in near future 19:52:35 still lot of works to do, but if we agree I can continue implementing that. And maybe make it ready for 19.05 19:52:40 thanks josef_moravec 19:53:01 I think we really need something like that 19:53:35 Did everybody leave already? 19:53:40 no 19:53:52 moving on? 19:54:15 #topic Review of coding guidelines 19:54:40 #info as bug 22026 has been reverted, update for PERL2 is obsolete 19:54:40 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22026 enhancement, P5 - low, ---, jasmineamohia.student, REOPENED , Remove `use Modern::Perl` from Koha::REST::classes 19:54:57 bug 22026 was reverted from master 19:54:59 #action Joubu update PERL2 to reflect revert of 22026 19:55:00 Back 19:55:21 ashimema: something to tell us? 19:56:14 #topic Set time of next meeting 19:56:32 are we sticking to every 2w? 19:56:59 it might be good to move on with the apis 19:56:59 I missed the last ones 19:57:07 Joubu: I think so 19:57:26 13 March, 14 UTC? 19:57:30 cait: I am trying to work on that when time permits 19:57:37 Will read back later 19:57:38 Sorry I missed what looks like a long discussion 19:57:39 I commented on the bug to revert.. 19:57:39 I still don't like the use of modern perl rather than being more explicit.. but it's not so bad that I wanted to break the tests or require packaging a new perl critic 19:58:24 #info Next meeting: 13 March 2019, 14 UTC 19:58:33 everybody agrees on that? 19:58:41 * josef_moravec agrees 19:58:42 yes 19:58:45 #endmeeting