14:02:49 #startmeeting Development IRC Meeting 7 June 2023 14:02:49 Meeting started Wed Jun 7 14:02:49 2023 UTC. The chair is tcohen. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:02:49 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:02:49 The meeting name has been set to 'development_irc_meeting_7_june_2023' 14:03:09 #link https://wiki.koha-community.org/wiki/Development_IRC_meeting_7_June_2023 14:03:17 #info Katrin Fischer, BSZ Germany 14:03:19 #topic Introductions 14:03:26 #info Tomas Cohen Arazi 14:03:39 #info Katrin Fischer, BSZ Germany 14:04:14 #info Nick Clemens, ByWaterSolutions 14:04:25 #info Thomas Dukleth, Agogme, New York City 14:04:43 #info Jonathan Druart 14:05:08 qa_team? 14:05:08 well, qa_team is cait, marcelr, khall, kidclamp, lukeg, aleisha, fridolin, ashimema, tuxayo, nugged, petrova, Joubu and dcook 14:05:20 RMaints? 14:05:20 somebody said RMaints was liliputech, wainui, lukeg and ashimema 14:05:26 needs updating :) 14:05:54 #info Owen Leonard, Athens County Public Libraries, Ohio, USA 14:06:00 #info Laura Escamilla, ByWaterSolutions 14:08:27 moving on? 14:08:46 yes 14:08:46 #info Martin Renvoize, PTFS Europe (Half here and in another meeting) 14:08:53 #topic Announcements 14:09:25 Anyone? 14:09:25 Anyone is free to give it a shot :-) 14:09:27 Is there any news on KohaCon? 14:09:46 did we get the info we were supposed to get end of May? 14:09:58 Hotels - not yet I think 14:10:19 I didn't see any end-of-May updates 14:10:20 nugged: around maybe? 14:11:42 #info German speaking Koha user meeting is scheduled for December 5th - CfP is open (see Koha calendar and koha-dach.eu) 14:13:35 can we make this faster maybe? 14:13:41 @later tell nugged: please show up and give us info 14:13:41 tcohen: The operation succeeded. 14:13:53 #topic Update from the Release Manager (23.11) 14:14:23 #action tcohen will send a roadmap page for 23.11 today 14:14:38 #action tcohen will send a call for testing CSRF fixes 14:15:04 I wanted to mention that I'll propose we use Zoom or similar for the next dev meeting 14:15:15 about the roadmap 14:15:17 could we move it to the wiki? 14:15:27 cait: yeah, excellent idea 14:15:29 +1 14:15:29 I think the framapad is a little chaotic and it's another tool/somethign that is not found 14:15:42 thanks cait 14:15:57 no need to action or announce on that, the link will be to a wiki page 14:16:16 about Zoom: let's try it 14:16:26 I've started pushing 14:16:29 things to master 14:16:32 shoudl we still use IRC for the minutes? 14:16:45 I decided to push early, things we always say we shuold push early 14:16:45 :-P 14:16:57 cait: yes, we will still use IRC for logging 14:17:09 We should still use IRC for freedom. 14:17:12 and I'm proposing this for the dev meetings 14:17:56 thd: we will give it a try 14:18:08 and see how it goes 14:18:32 when I said Zoom or similar 14:18:40 I meant whatever tool we prefer 14:18:46 we should probably use Jitsi 14:19:27 ok moving on 14:19:39 #topic Updates from the Release Maintainers 14:19:46 rmaints? 14:19:46 well, rmaints is liliputech, wainui, lukeg and ashimema 14:19:56 wahanui forget that 14:19:56 tcohen: I forgot that 14:20:06 :D 14:20:35 22.11.x is catching up.. don't think I've seen anything hit 23.05 from Frido yet 14:20:53 yeah 14:21:06 ooh.. I have seen a few now 14:21:07 anyone from biblibre around today? 14:21:18 or was that you tcohen 14:21:26 ashimema: I pushed a couple things 14:21:29 no rmaints is fridolin (23.05), PedroAmorim[m] and MatthewBlenkinsop[m] (22.11), lukeG (22.05) and Danyon (21.11) 14:21:35 coolios 14:21:43 Joubu++ 14:21:44 no rmaints? 14:21:44 somebody said no rmaints was fridolin (23.05), PedroAmorim[m] and MatthewBlenkinsop[m] (22.11), lukeG (22.05) and Danyon (21.11) 14:21:45 and I have no idea who is Danyon 14:21:48 Joubu++ 14:21:52 not sure that worked like you wanted :) 14:21:53 rmaints? 14:21:54 rmaints is probably liliputech, wainui, lukeg and ashimema 14:21:56 He's new from Catalyst 14:21:57 I asked that 14:21:58 forget rmaints 14:21:58 cait: I forgot rmaints 14:22:07 either an intern or brand new staff 14:22:10 no wahanui, rmaints is fridolin (23.05), PedroAmorim[m] and MatthewBlenkinsop[m] (22.11), lukeG (22.05) and Danyon (21.11) 14:22:13 rmaints? 14:22:13 rmaints is fridolin (23.05), PedroAmorim[m] and MatthewBlenkinsop[m] (22.11), lukeG (22.05) and Danyon (21.11) 14:22:14 forget no rmaints 14:22:14 tcohen: I forgot no rmaints 14:22:19 he's being backed up with Wanui I think? 14:22:26 yes, that#s what the wiki says 14:22:36 could be good to have them on IRC sometimes 14:22:39 I added it when i asked them 14:22:43 yeah 14:23:08 #actions tcohen will update the koha-release-team@theke.io email alias 14:23:20 Joubu: lol 14:23:24 ++ 14:23:45 #actions tcohen will update the koha-qa-team@theke.io email alias 14:23:47 what about post release actions? 14:24:04 https://tree.taiga.io/project/koha-ils/us/19 14:24:21 Bugzilla update is pending, but I'll get to it 14:24:38 I stil need to update the gitea access 14:24:41 We need Liz to update the front page with the new version (bug in website templates) 14:24:42 I wasn't able to access Gitea when was willing to update permissiosn 14:25:00 and I think manuals might need changes at some point 14:26:39 liz already updated the frontpage 14:26:52 but there's some caching she's not solving yet 14:26:54 it still says 22.11 14:26:57 aaah ok 14:27:13 ok, moving on 14:27:16 wait 14:27:26 does anyone have DAnyon's email address? 14:27:50 in good news: i updated the demo page, we have a first 23.05 demo from Admin Kuhn 14:27:55 tcohen: i thin it's n bugzilla already 14:28:08 cait: Xercode's is 23.05 as wel 14:28:09 I'll pm you 14:28:29 it's was master when I last checked 14:28:40 @later tell fridolin let's talk about the post-release actions that involve 23.05 14:28:40 tcohen: The operation succeeded. 14:28:44 23.06 - listed as development 14:28:50 ok 14:29:29 #topic Updates from the QA Team 14:29:32 Danyon's contact can be found on Bug 24401 14:29:32 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24401 new feature, P5 - low, ---, danyonsewell, Needs Signoff , REST API: Check-in 14:29:54 pm'd you the email address tcohen 14:29:58 thanks 14:30:05 oleonard++ 14:30:08 cait++ 14:30:13 Otherwise, I asked the QA team about some lessons learned and will respont to emails soon :) 14:30:16 the stage is yours 14:30:54 As always, we need more hands and brains than we have available, but I think we did a good job for 22.11 in keeping the old ones out of the list 14:31:52 the number... have been a bit too high at times for my liking, but something we can work on 14:32:01 qa_team++ 14:32:17 join QA, it's fun and we like people who know how to break stuff :) 14:33:24 nothing more from me 14:33:29 ok, moving on, will skip KohaCon and roadmap 14:33:54 #topic Actions from last meeting 14:33:58 cait? 14:33:58 i guess cait is looking at the smaller enh still as they can still go in until next week 14:35:09 which agenda are we following exactly? 14:35:20 https://wiki.koha-community.org/wiki/Development_IRC_meeting_7_June_2023 14:35:21 ? 14:35:43 I think Joubu means we skipped roadmap and KohaCon24? 14:36:01 I think only KohaCon24 14:36:05 (no KohaCon23 update forthcoming obviously) 14:36:06 ha, you said skipping KohaCon, but what next for KohaCon24? 14:36:15 sorry, lagging... 14:36:21 we could start asking the user groups again 14:36:33 #topic KohaCon24 14:36:47 there is "Extend to all continents?" 14:36:48 but we need to extend the deadline for sure, it says April 4 14:37:04 yes, we also could do that 14:37:23 it would mean adding back US and Europe to the list of eligible continents 14:37:50 ha.. 14:37:59 extend to all continent was my idea since no one volunteered from the eligible continents... But it can be as a last resort 14:38:19 * ashimema votes InLibro hosts 14:38:21 😉 14:38:29 +1 ! 14:38:31 inlibro++ 14:38:38 let's vote 14:38:39 never been to your neck of the woods 14:38:46 lol! I can ask, but we have to extend to all continents ;) 14:38:48 😂 14:38:55 deal 14:39:21 I don't think we should hesitate to extend to all continents after giving everyone a chance to volunteer 14:39:30 yeah 14:39:34 +1 14:39:35 we should set a rule 14:39:41 if deadline passes 14:39:46 I thought we had a rule. 14:39:49 [off] I keep thinking about it bc our new office has a really nice venue, and I'd love to have you all here 14:39:50 the limit is lifted 14:40:47 caroline: action you to update the wiki page? :) 14:40:55 or is that a conflict of interest now? 14:40:59 I think KohaCon24 should be discussed on a general meeting 14:41:08 we only have 4 nowadays 14:41:17 Yes, with details of Inlibro's proposal ;) 14:41:35 the last general meeting was missed and I don't think any was scheduled after 14:42:06 let's schedule one? 14:42:28 so we are not lifting the limit or just to discuss proposals? 14:42:44 we lift the limit 14:42:57 and we schedule a general meeting, to consider inlibro's proposal 14:43:09 :D 14:43:13 ok 14:43:15 when? 14:43:24 caroline: how much time do you need? ;) 14:44:10 #info The 'different continent' rule for KohaCon24 is lifted as there were no elegible proposals 14:44:34 caroline: Just tell the boss we came to a binding agreement without them 14:45:01 lol! He's out for the week, but I can bring the idea to him next week 14:45:09 time to vote then! 14:45:13 hahaha 14:45:19 inlibro++ 14:45:31 moving on hten? 14:45:46 #topic Roles for 23.11 14:46:04 [off] I need to hurry because kid's lunch is approaching 14:46:14 do we have all roles filled? 14:46:26 #link https://wiki.koha-community.org/wiki/Roles_for_23.11 14:46:56 Nothing under meeting facilitator, translation manager, packaging team... 14:47:01 https://wiki.koha-community.org/wiki/KohaCon24_Proposals updated the wiki page with a note, please check 14:47:20 mtj: are you willing to continue packaging Koha? 14:47:24 "cait and ashimema will put together the TODO notes from the hackfest on the Wiki" 14:47:30 has this been done? 14:47:36 i forgot which notes 14:47:39 Joubu: they skipped my question about it 14:47:39 lol 14:47:44 ha.. I thought we had 14:47:48 was that the missing docs notes? 14:47:52 but my brain is all fluff right now 14:48:07 we need to prepare meetings :D 14:48:12 yes 14:48:13 or that's messy 14:48:13 https://wiki.koha-community.org/wiki/Release_Teams will need further updates (and the bug too) if we change the team more 14:48:23 Joubu: are you also FQA our meetings? LOL 14:48:27 I saw the note earlier, but didn't remember, so wanted to ask (was prepared to ask ;) ) 14:48:28 yes, definitelly 14:48:35 :-P 14:48:48 anyway, maybe remove it for now 14:49:40 #action everyone should sign for 23.11 roles 14:49:54 we are missing an IRC meeting facilitator actually 14:50:02 Translation and Packaging 14:50:06 we have the RM improvising 14:50:12 and Newsletter editor 14:50:29 I can ask our current newsletter editor 14:50:36 there is a list there - https://wiki.koha-community.org/wiki/Development_IRC_meeting_26_April_2023 14:50:45 #link https://wiki.koha-community.org/wiki/Roles_for_23.11 14:51:17 which list? 14:51:22 oh, right 14:51:27 the TODO from the hackfest 14:51:46 ah right, I'l do that this week 14:52:19 what are we doing about the missing roles? 14:52:45 I'd love to recruit and Accessibility Advocate too 14:53:00 I don't think there's anything we can do 14:53:13 Vote for press gangs. 14:53:21 about translations... bgkriegel will keep doing what he does 14:53:30 and we don't have volunteers 14:53:43 luckily we've got some documentation on the things we need to run 14:54:32 We need to find a time to fix the manuals 14:54:40 who? 14:54:44 still no po files for the LTS manual 14:54:59 22.11 14:55:04 I've emailed many times 14:55:15 yeah, we need someone to volunteer 14:55:49 I am happy to test, but I think I can't do the technical part 14:57:13 can we jump to the codign guidelines review? 14:57:21 yes 14:57:32 I emailed for newsletter editor 14:57:59 I will ask rangi about the perldoc site, maybe we can build it automatically as we do with the api docs. Happy to take on that 14:58:19 I am nto sure if he runs that, used to be gmcharlt 14:58:20 and gitea, Joubu and I will upgrade it to latest Forgejo any time soon 14:58:27 ok 14:58:40 yep 14:58:54 happy to enterain discussing of moving it 14:59:02 * cait jumps 14:59:18 gmcharlt: do you have a script to build that? 14:59:24 or any docs? 14:59:39 we should make a gitlab project for it if possible 14:59:42 gmcharlt: sorry, but as you are here... can we have recent years? :) https://meetings.koha-community.org/ 15:00:12 newsletter editor is filled now :) 15:00:39 gmcharlt: can we schedule a call to talk about those services 15:00:51 wiki, meetings, perldoc 15:01:48 I ask because I need to leave soon 15:01:59 and I'm interested to talk now we have you here 15:02:46 ok moving on 15:02:53 #topic Review of coding guidelines 15:03:23 Any objections to adopt a perltidyrc for the project? 15:03:33 nope, push it :D 15:03:35 (once it is approved by devs on the bug) 15:03:39 yeah, of course 15:03:42 go for it 15:03:45 I'm using it already 15:03:50 me too 15:03:51 ok, stamp your signature ashimema 15:03:59 we should all set it up for a month and agree with it 15:04:12 I've been using it on VSCode 15:04:13 I think I already did 15:04:24 though actually.. I raised some concerns I think 15:04:30 updating the notes on how to use it with different editors would be nice 15:04:41 let's discuss the perltidyrc on the bug 15:05:01 #action Joubu will document on the wiki how to set the perltidyrc on vim 15:05:04 https://wiki.koha-community.org/wiki/Perltidy 15:05:15 #action tcohen will document on the wiki how to set perltidyrc on vscode 15:05:34 #link https://wiki.koha-community.org/wiki/Perltidy 15:05:37 I can try for Geany (might be the only one using it) when I see how you do it :) 15:05:46 excellent cait 15:05:47 cait++ 15:05:47 I've added it already to the suggestion for the guideline, but yes I can add it there as well 15:06:13 the wiki page says we don't use one, so should change that for sure, maybe with link to coding guidelines 15:06:13 About password field treatment 15:06:40 @later tell mtj please have a look at bug 30002 comment 23 15:06:40 Joubu: The operation succeeded. 15:07:49 anyone volunteers to document how password fields should be handled? 15:08:16 what's the problem? 15:08:16 That sounds like my department, I'll have to review the bug to get up to speed 15:08:16 the problem is probably time travel hasn't been invented. 15:08:32 quck, action oleonard :) 15:08:49 oleonard++ 15:08:53 there is nothing to do, add autocomplete="off" 15:08:55 excellent 15:08:55 darn tootin' it is. 15:09:06 there are a couple new attributes 15:09:07 looks like more that we need tests to catch regression 15:09:17 new-password or similar 15:09:46 indeed, I hadn't seen that one 15:09:58 ok, oleonard will look at it 15:10:13 #topic Set time of next meeting 15:10:19 I remembered this time 15:10:56 can we agree on 21 June? 15:11:32 +1 15:12:06 +1 15:12:14 at 18 UTC so fridolin can join?? 15:13:58 #info Next meeting: 21 Jun 2023, 14:00 UTC 15:14:08 * thd might be more awake. 15:14:10 tcohen++ 15:14:12 #endmeeting