/srv/irclogs.ubuntu.com/2025/01/28/#ubuntu-meeting.txt

=== bdrung_ is now known as bdrung
=== tsimonq2_ is now known as tsimonq2
=== tsimonq2_ is now known as tsimonq2
sarnoldgood morning15:29
joalifo/15:29
sarnoldjoalif: hmm. with just us two this doesn't seem likely to be a useful meeting. you could grab a package from the lists if you've got time, and for my part, we've got some of the security reviews assigned, and we'll conduct a training with some new folks, but I don't expect actual results in the next week15:37
sarnoldjoalif: so I propose we call it here, and I'll return to the morning routines :)15:38
joalifyup sounds good15:38
sarnoldthanks15:38
joalifbye15:38
=== Mr_Pan_ is now known as Mr_Pan
seb128hey20:00
amurray_o/20:00
=== amurray_ is now known as amurray
rbasako/20:00
seb128hey amurray rbasak!20:01
seb128#startmeeting Ubuntu Technical Board20:01
meetingologyMeeting started at 20:01:52 UTC.  The chair is seb128.  Information about MeetBot at https://wiki.ubuntu.com/meetingology20:01
meetingologyAvailable commands: action, commands, idea, info, link, nick20:01
seb128#topic Apologies20:02
seb128I didn't see any sign from Lukasz since he left Canonical but I'm going to assume he's not going to join us tonight20:02
seb128#topic Action review20:02
seb128ACTION: amurray to look into scripting for packages in flavor-specific overlays20:03
amurraycarry-over please20:03
seb128#action amurray to look into scripting for packages in flavor-specific overlays20:04
meetingologyACTION: amurray to look into scripting for packages in flavor-specific overlays20:04
seb128ACTION: 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_Delegations20:04
seb128I'm carrying that over still but I've seen some action from teams on documentation so I will try to pick that up again20:04
seb128#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_Delegations20:05
meetingologyACTION: 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_Delegations20:05
seb128ACTION: sil2100 to follow up on the Cinnamon 24.04 LTS Qualification to ensure the listed contacts can action the flavor20:05
seb128it was decided in the previous meeting to carry that over until we have a new board I think20:05
seb128so doing that20:06
seb128#action sil2100 to follow up on the Cinnamon 24.04 LTS Qualification to ensure the listed contacts can action the flavor20:06
meetingologyACTION: sil2100 to follow up on the Cinnamon 24.04 LTS Qualification to ensure the listed contacts can action the flavor20:06
seb128ACTION: amurray and seb128 to engage with IS re Canonical leavers and ubuntu LP team memberships20:06
seb128I've opened a RT for Canonical IS which got some activity and is triaged20:06
seb128rbasak wrote a script that could be used to ensure teams under community governance aren't modifier by the Canonical exit process, which seems to be a good step20:07
rbasakI haven't taken that script any further FWIW. I've been occupied with some personal matters.20:08
seb128rbasak, did you want to continue on that topic and own to propose that solution to IS?20:08
amurraywould it be useful to get the CC to review the script/the output of the script and then if we are happy with it then propose it to IS?20:08
rbasakseb128: I think that's difficult as I've leaving Canonical on Friday.20:09
rbasakWould it be easier for those at Canonical to take this on? I'm happy to help from the scripting/community end, but I'm not sure I'll be able to drive it effectively with Canonical IS any more.20:09
seb128right, I'm happy to continue the IS side of the discussion20:09
rbasakThanks!20:09
seb128I don't really have an opinion on getting review from CC or not, I think it's probably straightforward enough that it is not needed20:10
seb128but at the same time it doesn't hurt either20:10
seb128rbasak, opinion?20:10
rbasakI don't think it's necessary to get review20:10
rbasak(except IS will review it of course)20:10
amurrayno worries - yeah I wasn't sure if we thought it needed some other eyes on it but am happy for us to just proceed as we see fit20:11
seb128amurray, did you feel strongly about the CC review?20:11
amurrayno, am happy to go ahead without it20:11
seb128ok, well I will review and if I'm happy I will follow up with IS20:11
rbasakAn opportunity to enhance the script might be to also identify whether or not a team has an ultimate owner who is a member of ~canonical. If not, it's probably a not-Canonical not-Ubuntu team and membership of it shouldn't be touched.20:11
rbasakBut I don't think I'll have time for that in the next couple of weeks.20:12
rbasakSo probably better to go with what's there so far.20:12
seb128#action seb128 to continue the discussion with IS and propose the script from rbasak or its output to be integrated in their process20:12
meetingologyACTION: seb128 to continue the discussion with IS and propose the script from rbasak or its output to be integrated in their process20:12
seb128ack, we can always iterate later/improve20:13
seb128#topic Scan the mailing list archive for anything we missed (standing item)20:13
seb128I'm going to mention that I pinged the CC again (because I didn't see the summary of the governance sync posted on discourse), the TB election is still waiting for review from Mark from what I understand20:15
seb128they will extend the current board meanwhile20:15
seb128.20:15
seb128other topic I emailed the list about to discuss here20:15
seb128https://lists.ubuntu.com/archives/technical-board/2025-January/002969.html20:15
seb128the ubuntu.com TB description states20:16
seb128```20:16
seb128Nominations for the Technical Board will be considered for each release20:16
seb128(every six months). Mark Shuttleworth, as project sponsor, is20:16
seb128responsible for nominating candidates, and a poll of Ubuntu developers20:16
seb128will be conducted to select, or veto, the final membership. Appointments20:16
seb128are made for a period of two years.20:16
seb128```20:16
seb128which seems inaccurate/not to match what is happening20:16
rbasakSounds like we need someone to fix the text to be accurate again.20:16
rbasakI'm happy for that to be delegated to one TB member and trust them to do a good job :)20:16
seb128right, I was unsure if that was a change that was decided20:17
amurrayI can take that on - can draft something and circulate to you both if you like before getting it updated20:17
seb128or if practice drifted from what should happen20:17
seb128amurray, thanks20:17
rbasakAIUI, the current process has been happening since before I got involved in 2011.20:17
rbasakI'm not sure there are many people around any more who would know if the change was intentional.20:17
rbasakI can think of one person we could ping if curious. I don't want to bother them that much though if we don't need to know.20:18
seb128#action amurray to draft an updated description for the TB nominations process on ubuntu.com20:18
meetingologyACTION: amurray to draft an updated description for the TB nominations process on ubuntu.com20:18
rbasakI'm happy to describe the current process and leave the old one behind.20:18
seb128+120:18
* rbasak has an AOB topic20:19
seb128well, there is still one list thing20:19
seb128rbasak, can you provide context on https://lists.ubuntu.com/archives/technical-board/2025-January/002967.html and https://lists.ubuntu.com/archives/technical-board/2025-January/002968.html ?20:19
seb128did you move from an owner team that included the TB to direct set the TB as owner?20:20
rbasakSure. It's a minor thing that I don't think matters, but I moderated through the emails as I didn't want to hide anything.20:20
rbasakI "wrapped" ~git-ubuntu-import into ~git-ubuntu-owners. Ultimate TB ownership didn't change.20:21
rbasakThis is important because ~git-ubuntu-import is a "Code admin" under launchpad.net/ubuntu, to manage the "official" git repositories for the project20:21
rbasakSo the TB should be the ultimate owner20:21
seb128ack, makes sense, thanks for the context!20:22
rbasakBut for admin purposes, we need some people to be able to write to the repos if required, even if right now (pending the staging branches spec) they should be read-only.20:22
rbasakSo while addressing the bus factor, I did the wrapping so that the owners can add and remove themselves from the actual git-ubuntu-import team, so that they don't have to have write access all the time. As a type of "safety".20:23
rbasak.20:23
seb128thanks20:23
seb128I've to admit I still don't really understand who has access to git-ubuntu changes but I will study that20:24
rbasakahasenack, me and bryce.20:24
seb128despite being coredev and TB member I don't have acces to change the status of merge requests for example20:24
rbasakYes that's annoying.20:24
seb128I guess owners don't have special rights in that sense?20:25
rbasakThe staging spec was supposed to fix that but it's pending implementation at the Launchpad end.20:25
rbasakCurrently changing MP status requires write access to the target repo, but it's important that Ubuntu developers do not write to the git-ubuntu repos except through uploads.20:25
seb128well I though that by being owner the TB would have access though20:26
rbasakOne way around it might be to write a bot that changes MP status based on instructions in comments, or something like that20:26
rbasakI don't think ownership is treated as team membership20:26
seb128I see20:26
rbasakIt's just someone who can act as a team admin without necessarily being an owner20:26
rbasakWhich actually works quite well in general, IMHO.20:26
seb128right20:27
rbasakSince it's a good way to specify ultimate ownership but delegating all powers20:27
seb128thanks again, and let's move on, that's getting out of topic in context of the TB that was more curiosity from my side now20:28
seb128#topic Check up on community bugs and techboard bugs20:28
seb128#link https://bugs.launchpad.net/ubuntu-community/+bugs?field.assignee=techboard20:28
seb128#info No new community bugs20:28
seb128#link https://bugs.launchpad.net/techboard20:28
seb128#info No new techboard bugs20:28
seb128#topic Select a chair for the next meeting (next from https://launchpad.net/~techboard/+members)20:29
seb128#info The next chair will be amurray with rbasak as backup20:29
rbasakack20:29
seb128#topic AOB20:29
amurrayack20:29
seb128rbasak, you have one20:29
rbasakSorry I didn't raise this in the agenda properly. I've been occupied with some personal matters for the past week or so that couldn't wait.20:29
rbasakYou'll have seen my thread on moving from IRC to Matrix. I said I'd ask the TB, but it seems we have consensus on the ML anyway, so maybe that isn't really necessary at all.20:29
rbasakI'm planning to announce a move to Matrix for #ubuntu-devel and #ubuntu-release on 1 March, to give people time to set up accounts, etc. The old channels wouldn't shut down or presence banned or anything, but privileged team presence should move to Matrix instead, and we should try to hold conversations on Matrix as much as possible to avoid fragmentation.20:29
rbasakIs the TB OK with that, and to leave the details to me?20:29
rbasakI'm abandoning my proposal to merge -release and -devel since many people weren't sure about that.20:29
seb128+1 from me, and thank you for pushing that forward, it's about time we move to a more modern platform20:30
amurray+1 from me - thanks for driving this basak, it is long overdue20:30
rbasakGreat. Thanks! Nothing else from me.20:31
amurraynow to move this channel as well ;)20:31
seb128:)20:31
seb128amurray, any AOB?20:31
rbasakThis channel is a little more complicated20:31
rbasakThere's no replacement for meetingology AIUI20:31
amurraytrue20:31
rbasakSo I think it's open as to whether we should move or wait.20:31
rbasakBut I don't want to hold up the main move on that point.20:31
rbasakPerhaps we can set a deadline and move anyway, say in six months.20:32
rbasakOr earlier if someone ports meetingology earlier.20:32
rbasakDepends on how important people thing it is.20:32
amurrayI would also prefer we go to something more high bandwidth like google meet and we record those etc but yes then it would need someone to actually take notes during the meeting without meetingology20:32
rbasakI like it - it helps with logs, which is very useful for TB / DMB business IMHO.20:32
seb128let's talk about that with the new board when we have one I would say20:33
rbasakBut I can ask on the ML to see what others think.20:33
amurrayyep lets leave it to the next TB20:33
seb128maybe once better staffed we will have someone wanting to spend some time working on a solution20:33
seb128it's probably not going to me, the workload problem isn't likely to get better any time soon I think20:34
seb128to be me*20:34
seb128anyway20:35
seb128anything else?20:35
amurraynothing from me20:35
seb128that's a wrap then, thanks amurray and rbasak!20:35
seb128#endmeeting20:35
meetingologyMeeting ended at 20:35:47 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2025/ubuntu-meeting.2025-01-28-20.01.moin.txt20:35
amurraythanks seb128, rbasak20:35
rbasakThanks all!20:36
=== bandali is now known as mab

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!