/srv/irclogs.ubuntu.com/2021/04/20/#ubuntu-meeting.txt

=== mIk3_09 is now known as mIk3_08
=== cpaelzer__ is now known as cpaelzer
=== mIk3_09 is now known as mIk3_08
lunaAny meeting today?14:20
cpaelzerluna: MIR meeting in 8 min , but it will again be a calm and fast one14:22
lunacpaelzer: ah sticking around to look14:25
cpaelzer#startmeeting Weekly Main Inclusion Requests status14:30
meetingologyMeeting started at 14:30:03 UTC.  The chair is cpaelzer.  Information about MeetBot at https://wiki.ubuntu.com/meetingology14:30
meetingologyAvailable commands: action, commands, idea, info, link, nick14:30
cpaelzerhello MIR party people doko ddstreet sarnold didrocks999 jamespage14:30
jamespageo/14:30
ddstreeto/14:30
cpaelzerwelcome to another week that is generally crazy, but likely calm here14:30
cpaelzer#topic Review of previous action items14:30
cpaelzernone14:30
cpaelzer#topic current component mismatches14:30
cpaelzer#link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg14:30
cpaelzer#link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg14:30
didrocks999hey14:30
cpaelzerI spot nothing new in those two lists14:31
cpaelzergoing on14:31
=== didrocks999 is now known as didrocks
cpaelzer#topic New MIRs14: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-mir14:31
cpaelzerempty14:31
cpaelzer#topic Incomplete bugs / questions14: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-mir14:31
cpaelzernothing recent14:31
cpaelzerdidrocks: thanks for last wek promoting the scan case that completed14:31
cpaelzer#topic Any other business?14:32
didrocksyw :)14:32
cpaelzernothing from my side14:32
didrocksnothing for me either14:32
dokoo/14:32
dokoand bye14:32
cpaelzerthe combination of "us being on top of MIRs" plus the "time of the cycle" really shows in these calm weeks14:32
cpaelzer\o/14:32
lunaContinue to test 21.04 RCs and prepare for the release party on Thursday14:32
luna:)14:32
lunao/14:32
cpaelzerthat is the spirit luna14:33
cpaelzerbut then hunt potential RC bugs everyone14:33
cpaelzerenjoy the release week!14:33
cpaelzerquick and easy - thanks everyone14:33
cpaelzer#endmeeting14:33
meetingologyMeeting 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.txt14:33
didrocksthanks everyone14:33
sarnoldgood morning14:34
sarnoldoof. late enough to have missed the whole thing. sorry cpaelzer :(14:35
cpaelzerhehe14:36
cyphermoxo/18:59
rbasako/19:00
sil2100o/19:02
rbasakcyphermox: according to the agenda, you're up :)19:03
cyphermoxuh, I did last week19:03
cyphermoxI mean, before19:03
rbasakSounds like the last chair neglected to update the agenda :-P19:04
sil2100I was guilty of doing the same in the past!19:04
mdeslaur±o19:04
mdeslaur\o19:04
cyphermoxoh boy19:04
cyphermox:P19:04
cyphermoxalrighty then19:04
cyphermox#startmeeting Ubuntu Technical Board19:05
meetingologyMeeting started at 19:05:10 UTC.  The chair is cyphermox.  Information about MeetBot at https://wiki.ubuntu.com/meetingology19:05
meetingologyAvailable commands: action, commands, idea, info, link, nick19:05
cyphermox#chair cyphermox rbasak19:05
meetingologyCurrent chairs: cyphermox, rbasak19:05
cyphermox#topic Apologies19:05
cyphermox(but that means I was not prepared in advance, I will need to go look up things19:05
cyphermoxok, no apologies, apparently19:06
cyphermoxvorlon: you around too?19:06
cyphermox#topic Action review19:07
vorlonhi, sorry I'm late19:07
cyphermoxokay, I got what I need to continue19:08
cyphermox#subtopic rbasak to ask for a status update on ML re: MATE Boutique design review19:08
cyphermoxsup :)19:08
rbasakI did contact Martin, but have had no response.19:08
rbasakI sent another email just now.19:08
rbasakSo carry over please, and I'll keep trying to reach him.19:09
cyphermoxokay, so let's carry on this19: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
vorloncarry over19:09
cyphermox#subtopic vorlon to reply to seeded snap upload permissions question on list19:09
vorloncarry over :/19:09
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 step19:10
cyphermoxFWIW I took a task last meeting to bug vorlon, I did so; but late today...19:10
sil2100Sadly another carry over! It's on my TODO list all the time19:10
cyphermoxok19:10
sil2100I 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
cyphermoxsil2100: asking the same thing I asked vorlon, is it helpful if I try to remind you?19:10
vorlonyeah that's a carry-over also19:11
cyphermoxvorlon: ack19:11
cyphermox#topic Other agenda items19:11
cyphermoxNothing else was on the wiki.19:11
cyphermox#topic Pending mailing list items19:12
cyphermox^there is xnox's request there19:12
vorlonwhich isn't really a TB matter, and I'm mid-draft on a reply :)19:12
rbasakAlso, seb128's request, which I think is a little distinct.19:12
sil2100I wanted to ask abot that actually19:12
vorlonright19:12
cyphermoxrbasak: oh, I missed that one19:12
rbasakI would want to ask the existing team members' opinions.19:12
vorlonI think seb128's post is TB-relevant, and xnox's I'm going to take off list19:12
rbasak(in the first instance)19:12
sil2100Since 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
rbasakSince I think it makes sense for the teams to have say in how they should be run.19:13
xnoxvorlon:  well TB owns the ~ubuntu-archive team & i did CC the three ~ubuntu-archive admins =)19:13
vorlonsil2100: TB has extraordinary power to act on this but normally does not19:13
xnoxi'm guessing sil2100 meant to say that TB has it delegated to the ~ubuntu-archive team admins.19:13
cyphermoxthere's something to be said on making requirements explicit and clear; as well as expectations of the position19:13
xnoxvorlon:  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:14
xnoxand we on the kernel team want to improve that.19:15
cyphermoxwould 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:15
rbasakxnox: 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
vorloncyphermox: who is that question directed to? :)19:16
rbasakTo get some proper cross-team review on decisions19:16
vorlonas an Archive Team admin, this isn't something I'm looking for the tech board to do19:16
cyphermoxvorlon: any relevant person here who is currently on these teams19:16
rbasakvorlon: something I think the TB should do is grease the wheels to get the concern answered though.19:17
cyphermoxvorlon: I don't think it's a TB matter aside from; /maybe/, saying "pls make things clearer for people",19:17
rbasakvorlon: so in the first instance I'd like to hear a response from each of the three teams on that thread.19:17
vorlonrbasak: sure19:17
xnoxrbasak:  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
cyphermoxsomeone to take an action to make sure the responses make it?19:18
xnoxand 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:19
rbasakxnox: 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
rbasakUnfortunately, recently I've been pushed to review more server SRUs than others, and I've been pushing back on that.19:20
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
sil2100I think vorlon mentioned he's in the middle of writing a response, so let's wait on that19:21
sil2100Since as he mentioned, this is more of a ubuntu-archive admin thing than TB19:21
rbasakCan vorlon speak for all three teams?19:21
vorlonto be clear, the response I'm *currently* writing is to xnox, not to seb12819:22
vorlonrbasak: unfortunately yes? :)19:22
sil2100...;)19:22
vorlonbut I will respond to seb128 as well19:22
rbasakLooks like he can :)19:22
xnoxrbasak:  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 tip19:22
xnoxtop conditions. I have never used sru-accept / sru-release tooling, so that side of processing will need coaching.19:22
rbasakxnox: yeah yeah sure. This isn't an interview-xnox meeting :-)19:22
vorlon"versatile experience in many languages" but do you speak Bocce19:22
xnoxrbasak:  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
xnoxvorlon:  Keezx19:23
rbasakxnox: 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:23
mdeslaurvorlon: lol19:24
vorlon:)19:24
xnoxrbasak: 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
rbasakAnyway, so where are we? Defer on vorlon's response representing the three teams? Any other action needed?19:25
cyphermoxvorlon's response with the $team_hat would work for me19:25
mdeslaur+1 from me19:26
cyphermoxdo we need an action or is it already done?19:26
vorlonbest to add an action I think19:27
cyphermoxfair19:27
cyphermox#action vorlon to respond on list to seb128 on ~ubuntu-archive, ~ubuntu-sru team rules19:27
meetingologyACTION: vorlon to respond on list to seb128 on ~ubuntu-archive, ~ubuntu-sru team rules19:27
rbasakAnd ~ubuntu-release?19:27
vorlon^^19:28
cyphermoxsure19:28
cyphermox#action vorlon to respond on list to seb128 on ~ubuntu-archive, ~ubuntu-sru, ~ubuntu-release team rules19:28
meetingologyACTION: vorlon to respond on list to seb128 on ~ubuntu-archive, ~ubuntu-sru, ~ubuntu-release team rules19:28
cyphermox#topic Community bugs19:29
cyphermoxnone.19:29
cyphermox#topic Chair for next meeting19:29
cyphermox#agreed Next chair rbasak, backup would be vorlon.19:29
meetingologyAGREED: Next chair rbasak, backup would be vorlon.19:29
* vorlon nods19:29
cyphermoxand I'll go update the agenda ;)19:29
cyphermox#subtopic AOB19:29
cyphermoxAnything else?19:30
rbasakNothing from me thanks19:30
rbasakAnd thank you for being a good sport and chairing :)19:30
cyphermoxhehe19:30
cyphermox#endmeeting19:31
meetingologyMeeting 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.txt19:31
mdeslaurthanks everyone19:31
sil2100o/19:32

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