[14:32] <sarnold> good morninig
[14:32] <joalif> o/
[14:33] <cpaelzer> finally
[14:33] <cpaelzer> I made it
[14:33] <cpaelzer> former meeting was running over - sorry
[14:33] <cpaelzer> let me get this started
[14:34] <cpaelzer> #startmeeting Weekly Main Inclusion Requests status
[14:34] <meetingology> Meeting started at 14:34:30 UTC.  The chair is cpaelzer.  Information about MeetBot at https://wiki.ubuntu.com/meetingology
[14:34] <meetingology> Available commands: action, commands, idea, info, link, nick
[14:34] <cpaelzer> hi sarnold joalif slyon didrocks jamespage
[14:34] <slyon> o/
[14:34] <cpaelzer> #topic Review of previous action items
[14:35] <cpaelzer> only action is me wanting to thank you all to carry this on while I was sick and on sprint!
[14:35] <cpaelzer> #topic current component mismatches
[14:35] <cpaelzer> Mission: Identify required actions and spread the load among the teams
[14:35] <cpaelzer> #link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg
[14:35] <cpaelzer> #link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg
[14:35] <cpaelzer> new cycle, new mismatches showing up
[14:35] <cpaelzer> ahve you talked about pipewire->libldac before?
[14:35] <slyon> nope, seems new
[14:36] <cpaelzer> didrocks: seb128: that seems desktop'ish - would you talk to the team if one can check this new dependency?
[14:37] <cpaelzer> hmm didrocks might be unavailable
[14:37] <cpaelzer> I have pinged internally, maybe one joins - let us identify more new cases
[14:38] <cpaelzer> ruby-xmlrpc -> ruby->webrick is new to me
[14:38] <cpaelzer> did you check that last week?
[14:38] <slyon> ruby-xmlrpc looks new
[14:38] <slyon> ah... I think we might have left that for you :P
[14:39] <cpaelzer> fine and fair
[14:39] <cpaelzer> I'll talk with kanashiro later
[14:39] <slyon> thanks
[14:40] <cpaelzer> jaraco.text
[14:40] <cpaelzer> that is from the openstack context
[14:40] <cpaelzer> jamespage: ? ^^
[14:40] <slyon> we pinged him in the past about it, but he might not yet have had the time to check
[14:41] <cpaelzer> plenty of others have stubs - which is great as that defines an owner
[14:41] <slyon> yes, many are in the foundations backlog
[14:42] <cpaelzer> requests (python) -> python-charset-normalizer
[14:42] <didrocks> cpaelzer: sorry, meeting running over
[14:42] <cpaelzer> that is also server sadly, I do not know why this one pytohn lib is ours, but we will have a look
[14:42] <didrocks> yeah, will do pipewire
[14:42] <cpaelzer> np, welcome didrocks
[14:42] <cpaelzer> and thanks for that
[14:42] <didrocks> (still in meeting btw)
[14:42] <cpaelzer> I'll take requests for the server team
[14:42] <slyon> thanks!
[14:44] <cpaelzer> all others have stubs or are known false positives
[14:44] <cpaelzer> going on ...
[14:44] <cpaelzer> #topic New MIRs
[14:44] <cpaelzer> Mission: ensure to assign all incoming reviews for fast processing
[14:44] <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-mir
[14:45] <cpaelzer> desktop is flooding us :-)
[14:45] <cpaelzer> https://bugs.launchpad.net/ubuntu/+source/libwpe/+bug/1973031
[14:45] <cpaelzer> https://bugs.launchpad.net/ubuntu/+source/wpebackend-fdo/+bug/1973033
[14:45] <didrocks> yeah :p
[14:45] <cpaelzer> both looking for volunteers
[14:45] <didrocks> I can probably take one of them
[14:45] <cpaelzer> I could do the lib
[14:46] <cpaelzer> would you didrocks do the -fdo one?
[14:46] <didrocks> ack, I will do the -fdo
[14:46] <cpaelzer> assigned both
[14:46] <cpaelzer> #topic Incomplete bugs / questions
[14:46] <cpaelzer> Mission: Identify required actions and spread the load among the teams
[14:46] <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-mir
[14:47] <cpaelzer> ok we have a few recent updates ...
[14:47] <didrocks> iwd and g-t-e is waiting on desktop
[14:47] <cpaelzer> vulkan and smartcards are just tracking updates
[14:47] <cpaelzer> and yet to what didrocks said
[14:47] <cpaelzer> btw in that context I reviewed "ell" today, that is waiting on security now
[14:47] <sarnold> \o/
[14:47] <slyon> I'd like to consult the rest of the MIR team about iwd
[14:48] <didrocks> see how happy sarnold is :p
[14:48] <cpaelzer> let us do that in other business slyon
[14:48] <slyon> ack
[14:48] <cpaelzer> completing this section with
[14:48] <cpaelzer> https://bugs.launchpad.net/ubuntu/+source/python-invoke/+bug/1892875
[14:48] <cpaelzer> discussion going on betwen bdrung and jamespage - not really a discussion, but TL;DR no action needed atm
[14:49] <cpaelzer> #topic MIR related Security Review Queue
[14:49] <cpaelzer> Mission: Check on progress, do deadlines seem doable?
[14:49] <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-mir
[14:49] <cpaelzer> ell (just mentioned above) has a milestone set as seb mentioned when it is needed
[14:50] <cpaelzer> I'm still waiting for a milestone on vulkan-tools, but I know people are waiting on this as well
[14:50] <cpaelzer> sarnold: how does progress look on your side now?
[14:50] <sarnold> this last week was some yak-shaving, getting new coverity, new coverity license, installed and working on my poor old build laptop; a bug report I filed on the segfault during build was very well received :D
[14:50] <cpaelzer> tracking in place, people/resources available ?
[14:50] <sarnold> cpaelzer: it feels much happier now, yes
[14:51] <cpaelzer> ok, let me do my groundhog day - any news for telegraf then?
[14:51] <cpaelzer> it is at the top of the list, so it is the one I ask about
[14:51] <sarnold> a nice visit with an old friend :D https://github.com/influxdata/telegraf/issues/11092#issuecomment-1125404409
[14:51] <cpaelzer> hehe
[14:52] <sarnold> I think that's it for us
[14:52] <cpaelzer> that sounds like "ongoing" then
[14:52] <cpaelzer> thanks
[14:52] <cpaelzer> #topic Any other business?
[14:52] <cpaelzer> iwd from slyon?
[14:52] <slyon> bug 1971739
[14:52] <slyon> the question is: should we require security review?
[14:52] <cpaelzer> reading through it ...
[14:53] <slyon> iwd runs a daemon/service as root, but it has very good isolation/security in place in its systemd .service unit
[14:53]  * didrocks reads too
[14:53] <cpaelzer> I'd still vote for getting a review
[14:53] <slyon> what is the policy, we apply here? Usually, daemon as root => security review. But IMO that was before systemd-service isolation existed
[14:54] <cpaelzer> for me the question is not "is it well isolated" that is for the security team to decide. Instead it is "does this have an attack surface" -> if yes then need review
[14:54] <cpaelzer> it is a simplification, but that is how I handle it most of the time
[14:54] <didrocks> yeah, me too
[14:54] <cpaelzer> I'm not putting all my eggs into the "systemd will keep me safe and warm" basket
[14:54] <slyon> ack. I might have some bias there :D
[14:54] <didrocks> heh :)
[14:54] <slyon> I will be requiring security-review then
[14:54] <cpaelzer> to be clear I appreciate every isolation that is used and it makes the feeling better and more likely to pass review
[14:55] <cpaelzer> but it still needs one
[14:55] <cpaelzer> this will follow the same deadline as ell then, setting milestone
[14:55] <slyon> yes
[14:56] <cpaelzer> I updated the case
[14:57] <cpaelzer> anything else for "other business" ?
[14:57] <sarnold> nothing from me
[14:57] <didrocks> nothing for me
[14:57] <slyon> nothign
[14:57] <joalif> nothing
[14:58] <cpaelzer> neither from me
[14:58] <cpaelzer> to close this - just as expected "new cycle new fun"
[14:58] <cpaelzer> thank you all!
[14:59] <sarnold> thanks cpaelzer, all :)
[14:59] <cpaelzer> #endmeeting
[14:59] <meetingology> Meeting ended at 14:59:02 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2022/ubuntu-meeting.2022-05-17-14.34.moin.txt
[14:59] <slyon> thanks!
[14:59] <didrocks> thanks!
[14:59] <joalif> thanks all
[18:54] <cyphermox> o/
[18:58] <sil2100> o/
[18:58] <rbasak> o/
[19:00] <sil2100> Does anyone know who is to chair today? Since I missed the last TB meeting due to the sprint...
[19:00] <sil2100> Also, just for the note: I still can't log into the wiki
[19:00] <rbasak> I managed to log in and make changes earlier
[19:00] <rbasak> It's still slow. Perhaps it's just within the timeout for me.
[19:01] <sil2100> I'll try a few times then
[19:01] <rbasak> But because the wiki couldn't be updated before, I'm not sure the agenda or chair are up-to-date
[19:01] <cyphermox> the wiki was not updated earlier, still pointing to rbasak and vorlon
[19:01] <cyphermox> rbasak, so you have an update in flight?
[19:02] <rbasak> I don't
[19:02] <rbasak> I was just looking to see when the last meeting was and find its logs
[19:03] <rbasak> Was 5 April the last one or has there been a more recent one?
[19:03] <cyphermox> it was the last one, I think. previous was when everyone was at a sprint
[19:04] <cyphermox> ugh, that wasn't a clear sentence, was it?
[19:05] <rbasak> Yep confirmed
[19:06] <vorlon> hi, sorry I'm late
[19:06] <sil2100> o/
[19:06] <rbasak> https://irclogs.ubuntu.com/2022/04/05/%23ubuntu-meeting.html#t18:51
[19:07] <rbasak> That was the last meeting I think
[19:07] <rbasak> Who wants to chair this one?
[19:07] <rbasak> (link for divining the agenda)
[19:07] <rbasak> We only talked about the third party package requirements
[19:08] <sil2100> Let me chair then o/
[19:09] <rbasak> Before that was https://new.ubottu.com/meetingology/logs/ubuntu-meeting/2022/ubuntu-meeting.2022-03-08-20.03.html and there were no new actions then
[19:09] <rbasak> So I guess the agenda is up-to-date.
[19:09] <sil2100> #startmeeting Ubuntu Technical Board
[19:09] <meetingology> Meeting started at 19:09:20 UTC.  The chair is sil2100.  Information about MeetBot at https://wiki.ubuntu.com/meetingology
[19:09] <meetingology> Available commands: action, commands, idea, info, link, nick
[19:09] <sil2100> #topic Apologies
[19:09] <sil2100> ...no apologies \o/
[19:09] <cyphermox> I have a hard stop in an hour
[19:09] <sil2100> #topic Action Review
[19:09] <sil2100> ACTION: (everyone) review the Ubuntu Backports Team Charter for ratification
[19:10] <sil2100> I must say that I didn't look at it yet
[19:10] <rbasak> My comments are in the thread
[19:10] <rbasak> (summary: IMHO it's not ready for ratification as-is)
[19:11] <sil2100> Then reminder to myself and others that didn't do this yet: let's all read and comment on the ML
[19:11] <rbasak> But I would like to see some terms of reference defined and documented.
[19:12] <sil2100> Let's move on for now
[19:12] <sil2100> ACTION: (everyone) formal ratification of third party seeded snap security policy (finalize wording on the Google Doc)
[19:12] <rbasak> I have been working on the draft but we can discuss this in its own agenda item
[19:13] <sil2100> Ok, so let's move for now
[19:13] <sil2100> 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.
[19:13] <sil2100> vorlon: any progress here? ^
[19:15] <sil2100> I think I saw the card on Jira, so I think the answer is 'not yet' - but it's on the backlog for vorlon
[19:15] <sil2100> 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
[19:16] <vorlon> sil2100: correct :/
[19:16] <sil2100> So some good news and bad news. Good news is that I had a chat with Rex in Copenhagen about this, so I have a better understanding now. Bad news: nothing officially written besides scribbles
[19:16] <sil2100> I blame it on the wiki
[19:16] <sil2100> ...which apparently I was able to log onto now \o/
[19:17] <sil2100> ACTION: Review and leave feedback on the first version of the preamble and three first requirements https://pad.ubuntu.com/third-party-repository-requirements (all of the TB)
[19:17] <sil2100> I think this one we need to remove
[19:17] <sil2100> It's been moved to the google doc
[19:17] <sil2100> Oh, hah!
[19:17] <sil2100> ACTION: rbasak to move the pad to Google Doc
[19:17] <rbasak> done
[19:17] <sil2100> This is done, so yeah, let me clear those out
[19:17] <vorlon> should update the wiki to point to https://docs.google.com/document/d/1apUKR4gtOrfPGCWmtoebaQUhoy-fG8Cyo3VKJyhnpD0/edit ?
[19:17] <sil2100> ACTION: Discuss DMB inactivity expiration policy (all of the TB)
[19:18] <sil2100> I think this is already done, right? Or do we still need to discuss something here?
[19:18] <rbasak> I think we do need to discuss it, but haven't done yet.
[19:18] <rbasak> It could do with tying up. I'd like for the TB to ratify what the DMB wanted, but while doing it clear up the ambiguous bits.
[19:19] <rbasak> I don't mind drafting something, so you can carry it and assign to me for a concrete proposal if you'd like.
[19:19] <rbasak> I won't get to it immediately since I'm prioritising some other TB/DMB things and it's no longer an urgent thing.
[19:20] <sil2100> #action rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification
[19:20] <meetingology> ACTION: rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification
[19:20] <sil2100> rbasak: feel free to reach out to me in case you won't find the time for that one
[19:20] <rbasak> Thanks!
[19:20] <sil2100> ACTION: cyphermox to contact CC to trigger an election
[19:20] <sil2100> This is marked done
[19:21] <sil2100> I guess we had no candidates..?
[19:21] <rbasak> Was there a call for nominations?
[19:21] <sil2100> Yes, there was one for Marc's seat
[19:21] <cyphermox> I remember marking it done, but now that I didn't see anything go by I wanted to circle back and check at what the status of things are
[19:21] <rbasak> Oh yes. I remember now, sorry.
[19:21] <sil2100> Even two, since one was really short-period, then one longer... but then it all died out
[19:22] <sil2100> So I don't know what's the status of the actual nominations/election
[19:22] <rbasak> Maybe we need to ask the CC to continue driving it
[19:22] <sil2100> Should someone follow up?
[19:22] <sil2100> cyphermox: could you do that?
[19:22] <rbasak> Nominations aren't visible to us until after they've been shortlisted.
[19:22] <cyphermox> yep, I will take care of it
[19:23] <sil2100> #action cyphermox to follow up with the CC regarding the TB nominations and election
[19:23] <meetingology> ACTION: cyphermox to follow up with the CC regarding the TB nominations and election
[19:23] <sil2100> Thanks!
[19:23] <sil2100> Ok, this is all for the action items
[19:23] <sil2100> #topic Definition of our third party repository policy
[19:23] <sil2100> #link Definition of our third party repository policy
[19:24] <sil2100> Argh
[19:24] <sil2100> #link https://docs.google.com/document/d/1apUKR4gtOrfPGCWmtoebaQUhoy-fG8Cyo3VKJyhnpD0/edit
[19:24] <rbasak> I think I've incorporated all feedback into the draft, except for sil2100's suggest on some specifics for snaps which I think we agreed to put into an appendix.
[19:24] <rbasak> Please could you review the draft text in full now? It should be complete now except for polish and any further requested amendments.
[19:24] <rbasak> I'd like to run through the outstanding comments and suggestions and clean them up if you now if we have time for that.
[19:24] <sil2100> Let's just check if we have anything else to take care of
[19:24] <sil2100> No community bugs
[19:24] <sil2100> I suppose also no ML entries?
[19:25] <rbasak> There was the question of the DMB extension/election but I think that's settled now?
[19:26] <rbasak> I don't see any other ML activity
[19:26] <sil2100> Ok, so let's all take a look at the draft now
[19:26] <sil2100> cyphermox, vorlon: ^
[19:27] <vorlon> I'm going to beg off from this; I'm not feeling hot right now and don't think I'm going to be able to give a very good detailed review
[19:27] <rbasak> OK
[19:28] <vorlon> but I have reviewed it fairly recently (in terms of edit history) so hopefully won't have too much more to add
[19:28] <sil2100> vorlon: o/
[19:30] <sil2100> rbasak: ok, so I'm fine with the suggestions that you put on the document
[19:31] <rbasak> Great, thanks! Also I added wording for all the requirements not just the first three.
[19:31] <rbasak> (that's all the blue text
[19:31] <rbasak> )
[19:32] <sil2100> Ok, looking
[19:32] <cyphermox> my only comment would be about not mentioning Flatpaks, etc.; otherwise it's all looking good to me
[19:32] <rbasak> cyphermox: I added a comment on your comment just now
[19:32] <cyphermox> oh, sure, yes
[19:33] <cyphermox> basically, that's in line with what I mean, making it as general as possible
[19:33] <cyphermox> I'm all good then
[19:34] <sil2100> rbasak: this sounds very good. One really minor question (more of a formality) - should we use the 'TB' abbreviation in a formal document here, or better explicitly mention 'Technical Board'? As said, this is basically a minor question
[19:35] <rbasak> OK so what I think I'll do next is remove the notes (they'll be retrievable if needed from version history), leaving only the draft text. I need to add an appendix for snaps as sil2100 suggested. And then I think it'll be ready for wider consultation. I'll need to audit the existing snaps that fall under scope to define an initial list of exceptions.
[19:35] <rbasak> sil2100: agreed. I'll change that.
[19:35] <rbasak> vorlon: shall I give you a few days to look first?
[19:36] <sil2100> rbasak: +1 on that, I really like the overall sound of that
[19:36] <sil2100> Thank you for driving this to completion
[19:36] <rbasak> OK so that's on me to make progress again. Thank you for the feedback!
[19:39] <sil2100> Ok, I guess that's it then
[19:39] <sil2100> #topic AOB
[19:39] <sil2100> Anything else we should discuss?
[19:39] <sil2100> #topic Next chair
[19:40] <sil2100> Ok, so alphabetically after me should be cyphermox , but I think he was chairing the last time
[19:40] <cyphermox> hey, it's all good
[19:40] <sil2100> cyphermox: ok o/ So cyphermox as the chair an rbasak as backup
[19:40] <sil2100> Thanks!
[19:41] <sil2100> Let me update the agenda
[19:41] <sil2100> #endmeeting
[19:41] <meetingology> Meeting ended at 19:41:03 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2022/ubuntu-meeting.2022-05-17-19.09.moin.txt
[19:41] <sil2100> Thank you everyone
[19:41] <cyphermox> thanks sil2100
[19:41] <rbasak> Thank you for chairing!
[19:50] <vorlon> rbasak: I don't think you need to wait for me to re-review before further socializing it. thanks!
[20:09] <rbasak> ack