/srv/irclogs.ubuntu.com/2023/05/09/#ubuntu-meeting.txt

cpaelzerhello14:30
cpaelzer#startmeeting Weekly Main Inclusion Requests status14:30
meetingologyMeeting started at 14:30:46 UTC.  The chair is cpaelzer.  Information about MeetBot at https://wiki.ubuntu.com/meetingology14:30
meetingologyAvailable commands: action, commands, idea, info, link, nick14:30
cpaelzerPing for MIR meeting - didrocks joalif slyon sarnold cpaelzer jamespage ( eslerm dviererbe )14:30
slyono/14:30
cpaelzerNot sure if everyone made it back from the sprint yet14:30
eslermgood morning o/14:31
dviererbeHello o/14:31
cpaelzerbut in case you did - hello o/14:31
jbichahi, I'll be filing the MIRs related to transmission soon14:31
cpaelzerok, good to know ahead of time jbicha14:31
cpaelzerlet us see if syncs brought us something already14:31
cpaelzer#topic current component mismatches14:31
cpaelzerMission: Identify required actions and spread the load among the teams14:31
cpaelzer#link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg14:31
cpaelzer#link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg14:31
cpaelzertransmission (as mentioned by jbicha)14:32
cpaelzerjaraco.text was there last cycle and is still on openstack14:32
slyonpolicykit-1 -> duktape seems known (didn't we resolve that in the past?14:32
joalifo/14:32
cpaelzerjamespage: in case you read this now or later, what is the mantic minotaur plan for dependencies of jaraco ?14:32
didrockshello14:32
cpaelzeroh, one more thing14:32
cpaelzerI have went backwards on duktape IIRC14:32
cpaelzerit is still seen in component mismatch proposed right now14:33
cpaelzerI guess that is meant to land soo, was that ready - if not what was yet open?14:33
jamespagecpaelzer: unsure - I need to sync with coreycb and the ubuntu-ceph team to figure that out14:33
cpaelzerok jamespage, do that and get back to us14:33
jamespagebut I'll find out and return with news...14:33
cpaelzerI just want to avoid it hangs in mismatches for many more months14:33
jamespageyep me too14:33
jbichacpaelzer: I believe Desktop still has a required autopkgtest TODO for duktape14:34
cpaelzeryes, there were some open tasks14:34
cpaelzerthat very much could be one14:35
cpaelzerjbicha: do you know if that task of getting it ready is on the roadmap or anyones desk?14:35
slyonSo I think duktape should be marked "Incomplete" to reflect that?14:35
cpaelzerIt was incomplete after my review14:35
jbichacpaelzer: duktape is on Desktop's roadmap to try to get done within the next few weeks14:35
cpaelzerwent to security14:35
cpaelzerand they marked it "ok" after their ack14:36
cpaelzerincomplete is indeed the right status, thanks for suggesting slyon14:36
cpaelzerthanks jbicha, so in some near future Desktop will come back , call it ready, we will look again and then it can move14:36
cpaelzersounds reasonable14:36
jbicha👍14:36
cpaelzerstatus fixed14:38
slyonthx!14:38
cpaelzerok, next14:38
cpaelzer#topic New MIRs14:38
cpaelzerMission: ensure to assign all incoming reviews for fast processing14:38
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:38
cpaelzernothing there yet14:39
cpaelzernext14:39
cpaelzer#topic Incomplete bugs / questions14:39
cpaelzerMission: Identify required actions and spread the load among the teams14:39
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:39
cpaelzerno recent updates14:39
cpaelzerthe sprint and recent release made things rather easy :-)14:39
cpaelzer#topic Process/Documentation improvements14:40
cpaelzerMission: Review pending process/documentation pull-requests or issues14:40
cpaelzer#link https://github.com/canonical/ubuntu-mir/pulls14:40
cpaelzer#link https://github.com/canonical/ubuntu-mir/issues14:40
cpaelzerWe have my PR, but I'd postpone that to the AOB section at the end14:40
cpaelzerit is meant to trigger discussion and bikeshedding, that asks for the open-end section of the meeting14:40
cpaelzer#topic MIR related Security Review Queue14:40
cpaelzerMission: Check on progress, do deadlines seem doable?14:40
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:40
cpaelzerInternal link14:40
cpaelzer- ensure your teams items are prioritized among each other as you'd expect14:40
cpaelzer- ensure community requests do not get stomped by teams calling for favors too much14:41
cpaelzer#link https://warthogs.atlassian.net/jira/software/c/projects/SEC/boards/59414:41
cpaelzerWe have discussed about them just before the sprint14:41
cpaelzera few things in there, related to cargo and heif14:41
slyon(where cargo should be high priority and heif best effort)14:41
cpaelzerI haven't seen sarnold or eslerm today to ask about openscap/smartcards if they got new focus14:41
cpaelzerslyon: that prio isn't reflected14:41
cpaelzerbut we can fix it up14:41
eslermcargo discussion at the sprint was productive, unblocked our dependency concerns14:42
cpaelzerlibgit2 was related to cargo right?14:42
slyoncpaelzer: yes, so is http-parser14:42
slyonI've set those to "high" priority on the board14:42
eslermiirc, smartcards were removed a cycle or two ago since desktop was no longer owning them14:42
cpaelzerI see the "high" so year, you are good14:43
cpaelzersorry for the noise14:43
eslermpreviously, we needed hardware for testing and at least one package needed significant work14:43
cpaelzereslerm: ok, so no comeback of them yet14:43
cpaelzerthanks14:43
eslermyes, unless desktop wants them14:43
cpaelzeryep14:43
cpaelzer#topic Any other business?14:43
eslermit would be nice to support them14:43
cpaelzerfrom me, get the discussion on https://github.com/canonical/ubuntu-mir/pull/17 going14:44
-ubottu:#ubuntu-meeting- Pull 17 in canonical/ubuntu-mir "add re-reviews to the MIR process" [Open]14:44
didrocksthanks for tackling this cpaelzer!14:44
eslerm^14:44
slyon+1!14:44
cpaelzeryw, it isn't perfect but a start14:44
cpaelzerQuestion #1 I have is on preference of how to express the rules14:44
cpaelzerright now I have copied the template and modified it14:45
cpaelzerpro: readable14:45
cpaelzercon: duplication / redundancy14:45
slyonI suggested to add an asterisk (*) to the TODOs/sections that are needed for re-review14:45
cpaelzerwould you rather prefer to merge the "re-review" with the "review" template and flag them somehow?14:45
slyonI'm afraid the templates will diverge if handled separately14:45
eslermimo, clarity justifies redundancy14:45
didrocks+1 on slyon's proposal14:45
cpaelzer+1 on slyon's suggestion - at least let me do that and then we can have a look14:46
cpaelzerI haven't seen that yet14:46
slyonthe asterisk shouldn't affect clarity too much and we can give a nice explanation about the * below the template14:46
dviererbeI think a copy would be fine, because the template is much more often copied that edited, but I also like the * Idea14:46
cpaelzerWe already filter out the RULE: sections14:46
eslermslyon: that makes sense14:46
cpaelzerI think the same way we can restrict to only or without those14:46
cpaelzerone question though14:46
cpaelzerthere are things which "ONLY" apply to re-review14:47
cpaelzerwould you be ok with "*** TODO: ..." for those?14:47
slyon"Then potentially having a new [Re-review*] section below for stuff that's only relevant for re-reviews. And giving an explanation about the * below, too (as usual)."14:47
cpaelzeroh that is nice14:47
didrocksbut those are the exceptions, correct? I guess a dedicated marker is fine14:47
cpaelzerthanks for having better ideas on the layout14:47
cpaelzerok, I'll overhaul with that in mind for next week14:47
cpaelzerdviererbe: I've seen your question as well14:48
cpaelzerdviererbe: it is meant to be a continuous effort14:48
cpaelzerdviererbe: but no high hopes please14:48
dviererbethanks sylon also answered that in the github isue14:48
cpaelzerdviererbe: the amount we can do is <<< things in main14:48
cpaelzerso it will be slow14:48
cpaelzerok, the TL;DR is14:49
cpaelzer1. you are all generally +1 as you love Ubuntu with quality as much as I do14:49
cpaelzer2. I'll integrate all your good feedback14:49
cpaelzer3. I'll reset this PR to needs review14:49
cpaelzerfrom there we can work on GH and talk again here next week14:49
cpaelzerthat is ok for me for today14:49
slyonsounds great, thanks!14:49
didrockssounds good :)14:50
joalifsounds good :)14:50
eslermthanks cpaelzer14:50
dviererbethanks for all the work!14:50
cpaelzerok, there was nothing else14:50
cpaelzerclosing this ....14:50
cpaelzerthank you all!14:50
eslermo/14:50
cpaelzer#endmeeting14:50
meetingologyMeeting ended at 14:50:27 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2023/ubuntu-meeting.2023-05-09-14.30.moin.txt14:50
didrocksthanks!14:50
joalifthanks cpaelzer all :)14:50

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