/srv/irclogs.ubuntu.com/2024/05/28/#ubuntu-meeting.txt

=== cpaelzer_ is now known as cpaelzer
sarnoldgood morning14:30
cpaelzerhiho14:31
cpaelzergetting ready ...14:31
joalifo/14:31
slyonl/14:31
slyono/*14:31
eslermo/14:31
cpaelzersorry - 1m14:32
cpaelzer#startmeeting Weekly Main Inclusion Requests status14:33
meetingologyMeeting started at 14:33:29 UTC.  The chair is cpaelzer.  Information about MeetBot at https://wiki.ubuntu.com/meetingology14:33
meetingologyAvailable commands: action, commands, idea, info, link, nick14:33
cpaelzerPing for MIR meeting - didrocks joalif slyon sarnold cpaelzer jamespage ( eslerm dviererbe )14:34
cpaelzer#topic current component mismatches14:34
cpaelzerMission: Identify required actions and spread the load among the teams14:34
cpaelzer#link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg14:34
cpaelzer#link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg14:34
cpaelzerwelcome to a new cycle, all the sprinting and stuff made me be late14:34
cpaelzerI hope you handled all that is caused by syncs last week :-P14:34
cpaelzerok14:35
cpaelzerno MIR bugs, so we need to bring them up14:35
cpaelzerfirst: abseil -> googletest14:35
cpaelzerabseil = desktop14:35
slyonIt's a recommends, sho should probably be dropped to suggests..14:35
cpaelzerjbicha: didrocks: ^^ would you have a look there?14:35
cpaelzerhttps://launchpad.net/ubuntu/+source/abseil/20230802.1-414:36
cpaelzerthe diff only speaks about build depends14:36
cpaelzerand it is probably a test dependency14:36
cpaelzernext14:36
cpaelzerpython-pint -> requirejs and pydata-sphinx-theme14:37
cpaelzerreads like documentation14:37
cpaelzerjamespage:  that is openstack14:37
cpaelzerjamespage: could one of you have a look?14:37
cpaelzerhttps://launchpad.net/ubuntu/+source/python-pint/0.23-114:37
cpaelzeryep14:38
cpaelzerit is the doc package14:38
cpaelzerhttps://launchpad.net/ubuntu/lunar/amd64/python-pint-doc/0.19.2-114:38
cpaelzervs14:38
cpaelzerhttps://launchpad.net/ubuntu/oracular/amd64/python-pint-doc/0.23-114:38
cpaelzerjust an exclude rule would be enough14:39
cpaelzerthere is no strict reason for the doc package to be in main14:39
cpaelzernext14:39
cpaelzerpython-inflect ->python-typeguard14:39
cpaelzerjamespage: also openstack14:39
cpaelzerbut here it is a new real dependency14:40
cpaelzerhttps://launchpad.net/ubuntu/oracular/amd64/python3-inflect/7.2.1-114:40
cpaelzerlast but not least14:40
cpaelzerpython-arrow -> typeshed14:40
cpaelzerand another one for openstack jamespage14:40
cpaelzerI feel you just synced them all :-)14:40
cpaelzerchanged from https://launchpad.net/ubuntu/oracular/amd64/python3-arrow/1.2.3-1 to https://launchpad.net/ubuntu/oracular/amd64/python3-arrow/1.3.0-114:41
cpaelzerpython3-typing-extensions -> python3-typeshed14:41
cpaelzerok, component mismatches done14:41
cpaelzerjamespage:  will wake up to a lot of pings ... :-/14:42
cpaelzer#topic New MIRs14:42
cpaelzerMission: ensure to assign all incoming reviews for fast processing14:42
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-mir14:42
cpaelzertwo for us14:42
cpaelzerhttps://bugs.launchpad.net/ubuntu/+source/malcontent/+bug/189245614:42
-ubottu:#ubuntu-meeting- Launchpad bug 1892456 in malcontent (Ubuntu) "[MIR] malcontent" [Medium, New]14:42
cpaelzerhad a MIR and security review in the past14:42
cpaelzerbut the package changed a lot since14:43
cpaelzerso the ask is for a re-review14:43
cpaelzerI can take one14:43
cpaelzernext14:43
cpaelzerhttps://bugs.launchpad.net/ubuntu/+source/provd/+bug/206737314:43
-ubottu:#ubuntu-meeting- Launchpad bug 2067373 in provd (Ubuntu) "[MIR] provd" [Undecided, New]14:43
slyonI can take one for next week, too14:43
cpaelzerthanks , assigned14:44
cpaelzer#topic Incomplete bugs / questions14:44
cpaelzerMission: Identify required actions and spread the load among the teams14:44
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-mir14:44
cpaelzersysprof is still with jbicha for now14:44
cpaelzerthe others are pre sprint AFAICS14:44
cpaelzer#topic Process/Documentation improvements14:45
cpaelzerMission: Review pending process/documentation pull-requests or issues14:45
cpaelzer#link https://github.com/canonical/ubuntu-mir/pulls14:45
cpaelzer#link https://github.com/canonical/ubuntu-mir/issues14:45
cpaelzersome older ones that are stuck14:45
cpaelzerwe might mark them as that .. hmm14:45
cpaelzerwe need wording for https://github.com/canonical/ubuntu-mir/issues/5114:46
-ubottu:#ubuntu-meeting- Issue 51 in canonical/ubuntu-mir "cargo vendor adds unnecessary crates" [Open]14:46
cpaelzereslerm: do you think you could provide a PR that wraps the consensus mentioned by slyon into words14:46
eslermI can14:46
cpaelzerthanks in advance14:46
cpaelzerhttps://github.com/canonical/ubuntu-mir/issues/5514:47
-ubottu:#ubuntu-meeting- Issue 55 in canonical/ubuntu-mir "end-of-cycle unexpected changes" [Open]14:47
cpaelzerhas tackled the obvious things14:47
cpaelzerthe rest is "looking for volunteers" to tackle more14:47
cpaelzerspeak up if anyone wants to ... :-)14:47
eslermpossibly, we could add that an owning teams director needs to request late MIRs14:48
eslermwe had a last second libyuv request, which ended up not beeing needed after ack'd14:48
sarnoldthere's a few cases to care for -- one with the "the team didn't plan" and then the "oh upstream or debian has walked away from package foo because they're switching to package bar"14:49
sarnoldi think our "you get to talk to the director of security engineering" is a decent speedbump to discourage the first one, but I wish we could come up with some clever ideas to spot the overlooked packages14:49
cpaelzerI'm happy with adding "bring high level for late requests"14:50
cpaelzerbring wording in a PR for that for discussion please14:50
cpaelzerfor the other case let us brainstorm for 3 minutes ...14:50
cpaelzerIt plays into the "re-evaluate things in main" TBH14:51
cpaelzerwhich we asked for but got denied for resourcing14:51
eslermthat's not what I mean with #2214:51
sarnoldstorm idea one, look for new Replaces: or maybe dropped Depends: from other packages?14:51
eslermit is for cases where there is ack for the MIR, but then owning team goes idle for a long period of time (say 2 years)14:52
eslermI am okay dropping issue though14:52
sarnoldstorm idea two, look for new packages with small levenstein distances from packages already in main14:52
cpaelzersarnold: I think we usually get signal by bugs, the cases I see crashing as where responsibility and ownership is unclear.14:52
cpaelzersarnold: which does not mean I'd not like a scanner that provides extra signal14:52
cpaelzereslerm: now I got you - like "what is the consequence if they make us busy and then walk away" ?14:53
cpaelzereslerm: I'm not sure, but things change - so that can not always be prevented IMHO.14:53
cpaelzereslerm: not sure if defining negative consequences would help, or did you have something completely different in mind?14:54
eslermmostly, this occured and then a package was added to main, and I believe it should have had a quick re-review first14:54
eslermit's not about negative consequences for us doing the work, just that more work is needed if a review has gone "stale"14:54
slyonso adding something like a timeout on an ACK?14:55
eslermyes, I proposed 2 years14:55
slyonsounds reasonable to me.14:56
cpaelzerI'm +1 on timeout on an Ack14:56
slyoncpaelzer: that would be like our re-review idea, but only for things that didn't make it into "main" yet.14:56
cpaelzerWhile we do not get a re-review, if it didn't make it into main it is fine to time out14:57
cpaelzerslyon: exactly14:57
cpaelzeranyone willing to provide a wording PR for that?14:57
eslermI can propose a PR14:57
cpaelzerthank you14:57
cpaelzeruh, time flies14:57
cpaelzerlet us go on ...14:57
cpaelzer#topic MIR related Security Review Queue14:57
cpaelzerMission: Check on progress, do deadlines seem doable?14:57
cpaelzerSome clients can only work with one, some with the other escaping - the URLs point to the same place.14:57
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-mir14:57
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-mir14:57
cpaelzerInternal link14:57
cpaelzer- ensure your teams items are prioritized among each other as you'd expect14:57
cpaelzer- ensure community requests do not get stomped by teams calling for favors too much14:57
cpaelzer#link https://warthogs.atlassian.net/jira/software/c/projects/SEC/boards/59414:57
eslermI am stepping down from helping manage MIRs for Security14:58
eslermmy focus has changed to help coordinate CVEs14:58
eslermI've really enjoyed working on MIRs with all of you 🙏14:58
cpaelzerwe have the back to the future simplestreams reviews14:58
eslerm(I'll of course followup on GH PRs)14:58
cpaelzeroh no, we have upset eslerm with our back and forth14:58
cpaelzereslerm: please know that you will always be welcome to contribute and discuss14:58
slyon:( Thanks a lot for your awesome work as part of the MIR process!14:58
cpaelzersarnold: does that mean it is back to just you, or will you train another security-buddy?14:59
cpaelzereslerm: and thanks for your many great contributions14:59
sarnoldcpaelzer: that hasn't been discussed yet, I'm hoping for another buddy, but it will be a real challenge to step into eslerm's shoes14:59
cpaelzerfair14:59
cpaelzerok, the queue looks good14:59
cpaelzer#topic Any other business?14:59
cpaelzersee above :-)14:59
cpaelzernothing else from me14:59
slyonI fixed python-pint quickly https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=f9ce523d40c3ec774fc67eac1c0db5e85fc9f186 (cc jamespage)15:00
sarnoldnothing from me15:00
-ubottu:#ubuntu-meeting- Commit f9ce523 in ~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu "supported: Avoid python-pint-doc component-mismatch HEAD oracular"15:00
eslermI've really enjoyed these meetings :,)15:00
slyonnothing else :)15:00
cpaelzereslerm: you will still do reviews, juts not corodinate - right?15:00
sarnoldslyon: nice :)15:00
eslermI will do some reviews, but possibly not many this cycle15:00
cpaelzerslyon: still needs a demotion I guess15:00
cpaelzerok, thanks eslerm15:00
cpaelzersorry for the rush, but I need to jump15:00
sarnoldhappy hopping :)15:01
cpaelzersee you next week15:01
cpaelzer#endmeeting15:01
meetingologyMeeting ended at 15:01:08 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2024/ubuntu-meeting.2024-05-28-14.33.moin.txt15:01
slyono/15:01
eslermo/15:01
sarnoldthanks cpaelzer, eslerm, all :)15:01
didrockscpaelzer: I will forward the abseil case15:02
cpaelzerthanks didrocks15:02
didrockscpaelzer: but yeah, probably a test dep15:03

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