19:37:45 #startmeeting Development IRC meeting 24 July 2019 19:37:45 Meeting started Wed Jul 24 19:37:45 2019 UTC. The chair is kidclamp. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:37:45 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:37:45 The meeting name has been set to 'development_irc_meeting_24_july_2019' 19:37:48 #info Jon Knight, Loughborough University 19:37:55 #topic Introductions 19:38:06 #info Nick Clemens, bywater solutions 19:38:14 #info Alex Buckley, Catalyst IT Wellington NZ 19:38:17 #info Hayley Mapley, Catalyst IT Wellington NZ 19:38:19 #info Katrin Fischer, BSZ, Germany 19:38:25 #info David Nind, Wellington NZ 19:38:31 :) 19:39:06 #info Thomas Dukleth, Agogme, New York City 19:39:34 #topic Announcements 19:39:42 Anyone? Community day! 19:40:04 yes, on phone - wah 19:40:20 #info https://wiki.koha-community.org/wiki/Koha_Community_Project_Day_26_July_2019 19:40:50 A nice list of things to work on, so shaping up quite nicely! Thanks cait for kicking off! 19:41:54 There is a hashtag for Twitter, thanks Catalyst IT! #KohaCommunityDay 19:42:36 We're very excited for it! :) 19:42:53 excellent! 19:42:53 darn tootin' it is. 19:42:53 sorry :) 19:43:00 thx for helping out :) 19:43:21 hope my tweets were friendly - just wanted to make sure everyone undrestands this is ot only focused at dev 19:43:21 we're happy to help cait :) 19:43:25 the main idea is to bring community together 19:43:32 get us talking again, working on fun things... 19:43:39 I am gonna admit, I missed some of this discussion, is it like bigger bug squashing day? 19:43:42 ah, oka 19:43:54 yeah the idea was to have a wider focus than just bug squashing 19:44:06 Sorry - I promoted it on twitter as more dev based, but I see cait has corrected that. Sorry. 19:44:13 of course you can sqhash bugs, ubt if you want to do stats, or cook, or write or proof read... whatever :) 19:44:25 yeah i hope that didn't come across wrong! 19:44:31 very glad to see the advertising 19:44:42 More me misunderstanding the purpose of it. Sorry. 19:44:47 all good 19:45:02 moving on? 19:45:10 checking the infos sec 19:45:31 cool, yes 19:45:47 #info BibLibre's Koha Hackfest 2019: 30 September - 4th October, Marseille 19:46:05 (just thought I'd put that in there as a reminder) 19:46:19 excellent 19:46:19 darn tootin' it is. 19:46:27 #topic Update from the Release manager (19.11) 19:46:48 #info Oh great and powerful RM, we thank you for the benevolence you bestow upon our patches 19:47:04 Martin is doing great, but is occupied tonight 19:47:18 Watch the bugs, keep things moving 19:47:38 we are still in his "adventurous' pushing phase so big things are good 19:47:39 Update is on agenda page from ashimema: moving into a period of more adventurous pushing now.. two months before I get much more cautious again and start of a polishing for release phase 19:49:11 movign on 19:49:22 #topic Updates from the Release Maintainers 19:49:33 frido lukeg wizzyrea 19:51:19 #info maintenance releases now available - 18.11.08, 19.05.02 19:51:42 moving on 19:51:51 #info Updates from the QA team 19:51:56 cait? 19:51:56 somebody said cait was really good at running into things 19:52:48 sorry phone again 19:52:51 np 19:52:52 #info Fix all the bugs 19:52:56 :-) 19:53:36 signed off queue has many bugs, some large, could use some attention to move those 19:53:46 NSO growing as well 19:53:54 communityday++ 19:54:01 #info Josef Moravec, sorry being late 19:54:02 cait++ 19:54:06 weekly emails are appreciated 19:54:24 I read them even when I can't take action :-) 19:54:38 moving on? 19:55:09 #topic General development discussion (trends, ideas, ...) 19:55:55 #info Discussion on workflows with regards maintaining the mana-kb serverside project 19:56:08 #info See Bug 23161 - Alex A (Biblibre) and the Release Team 19:56:08 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23161 enhancement, P5 - low, ---, koha-bugs, NEW , We need to document the release process for this project? 19:57:02 I think we need BibLibre here for this, and maybe something to fully iron out at hackfest. BUt brainstorm next meeting at earlier time? 19:57:29 sounds good, need ashimema here too for that as well I think 19:57:44 #info tabled for next meeting 19:57:53 #info git repository splitting and cleanup - Chris C and Jonathan D 19:58:08 I think still a bit early for Rangi 19:58:19 and Joubu is having all the fun :-) 19:58:34 I assume git repro splitting may make bringing up/updating KohaDevBox's easier/faster? 19:59:18 splitting off the translation I assume? 19:59:22 it has come up before 19:59:28 I'm for it 20:00:21 https://wiki.koha-community.org/wiki/Git_Splitting_and_Shrinking 20:00:54 #info https://wiki.koha-community.org/wiki/Git_Splitting_and_Shrinking 20:01:12 I tihnk again we need some parties for discussion 20:01:24 #info tabled for next meeting 20:01:34 #topic Review of coding guidelines 20:01:46 #info Bug 22600 introduced a base class for commandline scripts, but we forgot to followup with a guidline and qa script change to catch new scripts without the base class. 20:01:46 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22600 blocker, P2, ---, martin.renvoize, RESOLVED FIXED, We should add an 'interface' field to accountlines 20:02:29 #link https://wiki.koha-community.org/wiki/Talk:Coding_Guidelines#Scripts 20:03:04 I am for it, I think we should add the guieline 20:03:26 do we need a vote? 20:03:38 looks good to me, so I think it should be added 20:03:49 not sure.. 20:04:14 do you normally vote on coding guideline changes, or if everyone agrees just accept? 20:04:18 I'd vote for it. 20:04:42 #startvote Should we add coding guideline Scripts - CMD1 as proposed on the wiki? yes,no,abstain 20:04:42 Begin voting on: Should we add coding guideline Scripts - CMD1 as proposed on the wiki? Valid vote options are yes, no, abstain. 20:04:42 Vote using '#vote OPTION'. Only your last vote counts. 20:04:47 #vote yes 20:04:51 #vote yes 20:04:54 #vote yes 20:04:54 #vote yes 20:04:54 #vote yes 20:05:06 #vote yes 20:05:31 #vote yes 20:06:03 #endvote 20:06:03 Voted on "Should we add coding guideline Scripts - CMD1 as proposed on the wiki?" Results are 20:06:03 yes (7): greenjimll, davidnind, kidclamp, josef_moravec1, alexbuckley, thd, hayley 20:06:08 hooray 20:06:18 sorry, got to run! 20:06:49 #info SQL12: Enforcing it more easily with a QA script addition and updating existing breakages - Tomas and Jonathan D 20:07:05 #link https://wiki.koha-community.org/wiki/Coding_Guidelines#SQL12:_Booleans SQL12 20:07:44 I agree with and support their work :-) 20:08:48 moving on? 20:09:09 does it need to be voted on, or is it a work in progress? 20:10:16 seems to be a bug and pull request 20:10:23 the guideline is in place I believe 20:10:59 The gitlab.com stuff says its awaiting a merge request? 20:11:31 https://gitlab.com/koha-community/qa-test-tools/merge_requests/12 20:11:32 so is for someone who has merge powers 20:11:51 so general support for them to go ahead with this, which is great! 20:11:59 Joubu++ 20:12:15 tcohen++ 20:12:22 movign on 20:12:36 #info general support for SQL12: Enforcing it more easily with a QA script addition and updating existing breakages 20:12:53 #info Revise JavaScript coding guideline JS8 to recommend ESLint; Add a default .eslintrc.json file to Koha. - Owen L 20:13:23 #link https://wiki.koha-community.org/wiki/Coding_Guidelines#JS8:_Follow_guidelines_set_by_JSHint JS8 20:14:11 Owen isn't here, but it seems sane to me 20:14:24 any questions or detractors? 20:14:40 none from me 20:14:45 I like that 20:15:06 Seems sane. 20:15:48 looks sensible 20:15:59 #startvote Should we update JS* as proposed by oleonard and adopt a default eslintrc.json file? 20:15:59 Begin voting on: Should we update JS* as proposed by oleonard and adopt a default eslintrc.json file? Valid vote options are Yes, No. 20:15:59 Vote using '#vote OPTION'. Only your last vote counts. 20:16:04 #vote Yes 20:16:09 #vote yes 20:16:10 #vote yes 20:16:12 #vote yes 20:16:17 #vote yes 20:16:28 #vote yes 20:16:31 #vote Yes 20:16:37 last call y'all 20:16:57 #endvote 20:16:57 Voted on "Should we update JS* as proposed by oleonard and adopt a default eslintrc.json file?" Results are 20:17:21 #topic Set time of next meeting 20:17:45 I liked the pause before (not) giving the results. Like Eurovision. :-) 20:18:04 *ad break* 20:18:08 hehe 20:18:10 yes (6): greenjimll, davidnind, kidclamp, josef_moravec1, thd, hayley 20:18:48 August 7th, 14:00 UTC? 20:19:00 Sounds good. 20:19:48 Hello, apols for barging into the meeting :) 20:19:48 What happened to 13.00 UTC? 20:20:08 or 13.30 UTC? 20:20:17 fine by me 20:20:26 I never remember the exact time 20:20:47 As long as it goes in the Koha meeting Google calendar, I'm fine with any of those. 20:21:15 #info Next meeting: 7 August 2019, 13:30 UTC 20:21:20 14 is fine for me but checking what we had done historically 13.00 UTC has been common and the preferred time for many time zones from a one time poll. 20:21:43 the time of this meeting works really well for nz, but we totally get that its not suitable for others and appreciate it needs to alternate so August 7th, 14:00 UTC sounds good 20:22:11 Does 14.00 UTC work at all in NZ? 20:22:15 heh, I set 13:30 - we should mark these down somewhere as the 'approved' time' 20:22:27 that's for next meeting :-) 20:22:28 https://wiki.koha-community.org/wiki/IRC_Meetings 20:22:47 #endmeeting