14:01:33 #startmeeting General IRC meeting 17 January 2024 14:01:33 Meeting started Wed Jan 17 14:01:33 2024 UTC. The chair is ashimema. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:33 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:33 The meeting name has been set to 'general_irc_meeting_17_january_2024' 14:01:40 #chair aude_c 14:01:40 Warning: Nick not in channel: aude_c 14:01:40 Current chairs: ashimema aude_c 14:01:48 #link https://wiki.koha-community.org/wiki/General_IRC_meeting_17_January_2024 Agenda 14:01:54 #topic Introductions 14:01:59 #info Please introduce yourself for the minutes with an #info 14:02:06 #info Owen Leonard, Athens County Public Libraries, Ohio, USA 14:02:06 #info Aude Charillon, PTFS Europe, UK 14:02:07 #info Martin Renvoize, PTFS Europe, UK 14:02:11 #info George Williams, Northeast Kansas Library System 14:02:23 oooh, there are a few people here 🙂 14:02:50 #info Katrin asked Aude and I to step in and chair, she sends her apologies, she has a clash. 14:02:51 #info Emily Lamancusa, Montgomery County Public Libraries, USA 14:02:51 #info Brendan Lawlor, CLAMS, Hyannis, MA, USA 14:02:54 #info Jessica Zairo, ByWater 14:03:01 #info Tomas Cohen Arazi 14:03:02 #info Thomas Dukleth, Agogme, New York City [power and light is back on] 14:04:01 #topic Announcements 14:04:02 brill, lots of friendly people 🙂 14:04:15 Almost regretting not setting up Jitsi link 14:04:26 #info Happy new year everyone! 👋 14:04:59 Any other announcements? :) 14:05:32 it's my first time attending an IRC meeting, so I'm kinda glad you didn't set up a jitsi this time 14:05:33 #info No specific announcements from the RM, we've started pushing enhancements and she's working through the queues now. Please keep QAing, that queue is rather high. 14:05:38 I notice that there is no Jitsi link for next week's development meeting. 14:06:26 * ashimema hasn't done the jitsi links before.. so I'm not sure how they're done.. hence not getting one in there when I noticed a little last minute a few minutes ago 14:06:44 #action aude_c to let cait know there is no Jitsi link for next week's development meeting 14:07:10 It's super easy and I could do it in seconds if people here wish to see each other's faces 14:07:19 No marcelr, so I'll re-iterate the call to arms around QA in his stead 14:07:30 * oleonard is happy to stick with IRC today 14:07:38 #info Fridolin Somers, Biblibre, France 14:07:39 ashimema: They seem to be fairly generic unless I have missed something. 14:07:57 #info QA queues are high, lets bolster efforts a little team 😉 14:08:21 I think that's all the noted announcements I had.. does anyone else here have anything they'd like recorded? 14:08:46 ooh, hackfest 14:10:17 #info There will be a Marseille Hackfest again this year, a little later though from 8th - 12th April. Biblibre have moved offices, so numbers may be a little more limited, but they are investigating additional office space options right now. 14:10:38 lets move on then 14:10:48 #topic KohaCon24 update 14:10:50 #topic KohaCon24 update 14:10:56 #info Caroline posted an update. 14:11:03 #link https://2024.kohacon.org/kohacon-2024-learning-and-building-together/ 14:11:10 #info Dates for KohaCon 2024 announced! 23 to 27 September 14:11:30 #info The call for proposals is open too. Use the link from the website or go straight to https://sondagebiblio.org/index.php/835536?lang=en 14:11:33 is there any way to participate in the hackfest remotely? 14:11:35 excellent 🙂 14:12:17 Brendan__CLAMS: Hi, it is not usally with a virtual connexion 14:12:34 any with the small place it migth be difficult 14:12:52 but everyone still is on IRC 14:12:53 The Marseille Hackfest tends to take a fairly organic approach.. i.e. the agenda gets built as we go.. However, there's often some zoom/jitsi etc interactions.. so if you're interested in joining any particular discussions or bringing anything in particular up I'm sure something can be arranged. 14:13:11 yep 14:13:24 Cool! thank you 14:13:27 we have the same need with corporate meetings 14:13:34 For example, we've had join EDI calls with the Swedish user groups in the past 14:13:36 sorry, I just came in, but I think everything has been said 14:13:47 and erm demonstrations.. 14:14:04 we may also record and broadcast some talks 14:14:10 keeping an 'ear' on irc is the best way to not miss something that's a little on the spur of the moment. 14:14:46 Anything else on Hackfest or KohaCon? 14:14:59 as for the KohaCon hackfest section.. I'll leave Caroline to elaborate there if there's anytihng to say 🙂 14:15:49 Nothing is set in stone. The "conference" part is for sure streamed online. We have no plan for streaming hackfest workshops, but we can surely do jitsi meets to include remote people 14:17:03 #info KohaCon24 conference very likely to be streamed, HackFest may include Jitsi meets to allow remote attendance, but more informally at the moment. 14:17:13 shall we move on.. 14:17:19 #topic Actions from last meeting 14:17:34 conference *for sure* streamed :) 14:17:42 #info All actions completed :D 14:17:50 Looks like we just have one leftover action which I think is a copy/paste from the last agenda 🙂 14:18:35 Unless anyone wants to own up to another action? 😅 14:18:47 #topic General business 14:18:49 not guitly.. this time 14:19:29 #info Do we want to start naming releases - or not? There was some discussion on bug 35504 14:19:29 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35504 blocker, P5 - low, ---, martin.renvoize, Pushed to stable , Release team 24.05 14:19:49 #link https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35504 14:19:49 04Bug 35504: blocker, P5 - low, ---, martin.renvoize, Pushed to stable , Release team 24.05 14:20:14 22.11 actually had the first codename, 'Rosalie' as a dedication to Rosalie Blake. 14:20:58 The discussion on bug 35504 was around adopting codenames more regularly and perhaps celebrating the current cycle having our first female in the Release Manager role. 14:20:59 Is the bug citation the correct bug number? 14:21:15 yeah.. discussion was 'an asside' in that bug 14:21:21 Yes, but the discussion is in the early comments 14:21:36 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35504#c2 14:21:36 04Bug 35504: blocker, P5 - low, ---, martin.renvoize, Pushed to stable , Release team 24.05 14:21:42 the codename was not added in the bug before we discus the idea here and get some sort of consensus. 14:21:54 I find the date numbering system to be so useful I don't think the naming of releases needs to be standard, but I'm happy to see it happen for special occasions. 14:22:11 +1 14:22:29 I agree.. I suppose the question is.. 'Is our first female rm a special occassion 😜 ' 14:22:43 ++ 14:22:51 I think that would be something to celebrate! 14:22:55 I certainly wouldn't want to switch away from the date system.. codenames are 'extras' in my eyes 14:23:04 I have a feeling cait would not want the release to be named after her 14:23:26 I suppose 3.14 sorta had a codename too.. it was 'Pie' 14:23:40 It doesn't have to be her name 14:23:50 #info Several people agree that naming of releases doesn't need to happen as the standard, but could happen for special occasions 14:23:53 we may use somthing close like "Catarina" 14:24:03 haha, indeed.. when I suggested he idea to her, she was more onboard with naming it after another famous women in tech 😜 14:24:11 how about Henriette for the programmer who created marc 14:24:23 That sounds cool 14:24:30 A dubious distinction XD 14:24:46 ;) 14:24:51 lol 14:25:03 I like that.. catches 'Library' and 'Technology' in one hit 14:25:27 and women in library and tech 14:25:34 And it's a cool name 14:26:00 a french touch 14:26:00 #info Should we treat our first woman Release Manager as a "special occasion" and therefore name the 24.05 release? If so, what could this name be? (that our RM herself would agree with) 14:26:27 Are we talking about Henriette Avram? https://www.loc.gov/loc/lcib/0605/avram.html 14:26:40 Shall I open a bug for it and we can put suggestions there for a vote next meeting? 14:26:48 Good evening all 14:26:48 I assume that everyone now knows that MARC is well preserved inside BibFrame as some major academic libraries objected to everything being left out of the original simple design of BibFrame 14:27:05 Can we increase barcode text 14:27:27 TriveniChandriki[m]: we are in a meeting at the moment 14:27:31 #info Suggestion of Henriette Avram, who created MARC 14:27:59 Oh sorry carry on 14:28:00 [off] Good for Henriette for getting out of the NSA and into LOC 14:28:09 #action ashimema to open a new bug to collect suggestions, so a vote can take place at a future meeting. 14:28:29 maybe the LOC job was just a cover lol 14:29:07 #info bug 35829 opened to collect suggestions for a release codename. 14:29:07 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35829 enhancement, P5 - low, ---, koha-bugs, NEW , Codename for 24.05 14:29:15 ashimema++ 14:29:33 Much of what LC does is a cover for something. It is Congress' library, though, not the president's. 14:30:03 Any other business (not on the agenda but that people would like to put forward now)? 14:30:15 OK.. did we have any other topics or business people would like to raise/discuss? 14:30:15 haha 14:30:22 thanks aude_c 14:30:32 😉 14:31:32 ok.. seems it's rather quiet on that front 14:31:41 #topic Set date and time for the next meeting 14:31:53 I've lost track.. what's the cadence of general meetings these days? 14:32:13 🤷‍♀️ 14:32:29 They might be only twice a year now. 14:32:33 I think it's every 6 months or something... 14:32:39 last one was July by the looks 14:32:45 so 2 a year? 14:32:48 I think the last meeting was in July of 2023 14:32:50 yup 14:33:05 In 2023 there are wiki pages for meetings in April and July... and January 2024 (need to fix that category) 14:33:13 the developer meetings are more frequent and we can always choose to call an extra one from one of those. 14:33:17 maybe at the end of this cycle 14:33:26 But if you want a decision for naming 24.05, you'll need to vote at an earlier meeting 14:33:46 we'll want one in early May I would think.. to vote the next team 14:33:49 ... with the provision for calling some extra general meeting if really necessary. 14:33:56 that's scary.. already thinking about the next cycle now 14:34:10 lets say early may 14:34:26 sounds good 14:34:39 and we can perhaps vote on names at a dev meeting with extended invites 14:34:47 Right, this was the 3rd Wednesday in January. Third Wednesday in May is 15th. How does that sound? Or the week before? 14:35:11 I think May 8 is better 14:35:20 I reckon 8th 14:35:30 as 22nd is the proposed release date in general 14:35:39 oh it is a holiday in France, May 8 14:35:46 second WW 14:36:00 ok.. 14:36:07 15th better for the french frido? 14:36:12 15th sound better indeed 14:36:25 still gives us a week to collar any extra's we want to pull in for the team 14:36:27 OK.. 15th 14:36:34 we have May 1 and 8 free so many are on extended holidays 14:36:35 does this time work well for people? 14:36:45 I'll make it work 14:37:24 sounds good to me 14:37:27 Yes, this time is good 14:37:33 #info Next meeting: 15 May 2024, 14 UTC 14:37:48 Thanks everyone! 14:37:54 we can tweak the time a little if I've got timezones and daylight savings wrong 😜 14:38:03 thanks a lot for chairing 14:38:07 #info Thanks to everyone who attended 🙂 14:38:14 #endmeeting