15:02:01 #startmeeting Koha Development Meeting, 21 May 2014, part 1 15:02:01 Meeting started Wed May 21 15:02:01 2014 UTC. The chair is gmcharlt. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:01 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:02:01 The meeting name has been set to 'koha_development_meeting__21_may_2014__part_1' 15:02:15 #info Agenda is http://wiki.koha-community.org/wiki/Development_IRC_meeting,_21_May_2014 15:02:20 #topic Introductions 15:02:22 #info wahanui, a bot that has become sentient 15:02:23 #info Tomas Cohen Arazi, Universidad Nacional de Cordoba 15:02:27 #info Owen Leonard, Athens County Public Libraries 15:02:33 #info Galen Charlton, 3.16 RM 15:03:10 #info Jason Etheridge, Equinox 15:04:00 #info Thomas Dukleth, Agogme, New York City 15:04:20 #info Martin Renvoize, PTFS Europe 15:04:21 #info Bernardo Gonzalez Kriegel, Córdoba Argentina 15:05:11 #info Wolfram Schneider, IndexData 15:05:13 hi 15:05:14 hola, ztajoli 15:05:55 ok, let's get started 15:06:00 #topic Announcements 15:06:07 #info Koha 3.16.0 will be released tomorrow 15:06:17 gmcharlt++ 15:06:19 * oleonard cheers 15:06:30 #info Galen will continue to push patches to master through Sunday; tcohen will take over the master branch on Monday 15:06:55 any other quick announcements? 15:07:14 gmcharlt++ 15:07:23 oh, one more 15:07:23 i think one more is better than one less but yeah they should be the same 15:07:31 #info 3.16.x will be branched tomorrow 15:07:48 ok, moving 15:07:53 #topic RM 3.18 comments 15:07:57 tcohen: you have the floor 15:08:08 hi every1 15:08:23 i wanted to say a few words on how i expect to do my RM work 15:09:02 I'd like to set a dashboard of the current "big" developments you are all involved in, or at least worried about 15:09:23 and I'll commit to find all the bottlenecks so everything goes as smooth as we can 15:09:52 I'll set (for now) a Trello board for that, and I expect to get some feedback from MMs 15:10:17 I also hope we can make dev meetings from frecquently 15:10:43 not as we need them, but something like twice a month 15:10:52 to catch up with everyone's works 15:11:19 I want all of you know I'm open to comments on all this 15:12:49 so far so good tcohen.. sounds promising. 15:12:51 tcohen: sounds good to me 15:12:53 that's it, I'll take notes of the "big things" you are all working on 15:13:19 (sorry, my boss came to my desk with a chatty attitude 15:14:04 Well, as CINECA, we will try test/sign-off as much as possible on UFT-8 ( bug 11944) 15:14:05 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11944 major, P5 - low, ---, gmcharlt, Needs Signoff , Cleanup Koha UTF-8 15:14:33 And on ACQ 15:15:10 tcohen: Ensure that the subject of discussion for development meetings motivate widespread interest and you should have sufficient participation. 15:15:33 thanks thd 15:15:35 We also probably send an RFC on ACQ, but also test/sign-off of others patch 15:15:52 I agree with thd ... I suggest making sure that the agenda for the dev meetings doesn't get too rote if you run them as frequently as twice a month 15:15:55 I like gmcharlt's two stage meetings to catch timezones.. do you intend on following suit tcohen? 15:15:58 bye 15:16:10 ashimema: yes 15:16:17 :) 15:16:42 one suggestion is (as often as possible) getting somebody to do a 10-15 minute presentation on some aspect of Koha development each emeeting 15:16:58 agree with the two above.. keep the agenda's tight, especially as they're going to be more frequent 15:17:01 (and I volunteer to do that at least a couple times) 15:17:20 my ultimate goal is that we share our problems with implementing stuff 15:17:35 sounds good to me.. also happy to volunteer from here (wether that be me, or me getting Colin to step up ;) ) 15:17:46 and that if (for example) we need to agree on an API definition so people can start coding, we can do it on the meeting 15:18:01 ashimema: there is a fine tradition of volun-telling folks who don't bother to attend the meeting ;) 15:20:37 ;) 15:20:53 tcohen: anything more you want to say? 15:20:54 Hi, I'm wondering what the status of the Koha plugin system is in 3.16. Can I run plugins on the opac site, and not only on the staff site? 15:20:59 Colin's working on EDI at the minute.. so I didn't fancy reminding him about the meeting ;) 15:21:02 ok, lets move to the tasty part 15:22:26 wosch: Koha's plugins currently support only staff-side functionality, in particular new items under the Tools and Reprts page 15:22:39 #topic Additions to Coding Guidelines 15:23:06 #info There is a proposal by cait to deprecate C4::SQLHelper now that DBIx::Class is available 15:23:11 #info more info on bug 11385 15:23:12 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11385 enhancement, P5 - low, ---, gmcharlt, NEW , C4::SQLHelper should be removed 15:23:34 cait++ 15:24:01 deprecation is easy enough in the sense of "no new code that uses SQLHelper" 15:24:19 I may poke at 11385 during the 3.18 cycle to work towards replacing it 15:24:30 for me ++ 15:24:35 gmcharlt: thanks for the clarification! 15:25:04 I'd adopt this coding guideline 15:25:23 +1 as well 15:25:36 and I hope the QA team agrees to enforce it for submissions 15:26:00 gmcharlt +1 for bringing all code to conform to current guidelines. 15:29:43 #agreed (pending confirmation) the coding guidelines will be revised to deprecate C4::SQLHelper 15:29:54 #topic How can we get "Bug 11944 - Cleanup Koha UTF-8" into Koha? 15:29:55 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11944 major, P5 - low, ---, gmcharlt, Needs Signoff , Cleanup Koha UTF-8 15:30:41 Joubu? 15:30:42 Joubu is, like, not his irc name 15:30:55 regarding magnuse's suggestion, though I am NOT old ;), I will volunteer to review the code and approach during the next few weeks 15:31:15 I also suggest the following - that a special sandbox be set up running the code 15:31:30 and I also suggest adopting magnuse's proposal of a GBSD solely for this bug 15:31:41 we do the best to test it (Paola Rossi) 15:32:46 #info Jane Wagner, LibLime/PTFS 15:32:50 apologies for being late 15:33:29 actually, cait's proposal of a dedicated GBSD 15:33:34 I think we need to have unit tests for encoding issues 15:33:43 agreed 15:33:56 Are there a unified set of patches for the bug which must all stand or fall together? 15:34:37 thd: many of the patches look like they need to stand together, but it also lokos like there are a few that could be split off and applied separately 15:34:51 so yeah, splitting those out would be good 15:35:46 Are there any current issues from which affect the character encoding storage or editing of bibliographic or authority records? 15:36:14 as far as I can tell, we have only ackknowledged visualization issues 15:36:19 and no others entry of bugzilla blocks it 15:36:50 The problem is on display/visualization, not store in DB o Zebra 15:37:39 ztajoli: though speaking of storage, you may find this to be of interest: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11811#c13 15:37:40 04Bug 11811: major, P1 - high, ---, dpavlin, In Discussion , tools/import_borrowers.pl doesn't support utf-8 encoded CSV 15:37:41 tchohen: There are past reports for the bug of problems with passwords and some other peripheral data storage issues. 15:37:46 For authority records, unimarc eng default setup gives problem 15:38:37 probably we need only to transfer french unimarc setup into eng 15:38:54 out of curiosity... who actively uses the English UNIMARC setup? 15:39:26 ztajoli: Does UNIMARC English setting affect the character encoding stored in the database? 15:39:45 And there the problems with pdf generation, label templating 15:40:16 Storing in database no 15:40:31 for unimarc default setup 15:40:44 but impossibile to use, so to input data 15:41:16 have we come to any conclusion regarding the proposals? 15:41:27 Probably no one use English UNIMARC authority setup. 15:42:07 But it is the default, so it used to test from Paola Rossi. So we find problems 15:42:12 tcohen: Do you have a simple test for automatically determining when character encoding is displaying incorrectly? 15:42:13 Who are actively working on this? 15:43:19 For test we use to insert Japanese kana and greek letters. No authomatic tests 15:43:22 unless somebody has any objections, I'm willing to volunteer to review the effort and to schedule a GBSD for it 15:43:31 (and to see about writing tests) 15:43:49 thd: the main issues IMHO are not explicitly decoding/encoding stuff as needed, or setting the proper config for the IO layer 15:44:31 there are places we can check for properly formed UTF-8 strings 15:44:44 gmcharlt: +1 15:45:25 #action gmcharlt will review the work for bug 11944 and organize a testing environment and a GBSD for some time in June 15:45:26 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11944 major, P5 - low, ---, gmcharlt, Needs Signoff , Cleanup Koha UTF-8 15:45:35 #topic Big stuff we are working on 15:46:15 gmcharlt: before that, who are working on 11944? 15:46:53 tcohen: I've said what I'm planning to do; at at this point, I think others need to step up to test as well 15:47:04 ok 15:47:38 tcohen: I should have some time to work on it in July. 15:49:01 any big projects to announce? 15:50:23 back again.. sorry got called away. 15:50:30 what is the status of ElasticSearch integration? 15:50:49 there's an effort underway for funding to work on it more 15:50:57 as I understand it, it's nealry 100% funded 15:51:12 so I'd expect updates from Catalyst at some point 15:51:15 eythian has been on alot of mornings (uk mornings that is) this week 15:51:25 maybe on part 2 15:51:26 he's been making inroads into it. 15:51:26 The main developer of 11944 is Jonathan Druart 15:51:59 he's probably best explaining state of affairs.. but I know he's looking for people to start testing now. 15:53:14 ok 15:53:23 we will all review what's been done 15:53:24 #topic Actions from previous dev meeting 15:53:30 #info there were no action items ;) 15:53:31 to make sure nothing breaks badly 15:53:36 #topic Set time of next meeting 15:53:46 tcohen: thoughts? 15:53:56 talking about UTF-8 cleanup 15:54:08 will we have those sandboxes set? 15:54:14 no, I mean about tsetting a date for the next meeting 15:54:33 June 4? 15:55:02 tcohen: there's a general meeting scheduled that day IIRC 15:55:15 yes 15:55:19 * tcohen is searching at the wiki 15:55:26 dug out ES progress git: http://git.catalyst.net.nz/gw?p=koha.git;a=shortlog;h=refs/heads/elastic_search 15:55:49 ok, next week then 15:56:06 June 11 15:56:21 +1 15:56:22 +1 15:56:25 +1 15:56:35 +1 15:57:09 same times? 15:57:23 yes 15:57:48 yes 15:57:55 #agreed (pending confirmation) the next development meeting will be on 11 June at 15 and 22 UTC 15:58:06 thanks, everybody 15:58:09 #endmeeting