20:59:29 #startmeeting Development IRC meeting 27 June 2018 20:59:29 Meeting started Wed Jun 27 20:59:29 2018 UTC. The chair is Joubu. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:59:29 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:59:29 The meeting name has been set to 'development_irc_meeting_27_june_2018' 20:59:38 #topic Introductions 20:59:43 #info Jonathan Druart 20:59:47 #info Tomas Cohen Arazi 20:59:48 #info Owen Leonard, Athens County Public Libraries, USA 20:59:57 #info Josef Moravec 21:00:05 #info Jon Knight, Loughborough University 21:02:47 #topic Announcements 21:02:47 New Zealand, where are you? 21:02:53 Anyone have something? 21:03:39 nope 21:04:20 #topic Update from the Release manager (18.11) 21:04:22 kidclamp: ? 21:05:01 #topic Updates from the Release Maintainers 21:05:04 rmaints? 21:05:10 ashimema1: ? 21:05:12 ashimema: ? 21:05:30 he's on the apologies 21:05:41 #topic Updates from the QA team 21:06:08 I have almost FQA bug 20271 21:06:08 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20271 major, P1 - high, ---, oha, Signed Off , Merge deleted biblio, biblioitems, biblio_metadata, and items tables with their "alive" cousins 21:06:11 It seems that it's not ready yet 21:06:22 we will need more pair of QA eyes on this one 21:06:32 I am waiting for author's answer 21:07:02 There are 10 major bugs waiting for SO 21:07:07 nothing else from me 21:07:15 Joubu: I will retest it, I have feeling that i didn't see deleted items in zebra search results... 21:08:21 I did not test it much, but it seems that we will need to test it a bit more before pushing it 21:08:26 but you are right, it will need even more attention... 21:09:24 ha, maybe I should add: 21:09:43 I have attached 2 patches on bugs related to bug 21010 21:09:43 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21010 enhancement, P5 - low, ---, koha-bugs, NEW , Add a script to search for data inconsistencies 21:09:54 I'd like to get feedback on the idea 21:10:06 Joubu: I signed them ;) 21:10:25 maybe it's redondant with the about page, or we will want to move some checks to the script 21:10:34 josef_moravec1: indeed, thanks :) 21:10:34 I like that idea and this is good start 21:10:38 * cait waves 21:11:08 Hi cait, do you have update for the QA team topic? 21:11:23 ah sorry, just got home 21:11:47 I could even imagine to have it as tool in UI - with links and fixes where possible 21:12:04 nothing special i tihnk 21:12:09 josef_moravec1: much more work :) 21:12:33 Joubu: true, but may be much more usefull ;) 21:13:05 yep, I would first start with a simple script, then identify the different needs/checks we want to implement 21:13:22 I agree ;) 21:13:46 moving on? 21:13:47 Will this just before database bugs, or will it include things like duff MARC fields? 21:13:59 s/before/be/ 21:14:20 yes 21:14:27 It's for DB inconsistencies 21:14:30 OK 21:15:13 the 2 checks so far are 1. authority types that are used in auth_header.authtypecode but not defined as authority types 21:15:45 and 2. items.holdingbranch and items.homebranch that are not defined (set to NULL in DB), that will make some script explode 21:16:11 it will help people identifying consistencies in the migrated data 21:16:23 It'll be interesting writing unit tests for this script. :-) 21:16:56 yes, the script is 20 lines long. As I said previously I would like to get feedback first 21:17:13 then I could spend more time if we identify more checks to implement 21:17:56 For instance we will certainly want one for the item types (depending on the pref) 21:18:23 if you have more ideas you can open bug reports and link them with 21010 21:18:39 #topic General development discussion 21:18:51 #topic REST API 21:18:53 and vs && 21:18:55 haha 21:19:18 it's not in the agenda ;) 21:19:23 he 21:19:26 about the API 21:19:41 On implementing bug... 21:19:52 bug 20942 21:19:52 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20942 new feature, P5 - low, ---, tomascohen, Signed Off , Add route to get patron's account balance 21:20:17 I tried to imagine the use case for rewriting the patron's account balance page 21:20:29 and noticed we really needed a more useful spec 21:20:32 so I changed it 21:20:39 and already implemented the change on the bug 21:20:44 I just wanted to let you know 21:20:56 and have you comment on that if you feel like 21:21:23 I've been looking at accountancy software and how they display this kind of stuffs, 21:21:25 ok, so no behaviour's changes expected with these changes? 21:21:28 and realized it is the way to go 21:21:46 it is basically splitting account lines into debits and credits 21:22:00 (so when they write a new UI don't need to think about Koha's internals) 21:22:02 forget this last question 21:22:24 and then I have another subject, which is more related to accounts 21:22:26 but required 21:22:29 for the API 21:22:46 Handy for GDPR output as well (eg Bug 20028) 21:22:46 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20028 enhancement, P5 - low, ---, koha-bugs, NEW , Export all patron related personal data in one package 21:23:09 basically, when it comes to credits 21:23:14 the current codebase uses 21:23:23 accounttype + payment_type 21:23:39 accounttype uses hardcoded values 21:23:48 and payment_type allows more flexibility 21:23:55 through authorized values 21:24:00 I'll make it short 21:24:05 debits are a problem :-D 21:24:18 because we have hardcoded values AND user-defined ones 21:24:23 both in accounttype 21:24:29 I would love to 21:24:39 - Create a debit_type column 21:24:44 it's what my banker told me as well 21:24:52 - Identify all hardcoded values 21:24:59 - Move all user-defined values to debit_type 21:25:12 and have it behave like credits/payments 21:25:26 Joubu: :-P 21:25:42 does anyone see a problem with this? 21:26:00 What will it break? :-) 21:26:26 I think it won't, greenjimll :-D 21:26:41 I like it already then. :-) 21:26:46 it will break things, but we do not know yet, it's Koha's fun 21:27:20 user-defined values? 21:27:23 I like that idea too 21:27:26 it will be covered by tests and they will pass, no matter they break all the other stuffs 21:27:30 hahaha 21:27:48 Joubu: for credits we have PAYMENT_TYPE, and for debits is MANUAL_INV 21:27:56 both are used for the same 21:28:05 but debits don't have a column 21:28:44 if you feel like something might not suit your POV, please pm me or better send me an email 21:28:59 I will just implement it and put it in consideration of the rest of the devs anyway 21:29:28 I've been looking at Evergreen interface (thanks to jeff) so I found nice things they do, and things we have they don't 21:30:13 ok, that's all from me 21:30:28 the /patrons/{patron_id}/account endpoint is ready for QA 21:30:32 #topic Review of coding guidelines 21:30:43 #topic Documentation - Cookies 21:30:51 #link https://wiki.koha-community.org/wiki/Coding_Guidelines#Documentation_.28DRAFT.29 21:31:22 "Documenting the use of cookies in Koha for the purpose of abiding to European GDPR and other data privacy regulations is required. If a new cookie is added, an old cookie is removed or updated, the documentation on Use of Cookies needs to be updated accordingly." 21:31:43 Does anyone disagree with that new DOC1 guidelines? 21:31:57 Sounds good to me. 21:32:15 same 21:32:39 does it need to be complete? 21:32:51 whaT? 21:32:53 what 21:32:55 the guideline? 21:33:00 https://wiki.koha-community.org/wiki/Use_of_Cookies 21:33:02 or the list? 21:33:03 ^^ right? 21:33:08 we should version it 21:33:13 no I think it's exhaustive already 21:33:13 and shift to 17.11+ 21:33:37 There is a "version" column 21:34:20 #info Guideline DOC1 has been accepted unanimously 21:34:51 nothing more? next meeting? 21:35:16 #topic Set time of next meeting 21:35:47 11 July 2018, 14 UTC? 21:36:11 +1 21:36:13 nope 21:36:22 there is the general meeting 21:36:49 I can do one then the other, right? 21:37:03 Good idea - might get more attendees 21:37:20 #info Next meeting: 11 July 2018, 15 UTC 21:37:29 #endmeeting