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

=== JanC is now known as Guest4670
=== JanC is now known as Guest1329
=== JanC is now known as Guest3444
=== JanC is now known as Guest9590
=== JanC is now known as Guest9046
=== JanC is now known as Guest3297
=== dviererbe1 is now known as dviererbe
cpaelzero/15:29
cpaelzer#startmeeting Weekly Main Inclusion Requests status15:30
meetingologyMeeting started at 15:30:00 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 ( eslerm dviererbe )15:30
sarnoldgood morning15:30
slyono/15:31
dviererbeo/15:31
cpaelzerhidiho, let's go15:32
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
cpaelzerplucky-release looks fine15:32
cpaelzerjemallox goes on, notihng new on jpeg-xl yet15:32
cpaelzerthe python things around openstack slowly become MIRs to review (one is in unapproved now)15:32
cpaelzerthat is it15:32
cpaelzerno action from component mismatches this time AFAICS15:33
sarnoldquiet .. must be december15:33
cpaelzerit is15:33
cpaelzer#topic New MIRs15:33
cpaelzerMission: ensure to assign all incoming reviews for fast processing15:33
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:33
cpaelzerempty15:33
jamespageo/15:33
cpaelzer#topic Incomplete bugs / questions15:33
cpaelzerMission: Identify required actions and spread the load among the teams15:33
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:33
cpaelzerhttps://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/2089690 is resolved for now, now new updates since15:34
-ubottu:#ubuntu-meeting- Launchpad bug 2089690 in rust-sequoia-sq (Ubuntu) "[MIR] rust-sequoia-sq" [Undecided, Incomplete]15:34
cpaelzerand one that might become a MIR15:34
cpaelzerhttps://bugs.launchpad.net/ubuntu/+source/python-legacy-cgi/+bug/208924415:34
-ubottu:#ubuntu-meeting- Launchpad bug 2089244 in python-legacy-cgi (Ubuntu) "[MIR] python-legacy-cgi" [Undecided, Incomplete]15:34
cpaelzerbut then it likely is a fast-path as the code was in main if I read doko's comment right15:34
cpaelzerstill, as long as it is in TBC I'd hold back our action15:34
cpaelzer#topic Process/Documentation improvements15:35
cpaelzerMission: Review pending process/documentation pull-requests or issues15:35
cpaelzer#link https://github.com/canonical/ubuntu-mir/pulls15:35
cpaelzer#link https://github.com/canonical/ubuntu-mir/issues15:35
sarnoldand some amount of "why was it dropped, and will it have upstream support" feels worth fleshing out15:35
cpaelzersarnold: sure, but let us see if foundations even wants to keep it15:35
cpaelzersarnold: often enough those are not even needed to be kept15:35
sarnold\o/15:35
cpaelzersarnold: we haven't seen it in mismatches 8yet)15:35
cpaelzerwow15:36
cpaelzersarnold: - just in time - 1 minute ago :-)15:36
cpaelzerhttps://github.com/canonical/ubuntu-mir/pull/7315:36
-ubottu:#ubuntu-meeting- Pull 73 in canonical/ubuntu-mir "Update README.md -- remove eslerm" [Open]15:36
sarnold:D15:36
cpaelzermakes sense, even though I'll miss him15:36
cpaelzerhe's not even on the channel so he won't see it :-)15:36
cpaelzerbut sure, it make sense to clean up15:36
sarnoldoh ;) ha15:36
cpaelzermerging ...15:36
cpaelzer#topic MIR related Security Review Queue15:37
cpaelzerMission: Check on progress, do deadlines seem doable?15:37
cpaelzerSome clients can only work with one, some with the other escaping - the URLs point to the same place.15:37
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:37
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:37
cpaelzerInternal link15:37
cpaelzer- ensure your teams items are prioritized among each other as you'd expect15:37
cpaelzer- ensure community requests do not get stomped by teams calling for favors too much15:37
cpaelzer#link https://warthogs.atlassian.net/jira/software/c/projects/SEC/boards/59415:37
cpaelzeryou said you have not been fully back to speed last time15:37
cpaelzerany improvement for you or those you are pushing to help you for those reviews sarnold?15:38
sarnoldI believe I have found a volunteer for jpeg-xl, and exfatprogs will likely have progress soon15:38
sarnoldmy own portion of improving our onboarding process has had no progress15:39
cpaelzerboth good15:39
cpaelzerprovd/libimobiledevice-glue in the queue?15:39
cpaelzeror can you only look at them once the others are out=15:39
cpaelzer?15:39
sarnoldthree day weeks look even shorter when there's interviews in the mix, too :/15:39
cpaelzerwe all know the same, I understand15:39
cpaelzerdo we need to do something about lenovo-wwan-unlock (in review) by eslerm?15:40
sarnoldthere's nothing hard preventing them from being started yet, just no 'interest' yet. I might need to resort to prodding rather than poking.15:40
cpaelzersince you said he looks at other things now?15:40
sarnoldoh, hmm. I added a comment to that bug a month ago with a lot of feedback and had no reply ..15:41
cpaelzerindeed15:42
cpaelzerand it is incomplete15:42
cpaelzerbut maybe put your name on it int he jira tracking?15:42
sarnoldyeah15:42
cpaelzergoing on15:42
cpaelzer#topic Any other business?15:42
cpaelzerI have one, which is a soft touch on re-reviews15:42
cpaelzerWe sometimes get them served on a silver plate15:42
slyonnothign from my side15:42
cpaelzere..g when source renames make it pop up again15:43
cpaelzerwe usually do, and that is fair to not hold up people, kind of quick-look / fast-path them as the code was in main before15:43
cpaelzerBut I wondered about the following case:15:43
cpaelzer"If the code in main is so long in main that there isn't any historical MIR record" => should we do a review15:44
cpaelzermaybe with none except extreme misses being "required", but I'd love to ahve the chance to "recommend" some15:44
sarnoldI like the idea15:44
cpaelzerWDYT - should we try to do that "not so fast" fast path if there is no audit trail as it is in main forever?15:45
cpaelzerthen at least one could check when it was last evaluated15:45
cpaelzerand by making all "recommended" we'd stay pragmatic and not hold up teams that do transitions15:45
slyonYes, I like that, too. It would probably catch quite a few misses.15:45
cpaelzerslyon:  jamespage: WDYT - if you are +1 I can file a PR for a rule change in that regard15:45
sarnoldwe have significantly raised the bar on our expectations for MIRs over time, we might prefer to say "more than ten years ago" or something similar, just to keep sliding this window ever forward, too15:46
cpaelzeryes slyon, I mostly think of things we added due to painful lessons learned15:46
cpaelzerok, I hear +1 all around15:46
cpaelzerlet me file an issue for it15:46
slyonI like sarnold's sliding window idea.15:46
slyonotherwise this would only be a one-off thing..15:46
cpaelzeryes, but a bit softer for now15:46
cpaelzerit is a window from "since we track it" to "now"15:46
sarnoldI figure it comes up pretty infrequently, i'm not sure there'd be a big workload difference to either one, heh15:47
cpaelzerbut it can be a demo for how a sliding window could look15:47
jamespageI think that makes sense15:47
slyonright. That should give use quite some backlog, already. But then we need to change the rules again a few years down the road (which is fine915:47
cpaelzerfiled https://github.com/canonical/ubuntu-mir/issues/74 for it15:49
-ubottu:#ubuntu-meeting- Issue 74 in canonical/ubuntu-mir "let us fully soft re-evaluate any requests that have no trackable bug" [Open]15:49
cpaelzerno other topics from me15:49
sarnoldcpaelzer: this rough outline is missing the "trigger" -- source renames, anything else?15:50
sarnoldwell, maybe "any requests" is the trigger ..15:50
cpaelzeradded15:51
sarnoldweb 2.0 isn't all bad :) heh15:51
cpaelzerhehe15:51
cpaelzerok closing then15:51
cpaelzeranything else?15:51
slyonthanks cpaelzer, all!15:52
sarnolduh I can't remember when exactly I'm off15:52
cpaelzeryou'll notice then sarnold :-)15:52
cpaelzer1115:52
cpaelzer1015:52
cpaelzer0115:52
cpaelzerout15:52
sarnold:D15:52
cpaelzer#endmeeting15:52
meetingologyMeeting ended at 15:52:40 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2024/ubuntu-meeting.2024-12-10-15.30.moin.txt15:52
sarnoldooo fun one15:52
sarnoldthanks cpaelzer, all :)15:52

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