20:04 #startmeeting Ubuntu Technical Board 20:04 Meeting started at 20:04:36 UTC. The chair is amurray. Information about MeetBot at https://wiki.ubuntu.com/meetingology 20:04 Available commands: action, commands, idea, info, link, nick 20:04 #topic Apologies 20:05 vorlon mentioned he would not be able to make this meeting in an email thread earlier but nothing from sil2100 that I saw 20:06 #topic Action review 20:06 * amurray vorlon to look into scripting for packages in flavor-specific overlays 20:06 will carry over 20:06 #action vorlon to look into scripting for packages in flavor-specific overlays 20:06 * meetingology vorlon to look into scripting for packages in flavor-specific overlays 20:06 * amurray seb128 to continue working with AA and Release teams to document their membership process and link to it from https://wiki.ubuntu.com/TechnicalBoard#Team_Delegations 20:06 carry over please... 20:06 #action seb128 to continue working with AA and Release teams to document their membership process and link to it from https://wiki.ubuntu.com/TechnicalBoard#Team_Delegations 20:06 * meetingology seb128 to continue working with AA and Release teams to document their membership process and link to it from https://wiki.ubuntu.com/TechnicalBoard#Team_Delegations 20:06 * amurray sil2100 to follow up on the Cinnamon 24.04 LTS Qualification to ensure the listed contacts can action the flavor 20:06 will also carry-over 20:07 #action sil2100 to follow up on the Cinnamon 24.04 LTS Qualification to ensure the listed contacts can action the flavor 20:07 * meetingology sil2100 to follow up on the Cinnamon 24.04 LTS Qualification to ensure the listed contacts can action the flavor 20:07 #topic Scan the mailing list archive for anything we missed (standing item) 20:07 #link https://lists.ubuntu.com/archives/technical-board/2024-December/thread.html 20:08 nothing other than a pending AMA I guess :) 20:08 Does anyone have any comment on my AMA suggestion? 20:08 I've had no feedback whatsoever except for Seb's question to Merlijn 20:08 indeed, sounds like that's delayed to next year, I guess Mark needs to approve the candidates and didn't reply to the CC yet... 20:09 I think it is a good idea - am not sure if we'll get much engagement but I like the idea of letting folks ask questions to help them clarify their votes and its a chance for the future TB to understand what issues / initiatives are important 20:09 no comment from my part, I'm happy to participate to an AMA session 20:10 I suppose we might as well make it coincide with a TB meeting because then it shouldn't really be any burden on any candidate. 20:10 But it seems likely we'll end up with no question! 20:10 similarly I've doubt on whether we will have participation/questions but let's see 20:10 yep - during the next respective TB meeting makes sense to me 20:11 which triggers a side question 20:11 do we need Mark to extend to the memberships? 20:11 since we will not have an election on time now 20:11 Yes - or any CC member can do it I think. 20:12 Might as well be Merlijn as he has the best handle on the schedule I think. 20:12 ah, right, they are owner 20:12 perhaps, but I don't think we need the explicit LP membership to have an informal AMA 20:12 I was looking at the admins 20:12 well, the membership is not for AMA 20:12 amurray: I think seb128 means for regular TB activities and (presumably) emergencies. 20:12 but I do wonder if we hit tasks where we need a TB members for the project at a time where we have none 20:13 I know it was needed at archive opening time for plucky for example 20:13 eg. if the DMB needs a PPU adding, that sort of thing. 20:13 but yeah, I think it's better to have acrive member in case we need something restricted to TB 20:13 right, I guess I was assuming the election etc would happen quite soon in the new year and so there wouldn't be much need for emergency powers etc - but I suppose it makes more sense to have it ready to go just in case 20:13 I will take an action item to talk to Merlijn about that if you want 20:14 sure 20:14 Thanks! 20:14 also I will take one to talk to IS/Lukasz about what happened there 20:14 #action seb128 to follow-up with Merlijn about temporarily extending TB memberships 20:14 * meetingology seb128 to follow-up with Merlijn about temporarily extending TB memberships 20:14 IS really need to have an allowlist of teams whose memberships continue when a Canonical employee leaves. 20:15 or the opposite, a list of teams they need to manage 20:15 So I saw a mailing list post from Heather around this topic, and I've been meaning to respond as well 20:15 I've seen several cases of people removed to random project they were working on in their freetime after leaving 20:16 (oh I see Heather's email was more about 2FA but is related) 20:17 #link https://lists.launchpad.net/launchpad-users/msg07251.html 20:17 I will share the RT/Cc you if you are interested 20:17 sure - I was going to say I can take an action to follow this up with IS but if there is already a RT then I don't want to duplicate things 20:20 although from the TB side I am happy to take an action to try and drive this forward from our perspective but via any existing RT etc 20:21 either way is fine to me 20:22 pick on, or just list you can me and we can figure out who gets to it first 20:22 one 20:22 shrug, that sentence is buggy, let me start again :p 20:22 pick one, or just list you and me and we can figure out who gets to it first 20:22 #action amurray and seb128 to engage with IS re Canonical leavers and ubuntu LP team memberships 20:22 * meetingology amurray and seb128 to engage with IS re Canonical leavers and ubuntu LP team memberships 20:24 #topic Check up on community bugs and techboard bugs 20:24 #link https://bugs.launchpad.net/ubuntu-community/+bugs?field.assignee=techboard 20:24 #link https://bugs.launchpad.net/techboard 20:25 nothing new 20:25 #topic Select a chair for the next meeting (next from https://launchpad.net/~techboard/+members) 20:26 so probably Robie and me as backup? 20:26 hmm without sil2100 on the list I guess it is rbasak with seb128 as backup 20:26 heh yep 20:26 Ah that's why. He just wanted to get out of chairing :-) 20:26 also next meeting is 01-14, just as a reminder that we agreed to skip the 12-31 one 20:26 I don't mind being picked 20:27 #agreed next meeting chair: rbasak, backup: seb128 20:27 AGREED: next meeting chair: rbasak, backup: seb128 20:27 #topic AOB 20:27 none from me 20:28 nor from me 20:29 Nor me 20:30 ok, then that's a wrap - thanks seb128 rbasak :) 20:30 #endmeeting