[14:29] <sarnold> good morning
[14:30] <slyon> hello!
[14:31] <joalif> hello
[14:32] <slyon> Ping for MIR meeting - didrocks joalif slyon sarnold cpaelzer jamespage – will you be around?
[14:32] <slyon> we might be a bit under-staffed today, due to sprint week
[14:33] <slyon> #startmeeting Weekly Main Inclusion Requests status
[14:33] <meetingology> Meeting started at 14:33:28 UTC.  The chair is slyon.  Information about MeetBot at https://wiki.ubuntu.com/meetingology
[14:33] <meetingology> Available commands: action, commands, idea, info, link, nick
[14:33] <slyon> #topic current component mismatches
[14:33] <slyon> #link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg
[14:33] <slyon> #link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg
[14:34] <cpaelzer> hi
[14:34] <cpaelzer> I'm partially here
[14:34] <slyon> I've investigated liburi-perl last week and coordinated with the Debian maintainer. This change (&component mismatch) will most probably be rolled back (see attached bug report)
[14:34] <slyon> I can see one new component-mismatch (moar -perl depends...): libchart-perl
[14:35] <slyon> it's tagged foundations-bugs, so I'll do an initial investigation on this
[14:35] <slyon> anything else?
[14:35] <sarnold> that's all I spotted
[14:35] <cpaelzer> me as well
[14:35] <slyon> #topic New MIRs
[14:35] <slyon> Mission: ensure to assign all incoming reviews for fast processing
[14:35] <slyon> we have two new MIRs
[14:35] <slyon> bug 1980968
[14:36] <cpaelzer> another lintian case
[14:36] <cpaelzer> I can take that
[14:36] <slyon> joalif: is this something you could have a look at? (shoudl be fairly small)
[14:36] <slyon> or cpaelzer
[14:36] <cpaelzer> self assigned
[14:36] <joalif> which one ?
[14:36] <cpaelzer> already gone joalif :-)
[14:36] <slyon> thanks
[14:36] <slyon> bug 1942394
[14:37] <cpaelzer> that is from us (so I shouldn't really review)
[14:37] <cpaelzer> it is the first trying the rust rules we landed
[14:37] <slyon> that's the first MIR case.. I might be able to take a look at that, not sure if I can make it in one week, tho. as I expect it to take a bit longer
[14:38] <slyon> (self assigned)
[14:38] <slyon> #topic Incomplete bugs / questions
[14:38] <slyon> Mission: Identify required actions and spread the load among the teams
[14:38] <slyon> #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-mir
[14:38] <slyon> vulkan-tools (bug 1946359) is just a tracking update (Impish EOL)
[14:39] <cpaelzer> slyon: if you have any direct question while looking at mdevctl please consider pingign athos directly
[14:39] <slyon> libregexp-ipv6-perl (bug 1981608) is my investigation about the -perl dependency mentioned earlier. not actionable right now
[14:39] <slyon> no other recent updates.
[14:39] <slyon> #topic MIR related Security Review Queue
[14:39] <cpaelzer> nice, glad it isn't too much
[14:39] <slyon> Mission: Check on progress, do deadlines seem doable?
[14:40] <slyon> #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-mir
[14:40] <slyon> #link https://warthogs.atlassian.net/jira/software/c/projects/SEC/boards/594 (internal)
[14:40] <slyon> sarnold: how are the security queues moving along?
[14:40] <cpaelzer> if you can sort by milestone
[14:41] <sarnold> they are moving :) it feels good
[14:41] <cpaelzer> there are at least 6 for this cycle
[14:41] <cpaelzer> and depending how we see mdevctl +1
[14:41] <slyon> cpaelzer: actually sarnold mentioned last week that the LP milestones are mostly ignored
[14:41] <cpaelzer> but I agree we had a few recent closed cases IIRC
[14:41] <slyon> and we should rather prioritize in jira
[14:42] <sarnold> one thing that worries me is wpe webkit stuff -- mdeslaur has asked for wpewebkit to be removed and blocked from debian syncs https://bugs.launchpad.net/ubuntu/+source/wpewebkit/+bug/1981592 but we've also got https://bugs.launchpad.net/ubuntu/+source/wpebackend-fdo/+bug/1973033 and https://bugs.launchpad.net/ubuntu/+source/libwpe/+bug/1973031 in progress
[14:42] <cpaelzer> sarnold: how would you want us to tag/prioritize it in there?
[14:42] <cpaelzer> or shoud I read last weeks log if you already explained?
[14:43] <sarnold> cpaelzer: there's a little chevron up or down, or little yellow equals sign, that's used for a priority field
[14:43] <cpaelzer> I know that
[14:43] <cpaelzer> but what does it mean
[14:43] <cpaelzer> if I need something for FF - what do you want me to set for example
[14:43] <sarnold> the high priority, please
[14:45] <sarnold> given how difficult / impossible it is to support the various webkits, this new flavour makes me worried that we'll wind up with twice as many packages that we can't reaistically support
[14:46] <sarnold> even if the wpebackend-fdo and libwpe packages are short-and-sweet and reasonable, do they "need" The Other wpewebkit package?
[14:46] <cpaelzer> this is from the desktop team
[14:47] <cpaelzer> sadly seb128 is offline (focus on sprint) and didrocks isn't here either (and not that involved there)
[14:47] <slyon> ACK, I am not in the known about wpewebkit either..
[14:47] <cpaelzer> who else from Desktop could we ping to re-consider not needing wpe?
[14:48] <cpaelzer> sarnold: maybe you'd need to send your feedback in a mail to seb128 or - even better for auditability - just update that bug ?
[14:48] <mdeslaur> those two libraries are needed for webkit2gtk and don't prevent wpewebkit from being removed from the archive
[14:48] <mdeslaur> (FYI)
[14:48] <cpaelzer> challenge them to reconsider if it is really strictly needed to add support for this
[14:48] <cpaelzer> mdeslaur: glad to learn that those are separate
[14:49] <sarnold> great, thanks mdeslaur :)
[14:49] <mdeslaur> there's a relevant blog post about it here: https://blogs.gnome.org/mcatanzaro/2022/07/15/best-practices-for-build-options/
[14:49] <sarnold> cpaelzer: I was worried about The Bug because we've got three of them in play at the moment
[14:50] <mdeslaur> (rule #2 in that blog post)
[14:50] <slyon> sarnold: is there any dependency on wpewebkit from those?
[14:50] <sarnold> slyon: none that I've found through manual inspection
[14:50] <sarnold> slyon: but dlopen sorts of things might make it harder to spot
[14:51] <slyon> good. I can't see any from "reverse-depends src:wpewebkit" either
[14:51] <slyon> so we might be fine to handle those independently. Maybe you could still reach out to the desktop team (or mention it on the bug report), just to double check and make everybody aware
[14:51] <sarnold> nice blog post, it reads very similar to the MIR requests, hehe
[14:52] <slyon> #topic Any other business?
[14:52] <sarnold> ack, will do, thanks
[14:52] <sarnold> none here
[14:52] <joalif> none
[14:52] <slyon> nothing here
[14:52] <slyon> ok, let's wrap this and get people back to the sprint!
[14:52] <slyon> thanks for your time! :)
[14:52] <slyon> #endmeeting
[14:53] <meetingology> Meeting ended at 14:53:00 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2022/ubuntu-meeting.2022-07-19-14.33.moin.txt
[14:53] <sarnold> thanks slyon, all :)
[14:53] <sarnold> happy sprinting
[14:53] <joalif> thanks slyon, all
[19:00] <sil2100> o/
[19:01] <rbasak> o/
[19:02]  * vorlon waves
[19:03] <vorlon> do we have editing capabilities on https://wiki.ubuntu.com/TechnicalBoardAgenda yet? I'm still locked out but I heard it was fixed for others
[19:04] <rbasak> I just hit the Edit button and it worked for me
[19:04] <sil2100> So far I'm logged in so I can edit it as well, if needed
[19:05] <vorlon> I had one random moment a couple of weeks ago where I managed to get logged in, then *immediately* managed to misclick on the logout button
[19:05] <vorlon> epic fail
[19:09] <sil2100> Ouch!
[19:10] <vorlon> anyone want to chair? :)
[19:13] <vorlon> the agenda says rbasak is the backup chair so I nominate him to either chair or edit the wiki to say something else
[19:14] <rbasak> lol
[19:14] <rbasak> #startmeeting Technical Board
[19:14] <meetingology> Meeting started at 19:14:52 UTC.  The chair is rbasak.  Information about MeetBot at https://wiki.ubuntu.com/meetingology
[19:14] <meetingology> Available commands: action, commands, idea, info, link, nick
[19:15] <rbasak> #topic Action Review
[19:15] <rbasak> ACTION: (everyone) review the Ubuntu Backports Team Charter for ratification
[19:15] <rbasak> ACTION: (everyone) formal ratification of third party seeded snap security policy (finalize wording on the Google Doc)
[19:15] <rbasak> ^ this one I'm still working on
[19:15] <rbasak> ACTION: vorlon to circle around with store, snapcraft, et all, and revise the snap source revision policy to be more clear with regards to rebuildability and GPL compliance. (rbasak, 19:06)
[19:15] <rbasak> ^ blocked on me?
[19:15] <rbasak> ACTION: 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 step (rbasak, 19:08)
[19:15] <rbasak> ACTION: rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification (sil2100, 19:20)
[19:15] <rbasak> ^ still pending
[19:15] <rbasak> ACTION: cyphermox to follow up with the CC regarding the TB nominations and election (sil2100, 19:23)
[19:16] <rbasak> Any progress on the others that needs reporting please? Otherwise carry everything over?
[19:16] <vorlon> rbasak: yeah I think that's blocked on the draft policy at this point
[19:16] <sil2100> Yeah, mine is a bit of a stupid thing. I had notes on the OEM Archive status but still didn't quite get to getting those formally written down
[19:16] <sil2100> I'm actually trying to do some of the writing right now
[19:16] <rbasak> OK so carry over everything?
[19:17] <rbasak> #topic Definition of our third party repository policy. See https://docs.google.com/document/d/1apUKR4gtOrfPGCWmtoebaQUhoy-fG8Cyo3VKJyhnpD0/edit
[19:17] <vorlon> afaik yes
[19:17] <rbasak> I've made some progress in identifying relevant snaps
[19:17] <rbasak> I scanned the archive for dependencies on snapd on the assumption that all "transitional packages" would pull them in.
[19:17] <rbasak> Also I scanned some set of seeds to see what seeds might seed snaps directly. See my question in #ubuntu-devel - did I get them all?
[19:17] <rbasak> I stuck them in an appendix at the bottom of the document for now.
[19:18] <rbasak> The only unusual things are ember/cyphesis-cpp that came in through Debian
[19:18] <rbasak> And freeshow which was packaged as a snap by ubuntu-studio (AFAICT) and then seeded.
[19:18] <vorlon> there are transitional deb-to-snap packages in Debian?
[19:18] <rbasak> Indeed :)
[19:18] <vorlon> o_O
[19:19] <sil2100> wow
[19:19] <rbasak> See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950926
[19:19] <rbasak> On these ones, I think it would make sense to apply our policy completely, possibly blocklisting autosync if the requirements are not met. But I'll talk to the maintainer first.
[19:20] <rbasak> On the Ubuntu Studio freeshow, I expect the snap can be trivially adjusted to meet our requirements anyway. I'll talk to Eickmeyer
[19:20] <rbasak> Are there any other sources of snaps I might have missed?
[19:21] <vorlon> sounds complete to me
[19:21] <vorlon> with the caveat that packages might have missed the dep on snapd on account of it being in the base system
[19:22] <rbasak> Any ideas on identifying those?
[19:22] <vorlon> uh codesearch.ubuntu.com
[19:22] <vorlon> (does not exist)
[19:22] <rbasak> I think I might know someone. But I suspect that searching for "snap" will have too many false positives :-/
[19:23] <vorlon> 'snap install'?
[19:23] <rbasak> But that doesn't really stop us determining a policy and dealing with new things as they are discovered.
[19:23]  * vorlon nods
[19:23] <rbasak> subprocess.check_call(['snap', 'install']) etc :-/
[19:24] <rbasak> If there are no other comments, I'll carry on with this and we can move on from this topic?
[19:24] <sil2100> +1 o/
[19:24] <rbasak> #topic Scan the mailing list archive for anything we missed (standing item)
[19:25] <vorlon> (FWIW I assumed we would only need to worry about this in maintainer scripts, which are 99.9% shell)
[19:25] <rbasak> Only the post from Philipp Kewisch. sil2100 and I have already talked to him.
[19:25] <rbasak> #topic Check up on community bugs (standing item)
[19:25] <vorlon> I invited him to this meeting but he may not make it
[19:26] <sil2100> It was a good talk. But I forgot to make any notes during the meeting
[19:26] <rbasak> No community bugs listed.
[19:26] <rbasak> #topic Select a chair for the next meeting (next from https://launchpad.net/~techboard/+members)
[19:26] <sil2100> Could have been a good idea for the other TB members to read, eh...
[19:26] <rbasak> vorlon I guess? :-P
[19:26] <rbasak> #topic AOB
[19:26] <rbasak> AOB?
[19:27] <vorlon> that's to me as next chair?  sure
[19:27] <rbasak> I'll change the agenda doc accordingly :-)
[19:28] <rbasak> #endmeeting
[19:28] <meetingology> Meeting ended at 19:28:22 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2022/ubuntu-meeting.2022-07-19-19.14.moin.txt
[19:28] <rbasak> Thanks all!
[19:28] <vorlon> thanks
[19:29] <sil2100> Thanks o/
[19:39]  * genii sweeps up, washes the coffee mugs and puts them away