13:01:41 #startmeeting Development IRC meeting 26 April 2017 13:01:41 Meeting started Wed Apr 26 13:01:41 2017 UTC. The chair is kidclamp. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:01:41 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:01:41 The meeting name has been set to 'development_irc_meeting_26_april_2017' 13:01:47 #topic Introductions 13:01:47 #info wahanui, a bot that has become sentient 13:02:01 #info Nick Clemens, ByWater Solutions, USA 13:02:04 #info Owen Leonard, Athens County Public Libraries, USA 13:02:06 #info Katrin Fischer, BSZ, Germany 13:02:20 #info Alex Sassmannshausen, PTFS Europe, Belgium 13:02:26 #info Jonathan Druart 13:02:27 #info, Michael Cabus, ByWater Solutions, USA (Princeton NJ) 13:03:54 should i do the same? :) 13:04:03 yes 13:04:03 yes please oha 13:04:08 jajm: around? 13:04:18 #info Claire Gravely, BSZ, Germany 13:04:19 #info Francesco Rivetti 13:04:36 Joubu, yep 13:04:42 #info Julian Maurice, BibLibre 13:05:03 #info Marc Véron, Koha Support Schweiz, www.koha-support.ch 13:05:08 alex_a, blou, fridolin1, francharb, LibraryClaire, nlegrand? 13:05:16 #info Petter G. Åsen, Oslo public library 13:05:18 fredericd:? 13:05:33 ^ 13:05:36 I am going to create a list of people to ping 5min before the min... 13:05:41 LibraryClaire: Hi! :) 13:05:46 hi ;) 13:06:02 #info Alex Arnaud, Biblibre 13:06:25 Joubu: we (bywater) all have alerts set for groups, heydevs, heysales, etc - maybe we could have people opt in for shouts in here? 13:06:52 you rang? 13:06:54 #info Magnus Enger, Libriotech, Norway 13:07:27 Joubu, an automatic ping before the meetings would be great :) I add an alert to google calendar, but that's not enough 13:07:29 kidclamp: may work yes 13:07:54 #topic Announcements 13:07:56 maybe a claendar one could subscribe to? 13:08:02 not sure where we could put it, but it might help 13:09:03 can huginn or wahanui be set to ping us on a schedule? 13:09:12 #info Tomás Cohen Arazi, Theke Solutions 13:09:15 #info Josef Moravec, Municipal library Usti nad Orlici 13:09:22 full house 13:09:34 any announcements from anyone? 13:10:31 Elasticsearch in Kohadevbox 13:10:57 I may submit a RM proposal in the next few days 13:10:58 #info Elasticsearch 1.x support in kohadevbox has been removed, and the default it is now to install ES 5.x 13:11:13 Joubu++ 13:11:15 bug 18434 13:11:15 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18434 major, P5 - low, ---, nick, Signed Off , Elasticsearch indexing broken with newer catmandu version 13:11:19 tcohen++ 13:11:58 #info Jonathan is working on a RM proposal 13:12:16 Joubu++ 13:12:17 Joubu++ 13:12:24 #info Barton Chittenden, BWS, Louisville KY 13:12:43 RM? 13:12:43 RM is jcamins 13:12:51 oha: Release Manager 13:12:52 Release Manager is probably at KohaCon 13:12:52 RM= Release Manager 13:12:56 of course 13:13:24 moving on 13:13:27 #topic Update from the Release manager (17.05) 13:13:38 wahanui: forget RM 13:13:39 oleonard: I forgot rm 13:14:20 khall is not here - he plans to push all pqa enhancements before the slush so get those in now 13:14:40 he sent out dates in his email and Joubu repeated 13:14:54 May 5 - Feature Slush 13:14:54 May 12 - Feature Freeze, String Freeze, 1st Draft of Release Notes 13:14:54 May 19 - Release Beta, 2nd Draft of Release Notes 13:14:54 May 26 - Final Release 13:14:54 May 27 - Champagne! 13:15:17 any comments? 13:15:35 Champagne on my Birthday... bonus ;) 13:15:58 I will certainly s/Champagne/Beers/ 13:16:05 Maybe if you were old enough ashimema 13:16:06 forget RM 13:16:07 So… we would really love to get stockrotation in this release, but that obviously depends on QA being good on it. 13:16:36 haha 13:16:39 If we get it Signed Off before Feature Slush might that still work? what does community think? Not sure about the deadlines and what they mean? 13:17:05 nothing matching "stock" in the NQA queue 13:17:08 bug#? 13:17:09 #info francharb, inlibro 13:17:23 thanks Joubu for the reminder 13:17:46 11897 Joubu 13:17:46 atheia: I explained what means the deadling in my email from yesterday 13:17:52 bug 11897 13:17:52 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11897 enhancement, P5 - low, ---, alex.sassmannshausen, Failed QA , Stock Rotation for Koha 13:18:10 Sorry — I must have missed that email somehow! (I blame my terrible cold!) 13:18:49 moving on 13:18:54 #topic Updates from the Release Maintainers 13:19:11 cait, jajm, mtj 13:19:25 ah sorry 13:19:40 ok, release 16.11.07 is done 13:19:53 the next 3.22.x (3.22.21) release will probably be the last 13:19:59 makes sense 13:20:12 16.11.08 is planned for 22nd again, with string freeze a week before 13:20:15 jajm++ 13:20:24 cait1++ 13:20:25 i plan to push Hea2 patches soon 13:20:43 jajm: would be great to have hea v2 in it then 13:20:58 some tests on Jenkins are failing - still need some help with that 13:21:04 #info 3.22.21 will be final 3.22 release 13:21:21 #info 16.11.08 is planned for release on the 22nd 13:21:36 #info hea2 is being considered for both 13:21:53 Joubu++ 13:21:53 Joubu, ok 13:22:08 https://jenkins.koha-community.org/job/Koha_16.11.x_D8/lastCompletedBuild/testReport/ 13:22:20 #link https://jenkins.koha-community.org/job/Koha_16.11.x_D8/lastCompletedBuild/testReport/ failing tests on Jenkins for 16.11.x 13:22:47 anything else? 13:22:47 anything else is, like, just being crap 13:23:00 wahanui you are full of sass 13:23:01 ...but wahanui is a bot|a repository of important and useful and accurate information or at least partially slow.|a little bit creepy.|right sometimes|a strange duck|a bot...|rumoured to be a sentient bot with sass| an extremely creepy stalker bot.... you have been warned|a parrot| wrong| on fire| gaining knowledge faster than sustainable|canadian|google| wahanui couldn't be bothered to show up|laser kiwi of the bo 13:23:21 moving on :-) 13:23:28 #topic Updates from the QA team 13:23:50 Joubu sent a good summary of things yesterday, please read his email 13:24:05 Joubu++ 13:24:06 #info read 'what's on in koha-devel 12' for a good update 13:24:35 Joubu++ 13:25:41 I still owe an email or wiki page on elastic and am working on that 13:26:06 joubu++ 13:26:15 kidclamp++ 13:26:16 but as tcohen mentioned it 5.x is built into kohadevbox and please ask if you have any troubles getting it going 13:26:17 Joubu++ 13:26:33 #action kidclamp is working on a summary/update of ES work 13:27:05 #info atheia asks for SO/QA to look at bug 11897 13:27:05 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11897 enhancement, P5 - low, ---, alex.sassmannshausen, Failed QA , Stock Rotation for Koha 13:28:12 we have 1 critical and 5 majors in the NQA queue 13:28:44 anyone interested in joinin QA for the next release shoudl submit their names - there is plenty of low hanging fruit to train on 13:28:48 so don't be afraid 13:29:04 #info interested members please submit their names for QA for next release 13:29:54 anything to add joubu, jajm, ashimema marcelr, tcohen , fridolin1 13:30:35 think you've nicely covered it there.. we need as much help as we can get 13:30:48 I'd like to add 13:30:59 that there are lots of REST api implementing bugs 13:31:01 also, don't feel afraid about not having enough time.. anything you can fit in helps 13:31:08 that lack QA for a lot of time 13:31:27 5 people is not enough :) 13:31:28 I volunteer to help, but please bug owners, answer the questions! 13:32:12 and signing off on QA teams patches (or offering cookies) is a good way to get your patches looked at :-) 13:32:19 many hands and all that 13:32:48 I really want to do more QA so I can help 13:32:57 *newbie, but wanting to be more skilled 13:33:17 SO is also a really good place to start 13:33:18 okay, kidclamp. 13:33:22 bah 13:33:55 * ashimema is always happy to try and help upskill people so that's another 13:33:58 kidclamp: it is the definition of corruption, right? :) 13:34:16 * barton may take ashimema up on that :-) 13:34:39 so yeah.. don't fell put off.. instead if your not confident about something just ask someone.. 13:34:49 #info the QA team wants to help you learn - so ask us questions and get involved 13:35:00 * ashimema knows he's been crap of late.. but I will always try to get back to people eventually ;) 13:35:07 :) 13:35:16 ashimema++ 13:35:30 I was thinking that maybe we could have a signoff-fest or something... 13:35:36 wahanui: so 13:35:37 i think so is a really good place to start 13:35:42 a bit like a GBSD, but for sign offs. 13:35:45 wahanui forget so 13:35:45 kidclamp: I forgot so 13:35:56 GBSD is for sign offs :-) 13:36:07 sorry im underwarter 13:36:08 oh. 13:36:15 well. 13:36:30 fridolin1 (blub blub) 13:36:34 shows you what I know ;-) 13:36:37 I think GBSD for bugfixes only, before the release would be great 13:36:54 +1 on that 13:37:10 I'm game :-) 13:37:15 may 10th? same as next dev meeting? 13:37:23 I'm game too! 13:37:24 since we should all be around then? 13:37:40 Yeah, cool idea! 13:37:43 works for me 13:37:46 is it not too late? 13:37:57 if we just do bugs and not enhancments 13:38:00 ah ok 13:38:05 and is early for next release 13:38:28 indeed.. make is 'bug only' then it should be solid 13:39:03 #action GBSD - bugs only edition - May 10th to clean up for 17.05 release 13:39:09 There are not much bugs with patches attached, should be easy to make all them moved forward 13:39:31 kidclamp++ :) 13:40:10 if there aren't enough maybe devs can patch some more :-) 13:40:28 count on me for that :p 13:40:45 would people be interested to have a doc writing event after the release? 13:40:46 I am going to focus on bugfixes for the next 2 weeks 13:41:02 okay, I think we bled into next topic too 13:41:09 #topic General development discussion (trends, ideas, ...) 13:41:30 #info Joubu is working on bug fixes for next two weeks, help is appreciated 13:41:31 cait1, good idea! 13:41:42 cait1: I think that's a good idea too. 13:41:49 cait++ 13:41:59 cait1++ 13:42:04 * cait1 wrote herself a reminder about that 13:42:11 I was thinking similar.. 13:42:17 * ashimema still has some shibboleth docs to write :( 13:42:50 * magnuse has to leave 13:42:57 #action cait wants to schedule a doc writing fest after GBSD 13:43:11 #action cait wants to schedule a doc writing fest after the release that is 13:43:19 Joubu++ 13:43:36 any more topics? dont want to keep us all too long - there is a release on the way! 13:43:54 heh 13:44:01 #topic Review of coding guidelines 13:44:07 we have needs to have a system to execute background jobs 13:44:20 and i know Joubu will need something as well like that 13:44:33 not sure if this is the right moment/place to talk about it tho 13:44:48 oha: I sent an email to dcook yesterday, he announced something about that 2 months ago 13:44:59 I'd like to know if he has something on the grill to submit 13:45:11 or if we should start our own from scratch 13:45:22 ok, count me in if in case 13:45:55 * ashimema uses Minion for background tasks.. fits lovely with Mojo 13:46:10 #info joubu and oha looking at background jobs, trying to coordinate with dcook in case he has begun work 13:46:41 ashimema: any pointers are welcome 13:46:58 #link https://wiki.koha-community.org/wiki/Coding_Guidelines#PERL17:_Unit_tests_are_required guideline_proposal1 13:46:58 * ashimema willl go dig out the email and reply there 13:47:09 oha: http://lists.koha-community.org/pipermail/koha-devel/2017-April/043671.html 13:47:21 Joubu: thanks. ashimema great! 13:47:22 #link https://wiki.koha-community.org/wiki/Coding_Guidelines#PERL26:_Koha::Exceptions guideline_proposal2 13:48:07 marcelr is not around, but does anyone have comments or questions on these? 13:48:28 * ashimema is quickly reading those two 13:48:59 yes, something 13:48:59 something is fishy 13:49:09 I'm deffo happy with the first one 13:49:11 I am rewriting stuffs, and moving them to Koha, right? 13:49:20 I think that everybody is aware of that 13:49:23 if you say so :-) 13:49:27 I submit tests when I move stuffs 13:49:42 so I do not think it is necessary to have people working on writing tests for C4 13:49:51 just signoff my patches... 13:50:07 hmm..but if they add to C4 does it not help you to have existing tests when moving? 13:50:12 hm even when something i changed in C4? 13:50:17 I mean, I am happy to write less tests :-) 13:50:19 also happy with the move to Exceptions 13:50:30 Joubu++ that does make sense 13:50:34 * oha must go :( 13:50:35 ideally we shouldn't do that, but there might be bug fixes etc. with regression tests 13:50:57 maybe I did not understand what the guidelines says 13:51:14 I think it's a good guideline with room for judgement calls on testing old code? 13:51:14 always feel better when there are tests when i push holds stuff for example :) 13:51:21 someone to resume? 13:51:24 I think it's mostly covered by `as well as for changes to existing routines (perhaps excluding very trivial edits)` 13:51:36 i.e. if someone doesn't add tests to C4 QA can judge whether to pass or fail 13:51:36 Unit tests must be provided for *ALL* new routines in modules, as well as for changes to existing routines ... 13:51:40 yes but... that is already the case for years now :) 13:52:07 ok, so nothing new. We are just writing down something that was missing 13:52:10 it's just good to have it in writing :) 13:52:15 yep 13:52:16 yup 13:52:17 pretty much 13:52:18 yup 13:52:20 ok sorry then :) 13:52:21 good for new people and also to back up qa etc 13:53:13 * ashimema would also be tempted to somehow try and encourage documentation submissions along with the code submissions. 13:53:36 #startvote Should we accept the proposed changes to guideline PERL17? Yes,No 13:53:36 Begin voting on: Should we accept the proposed changes to guideline PERL17? Valid vote options are Yes, No. 13:53:36 Vote using '#vote OPTION'. Only your last vote counts. 13:53:45 #vote Yes 13:53:50 #vote Yes 13:53:52 sometimes I spend half the time QA'ing somthing trying to get my head around what it's actually meant to do.. it would really help everyone if new features had full documentation submitted as part of the bug 13:53:57 #vote Yes 13:53:58 #vote yes 13:53:59 #vote Yes 13:53:59 #vote Yes 13:54:07 #vote Yes 13:54:12 #vote Yes 13:54:19 #vote Yes 13:54:25 ashimema: ideally the test plans should help - but having help pages/manual patches would be great too 13:54:32 glast call 13:54:37 ashimema: if so, where would we stick the documentation? Because there is a separate process for koha docs submission no? 13:54:42 documentation++ 13:54:46 #endvote 13:54:46 Voted on "Should we accept the proposed changes to guideline PERL17?" Results are 13:54:46 Yes (9): Joubu, cait1, josef_moravec, ashimema, atheia, barton, kidclamp, tcohen, mveron 13:55:02 discussion on PERL26? 13:55:07 yeah.. test plans certainly help.. but sometimes it's more involved understanding the background of how to setup the test than it is to just run through the actual bit of the plan.. 13:55:22 PERL26++ from me 13:55:29 we got a bit of a backlog with documenation right now - will have to catch up 13:55:42 indeed.. that's kinda my point cait ;) 13:55:50 I know :) 13:56:01 maybe soething for a meeting with rangi around 13:56:09 to see how we could make it work workflow-wise 13:56:20 cait++ 13:56:23 #startvote Should we accept the proposed changes to guideline PERL26? Yes,No 13:56:23 * ashimema is generally trying to encourage documentation submissions with new work at ptfs-e these days 13:56:23 Begin voting on: Should we accept the proposed changes to guideline PERL26? Valid vote options are Yes, No. 13:56:23 Vote using '#vote OPTION'. Only your last vote counts. 13:56:28 we need an example module for exception. We do not have much things using it pushed 13:56:31 #vote Yes 13:56:35 #vote yes 13:56:40 #vote Yes 13:56:43 #vote Yes 13:56:43 #vote yes 13:56:48 The guideline suggests an example no? 13:56:48 #vote Yes 13:56:48 #vote Yes 13:56:57 #vote yes 13:56:57 (I didn't look at the example yet though) 13:57:08 last call 13:57:28 #endvote 13:57:28 Voted on "Should we accept the proposed changes to guideline PERL26?" Results are 13:57:28 Yes (8): Joubu, cait, josef_moravec, ashimema, atheia, barton, kidclamp, tcohen 13:57:46 #info as people work on exceptions please add best examples to PERL26 13:57:49 there is no guideline for logging 13:58:02 atheia: yes indeed but the example is not the perfect example :) 13:58:22 and would be good to have a small piece of code on the wiki, instead of refering to the codebase 13:58:41 Yeah, fair enough, that sounds sensible. 13:59:08 #action marcelr please provide a code snippet for PERL26 if you have one :-) 13:59:27 #topic Set time of next meeting 13:59:30 * ashimema is slightly upset that there's no POD in Koha::Exceptions :( 14:00:11 even if it just told you to go read the POD on Exception::Class 14:00:23 Hey… should we be talking about the gender neutral language guideline proposal? 14:00:24 hm 14:00:25 https://perldoc.koha-community.org/ 14:00:30 are we missing the newer versions there? 14:00:32 Or is that somehow out of scope? 14:00:43 May 10th, 21 UTC? NZ folks have had a hard time making meeting and that would help 14:00:57 sounds good to me 14:01:13 * ashimema doesn't see a gender neutral language proposal 14:01:31 not in the agenda 14:01:38 ashimema: there was something on the mailing list. 14:01:38 hm yeah, but it was written 14:01:42 bug 18432 14:01:42 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18432 trivial, P5 - low, ---, ephetteplace, Pushed to Master , Most code comments assume male gender 14:01:43 and the author does not seem around :) 14:01:43 i tihnk maybe not aware on how to add 14:02:00 #link https://wiki.koha-community.org/wiki/Draft:Gender_Neutral_Pronouns 14:02:29 so is a coding guideline proposal? 14:02:43 i'd say so - maybe we could find a better example later 14:02:48 Yeah, I think that was the if I recall correctly. 14:02:49 I think add to next meeting 14:02:57 ok 14:03:02 agreed.. 14:03:03 Sure. 14:03:31 there's also a proposal dating back to 2014 about formalising in a guidline that we use american english 14:03:32 #action phette23 should add gender neutral pronouns proposal to coding guidleines for next meeting 14:03:39 * Joubu is happy that someone reads his test's descriptions 14:03:42 in the 'discussion' tab on the wiki 14:03:50 ^^ 14:04:27 #info Next Meeting: May 10th 2017, 21 UTC 14:04:28 heh and i commented 14:04:36 last call 14:04:41 +1 14:04:42 * Joubu would have spent more than 3sec to write it, if he had known... 14:05:23 #endmeeting