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

=== philroche_ is now known as philroche
cpaelzerhuhu14:29
dviererbeHello o/14:30
cpaelzer#startmeeting Weekly Main Inclusion Requests status14:30
meetingologyMeeting started at 14:30:27 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
sarnoldgood morning14:30
jamespageo/14:30
slyono/14: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
cpaelzernothing new in non-proposed14:31
cpaelzerhmm14:32
slyongeoip looks new14:32
slyonis the server team tracking that?14:32
cpaelzernginx -> geoip sounds familiar14:32
cpaelzerI think we changed to geoip2 two cycles back14:32
cpaelzerI'll take care to check what is going on14:32
cpaelzerI see that openstack started on jaraco14:32
cpaelzerand then there is transmission14:33
cpaelzerDesktop package14:33
sarnoldmantic-proposed has a 'drop geoip' in the changelog https://launchpad.net/ubuntu/+source/nginx/+changelog -- it might solve itself in a few days? :)14:33
cpaelzerdidrocks isn't here today to use his Desktop connections, seb128 isn#t her eeither14:34
cpaelzerpinging jbicha if there is any known context on transmission14:34
sarnold  * Switch back to gtk4, now that the previous upload migrated.14:34
sarnold    the MIR of gtkmm4.0 is planned.14:34
jbichait's still on my todo list to file the MIRs for gtkmm4.0 (& related pkgs)14:34
cpaelzerok, we are happy to wait14:34
sarnoldhttps://launchpad.net/ubuntu/+source/transmission/+changelog  -- this one looksl ike the tip of the iceberg for new work, heh14:35
cpaelzersarnold: on geoip - the changelog has this under dropped changes14:35
cpaelzersarnold: "[No longer required due to Debian packaging split]"14:35
sarnoldcpaelzer: oh!14:35
cpaelzersarnold: but it seems that didn't fully work, chances are something is now split and meant to migrate to universe14:35
cpaelzerI'll talk with bryce14:35
cpaelzerok14:36
cpaelzerthat means we are ok with all findings in mismatches today14:36
cpaelzer#topic New MIRs14:36
cpaelzerMission: ensure to assign all incoming reviews for fast processing14: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-mir14:36
cpaelzerone new14:36
cpaelzerhttps://bugs.launchpad.net/ubuntu/+source/dhcpcd5/+bug/201919114:36
-ubottu:#ubuntu-meeting- Launchpad bug 2019191 in dhcpcd5 (Ubuntu) "[MIR] dhcpcd5" [Undecided, New]14:36
slyonthis will be the (future) replacement for isc-dhcp-client14:37
cpaelzerAnyone able to do the review and not having Thu (and probably Fri) off due to public holiday in a lot of central europe?14:37
* slyon abstains, due to it being a Foundations package14:38
cpaelzeryeah, I guess I can take one - but due to said public holiday it will be somewhen next week14:38
cpaelzer#topic Incomplete bugs / questions14:38
cpaelzerMission: Identify required actions and spread the load among the teams14:38
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:38
cpaelzersome updates on duktape, but not yet ready to be acted on14:39
cpaelzernothing else in this list yet14:39
cpaelzer#topic Process/Documentation improvements14:39
cpaelzerMission: Review pending process/documentation pull-requests or issues14:39
cpaelzer#link https://github.com/canonical/ubuntu-mir/pulls14:39
cpaelzer#link https://github.com/canonical/ubuntu-mir/issues14:39
cpaelzerjust my re-review topic which we can handle in AOB14:40
cpaelzernothing else in those lists14: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:40
cpaelzer#link https://warthogs.atlassian.net/jira/software/c/projects/SEC/boards/59414:40
cpaelzersarnold: this is the time to make progress on those items not being pressing issues14:40
cpaelzersarnold: because in a month or two the list will be dominated by "I NEED THIS" items14:40
cpaelzersarnold: so how is current velocity on reviews looking?14:41
* cpaelzer checks #security channel for distractions of sarnold ...14:42
sarnoldcpaelzer: heh, no progress lately; there has been some ongoing work on the tooling to try to improve the tooling. one current hurdle is that our coverity license has expired, and re-signing that contract is stuck somewhere; people are poking and prodding even while on vacation :/14:42
cpaelzeroh14:43
sarnoldthere's enough folks on post-sprint recovery and lss and so on that we're not yet at full force14:43
cpaelzerso without this license, is review fully blocked ?14:43
cpaelzeror just "less good"14:43
sarnoldnot completely, but it is enough of a hurdle to be obnoxious14:43
cpaelzerok, thanks for the FYI14:43
cpaelzer#topic Any other business?14:43
cpaelzeras last week - just https://github.com/canonical/ubuntu-mir/pull/1714:44
-ubottu:#ubuntu-meeting- Pull 17 in canonical/ubuntu-mir "add re-reviews to the MIR process" [Open]14:44
cpaelzerthanks for your feedback so far14:44
cpaelzerI know I need to create a good way to find those old bugs14:44
cpaelzerbut other than that everyone seems happy so far14:44
cpaelzerany other feedback or request for change that didn#t make it into thr github PR?14:45
sarnoldI think I forgot to mention a pal's spell checking action https://www.check-spelling.dev/14:45
sarnoldif we wanted to keep the spelling in good order, this might be worth dropping in14:45
sarnoldbut if we make so few changes and spelling doesn't *really* matter, it's just nice to have, it might not be worth the ongoing cost14:46
cpaelzeris that free to activate without pain?14:46
dviererbe*creating a bookmark*14:46
sarnoldI think so, but I'm not actually well-versed in github actions; I think it's 'just' a matter of cloning the repo, dropping a .github/ directory thingy in place, pushing it, and letting the bot do the rest14:46
cpaelzerI'll have a look14:47
cpaelzerthanks14:47
dviererbeI can investigate this. I have some experience with github actions14:47
slyonhere's a template: https://github.com/check-spelling/spell-check-this14:47
cpaelzerthanks dviererbe for the volunteering14:48
cpaelzerI guess you can fork and experiment there, and once you know how open a PR and/or contact me to get things done in the main repo?14:48
dviererbeI'll do that14:49
sarnoldwoot, thanks :)14:49
cpaelzerI'll take the todo that slyon gave me to add the "old MIR bug" query14:49
cpaelzerand thereby, the agenda of today is at the end14:49
cpaelzeranything else?14:49
sarnoldnothing from me14:49
sarnoldexcept a gigantic curiosity how that 'old mir bug' query will work14:49
slyonnothing, thanks!14:50
cpaelzersarnold: magic :-)14:50
sarnoldI don't have a clue how I'd even start tackling it, if it were my todo :)14:50
sarnold:D14:50
slyon(it's not just "old MIR bug", there might be packages without any bug14:50
sarnoldprobably about a thousand of them..14:50
cpaelzerhehe14:50
cpaelzerthe API isn't too bad14:50
cpaelzerof LP I mean14:50
sarnoldI wasn't there, but my guess is the starting point was "what's installed on every one of elmo's computers" :)14:51
cpaelzerIt is most likely not a query, but a python program14:51
cpaelzersarnold: that might have been true :-)14:51
cpaelzerbut for today, let us close the meeting here14:51
cpaelzerhave fun everyone!14:51
sarnoldthanks cpaelzer, all; enjoy the long weekens, those who have them :)14:51
cpaelzer#endmeeting14:51
meetingologyMeeting ended at 14:51:52 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2023/ubuntu-meeting.2023-05-16-14.30.moin.txt14:51
=== ebarretto_ is now known as ebarretto
seb128hey18:59
* vorlon waves18:59
amurrayo/19:00
rbasako/19:00
vorlonrbasak: calendar says you're chair?19:01
rbasakOh, OK.19:01
rbasak#startmeeting Technical Board19:01
meetingologyMeeting started at 19:01:33 UTC.  The chair is rbasak.  Information about MeetBot at https://wiki.ubuntu.com/meetingology19:01
meetingologyAvailable commands: action, commands, idea, info, link, nick19:01
rbasak#topic Action Review19:01
rbasakACTION: amurray to follow up with backporters team on Mattia's draft charter proposal19:01
rbasakI think I've seen the followup. Did we get a reply?19:01
vorlon(fwiw sil2100 is out this week; didn't see an apology but not surprised he's not here)19:02
amurrayre backporters - no not that I have seen19:02
rbasakMaybe another poke is appropriate?19:02
amurrayI will ping them again later this week19:02
rbasakIt'd be nice to see a conclusion on this. I wonder if it would be appropriate to set a deadline at some point, and if no reply then we just use the current draft and call it done. I wouldn't mind it being long eg. months, but it'd be nice to have _some_ end point.19:03
rbasakThanks19:03
rbasakACTION: seb128 to help draft an exception to the "must build on all architectures" requirement for snaps19:03
rbasakAnd related19:04
rbasakACTION: seb128/amurray/sil200 to help drafting the snap-store Ubuntu-specific tracks usage19:04
seb128no progress sorry :/19:04
rbasakACTION: rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification19:04
rbasakSame here, sorry19:04
rbasakACTION: sil2100 to start a draft summarizing the OEM archive portion of the meeting which x-nox and TB will review, edit, and ratify before we move on to figuring out the next step19:04
rbasakHe's out, so that will need to carry over too19:04
seb128I hope to have more time for $things now that Lunar is out though19:04
rbasakThanks!19:04
rbasak#topic Scan the mailing list archive for anything we missed (standing item)19:04
rbasakI see nothing relevant in April or May.19:05
vorlonthere's a private email thread; I wonder if folks want to bring that topic public and discuss here?19:05
rbasak#info Nothing outstanding in recent ML posts19:06
rbasakI'm happy to discuss that publicly if others are19:06
vorlon(I just replied to it a half hour ago, so undertsandable if folks aren't current)19:06
rbasakI'd also be happy for my reply to be made public in its entirety.19:07
rbasak(so feel free to quote me from there in pubilc, etc)19:07
vorlonseb128: ?19:07
seb128sorry, I was busy reading vorlon's reply on that discussion :p19:08
vorlon:)19:08
vorlonfwiw my specific email wasn't drafted for public consumption so please don't quote it, but addressing the content is fine19:08
seb128I'm also fine discussing it in public19:08
seb128I wonder if now is right though, we got 3 replies since yesterday unsure if everyone had time to read/digest those19:09
vorlonack, I'm certainly fine to defer19:10
amurrayI'm fine to discuss it in public but I wonder if perhaps let's finish up the existing conversation privately then we can document the outcome publicly?19:10
rbasakTo make progress, how about we give each other a couple of weeks to raise any objections to discussing the topic publicly? After that time, maybe we can effectively replay the thread but publicly.19:10
seb128wfm19:10
amurray+119:11
vorlon+119:12
rbasakfwiw my specific email wasn't drafted for public consumption> yeah I agree since it referred to specific individuals and that maybe shouldn't be made public (just for anyone following along)19:12
rbasak#topic Check up on community bugs and techboard bugs19:13
rbasak#info No new community bug activity19:13
rbasak#topic Select a chair for the next meeting19:13
rbasakWe're going alphabetically, right? So seb128 next with vorlon as backup?19:14
vorlonsounds good19:14
seb128ack19:14
rbasak#info seb128 will chair next, with vorlon as backup19:14
rbasak#topic AOB19:14
rbasakAOB?19:14
vorlonnothing here19:15
rbasak#info No OB19:15
rbasak#endmeeting19:15
meetingologyMeeting ended at 19:15:58 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2023/ubuntu-meeting.2023-05-16-19.01.moin.txt19:15
rbasako/19:15
amurraythanks for chairing rbasak19:16
seb128thanks!19:16

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