14:00:20 #startmeeting Development IRC meeting 21 April 2021 14:00:20 Meeting started Wed Apr 21 14:00:20 2021 UTC. The chair is Joubu. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:20 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:20 The meeting name has been set to 'development_irc_meeting_21_april_2021' 14:00:25 no snow in the desert!! 14:00:29 right no 14:00:31 now 14:00:31 #topic Introductions 14:00:40 #info Jonathan Druart 14:00:47 sorry for interupting you! :) 14:00:54 #info Tomas Cohen Arazi, Theke Solutions 14:00:56 #info Nick Clemens, ByWater Solutions 14:01:05 #info Thomas Dukleth, Agogme, New York City 14:01:19 #info Henry Bolshaw, House of Lords Library, UK 14:01:24 #info Joy Nelson, ByWater Solutions 14:01:31 #info Owen Leonard, Athens County Public Libraries, Ohio, USA 14:01:43 #link https://wiki.koha-community.org/wiki/Development_IRC_meeting_21_April_2021 14:02:04 hi all :) 14:02:06 #topic Announcements 14:02:10 Anyone have something? 14:02:35 #info Martin Renvoize, PTFS-Europe 14:03:00 #topic Update from the Release Manager (21.05) 14:03:09 Release dates have been announced on the general mailing list earlier today: 14:03:12 * May 1st - "Soft" feature freeze, nothing big or with high risk of side-effects will be included into the final release if not marked as Passed QA 14:03:16 * May 4-7 - "Hard" feature freeze, nothing considered as an improvement will be pushed if not marked as Passed QA 14:03:20 * May 12th - String freeze, draft of release notes published 14:03:23 * May 19th - Only bug fixes considered as major, critical or blocker will be pushed 14:03:27 * May 28th - Final release 14:03:34 Joubu++ 14:03:44 how does it sound? 14:04:06 Great, releasing a friday means beer party 14:04:06 +1 14:04:19 I will start using the rel_21_05_candidate bz keyword more and more, keep an eye on it - https://frama.link/koha_bz_rel_21_05_candidate 14:04:20 +1 14:04:20 souns good but scares me the same time 14:04:22 does that count? 14:04:27 It sounds great but everything is happening so fast! 14:04:33 #info Katrin Fischer, BSZ, Germany 14:04:46 henryb foudn the better words :) 14:05:02 +1 14:05:06 cannot be later than on 28th :) 14:05:11 indeed 14:05:23 You should also watch the bug reports with missing release notes 14:05:24 it's the usual flow 14:05:28 There is a shared search 14:05:35 https://bugs.koha-community.org/bugzilla3/buglist.cgi?cmdtype=dorem&list_id=369387&namedcmd=Needs%20release%20notes&remaction=run&sharer_id=378 14:05:44 #info Kyle M Hall, ByWater Solutions 14:05:57 #info keep an eye on the 21.05 candidate list https://frama.link/koha_bz_rel_21_05_candidate 14:06:16 #info Watchout the missing release notes! https://bugs.koha-community.org/bugzilla3/buglist.cgi?cmdtype=dorem&list_id=369387&namedcmd=Needs%20release%20notes&remaction=run&sharer_id=378 14:06:30 To clarify, I wasn't suggesting the timetable should change I'm just surprised how quickly time passes :) 14:07:16 heh yes, only 1 month left! 14:07:17 I understood it like that 14:07:19 5 weeks! 14:07:26 is there a new roadmap doc for planning the next cycle yet? 14:07:52 ashimema: we could start thinking about it indeed, like in 2 weeks? 14:07:56 Project Koha_Master_D9_MDB_Latest build #568: UNSTABLE in 34 min: https://jenkins.koha-community.org/job/Koha_Master_D9_MDB_Latest/568/ 14:08:29 * ashimema likes to have a place to put things early.. that way he can put them there then they're out of his brain so he can concentrate on the more immediate tasks 14:08:32 ~2 weeks before the release. But we should focus on 21.05 first :) 14:09:00 haha.. I'll just note mine locally for now then .. and try to get them out of my brain 14:09:22 yes, I have mine already as well ;) 14:09:36 will be fun to merge them 14:09:50 #topic Updates from the QA team 14:10:01 Writing things tends to reduce brain consumption. 14:10:19 NQA queue is back under 100 14:11:01 but still too many, and we have 2 criticals + 2 majors 14:11:05 I've struggled to focus on QA much this month.. only really had a couple of days 14:11:14 same here 14:11:16 trying to do what I can when I can 14:11:19 we need more hands on deck 14:11:29 little dissapointing I'm still number 3 in the list.. even with that being the case 14:11:42 * oleonard has been trying to focus on non-enh signoffs 14:11:55 nice one oleonard 14:12:01 yep 14:12:03 that's the way oleonard, thanks :) 14:12:07 but we also have some long istting stuff 14:12:22 istting? 14:12:24 personally... I'd be really really happy to see bug 14237 movign 14:12:24 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14237 enhancement, P2, ---, aleisha, Signed Off , Allow bibs to be added to course without items 14:12:30 sitting sorry 14:12:31 hi 14:12:58 Hi maya-das we are in the middle of a developers meeting at the moment, stick around until after if you have a question 14:13:02 cait: will take a look today 14:13:04 hi maya-das - we are just in ameeting, you are welcome to stay, but questions might be a bit hard to answer right now 14:13:18 oleonard: jinx? :) 14:13:27 :) 14:14:02 oleonard >> ok 14:14:02 nothing more to add for QA i think 14:14:04 something else for/from QA? 14:14:15 please look at the bad and the old as pointed out in my mails :) (and beyond those of course) 14:14:33 #topic Updates from the Release Maintainers 14:14:58 (yes I did swap the 2 topics!) 14:15:30 trying to keep us on our toes 14:15:35 April releases are expected for Monday 26th 14:15:38 #info April releases are expected for Monday 26th 14:15:49 i noticed the strings haven't been updated for 20.11 14:16:03 they had been already updated before, but not since fridolin announced and there were some strings pushed 14:16:27 do we need to ping Bernardo? 14:16:43 i am not sure, i was hoping to catch fridolin today, but haven't spotted him yet 14:16:47 i am nto sure how this works at the moment 14:16:54 Were you saying pootle is not up-to-date? 14:16:58 it looks like the scheduled string update around 15th happened 14:17:00 but none after 14:17:08 yes 14:17:20 also.. manual builds for 20.11 are broken again 14:17:23 after 15th new strings were pushed and 20.11 string frezeed announced 14:17:38 ok, we will catch Frido when he will be around then 14:17:39 but i am waiting for some navigation links to show up and they haven't yet 14:18:08 bug 28006 14:18:08 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28006 enhancement, P5 - low, ---, oleonard, Pushed to stable , Restore "Additional fields" link on serials navigation menu 14:18:08 ashimema: because of disk space issues again? 14:18:17 I don't think so 14:18:42 it was the merges of translations that hit it.. those builds are taking longer than the 1h timeout on gitlab build servers I think 14:18:47 I've not investigated deeply yet 14:19:07 @later tell fridolin looks like the string for 20.11 are not up-to-date on pootle, something missing in your workflow for April? 14:19:07 Joubu: The operation succeeded. 14:19:13 string*s* 14:20:00 ashimema: erk, did you raise an alert flag? Can we extend the timeout? 14:20:16 I literally got told about it 20 mins before this meeting 14:20:17 ;) 14:20:23 so haven't done anything yet ;) 14:20:26 ok, will see after the meeting then :) 14:20:33 looking at the builds it's been dead for a month 14:20:40 #topic Status of roadmap projects 14:21:07 things are stuck for most of the topics 14:21:20 I am still hoping a QA stamp on bug 22544 14:21:20 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22544 enhancement, P5 - low, ---, jonathan.druart, Patch doesn't apply , Move C4:NewsChannels to Koha namespace 14:21:51 ha, does not apply! I missed that one :D 14:21:54 Katrin was on that.. but it's failing to apply 14:21:56 aha :) 14:22:16 and some QA issues need to be fixed on bug 14957 14:22:16 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14957 new feature, P5 - low, ---, glasklas, Failed QA , Write protecting MARC fields based on source of import 14:22:16 yeah i tried, but didn't get far sorry 14:22:22 same 14:22:41 I will rebased the news stuff right after the meeting! 14:22:44 #info Mason James, NZ 14:22:57 #topic Actions from last meeting 14:22:58 hi people, sorry i'm late :) 14:23:04 #topic Joubu create the "roles for 21.11" wiki page and send an email to the list 14:23:12 done, see https://wiki.koha-community.org/wiki/Roles_for_21.11 14:23:27 (lot of people missing there!) 14:23:32 hi mtj - difficult time for you! 14:23:56 maybe weshoudl put election date on the page 14:24:01 that's been set already, right? 14:24:07 yes, next general meeting 14:24:07 somebody said next general meeting was 13 November, so does 14 November 13:00 ITC work okay? 14:24:20 https://wiki.koha-community.org/wiki/General_IRC_meeting_12_May_2021 14:24:27 12 May 2021, 14:00 UTC 14:24:34 and add elections there? 14:24:35 i am on it 14:24:42 thanks 14:25:00 #topic mtj write something about the new packages for the 21.05 release notes 14:25:05 done - https://wiki.koha-community.org/wiki/Package_types 14:25:08 thanks mtj for that one! 14:25:41 #info New wiki page to explain the different debian packages has been written - https://wiki.koha-community.org/wiki/Package_types 14:25:56 #topic ashimema Write a coding guideline to clarify our message types: 'alert' vs 'error' (context of bug 27695) 14:25:56 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27695 minor, P5 - low, ---, oleonard, Pushed to master , Fix style of messages on Elasticsearch configuration page 14:26:18 I need to postpone that one once again 14:26:33 sorry.. just haven't had a moment 14:26:35 #action ashimema Write a coding guideline to clarify our message types: 'alert' vs 'error' (context of bug 27695) 14:26:43 thanks 14:26:46 #topic General development discussion (trends, ideas, ...) 14:26:54 #topic Email unsubscribe - CAN-SPAM / GDPR - how to implement opt-out for Koha 14:26:56 kidclamp: ? 14:26:57 wiki updates done 14:27:12 This is something we are working on as we face some issues in sending out emails 14:27:33 Patrons will mark messages as SPAM, this eventually can put our servers on block lists 14:27:48 interesting 14:27:53 one of the features that is needed is an 'Unsubscribe' link in the messages 14:28:15 or alternately, a way to show that patrons have agreed to receive transactional message 14:28:15 sounds like a good idea in general 14:28:18 yes, definitely 14:28:41 really we are interested in whether there are any GDPR related issues around this, or if anyone else int he community faces this problem? 14:28:43 yup.. 14:28:55 it's mandatory 14:28:55 we've never had such a problem 14:29:05 you have to include an unsubscribe link 14:29:14 (I...think) 14:29:22 not sure if that applies to overdues 14:29:35 how have libraries implemented it? 14:29:58 in theory overdues are excluded for us too, but in practice they still count against us 14:30:18 I know that there is discussion about informational emails 14:30:24 if it's not related to their actions witht he library 14:30:30 you can't just emai them things 14:30:45 but stuff related to their circulation directly (renewal, overdue) should be ok i think 14:31:15 if we get questions about other types of email we help get a list, but we tell them to check with their appointed data privacy person 14:32:14 if that makes sense? we haven' t had requests so far as you can opt them out of most messages and we are not using all of them anyway 14:32:41 via messaging preferences you can turn off a lot of the emails... are there some more problematic than others? 14:32:50 the patron_emailer script doesn't have an opt-out currently 14:33:05 yeah we don't use that at all at the moment 14:33:11 and I think ooffering an unsubscribe on the overdues would be an eventual goal for us 14:33:59 if it's a marker you put in the templates, it's would be easy to control when it shows 14:34:07 Kyle and I discussed this morning the possibility of adding 'my messages' to patron opac view, and adding a transport of way for patrons to get notices in the opac, but not necessarily have them 'sent' 14:34:32 i think there is an open bug to have the message view i staff in opac too alreay 14:34:39 that goes the same direction 14:34:40 for unsubscribe I really wonder about just linking to the patron messaging preferences 14:34:50 largely though, it sounds like no one is finding they need additional option to meet GDPR requirements or others? 14:34:54 and then we culd have a message transport type "opac" to 14:34:55 and trying to follow through and add more of the notices to that set 14:35:03 but i'd still show them all if we are on that already 14:35:08 that's a nice idea, kidclamp. Even we could enqueue things even if a patron does not have the mtt (like no email), and it would be visible in their OPAC account 14:35:23 I do like that idea too 14:35:45 kidclamp: ask the list? :) 14:35:57 #info tuxayo/Victor Grousset, France 14:36:20 * tuxayo scrolls back 14:36:39 Project Koha_Master build #1620: UNSTABLE in 1 hr 2 min: https://jenkins.koha-community.org/job/Koha_Master/1620/ 14:36:44 can do, we are working on deciding waht we need and how we should implement, so just collecting info for now 14:37:08 kidclamp: i think having privacy features like that is never wrong, even if it's not a must have maybe 14:37:13 or not a must have evrywhere 14:38:12 talljoy: any more questions you have? 14:39:16 I think we can move on, and we will email the list if we have more questions 14:40:04 #action kidclamp Ask the ML for additional info about how to implement opt-out for notices. One idea would be to have "My message" at the OPAC 14:40:23 #topic Set time of next meeting 14:40:56 Project Koha_Master_D9 build #1624: UNSTABLE in 32 min: https://jenkins.koha-community.org/job/Koha_Master_D9/1624/ 14:41:06 #info Next meeting: 5 May 2021 14 UTC 14:41:21 no objections? 14:41:27 5sec 14:41:31 #endmeeting