22:00:43 #startmeeting Development IRC meeting 9 August 2017 22:00:43 Meeting started Wed Aug 9 22:00:43 2017 UTC. The chair is cait. Information about MeetBot at http://wiki.debian.org/MeetBot. 22:00:43 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 22:00:43 The meeting name has been set to 'development_irc_meeting_9_august_2017' 22:00:48 #topic Introductions 22:00:49 #info wahanui, a bot that has become sentient 22:00:51 #info Tomas Cohen Arazi, Theke Solutions 22:00:58 #info Jesse Weaver 22:00:59 Project Koha_Master_D8 build #237: UNSTABLE in 2 hr 2 min: https://jenkins.koha-community.org/job/Koha_Master_D8/237/ 22:01:00 * Jonathan Druart: Bug 18906: Display all funds the logged in user can use 22:01:00 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18906 major, P5 - low, ---, jonathan.druart, Pushed to Master , Superlibrarian and budget_manage_all users should always see all funds 22:01:03 * Jonathan Druart: Bug 18898 - Some permissions for Reports can be bypassed 22:01:03 please introduce yourself with #info following tcohen's example 22:01:04 * Jonathan Druart: Bug 19023 - inventory tool performance 22:01:05 * Jonathan Druart: Bug 17829: (follow-up) Move GetMember to Koha::Patron - routing-lists.pl 22:01:05 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18898 major, P5 - low, ---, dcook, Pushed to Master , Some permissions for Reports can be bypassed 22:01:06 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19023 major, P5 - low, ---, fridolin.somers, Pushed to Master , inventory tool performance 22:01:06 #info Liz Rea, Catalyst IT 22:01:07 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17829 enhancement, P5 - low, ---, jonathan.druart, RESOLVED FIXED, Move GetMember to Koha::Patron 22:01:07 #info Chris Cormack, Catalyst IT 22:01:13 #info Katrin Fischer, BSZ, Germany 22:01:14 #info Bob Birchall, Calyx 22:01:23 #info Alex Sassmannshausen, PTFS Europe, UK 22:01:30 #info Josef Moravec, Municipal LIbrary Usti nad Orlici, Czech Republic 22:01:31 #chair tcohen 22:01:31 Current chairs: cait tcohen 22:01:36 #link https://wiki.koha-community.org/wiki/Development_IRC_meeting_9_August_2017 today's agenda 22:01:41 #info Lee Jamison, Marywood University 22:02:07 hi everyone 22:02:12 #info Mason James, NZ 22:02:17 hi folks 22:02:31 hi mtj 22:02:46 hello, NZ :) 22:02:49 ready to continue? :) 22:02:51 (/AUS) 22:02:58 #topic Announcements 22:03:21 anyone? 22:03:22 i heard anyone was free to organize one at any time :-) 22:03:28 I wanted add a small comment 22:03:43 #info We just added a section on how to add screenshots to the manual with gitlab 22:03:46 #link https://wiki.koha-community.org/wiki/Development_IRC_meeting_9_August_2017 22:03:49 hm wrong link 22:04:02 #link https://wiki.koha-community.org/wiki/Editing_the_Koha_Manual#Normal_-_Adding_screenshots_with_gitlab right link 22:04:12 tcohen: go ahead 22:04:16 #info Bag Brendan gallagher 22:04:42 #info tcohen is doing QA full time this week, please help him notice things you consider important besides the ones the RM notes 22:04:43 #info Michael Cabus, caboose 22:05:05 cait++ 22:05:06 tcohen: the clean-up script 22:05:22 tcohen++ 22:05:25 hackfest friday and saturday at kohaus 22:05:31 cait: yes, I've added a followup to it, and am discussing it with Joubu, its quite tricky 22:05:35 tcohen: bug 14826 22:05:35 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14826 enhancement, P5 - low, ---, kyle.m.hall, Signed Off , Resurrect account offsets table 22:05:37 yeah, it is 22:05:47 it would be great if people from oceania could take a look 22:05:50 maybe we can do the issues first, they seem less tricky than the others 22:05:51 while we sleep 22:06:16 looking for the bug number 22:06:18 I will we be trying to teach people how to use the sandboxes. Also tcohen I may try to help some people set up their own kohadevbox - so I may need to ping you for help 22:06:25 josef_moravec: I did that too, asked for some followups khall promply submitted before I was released from others he 22:06:33 tcohen: do you have it on hand? 22:06:34 bag: np 22:06:43 cait: which? 22:06:43 which is the most maintainable 22:06:54 bug 19016 22:06:54 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19016 major, P5 - low, ---, jonathan.druart, In Discussion , Add a script to fix corrupted data 22:06:55 bag: if you can, please also encourage to try editing the manual 22:06:58 bag: you should also mention they can help write the manual if they like to document! ;D 22:07:05 haha 22:07:08 cait: I’m going to ask jzairo to lead that up 22:07:25 but rangi encouraged most here to do manual work :) 22:07:35 #info bug 19016 - Add a script to fix corrupted data needs attention and testers 22:07:58 I will be around too if there are questions, i think at least some of the time 22:08:03 another thing I'd like to mention is that 22:08:26 thanks cait 22:08:44 it's always a trip for me to see tables i created in 1999, that got removed, now coming back :-) 22:08:57 #info Koha-US Conference is taking place this week, it's broadcasted http://koha-us.net/index.php/2017_Koha-US_Conference 22:08:57 ha 22:09:07 our jenkins nodes design is quite difficult to keep in sync so it works with different dependencies 22:09:30 right now we have a situation in which pushing the needed REST api upgrade patches 22:09:47 would require newer deps, and break jenkins tasks for stable branches 22:09:54 to make it short 22:10:14 I'm trying to have a kohadevbox-derived docker image to use for jenkins 22:10:35 making it easier to keep running environments adjusted as needed 22:10:45 can you do your own #info plz? :) 22:10:52 anyone willing to help with opinions is welcome! 22:11:14 #info tcohen and Joubu are exploring ways of containerizing jenkins tasks 22:11:27 tcohen: larryb said he can create another node for you. Get in touch with him 22:11:36 bag: thanks 22:11:43 tcohen: I know that mtompset had been doing some work with koha/docker..he may have some input for you :) 22:12:03 #info ByWater is handing the community another jenkins node in the meantime 22:12:14 LeeJ: thanks 22:13:04 ok, moving on? 22:13:05 that's all from me 22:13:22 #topic Update from the Release manager (17.11) 22:13:42 #info Joubu left his apologies 22:14:08 #link https://koha-community.org/whats-on-in-koha-devel-14/ for recent information about urgent topics and new things 22:15:10 #info We will need help updating the manual and especially the help pages prior to 17.11 release in order to be able to switch it over to the Sphinx based one 22:15:51 we need to fix links 22:15:58 besides adding content of course 22:16:04 moving on 22:16:20 #topic Updates from the Release maintainers 22:16:30 fridolis is not around, mtj? 22:16:36 fridolin 22:16:37 well, fridolin is busy at the moment, I asked him to backport the bug fix 22:17:08 #info 16.11.11 will be the next 16.11.x release, planned on schedule, string freeze on the 15th, release on 22nd 22:17:35 I hope we can include the script to fix data by then or have at least a partial fix for the most urgent (issues/old_issues) 22:17:38 mtj? 22:17:38 mtj is the 16.5 Rmaint for the 16.11 release cycle 22:17:56 #info 16.05.16 should be on schedule this month too 22:18:49 moving on? 22:19:00 #topic Updates from the QA team 22:19:10 anyone from the QA team around? 22:19:13 #info Owen Leonard, late. 22:19:30 yes 22:19:35 22:19:40 woops 22:19:56 #info QA team members are urged to spend some time on blockers and major bugs 22:20:26 as marcelr said, enhancements will start to get stuck 22:20:33 and we love enhancements 22:20:36 yeah 22:20:49 lets work on bugs (which we love to get fixed) 22:21:09 if possible, add the tests you consider are needed and PQA on them 22:22:28 fixing_bugs++ 22:22:33 we got some evil ones to deal with atm 22:22:46 let's get this done and then add all the shiny features ;) 22:22:47 brb 22:22:49 moving on? 22:22:54 yeah 22:22:58 yeah x2 22:23:13 #topic General development discussion (trends, ideas...) 22:23:20 pianohacker: please start :) 22:23:36 hi 22:23:38 back 22:24:09 okay, short version: we need to figure out how we feel about IE working on the staff client 22:24:11 long version 22:24:47 I'm working on the (now) Preact-based circ rules editor (mockup very soon), and if we don't want to beat our head against a transpiler 22:25:00 (a discussion which has gotten stuck a couple times now) 22:25:13 Let's beat our head against a transpiler 22:25:38 pianohacker: can we leave the current circ editor inplace and just add the other new one as a option if you so choose? 22:26:02 then IE people can still use the old version. (yeah that is just a work around and doesn’t answer the question) 22:26:03 bag: if people are okay with being locked out of the new shiny, that's totally okay with me 22:26:26 well, is it all IE, or only older versions 22:26:37 oleonard: I would absolutely love to, but do we have a path forward that's not covered in bikesheds? 22:26:38 I thought the newer ones were better at standards 22:26:53 wizzyrea: all IE for any ES6 features :/ edge works but is apparently not very common 22:27:02 We're back in the world where the latest IE is exclusive to the latest version of Windows 22:27:08 yeah... 22:27:11 It would make it easier for inclusion - you could even systempref it (maybe?) yay more sysprefs 22:27:28 ugh. 22:27:31 bag: I suspect that will make maintenance twice as difficult 22:27:34 yeah no 22:27:38 let's not do that to ourselves. 22:27:44 thanks oleonard that was what I was missing in my thoughts 22:27:46 I would strongly prefer not to syspref it; AdvancedCatalogingEditor is currently enabled on 2/608 Koha installations in hea 22:27:53 just to pick a random example ;) 22:27:57 right - maintaining two circ rules - that’s out 22:28:20 pianohacker: my library is one! :D 22:28:21 thenew circulation rules also try to be more flexible too 22:28:36 LeeJ: that does make me (and kidclamp) happy to hear :) 22:29:15 yes; so the old interface isn't a perfect representation (since you don't have to set every value for every branch/category/itemtype) 22:29:21 As far as I'm concerned the idea of a preprocessor and/or transpiler isn't too bikeshedded really. It's just that I aimed to take the lead on it and then my Koha dev time was cut back drastically 22:29:52 i like the new circ rules, but (as you all know) it's vitally important we get it right 22:30:17 oleonard: do you think we have a decent shot at getting webpack/babel/npm into the Koha build/dev workflow? 22:31:04 I'm not confident that webpack will work well without doing major changes to the way we handle JavaScript in general, so I'm leaning towards gulp still 22:31:12 pianohacker: might be older versions on hea too? or just copy cataloguing 22:31:13 maybe you and I could talk about that another time 22:31:31 because the only thing that has no obstacles (besides our sanity) is developing Preact using IE-compatible ES3. 22:31:48 oleonard: agreed :) 22:32:41 as rangi says, code speaks, that's the only way to see the benefits of adopting new stuffs and changing workflows 22:32:52 I still think it's vital to Koha's front-end future that we choose /something/ to do preprocessing stuff 22:33:36 It is theoretically possible, though gross, to check in the compiled code (like how we handle LESS) 22:33:37 silly question maybe, but what does a transpiler do? 22:33:49 translate code for different versions? 22:34:00 yup, that's the main relevant feature. 22:34:57 cait: perhaps add this to the info for reference? https://scotch.io/tutorials/javascript-transpilers-what-they-are-why-we-need-them 22:35:29 okay, just to summarize; we would prefer not to have two parallel circ rule interfaces, for reasons of maintainability 22:35:40 #link https://scotch.io/tutorials/javascript-transpilers-what-they-are-why-we-need-them - we discussed about adding a trnaspiler / preprocessing stuff 22:35:53 i think it might get in the way fast 22:36:02 with the new stuff you want to add 22:36:07 natively using ES6 features (without transpilation) is out, because we don't want to completely cut off the IE users 22:36:09 and also every new option will have to be added twice 22:36:12 right 22:36:25 we stopped doing 2 opac templates because we didn't really manage that all too well 22:37:15 there's two options left: a) work on including a transpiler b) continue to write JS that works in IE. 22:37:36 transpiler++ 22:37:45 transpiler++ 22:37:46 um. concerns about dropping IE> 22:37:56 transpiler++ 22:38:17 Can we agree on IE10+ ? 22:38:34 * wizzyrea signs off on that 22:38:37 I think requiring a specific browser for a tool is not a big deal 22:38:38 yup 22:38:46 oleonard: is IE10 the current standard minimum? 22:38:47 have you ever worked with government? 22:38:59 requiring a specific browser is a very. big. deal. 22:39:04 i say go for the version ms still supports 22:39:05 hm 22:39:16 IE11 is the highest version still available on Windows 7 22:39:32 I'm not sure about Windows 8, but Windows 10 has IE "Edge" 22:39:33 I think 11+ 22:39:34 https://www.microsoft.com/en-us/windowsforbusiness/end-of-ie-support 22:39:37 that's the main reason I actually agreed with dcook's mailing list post, as much is it made me grind my teeth. 22:39:52 so 10 is not actually supported 22:40:09 Okay cool. 11+ 22:40:17 MS has forced everyone up anyway I think 22:40:20 yeah 22:40:30 i'm sure you'll find stragglers 22:40:35 Okay. I will work (in conjunction with oleonard) on putting together some transpiler stuff. It may not be the perfect, ideal build pipeline, but it's a path forward. 22:40:57 but we do them no favours leaving them on a browser thats had no security patches since jan 2016 22:41:10 pianohacker++ oleonard++ transpiler++ 22:41:24 https://www.microsoft.com/en-us/windowsforbusiness/end-of-ie-support 22:41:48 maybe start a wiki page with some of those links and information? 22:41:49 Quick minivote; if it substantially eases getting this new project integrated, how bad would checking in the transpiled JS be? 22:41:52 it might beuseful later on 22:41:58 Does anyone know if it's possible to import multiple items from an individual MARC record? For example, if a MARC record has holding information for a multi-volume set with multiple barcodes, can Koha import both the bib and the item info? 22:42:07 jfowler, we are in a meeting can you hold on? 22:42:16 sure. Sorry guys. 22:42:19 sok :) 22:42:20 we should be done soonish :) no worries 22:42:48 pianohacker: I'm not sure about that 22:43:22 I think transpiling might be better done on testing/packaging time 22:43:55 it's not ideal, and if at all possible would not be permanent, but do we have any steps in the current dev workflow to include "npm build" or "npm watch"? 22:44:08 Let's postpone that discussion until pianohacker and I have had a chance to come up with a proposal 22:44:13 kk 22:44:17 oh yeah hi pianohacker - great to have you here :) 22:44:26 oh hi bag :) 22:45:42 oleonard: good idea 22:46:21 #action pianohacker and oleonard are going to work out a proposal for adding a transpiler into our workflow 22:46:21 hope that was right :) 22:46:21 Looks good to me 22:46:21 yup! I think that wraps up that discussion for the time being 22:46:21 any last minute additions before i move on? 22:46:22 #topic Review of coding guidelines 22:46:22 we got no proposals on the wiki - someone has something? 22:46:22 #topic Review of coding guidelines 22:46:22 hm, didn't change 22:46:24 ah 22:46:30 huginn is sleepy 22:46:31 cait: I've exhausted my database of quotes 22:46:39 you are exhausted... i understand 22:46:45 amen 22:46:52 ok, moving on then 22:47:01 #topic Set time of next meeting 22:47:13 I got no idea of how this curerntly works 22:47:16 i think every 2 weeks? 22:47:34 yes, in 2 weeks 22:47:37 alternating between, what, 10 and 22 UTC? 22:47:42 exactly 22:47:44 looks like 14 and 21 22:47:49 https://wiki.koha-community.org/wiki/IRC_Meetings 22:48:28 I certainly prefer 14 ;) 22:48:35 24th, 14? 22:48:42 23rd 22:48:48 ok 22:48:53 wednesdays 22:48:53 wednesdays is when I stab people, same problem. 22:49:04 it's already thursday here :) 22:49:21 #agreed Next meeting will be on August 23, 14 UTC 22:49:27 thx all for attending! 22:49:32 #endmeeting