[14:20] <luna> Any meeting today?
[14:22] <cpaelzer> luna: MIR meeting in 8 min , but it will again be a calm and fast one
[14:25] <luna> cpaelzer: ah sticking around to look
[14:30] <cpaelzer> #startmeeting Weekly Main Inclusion Requests status
[14:30] <meetingology> Meeting started at 14:30:03 UTC.  The chair is cpaelzer.  Information about MeetBot at https://wiki.ubuntu.com/meetingology
[14:30] <meetingology> Available commands: action, commands, idea, info, link, nick
[14:30] <cpaelzer> hello MIR party people doko ddstreet sarnold didrocks999 jamespage
[14:30] <jamespage> o/
[14:30] <ddstreet> o/
[14:30] <cpaelzer> welcome to another week that is generally crazy, but likely calm here
[14:30] <cpaelzer> #topic Review of previous action items
[14:30] <cpaelzer> none
[14:30] <cpaelzer> #topic current component mismatches
[14:30] <cpaelzer> #link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg
[14:30] <cpaelzer> #link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg
[14:30] <didrocks999> hey
[14:31] <cpaelzer> I spot nothing new in those two lists
[14:31] <cpaelzer> going on
[14:31] <cpaelzer> #topic New MIRs
[14:31] <cpaelzer> #link https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-date_last_updated&field.status%3Alist=NEW&assignee_option=none&field.assignee=&field.subscriber=ubuntu-mir
[14:31] <cpaelzer> empty
[14:31] <cpaelzer> #topic Incomplete bugs / questions
[14:31] <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:31] <cpaelzer> nothing recent
[14:31] <cpaelzer> didrocks: thanks for last wek promoting the scan case that completed
[14:32] <cpaelzer> #topic Any other business?
[14:32] <didrocks> yw :)
[14:32] <cpaelzer> nothing from my side
[14:32] <didrocks> nothing for me either
[14:32] <doko> o/
[14:32] <doko> and bye
[14:32] <cpaelzer> the combination of "us being on top of MIRs" plus the "time of the cycle" really shows in these calm weeks
[14:32] <cpaelzer> \o/
[14:32] <luna> Continue to test 21.04 RCs and prepare for the release party on Thursday
[14:32] <luna> :)
[14:32] <luna> o/
[14:33] <cpaelzer> that is the spirit luna
[14:33] <cpaelzer> but then hunt potential RC bugs everyone
[14:33] <cpaelzer> enjoy the release week!
[14:33] <cpaelzer> quick and easy - thanks everyone
[14:33] <cpaelzer> #endmeeting
[14:33] <meetingology> Meeting ended at 14:33:46 UTC.  Minutes at https://new.ubottu.com/meetingology/logs/ubuntu-meeting/2021/ubuntu-meeting.2021-04-20-14.30.moin.txt
[14:33] <didrocks> thanks everyone
[14:34] <sarnold> good morning
[14:35] <sarnold> oof. late enough to have missed the whole thing. sorry cpaelzer :(
[14:36] <cpaelzer> hehe
[18:59] <cyphermox> o/
[19:00] <rbasak> o/
[19:02] <sil2100> o/
[19:03] <rbasak> cyphermox: according to the agenda, you're up :)
[19:03] <cyphermox> uh, I did last week
[19:03] <cyphermox> I mean, before
[19:04] <rbasak> Sounds like the last chair neglected to update the agenda :-P
[19:04] <sil2100> I was guilty of doing the same in the past!
[19:04] <mdeslaur> ±o
[19:04] <mdeslaur> \o
[19:04] <cyphermox> oh boy
[19:04] <cyphermox> :P
[19:04] <cyphermox> alrighty then
[19:05] <cyphermox> #startmeeting Ubuntu Technical Board
[19:05] <meetingology> Meeting started at 19:05:10 UTC.  The chair is cyphermox.  Information about MeetBot at https://wiki.ubuntu.com/meetingology
[19:05] <meetingology> Available commands: action, commands, idea, info, link, nick
[19:05] <cyphermox> #chair cyphermox rbasak
[19:05] <meetingology> Current chairs: cyphermox, rbasak
[19:05] <cyphermox> #topic Apologies
[19:05] <cyphermox> (but that means I was not prepared in advance, I will need to go look up things
[19:06] <cyphermox> ok, no apologies, apparently
[19:06] <cyphermox> vorlon: you around too?
[19:07] <cyphermox> #topic Action review
[19:07] <vorlon> hi, sorry I'm late
[19:08] <cyphermox> okay, I got what I need to continue
[19:08] <cyphermox> #subtopic rbasak to ask for a status update on ML re: MATE Boutique design review
[19:08] <cyphermox> sup :)
[19:08] <rbasak> I did contact Martin, but have had no response.
[19:08] <rbasak> I sent another email just now.
[19:09] <rbasak> So carry over please, and I'll keep trying to reach him.
[19:09] <cyphermox> okay, so let's carry on this
[19:09] <cyphermox> #subtopic formal ratification of third party seeded snap security policy, depends on:
[19:09] <cyphermox> #subtopic 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:09] <vorlon> carry over
[19:09] <cyphermox> #subtopic vorlon to reply to seeded snap upload permissions question on list
[19:09] <vorlon> carry over :/
[19:10] <cyphermox> #subtopic sil2100 to start a draft summarizing the OEM archive portion of the meeting which xnox and TB will review, edit, and ratify before we move on to figuring out the next step
[19:10] <cyphermox> FWIW I took a task last meeting to bug vorlon, I did so; but late today...
[19:10] <sil2100> Sadly another carry over! It's on my TODO list all the time
[19:10] <cyphermox> ok
[19:10] <sil2100> I will finally do it!
[19:10] <cyphermox> #subtopic vorlon to update the list for Thunderbird update (https://irclogs.ubuntu.com/2021/01/26/%23ubuntu-meeting.html#t20:22)
[19:10] <cyphermox> sil2100: asking the same thing I asked vorlon, is it helpful if I try to remind you?
[19:11] <vorlon> yeah that's a carry-over also
[19:11] <cyphermox> vorlon: ack
[19:11] <cyphermox> #topic Other agenda items
[19:11] <cyphermox> Nothing else was on the wiki.
[19:12] <cyphermox> #topic Pending mailing list items
[19:12] <cyphermox> ^there is xnox's request there
[19:12] <vorlon> which isn't really a TB matter, and I'm mid-draft on a reply :)
[19:12] <rbasak> Also, seb128's request, which I think is a little distinct.
[19:12] <sil2100> I wanted to ask abot that actually
[19:12] <vorlon> right
[19:12] <cyphermox> rbasak: oh, I missed that one
[19:12] <rbasak> I would want to ask the existing team members' opinions.
[19:12] <vorlon> I think seb128's post is TB-relevant, and xnox's I'm going to take off list
[19:12] <rbasak> (in the first instance)
[19:13] <sil2100> Since what I wrote in the private conversation was my understanding of the situation, but I wanted to know if maybe the TB has some powers over granting AA status?
[19:13] <rbasak> Since I think it makes sense for the teams to have say in how they should be run.
[19:13] <xnox> vorlon:  well TB owns the ~ubuntu-archive team & i did CC the three ~ubuntu-archive admins =)
[19:13] <vorlon> sil2100: TB has extraordinary power to act on this but normally does not
[19:13] <xnox> i'm guessing sil2100 meant to say that TB has it delegated to the ~ubuntu-archive team admins.
[19:13] <cyphermox> there's something to be said on making requirements explicit and clear; as well as expectations of the position
[19:14] <xnox> vorlon:  sil2100: i want to apply to ~ubuntu-sru too. Since ~ubuntu-kernel has too much stuff that needs help on ~ubuntu-sru & ~ubuntu-archive side of things.
[19:15] <xnox> and we on the kernel team want to improve that.
[19:15] <cyphermox> would having a list of volunteers to pick from/consider when these teams are short-staffed help at all, and make it clear that some people expressed interest and may need coaching?
[19:16] <rbasak> xnox: so one idea is that a member of one of these special teams doesn't necessarily join to work on their own team's stuff.
[19:16] <vorlon> cyphermox: who is that question directed to? :)
[19:16] <rbasak> To get some proper cross-team review on decisions
[19:16] <vorlon> as an Archive Team admin, this isn't something I'm looking for the tech board to do
[19:16] <cyphermox> vorlon: any relevant person here who is currently on these teams
[19:17] <rbasak> vorlon: something I think the TB should do is grease the wheels to get the concern answered though.
[19:17] <cyphermox> vorlon: I don't think it's a TB matter aside from; /maybe/, saying "pls make things clearer for people",
[19:17] <rbasak> vorlon: so in the first instance I'd like to hear a response from each of the three teams on that thread.
[19:17] <vorlon> rbasak: sure
[19:18] <xnox> rbasak:  i fully understand that. And i know enough about the make up of the distro, seeds, components, components missmatches / arch missmatches, etc. to handle most AA requests correctly.
[19:18] <cyphermox> someone to take an action to make sure the responses make it?
[19:19] <xnox> and punt things i don't to those who are more experienced and/or seek coaching. (ie. source NEW / binary NEW reviews, which i have never done)
[19:20] <rbasak> xnox: so just to be clear, this is something that for at least ~ubuntu-sru I had heard Adam say multiple times - that to take this example, if you joined ~ubuntu-sru to relieve kernel backlog, you'd do that by reviewing other SRUs, and that'd make others more available to work on kernel SRUs.
[19:20] <rbasak> Unfortunately, recently I've been pushed to review more server SRUs than others, and I've been pushing back on that.
[19:21] <rbasak> (however I don't have involvement with kernel SRUs because I have no idea how they work and haven't been mentored on that side of things at all)
[19:21] <sil2100> I think vorlon mentioned he's in the middle of writing a response, so let's wait on that
[19:21] <sil2100> Since as he mentioned, this is more of a ubuntu-archive admin thing than TB
[19:21] <rbasak> Can vorlon speak for all three teams?
[19:22] <vorlon> to be clear, the response I'm *currently* writing is to xnox, not to seb128
[19:22] <vorlon> rbasak: unfortunately yes? :)
[19:22] <sil2100> ...;)
[19:22] <vorlon> but I will respond to seb128 as well
[19:22] <rbasak> Looks like he can :)
[19:22] <xnox> rbasak:  indeed. I have versatile experience in many languages to review most SRUs too. I have done changes to server packages / openstack stuff / most of universe / toolchains / bootloaders / and things in between. Having submitted many SRUs, I have experience to understand when SRUs are under documented. And have giving review feedback / refused to sponsor SRUs until things were in a tip
[19:22] <xnox> top conditions. I have never used sru-accept / sru-release tooling, so that side of processing will need coaching.
[19:22] <rbasak> xnox: yeah yeah sure. This isn't an interview-xnox meeting :-)
[19:22] <vorlon> "versatile experience in many languages" but do you speak Bocce
[19:23] <xnox> rbasak:  i did contributed to the design of many kernel packaging changes =) and like how the signing is submitted. And has changed/evolved since. *sorry*
[19:23] <xnox> vorlon:  Keezx
[19:23] <rbasak> xnox: hope that didn't come across badly. I just mean that we should agree how to approach this first, without considering any individual candidate.
[19:24] <mdeslaur> vorlon: lol
[19:24] <vorlon> :)
[19:25] <xnox> rbasak: it's a process =) i fully understand that none of that happens overnight. And know the histories of people becoming / growing into these roles.
[19:25] <rbasak> Anyway, so where are we? Defer on vorlon's response representing the three teams? Any other action needed?
[19:25] <cyphermox> vorlon's response with the $team_hat would work for me
[19:26] <mdeslaur> +1 from me
[19:26] <cyphermox> do we need an action or is it already done?
[19:27] <vorlon> best to add an action I think
[19:27] <cyphermox> fair
[19:27] <cyphermox> #action vorlon to respond on list to seb128 on ~ubuntu-archive, ~ubuntu-sru team rules
[19:27] <meetingology> ACTION: vorlon to respond on list to seb128 on ~ubuntu-archive, ~ubuntu-sru team rules
[19:27] <rbasak> And ~ubuntu-release?
[19:28] <vorlon> ^^
[19:28] <cyphermox> sure
[19:28] <cyphermox> #action vorlon to respond on list to seb128 on ~ubuntu-archive, ~ubuntu-sru, ~ubuntu-release team rules
[19:28] <meetingology> ACTION: vorlon to respond on list to seb128 on ~ubuntu-archive, ~ubuntu-sru, ~ubuntu-release team rules
[19:29] <cyphermox> #topic Community bugs
[19:29] <cyphermox> none.
[19:29] <cyphermox> #topic Chair for next meeting
[19:29] <cyphermox> #agreed Next chair rbasak, backup would be vorlon.
[19:29] <meetingology> AGREED: Next chair rbasak, backup would be vorlon.
[19:29]  * vorlon nods
[19:29] <cyphermox> and I'll go update the agenda ;)
[19:29] <cyphermox> #subtopic AOB
[19:30] <cyphermox> Anything else?
[19:30] <rbasak> Nothing from me thanks
[19:30] <rbasak> And thank you for being a good sport and chairing :)
[19:30] <cyphermox> hehe
[19:31] <cyphermox> #endmeeting
[19:31] <meetingology> Meeting ended at 19:31:19 UTC.  Minutes at https://new.ubottu.com/meetingology/logs/ubuntu-meeting/2021/ubuntu-meeting.2021-04-20-19.05.moin.txt
[19:31] <mdeslaur> thanks everyone
[19:32] <sil2100> o/