[15:30] <cpaelzer> o/
[15:31] <cpaelzer> #startmeeting Weekly Main Inclusion Requests status
[15:31] <meetingology> Meeting started at 15:31:09 UTC.  The chair is cpaelzer.  Information about MeetBot at https://wiki.ubuntu.com/meetingology
[15:31] <sarnold> good morning
[15:31] <meetingology> Available commands: action, commands, idea, info, link, nick
[15:31] <doko> o/
[15:31] <cpaelzer> hello doko sarnold didrocks jamespage ddstreet
[15:31] <ddstreet> o/
[15:32] <cpaelzer> let us get this party started
[15:32] <jamespage> o/
[15:32] <cpaelzer> #topic Review of previous action items
[15:32] <cpaelzer> only reviews, but of that a lot
[15:32] <cpaelzer> I've seen ddstreet complete one
[15:32] <cpaelzer> I myself completed a bunch and helped doko
[15:32] <cpaelzer> so let me turn this around - are there MIR review left open that you'd know of?
[15:33] <cpaelzer> I checked before the meeting and only found new cases (to be distributed today) and such assigned to seucrity atm
[15:33] <cpaelzer> let me knwo if you are backlog on a review so we can make sure it is not blocked on us for too long
[15:33] <cpaelzer> you can also reply on that later
[15:33] <cpaelzer> let us go on
[15:33] <cpaelzer> #topic current component mismatches
[15:33] <cpaelzer> #link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg
[15:33] <cpaelzer> smaller than it was as several things resolved
[15:34] <cpaelzer> nothing new in there
[15:34] <cpaelzer> needrestart will later be distrubted for reviews
[15:34] <cpaelzer> all other unapproved but existing MIRs are on security
[15:34] <cpaelzer> #link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg
[15:35] <cpaelzer> diddledan: can https://bugs.launchpad.net/ubuntu/+source/libinih/+bug/1883890 be promoted now?
[15:35] <cpaelzer> sorry, I meant didrocks
[15:35] <diddledan> :-p
[15:35] <didrocks> o/
[15:35] <didrocks> diddledan is used to it :)
[15:35] <didrocks> yes, I just need to update the status
[15:36] <didrocks> ah, I did it, that was a week ago :)
[15:36] <cpaelzer> ok I'll leave this case with you then
[15:36] <didrocks> pending on seb doing the correct upload
[15:36] <cpaelzer> oh I thought that happened already
[15:36] <cpaelzer> but ok
[15:36] <cpaelzer> that is the right way
[15:36] <cpaelzer> #topic New MIRs
[15:36] <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
[15:37] <cpaelzer> that is one bug with 5 dependencies
[15:37] <cpaelzer> each of us pick one to review ?
[15:37] <didrocks> (all perl though, Friday task for sure…)
[15:37] <didrocks> taking the first one libint-perl
[15:38] <cpaelzer> OTOH 4/5 of those are lib*perl which have a quick pass process AFAIK from doko explaining us last time
[15:38] <cpaelzer> yeah me takes the second fin-perl
[15:38] <cpaelzer> find
[15:38] <didrocks> "wooohooo"
[15:38] <cpaelzer> everyone should realize that the last one gets the only complex package
[15:38] <cpaelzer> so volunteer yourself fast :-)
[15:39] <cpaelzer> three mroe to go libmodule-scandeps-perl libsort-naturally-perl and needrestart itself
[15:39] <doko> lib*-perl ;p
[15:39] <didrocks> if I were you, I would avoid anything with *scan* in the name :)
[15:39] <cpaelzer> ok doko is the *perl* pro and got two
[15:39] <cpaelzer> that leaves needrestart for ddstreet or sarnold or jamespage ?
[15:39] <cpaelzer> who has a chance to do this the next few days?
[15:39] <ddstreet> sure, i can take it
[15:40] <cpaelzer> aesome
[15:40] <cpaelzer> +w
[15:40] <cpaelzer> #topic Incomplete bugs / questions
[15:40] <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
[15:41] <cpaelzer> mtd is on security and only shows up here for the dependency tracking
[15:41] <cpaelzer> fixed
[15:41] <cpaelzer> abseil is not to be promoted and sorted out by seb128
[15:41] <cpaelzer> ok for now IMHO
[15:41] <cpaelzer> #topic Any other business?
[15:42] <cpaelzer> didrocks: what became of the voting?
[15:42] <cpaelzer> still many are missing right?
[15:42] <cpaelzer> I've seen activity of most of us here today
[15:42] <didrocks> yeah :/
[15:42] <cpaelzer> what is the summary on votes so far
[15:42] <didrocks> I can reask by email
[15:42] <cpaelzer> sure
[15:43] <cpaelzer> WFM
[15:43] <didrocks> basically, +2 (you and I) based on the according tooling being developed and -1 from doko
[15:43] <didrocks> I told we can invite the requester (seb) to the conversation
[15:43] <didrocks> no answer
[15:43] <didrocks> I feel people being against should discuss with the requester (either during the meeting, but it obviously doesn’t work) or via email
[15:43] <cpaelzer> jamespage: sarnold: ddstreet: anyone of you able to call your vote on this now?
[15:43] <cpaelzer> or do we need to go to mail again?
[15:44] <ddstreet> i can vote now, sure
[15:44] <didrocks> sarnold voted +0 IIRC, but that was off email and without the full rationale, unsure if he would revisit
[15:44] <sarnold> I thin kI'd prefer the email; I voted -1 way back when, but I think I remembered some of the email conversation causing me to lean towards a +1 if there's sufficient changes .. it's been so long, i'd like to reread things
[15:45] <ddstreet> specifically the vote is for 'can a team subscriber wait until after MIR approval before subscribing' right?
[15:45] <didrocks> exactly
[15:45] <didrocks> and one proposal is: "given that we write some tooling for AA to ensure at least one of whitelisted team is subscribed to bugs"
[15:45]  * jamespage reads again
[15:46] <didrocks> (which will help in the cause of demotion -> promotion after a while because it was already in main in the past)
[15:46] <ddstreet> i'm +1 on it, provided there is either tooling or at least a small process doc change to account for the change in process
[15:46] <didrocks> (I don’t think the tooling would be too complex, so better that only relying on doc, which still needs to be updated)
[15:47] <didrocks> that than*
[15:47] <cpaelzer> seems you have a majority already with 3 on "if the tooling exists and process docs update"
[15:47] <cpaelzer> maybe if jamespage has a vote as well this can conclude
[15:48] <jamespage> I'm +1 but concur with cpaelzer esp in his point 2) about the intended team subscribed at least being documented in the MIR
[15:48] <cpaelzer> then it would be on your didrocks to prep and propose the AA-tooling changes - once accepted we can update the MIR docs
[15:48] <didrocks> ack then, so 2 tasks before allowing this change of process: AA-tooling + doc
[15:48] <cpaelzer> and from that point no more us but the AAs would check for the subscription
[15:48] <didrocks> yeah, just the fact that a team will volounteer to be subscribed
[15:48] <cpaelzer> and I'd emphasize in the doc update that there is nothing bad at all if one wants to subscribe early
[15:49] <didrocks> ofc
[15:49] <cpaelzer> just that you no more "have to"
[15:49] <cpaelzer> ok that LGTM now
[15:49] <cpaelzer> anything else?
[15:49] <didrocks> sounds good :)
[15:49] <cpaelzer> didrocks: for auditability would you summarize that as reply to the thread you started?
[15:49] <didrocks> moving to the Go discussion? (another email thread to close)
[15:49] <didrocks> cpaelzer: will do
[15:49] <cpaelzer> Uh you tihnk we will get far with Go today ... ?
[15:49] <didrocks> no, was more some kind of a joke, really :)
[15:50] <sarnold> :)
[15:50] <didrocks> just a gentle reminder if people can contribute to it
[15:50] <cpaelzer> worth a ping yeah
[15:50] <cpaelzer> ok closing for today
[15:50] <cpaelzer> thanks for all your time
[15:50] <cpaelzer> and happy reviewing
[15:50] <didrocks> thanks!
[15:50] <cpaelzer> #endmeeting
[15:50] <meetingology> Meeting ended at 15:50:56 UTC.  Minutes at https://new.ubottu.com/meetingology/logs/ubuntu-meeting/2021/ubuntu-meeting.2021-02-23-15.31.moin.txt
[15:50] <sarnold> thanks cpaelzer, all :)
[15:50] <ddstreet> o/ thanks
[19:57] <sil2100> o/
[19:57] <rbasak> o/
[19:57] <mdeslaur> o/
[20:00] <sil2100> Guess we're missing one more for quorum
[20:00]  * rbasak will hang around for ten minutes
[20:01] <sil2100> Should we still go through the action items anyway, to check if there're updates?
[20:02]  * vorlon waves
[20:03] <vorlon> quorum> there were 3 hands up, doesn't that qualify? :)
[20:03] <vorlon> #startmeeting
[20:03] <meetingology> Meeting started at 20:03:42 UTC.  The chair is vorlon.  Information about MeetBot at https://wiki.ubuntu.com/meetingology
[20:03] <meetingology> Available commands: action, commands, idea, info, link, nick
[20:03] <vorlon> #topic Apologies
[20:04] <vorlon> I don't see any on the mailing list
[20:04] <sil2100> I'd like to apologise for missing the last meeting
[20:04] <vorlon> :)
[20:04] <sil2100> Was uh, a weird week
[20:04] <vorlon> #topic Action review
[20:05] <vorlon> ACTION: Wimpress To follow-up on-list with design review to address MATE Boutique security/consent concerns.
[20:05] <vorlon> Wimpress: ^^ is there anyone else from Ubuntu MATE who could take this up with us?
[20:06] <vorlon> #action Wimpress To follow-up on-list with design review to address MATE Boutique security/consent concerns.
[20:06] <meetingology> ACTION: Wimpress To follow-up on-list with design review to address MATE Boutique security/consent concerns.
[20:06] <vorlon> ACTION: formal ratification of third party seeded snap security policy, depends on:
[20:06] <vorlon> 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.
[20:06] <vorlon> which is carry-over for me
[20:06] <vorlon> #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.
[20:06] <meetingology> 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.
[20:06] <vorlon> ACTION: vorlon to reply to seeded snap upload permissions question on list
[20:06] <vorlon> also carry-over
[20:06] <vorlon> #action vorlon to reply to seeded snap upload permissions question on list
[20:06] <meetingology> ACTION: vorlon to reply to seeded snap upload permissions question on list
[20:06] <vorlon> ACTION: xnox to start a draft summarizing the OEM archive portion of the meeting which vorlon and mdeslaur will review, edit, and ratify before we move on to figuring out the next step ([2/3 subquorum required if one of us slacks, to avoid holding up the process])
[20:07] <vorlon> xnox: ^^ we're still waiting on this from you, can you make some time for it please?
[20:07] <vorlon> ACTION: sil2100 to follow up with xnox about OEM archive documentation
[20:07] <vorlon> sil2100: have you? :)
[20:07] <sil2100> Yes
[20:07] <vorlon> cool - any update from xnox?
[20:08] <sil2100> So I poked xnox about that and well, got what we currently have - but it's not in any discoverable place
[20:08] <sil2100> Basically xnox pointed me at the ML posts:
[20:08] <cyphermox> o/
[20:08] <sil2100> https://lists.ubuntu.com/archives/technical-board/2020-January/002478.html
[20:08] <sil2100> https://lists.ubuntu.com/archives/technical-board/2019-August/002456.html
[20:08] <vorlon> right, a mailing list post is definitely not a draft, so...
[20:09] <sil2100> Now the question is: do we want to make sure this is saved somewhere on a wiki? Maybe we should decide on where this should go?
[20:09] <sil2100> Wiki, discourse?
[20:09] <vorlon> given that this is supposed to be a policy, I think it belongs in the wiki (with all the othesr)
[20:09] <sil2100> I can continue poking xnox or actually taking all that info there and nicely fitting it on a wiki
[20:09] <sil2100> *take
[20:09] <vorlon> sil2100: do you want to take the action of a first draft then?
[20:10] <sil2100> vorlon: yeah, I can o/
[20:10] <vorlon> sweet
[20:10] <vorlon> #action 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
[20:10] <meetingology> ACTION: 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
[20:10] <vorlon> ACTION: mdeslaur to follow up on xnox's track clarification post to the list from 2020-08-12
[20:10] <sil2100> I suppose we don't really have a wiki path for OEM stuff right now, right?
[20:10] <vorlon> mdeslaur: ?
[20:10] <vorlon> sil2100: no, but this is about Ubuntu technical policy, not about "OEM"
[20:11] <mdeslaur> he said the track clarification was already added to the wiki, so it's completed
[20:11] <vorlon> mdeslaur: thanks
[20:11] <sil2100> vorlon: true that o/
[20:11] <vorlon> #done mdeslaur to follow up on xnox's track clarification post to the list from 2020-08-12
[20:12] <vorlon> ACTION: vorlon to update the list for Thunderbird update (https://irclogs.ubuntu.com/2021/01/26/%23ubuntu-meeting.html#t20:22)
[20:12] <vorlon> carry-over, I'll get it done this week I swear
[20:12] <vorlon> #action vorlon to update the list for Thunderbird update (https://irclogs.ubuntu.com/2021/01/26/%23ubuntu-meeting.html#t20:22)
[20:12] <meetingology> ACTION: vorlon to update the list for Thunderbird update (https://irclogs.ubuntu.com/2021/01/26/%23ubuntu-meeting.html#t20:22)
[20:12] <vorlon> ACTION: rbasak to write up proposal for how to do decision documentation for the future
[20:12] <vorlon> rbasak: I think this might be done?
[20:12] <rbasak> I posted that to the list.
[20:12]  * vorlon nods
[20:12] <sil2100> I saw an e-mail sent out, yes
[20:12] <vorlon> #done rbasak to write up proposal for how to do decision documentation for the future
[20:12] <sil2100> rbasak: thanks o/
[20:12] <vorlon> excellent
[20:12] <rbasak> Any feedback or further action from that?
[20:14] <vorlon> none from me
[20:14] <vorlon> no new agenda items on https://wiki.ubuntu.com/TechnicalBoardAgenda, so
[20:14] <vorlon> #topic Scan the mailing list archive for anything we missed (standing item)
[20:14]  * rbasak has one AOB item
[20:15] <vorlon> we were cc:ed on a question from teward to sabdfl; but that's only to keep us in the loop and I don't see any action there https://lists.ubuntu.com/archives/technical-board/2021-February/002543.html
[20:15] <rbasak> Agreed - I asked Thomas and he confirmed no action is expected from the TB at the moment.
[20:16] <vorlon> and Laney asked about documentation of LTS status which sil2100 responded to
[20:16] <vorlon> sil2100: do you think we *should* have a more specific place for documenting LTS status?
[20:16] <vorlon> the release notes are kind of late to be gathering this info
[20:17] <sil2100> hm, we do normally always reach out to flavors beforehand whenever an LTS is being worked on per policy
[20:17] <vorlon> yes, but where does this get documented between the time you reach out to flavors, and the time the release notes start being created?
[20:17] <sil2100> I don't think so, no
[20:19] <sil2100> I'm looking at possible places where this could be actually documented better, I see we had an https://wiki.ubuntu.com/LTS wiki page with some LTS info
[20:19] <sil2100> But anyway, maybe it's enough to just put that info in the release tracking thread whenever an LTS is worked on? Or hm, maybe better, on the release schedule thread?
[20:20] <sil2100> Since on the release schedule threads we already have additional info like when transitions are planned and who is working on which milestone
[20:20] <vorlon> what's the release tracking thread?
[20:20] <sil2100> Like, you know, one of these: https://discourse.ubuntu.com/t/groovy-gorilla-20-10-release-status-tracking/18647
[20:20] <sil2100> Since we're tracking release checklist items there, it's created relatively early
[20:20] <sil2100> But I think maybe the release schedule would be actually a better idea
[20:21] <vorlon> ah
[20:21] <sil2100> Since it fits conceptually as well, since support status means when point releases might be prepared and for who
[20:21] <vorlon> well I think I would leave it up to you whether you think there should be further action here
[20:22] <sil2100> I'll bring it up with the release team and we'll figure something out, but I'm leaning towards the release schedule indeed
[20:22] <sil2100> It's easily discoverable then
[20:23] <vorlon> #action sil2100 to discuss with release team where to document decisions about LTS status of flavors (prior to release notes creation late in cycle)
[20:23] <meetingology> ACTION: sil2100 to discuss with release team where to document decisions about LTS status of flavors (prior to release notes creation late in cycle)
[20:23] <vorlon> #topic Check up on community bugs (standing item)
[20:23] <vorlon> #link https://bugs.launchpad.net/ubuntu-community/+bugs?field.assignee=techboard
[20:23] <vorlon> zaro boogs
[20:23] <vorlon> #aob
[20:23] <vorlon> rbasak: you had something?
[20:23] <vorlon> #topic aob
[20:24] <rbasak> I released the Thunderbird update today to Focal.
[20:24] <rbasak> oSoMoN asked about doing the same for Bionic, but we hadn't discussed that previously.
[20:24] <rbasak> I trust it'll be fine on the same basis as the Focal update, but I thought I'd check.
[20:25] <mdeslaur> I think only one of the problematic packages was in bionic when I checked
[20:25] <vorlon> seems ok, we didn't make any focal-specific decisions there so as long as the revdep situation is similar?
[20:25] <mdeslaur> I believe it's fine for bionic also
[20:25] <rbasak> I haven't checked the rdep situation
[20:25] <vorlon> but I guess you would as part of SRU team due diligence?
[20:25] <rbasak> Yes I'll check
[20:26] <rbasak> How about we approve it on condition the SRU consider the situation effectively the same, and we'll consult the TB if we consider there to be any substantial difference?
[20:26] <vorlon> ok then it seems alright to me; if you find any new wrinkles for bionic we can discuss on list, but otherwise I think it follows from the discussion we already had about focal?
[20:26] <cyphermox> yes
[20:26] <rbasak> +1
[20:27] <rbasak> Thanks
[20:27] <vorlon> excellent
[20:27] <vorlon> #topic Select a chair for the next meeting (next from https://launchpad.net/~techboard/+members)
[20:27] <vorlon> #info next chair will be sil2100, with mdeslaur as backup
[20:27] <mdeslaur> ack
[20:27] <sil2100> o/
[20:27] <vorlon> straightforward :)
[20:27] <vorlon> anything else?
[20:27] <mdeslaur> nope
[20:28] <sil2100> Nothing here
[20:28] <vorlon> #endmeeting
[20:28] <meetingology> Meeting ended at 20:28:07 UTC.  Minutes at https://new.ubottu.com/meetingology/logs/ubuntu-meeting/2021/ubuntu-meeting.2021-02-23-20.03.moin.txt
[20:28] <vorlon> thanks, all!
[20:28] <sil2100> Thanks vorlon, everyone o/
[20:28] <mdeslaur> thanks everyone!
[21:04] <oSoMoN> ah sorry I missed the meeting, thanks rbasak for bringing up the topic of the thunderbird update on bionic
[21:06] <oSoMoN> that sounds like a plan, I'll work closely with Robie to ensure there are no surprises (I don't anticipate any, it should be very similar to the focal update, except that tinyjsd isn't in bionic, only jsunit)