/srv/irclogs.ubuntu.com/2024/12/17/#ubuntu-meeting.txt

=== genii_ is now known as genii
cpaelzero/15:30
cpaelzer#startmeeting Weekly Main Inclusion Requests status15:30
meetingologyMeeting started at 15:30:42 UTC.  The chair is cpaelzer.  Information about MeetBot at https://wiki.ubuntu.com/meetingology15:30
meetingologyAvailable commands: action, commands, idea, info, link, nick15:30
cpaelzerPing for MIR meeting - didrocks joalif slyon sarnold cpaelzer jamespage ( dviererbe )15:30
cpaelzersome may already be out for EOY15:30
cpaelzerand I'm slightly distracted with a sick rabbit on my lap15:31
cpaelzerbut we will get this done15:31
sarnoldgood morning15:31
sarnoldaww poor bunny :(15:31
cpaelzer#topic current component mismatches15:32
cpaelzerMission: Identify required actions and spread the load among the teams15:32
cpaelzer#link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg15:32
cpaelzer#link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg15:32
cpaelzernormal view is good15:32
cpaelzerproposed has a bit15:32
cpaelzerhmm, I didn't pick up sanlock as new15:32
cpaelzerbut it is there15:32
cpaelzerI'll ask sergio15:32
sarnoldhah, and I missed augeas entirely15:32
sarnoldit's already got an approved MIR?15:33
sarnoldis this *ancient* MIR bug really "the bug"? https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/43483615:33
-ubottu:#ubuntu-meeting- Launchpad bug 434836 in augeas (Ubuntu Karmic) "[MIR] augeas" [High, Fix Released]15:33
cpaelzerit was there in the long past15:33
cpaelzeranyway conside this to be done15:34
sarnold.. I have to wonder if charms would have been easier if this were part of main15:34
sarnoldbut apparently it was, and they weren't? :)15:34
cpaelzeryep15:34
cpaelzerabseil -> google test sounds like a memory15:34
cpaelzerseb128: jbicha: would one of you plesae look afte rabseil?15:35
seb128will do15:35
cpaelzerhighway is a known case15:35
cpaelzerso is jemalloc15:35
cpaelzerall in reviewstages15:35
cpaelzerand then the set of openstack packages which grind their way to proper cases15:35
cpaelzerall good, actions distributed15:35
cpaelzergoing on15:35
cpaelzer#topic New MIRs15:36
cpaelzerMission: ensure to assign all incoming reviews for fast processing15:36
cpaelzer#link https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-date_last_updated&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&assignee_option=none&field.assignee=&field.subscriber=ubuntu-mir15:36
cpaelzerflexcache was updated to be ready15:36
cpaelzerI'll do the review15:36
cpaelzer#topic Incomplete bugs / questions15:37
cpaelzerMission: Identify required actions and spread the load among the teams15:37
cpaelzer#link https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-date_last_updated&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.subscriber=ubuntu-mir15:37
cpaelzerthree caes with recent updates15:37
slyono/15:37
cpaelzerhttps://bugs.launchpad.net/ubuntu/+source/rust-sequoia-sqv/+bug/2089690 - non change, just more incomplete bug task states15:37
-ubottu:#ubuntu-meeting- Launchpad bug 2089690 in rust-sequoia-sqv (Ubuntu) "[MIR] rust-sequoia-sq" [Undecided, Incomplete]15:37
cpaelzerhttps://bugs.launchpad.net/ubuntu/+source/libgit2/+bug/208087215:37
-ubottu:#ubuntu-meeting- Launchpad bug 2080872 in libgit2 (Ubuntu) "libgit2: replace unmaintained http-parser dependency with llhttp" [Undecided, Incomplete]15:37
cpaelzerassigning to people15:37
cpaelzerok15:37
cpaelzerhttps://bugs.launchpad.net/ubuntu/+source/nbd/+bug/205448015:37
-ubottu:#ubuntu-meeting- Launchpad bug 2054480 in nbd (Ubuntu) "[MIR] nbd-client" [Undecided, Incomplete]15:37
sarnoldlibgit2 is more than that15:38
cpaelzerdiscussions between Pragyansh and sarnold15:38
sarnoldnear the very top there's a new merge proposal15:38
cpaelzerreadiny ...15:38
cpaelzerI ee, asssigned to sponsors15:38
sarnoldI wish the 'flow' of comments could indicate that, I also jumped right past it yesterday when talking it over with eslerm :)15:38
cpaelzernice15:39
sarnoldis there anything we need to do to encourage this one along?15:39
cpaelzerthis is what we wanted and discussed as least worse option15:39
cpaelzerno it will be picked up by patch pilots of foundations sponsors I'd assume15:39
sarnoldcool cool15:40
slyonwell... it's still "on hold", why's that?15:40
cpaelzersarnold: your comment on https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/2054480 - do you consider it a hint or a blocking (all arch need to be enabled)15:40
-ubottu:#ubuntu-meeting- Launchpad bug 2054480 in nbd (Ubuntu) "[MIR] nbd-client" [Undecided, Incomplete]15:40
slyonlatest comment was "Currently pending review from the security team"15:40
cpaelzerI need to read more what the recent comments are about15:40
cpaelzerseems the apparmor profile15:40
cpaelzerindeed slyon15:41
cpaelzersarnold:  is that review what you've been going over with eslerm?15:41
cpaelzershould we add a ubuntu-security review slot maybe?15:41
sarnoldcpaelzer: libgit2, eslerm raised it with me, I think he's mostly interested in making sure that goes all the way to completion15:42
slyonwell, sarnold already did the quick approval here: https://bugs.launchpad.net/ubuntu/+source/libgit2/+bug/2080872/comments/515:42
-ubottu:#ubuntu-meeting- Launchpad bug 2080872 in libgit2 (Ubuntu) "libgit2: replace unmaintained http-parser dependency with llhttp" [Undecided, Incomplete]15:42
sarnoldcpaelzer: nbd, I don't think anybody has raised that one15:42
cpaelzerI like that they work on tests and appamor - I wonder at what point we should call the propose sufficient15:44
cpaelzerI want to avoid some others rushing through without by saying they tried and can't - and those that spend the effort to be punished by small thing in it15:44
sarnoldugh I think they went off into the weeds on this one15:44
cpaelzerto be clear - all I am is unsure15:44
cpaelzerbut I'm tending to want to reward that go for tests and isolation with a positive posture15:45
cpaelzerso when they come back for review or sponsoring I'd feel +1'ish (plus actually looking at it in depth)15:45
cpaelzersarnold:  this feels they tried to explain to you in the last comment15:45
cpaelzerI'm unsure if more pings there help much, maybe send a DM and discuss this whenever you are both online?15:46
cpaelzerand then add a comment on the bug with whatever your closing state is afte rthat discussion?15:46
sarnoldcpaelzer: I'll write up a comment15:46
sarnold"both online" is going to be a Big Challenge, I have a few hours left in the year :)15:47
cpaelzerslyon: do you know if Pragyansh is in EOY already?15:47
cpaelzernot sure if you still see the foundations calendar15:47
cpaelzersarnold: ok I see why you therefore consider a bug comment15:47
cpaelzerok15:47
cpaelzerlet us go on15:47
cpaelzer#topic Process/Documentation improvements15:47
cpaelzerMission: Review pending process/documentation pull-requests or issues15:47
cpaelzer#link https://github.com/canonical/ubuntu-mir/pulls15:47
cpaelzer#link https://github.com/canonical/ubuntu-mir/issues15:47
slyoncpaelzer: sarnold:, no r41k0u still seems to be around15:47
cpaelzerhttps://github.com/canonical/ubuntu-mir/pull/72 is still draft - not touching this one15:48
-ubottu:#ubuntu-meeting- Pull 72 in canonical/ubuntu-mir "vendor/Rust: more comprehensive dependency removal" [Open]15:48
cpaelzerhttps://github.com/canonical/ubuntu-mir/pull/75 would be ready if you like it slyon and sarnold?15:48
-ubottu:#ubuntu-meeting- Pull 75 in canonical/ubuntu-mir "Add rules to re-evaluate very old renames" [Open]15:48
cpaelzerit is what we discussed, allowing for doing a bit more than "auto-yes" when we see renames - AND - the case is super duper old15:49
cpaelzerand allowing this to be non gating15:49
sarnoldreading15:49
cpaelzerand furthermore allowing teams to suggest for re-review - which is a nice offering but has to be balanced15:49
cpaelzere.g. we recently had a full rewrite in rust - that is worth re-checking and I've done so15:49
cpaelzerthere is no rush, if you both are happy in 3 min - fine. Otherwise leave your comments and I can evolve it until the meeting next year15:50
slyon+1, lgtm15:51
sarnold> We'd appreciate if the owning team could file a MIR-reporter bug for it, but would not insist on it if they can't. In that case we create a stub for it.15:51
sarnoldif the goal is to get packages onto our queue, asking for the bug doesn't seem to be too much to ask, right/15:52
sarnoldas a percentage of effort ..15:52
cpaelzerif they self-ask then it would be no challenge15:52
cpaelzerbut if all that happened is auto sync libfoo3 over libfoo215:52
cpaelzerthen I thought we can ask, but not insist15:52
sarnoldahhh, to avoid a potential case of a team needing to do a dozen of them in one cycle?15:53
cpaelzeryes15:53
slyonright. Filing a MIR bug takes quite some investigation, and people might not like that. We could still file a stub and do the review/recommendations in there15:53
sarnoldokay, sounds good. baby steps.15:53
cpaelzerhence all of this is optional - a first step to a better world but acknowledging the shrotages15:53
cpaelzeralso Schrott :-) but actuall shortages15:53
slyon:)15:53
sarnold:D (I had to look that one up)15:54
cpaelzerBTW I also have more ruls to put down out of archive admin work on multivers/restricted - but one at a time15:54
cpaelzerok 2x good15:54
cpaelzermerging15:54
cpaelzer#topic MIR related Security Review Queue15:54
cpaelzerMission: Check on progress, do deadlines seem doable?15:54
cpaelzerSome clients can only work with one, some with the other escaping - the URLs point to the same place.15:54
cpaelzer#link https://bugs.launchpad.net/~ubuntu-security/+bugs?field.searchtext=%5BMIR%5D&assignee_option=choose&field.assignee=ubuntu-security&field.bug_reporter=&field.bug_commenter=&field.subscriber=ubuntu-mir15:54
cpaelzer#link https://bugs.launchpad.net/~ubuntu-security/+bugs?field.searchtext=[MIR]&assignee_option=choose&field.assignee=ubuntu-security&field.bug_reporter=&field.bug_commenter=&field.subscriber=ubuntu-mir15:54
cpaelzerInternal link15:54
cpaelzer- ensure your teams items are prioritized among each other as you'd expect15:54
cpaelzer- ensure community requests do not get stomped by teams calling for favors too much15:54
cpaelzer#link https://warthogs.atlassian.net/jira/software/c/projects/SEC/boards/59415:54
cpaelzerjpeg-xl was on my mind15:55
cpaelzerit is still in TODO but now has a name15:55
cpaelzeris that good sarnold?15:55
sarnoldyes, it is good, but likely very little has been done recently :)15:55
jbichaI just uploaded a jpeg-xl security fix to plucky today 😐15:55
cpaelzerhope for increased progress in january?15:55
sarnoldalso, our poor coverity server seems unhappy after repatriating :( we're looking into charming it up to deploy into one of the prodstacks now that we have decent vm capacity15:56
sarnoldI also hope so, I'll certainly be a bit pointier in asking for status updates post-holidays :) -- december is not a month for getting things done :/15:56
cpaelzerok, so TL;DR many reasons, the queue is not moving much but gladly not (yet) huge either15:56
cpaelzerit is THE month to get things done, get into the close-out-before-EOY feeling15:57
sarnoldrodrigo did sound optimistic to push exfatprogs over the finish line soon :)15:57
cpaelzergreat15:57
sarnoldwe shouldn't schedule our use-it-or-lose-it-PTO rally in the same month15:57
cpaelzerI think that is it then for today15:57
cpaelzeryes @sarnold15:57
cpaelzer#topic Any other business?15:57
slyonnothing.15:57
jbichabtw, Desktop intends to file a MIR soon for https://gitlab.gnome.org/GNOME/glycin as a dependency for the loupe image viewer. Probably more of a 25.10 project but we are trying to give Security more time.15:57
cpaelzerenjoy the downtime for some fresh energey next year15:57
sarnoldsee you next year :)15:57
jbichait's a bit of a next gen gdk-pixbuf15:58
cpaelzeryeah jbicha, doing that early will help15:58
slyonjbicha: thanks for the heads up!15:58
sarnoldjbicha: hopefully without a scary warning to the console every single upgrade? :)15:58
cpaelzerbut I assume it will need to exist alongside gdk-pixbuf for a whiel15:58
slyonif you could file a stub MIR already, that might help to keep it on our radar15:58
sarnold> The decoding happens in sandboxed modular image loaders15:58
cpaelzerindeed15:58
sarnoldWOOOHOOO15:58
jbichayes, this was filed recently but it's very early: https://gitlab.gnome.org/GNOME/Initiatives/-/issues/5315:59
cpaelzerI want to keep the feeling of hope and call it done for today15:59
-ubottu:#ubuntu-meeting- Issue 53 in GNOME/Initiatives "Move away from GdkPixbuf" [Opened]15:59
slyonthanks cpaelzer, all!15:59
cpaelzernice to show advantages AND drawbacks15:59
cpaelzerthat background in a stub would indeed already help15:59
cpaelzer#endmeeting15:59
meetingologyMeeting ended at 15:59:46 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2024/ubuntu-meeting.2024-12-17-15.30.moin.txt15:59
sarnoldahh, nice, 'farbfeld' format! so micha can always forget the farbfeld.16:00
sarnoldthanks cpaelzer, all :)16:00
rbasako/20:00
amurrayo/20:00
seb128o/20:01
seb128I just noticed that Lukasz isn't listed on https://launchpad.net/~techboard/+members#active anymore20:03
seb128did he leave the team?20:03
amurrayI wonder if this happened as part of his off-boarding from Canonical?20:03
seb128anyway I guess it's only the 3 of us and Steve/Lukasz where chair and backup so amurray you are next20:03
amurrayah ok - give me a couple secs to remember how to drive meetingology :)20:04
seb128amurray, oh, could well be, the IS process doesn't seem to be precise20:04
amurray#startmeeting Ubuntu Technical Board20:04
meetingologyMeeting started at 20:04:36 UTC.  The chair is amurray.  Information about MeetBot at https://wiki.ubuntu.com/meetingology20:04
meetingologyAvailable commands: action, commands, idea, info, link, nick20:04
amurray#topic Apologies20:04
amurrayvorlon mentioned he would not be able to make this meeting in an email thread earlier but nothing from sil2100 that I saw20:05
amurray#topic Action review20:06
amurrayACTION: vorlon to look into scripting for packages in flavor-specific overlays20:06
amurraywill carry over20:06
amurray#action vorlon to look into scripting for packages in flavor-specific overlays20:06
meetingologyACTION: vorlon to look into scripting for packages in flavor-specific overlays20:06
amurrayACTION: 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:06
seb128carry over please...20:06
amurray#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:06
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:06
amurrayACTION: sil2100 to follow up on the Cinnamon 24.04 LTS Qualification to ensure the listed contacts can action the flavor20:06
amurraywill also carry-over20:06
amurray#action sil2100 to follow up on the Cinnamon 24.04 LTS Qualification to ensure the listed contacts can action the flavor20:07
meetingologyACTION: sil2100 to follow up on the Cinnamon 24.04 LTS Qualification to ensure the listed contacts can action the flavor20:07
amurray#topic Scan the mailing list archive for anything we missed (standing item)20:07
amurray#link https://lists.ubuntu.com/archives/technical-board/2024-December/thread.html20:07
amurraynothing other than a pending AMA I guess :)20:08
rbasakDoes anyone have any comment on my AMA suggestion?20:08
rbasakI've had no feedback whatsoever except for Seb's question to Merlijn20:08
seb128indeed, 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:08
amurrayI 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 important20:09
seb128no comment from my part, I'm happy to participate to an AMA session20:09
rbasakI 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
rbasakBut it seems likely we'll end up with no question!20:10
seb128similarly I've doubt on whether we will have participation/questions but let's see20:10
amurrayyep - during the next respective TB meeting makes sense to me20:11
seb128which triggers a side question20:11
seb128do we need Mark to extend to the memberships?20:11
seb128since we will not have an election on time now20:11
rbasakYes - or any CC member can do it I think.20:11
rbasakMight as well be Merlijn as he has the best handle on the schedule I think.20:12
seb128ah, right, they are owner20:12
amurrayperhaps, but I don't think we need the explicit LP membership to have an informal AMA20:12
seb128I was looking at the admins20:12
seb128well, the membership is not for AMA20:12
rbasakamurray: I think seb128 means for regular TB activities and (presumably) emergencies.20:12
seb128but I do wonder if we hit tasks where we need a TB members for the project at a time where we have none20:12
seb128I know it was needed at archive opening time for plucky for example20:13
rbasakeg. if the DMB needs a PPU adding, that sort of thing.20:13
seb128but yeah, I think it's better to have acrive member in case we need something restricted to TB20:13
amurrayright, 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 case20:14
seb128I will take an action item to talk to Merlijn about that if you want20:14
amurraysure20:14
rbasakThanks!20:14
seb128also I will take one to talk to IS/Lukasz about what happened there20:14
amurray#action seb128 to follow-up with Merlijn about temporarily extending TB memberships20:14
meetingologyACTION: seb128 to follow-up with Merlijn about temporarily extending TB memberships20:14
rbasakIS really need to have an allowlist of teams whose memberships continue when a Canonical employee leaves.20:14
seb128or the opposite, a list of teams they need to manage20:15
amurraySo I saw a mailing list post from Heather around this topic, and I've been meaning to respond as well20:15
seb128I've seen several cases of people removed to random project they were working on in their freetime after leaving20:15
amurray(oh I see Heather's email was more about 2FA but is related)20:16
amurray#link https://lists.launchpad.net/launchpad-users/msg07251.html20:17
seb128I will share the RT/Cc you if you are interested20:17
amurraysure - 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 things20:17
amurrayalthough 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 etc20:20
seb128either way is fine to me20:21
seb128pick on, or just list you can me and we can figure out who gets to it first20:22
seb128one20:22
seb128shrug, that sentence is buggy, let me start again :p20:22
seb128pick one, or just list you and me and we can figure out who gets to it first20:22
amurray#action amurray and seb128 to engage with IS re Canonical leavers and ubuntu LP team memberships20:22
meetingologyACTION: amurray and seb128 to engage with IS re Canonical leavers and ubuntu LP team memberships20:22
amurray#topic Check up on community bugs and techboard bugs20:24
amurray#link https://bugs.launchpad.net/ubuntu-community/+bugs?field.assignee=techboard20:24
amurray#link https://bugs.launchpad.net/techboard20:24
amurraynothing new20:25
amurray#topic Select a chair for the next meeting (next from https://launchpad.net/~techboard/+members)20:25
seb128so probably Robie and me as backup?20:26
amurrayhmm without sil2100 on the list I guess it is rbasak with seb128 as backup20:26
amurrayheh yep20:26
rbasakAh that's why. He just wanted to get out of chairing :-)20:26
seb128also next meeting is 01-14, just as a reminder that we agreed to skip the 12-31 one20:26
rbasakI don't mind being picked20:26
amurray#agreed next meeting chair: rbasak, backup: seb12820:27
meetingologyAGREED: next meeting chair: rbasak, backup: seb12820:27
amurray#topic AOB20:27
seb128none from me20:27
amurraynor from me20:29
rbasakNor me20:29
amurrayok, then that's a wrap - thanks seb128 rbasak :)20:30
amurray#endmeeting20:30
meetingologyMeeting ended at 20:30:05 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2024/ubuntu-meeting.2024-12-17-20.04.moin.txt20:30
rbasakThanks all!20:30
seb128thanks amurray and rbasak, have nice holidays and see you next year!20:30
amurraythanks - you two too :) have a great break, will see you on the 14th if not beforehand20:30

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