[14:22] <didrocks> cpaelzer: hey, I can’t attend the meeting today, but I will read the backlog
[14:29] <cpaelzer> hi
[14:29] <cpaelzer> didrocks: chances are it will be as empty-content as last week (praise the freeze)
[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> sarnold: jamespage: didrocks: ddstreet: doko: ping MIR-party people
[14:30] <ddstreet> o/
[14:31] <sarnold> good morning
[14:31] <cpaelzer> extra ping for jamespage as the only interestign bit seems to be coud archive related
[14:31] <cpaelzer> getting started
[14:31] <cpaelzer> Using the agreed "fast path" of our meeting I anted to let you know that
[14:32] <cpaelzer> action-items, component-mismatches, new MIRs and incomplete MIRs all have no new entries and can be skipped today
[14:32] <cpaelzer> the one thing worth to bring up is
[14:32] <cpaelzer> #topic current component mismatches
[14:32] <cpaelzer> #link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg
[14:32] <doko> o/
[14:33] <cpaelzer> There we see cinder <-> python-boto*
[14:33] <doko> I pinged icey about that last week
[14:34] <icey> doko: cpaelzer: I believe that coreycb uploaded a change to resolve that yesterday
[14:34] <sarnold> https://launchpad.net/ubuntu/+source/cinder/2:18.0.0~b1-0ubuntu2
[14:34] <cpaelzer> https://launchpad.net/ubuntu/+source/cinder/2:18.0.0~b1-0ubuntu2
[14:34] <cpaelzer> ok
[14:35] <cpaelzer> that seems to be on the way to be resolved then
[14:35] <cpaelzer> Which is great
[14:35] <cpaelzer> that leads to
[14:35] <cpaelzer> #topic Any other business?
[14:35] <cpaelzer> so what's up?
[14:35] <doko> one thing
[14:35] <cpaelzer> @sarnold are you planning ahead security reviews in 21.10 cycle or is it to early to bother about that?
[14:35] <cpaelzer> doko: what is it?
[14:36] <sarnold> cpaelzer: heh, we're still working on reviews from N cycles in the past..
[14:36] <doko> I'd like to add a requirement that a package in main must not be on the lto-disabled list, but the fix, or the work-around should be directly in the package
[14:37] <cpaelzer> so you'd want the lto-disable in the package and not in the list
[14:37] <cpaelzer> sounds reasonable to me to enforce maintainer-awareness
[14:37] <cpaelzer> any reasons opinions against that suggestion?
[14:37] <sarnold> what's involved in a maintainer opting into the lto-disable in their package?
[14:38] <cpaelzer> https://wiki.ubuntu.com/ToolChain/LTO
[14:38] <doko> for universe? just uploading a new lto-disabled-list package
[14:38] <cpaelzer> export DEB_BUILD_MAINT_OPTIONS=optimize=-lto
[14:39] <sarnold> nice docs doko :)
[14:40] <doko> so agreed?
[14:41] <sarnold> yeah, I think this is a good idea
[14:41] <cpaelzer> +1 - I'm already writing the text for it
[14:41] <doko> sarnold: I would suggest doing the disablement for hirsute security uploads as well, if you find something that doesn't build/work with lto
[14:41] <sarnold> doko: ack, thanks, I'll pass it along
[14:42] <doko> but filing a bug report would be appreciated
[14:42] <cpaelzer> 3/3 votes for that change
[14:42] <cpaelzer> no more people here and it seems rather non controversial
[14:42] <cpaelzer> adding the change to the wiki ...
[14:43] <doko> ta
[14:44] <cpaelzer> done
[14:44] <cpaelzer> to review template and the explanations
[14:44] <cpaelzer> anything else ?
[14:44] <sarnold> nothing from me
[14:45] <cpaelzer> ok and doko said one (=1) thing which we handled
[14:45] <cpaelzer> closing this early giving you back some time
[14:45] <cpaelzer> thanks @all
[14:45] <cpaelzer> #endmeeting
[14:45] <meetingology> Meeting ended at 14:45:46 UTC.  Minutes at https://new.ubottu.com/meetingology/logs/ubuntu-meeting/2021/ubuntu-meeting.2021-04-06-14.30.moin.txt
[14:45] <sarnold> thanks cpaelzer, doko :)
[18:58] <cyphermox> o/
[19:00] <rbasak> o/
[19:01] <mdeslaur> turns out I'm here after all
[19:01] <mdeslaur> o/
[19:01] <cyphermox> cool
[19:02] <cyphermox> #startmeeting Ubuntu Technical Board
[19:02] <meetingology> Meeting started at 19:02:18 UTC.  The chair is cyphermox.  Information about MeetBot at https://wiki.ubuntu.com/meetingology
[19:02] <meetingology> Available commands: action, commands, idea, info, link, nick
[19:02] <cyphermox> #chair cyphermox rbasak
[19:02] <meetingology> Current chairs: cyphermox, rbasak
[19:02] <cyphermox> #topic Apologies
[19:02] <cyphermox> mdeslaur is here after all.
[19:03] <cyphermox> are we quorate? vorlon?
[19:04] <rbasak> I think we only need three if we ignore sabdfl
[19:04] <cyphermox> right, just checking if we're more anyway :)
[19:04] <cyphermox> #topic Action review
[19:05] <cyphermox> #subtopic Wimpress To follow-up on-list with design review to address MATE Boutique security/consent concerns.
[19:05] <rbasak> o/
[19:05] <rbasak> This action seems to be stuck here forever, seeing as no TB member can action it.
[19:06] <cyphermox> yes
[19:06] <rbasak> Can I suggest that we come up with a plan to move it forward?
[19:06] <cyphermox> well, it's something that blocks a request; so presumably the request can't move forward until that's adressed, and it's probably all on Wimpress's tasks?
[19:07] <cyphermox> or maybe not
[19:07] <cyphermox> in any case, I agree if it can't be actioned, let's drop and/or figure a way to make it go away
[19:07] <cyphermox> rbasak: suggestion?
[19:08] <rbasak> It's not a request; AIUI it's an objection on the basis that current behaviour (or at least, behaviour at the time it was raised) violates Ubuntu policy.
[19:08] <cyphermox> ok
[19:09] <rbasak> So, if the current status isn't acceptable to the TB, the TB presumably needs to either continue coaxing people into fixing it, or, if required, enforce.
[19:09] <rbasak> How about I write to the ML thread asking for a status update?
[19:09] <rbasak> I'll take that action.
[19:09] <cyphermox> ok
[19:09] <rbasak> And then we can go from there.
[19:10] <cyphermox> #action rbasak to ask for a status update on ML re: MATE Boutique design review
[19:10] <meetingology> ACTION: rbasak to ask for a status update on ML re: MATE Boutique design review
[19:10] <cyphermox> sounds good?
[19:10] <rbasak> +1
[19:10] <rbasak> thanks
[19:10] <cyphermox> yw, thanks for taking that action
[19:10] <cyphermox> #subtopic formal ratification of third party seeded snap security policy, depends on:
[19:10] <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:11] <cyphermox> I'm going to guess it's a carry, but similarly, it needs to eventually move
[19:11] <cyphermox> I would take the action to bug vorlon more about it
[19:11] <mdeslaur> heh
[19:12] <cyphermox> similarly;
[19:12] <rbasak> :)
[19:12] <cyphermox> #subtopic vorlon to reply to seeded snap upload permissions question on list
[19:12] <rbasak> It's a little different though, since the buck is with the TB itself on that one.
[19:12] <cyphermox> I would give him one last chance
[19:13] <rbasak> Not that I'm excusing it not being sorted timely, but what we need to do about that is possibly quite different.
[19:14] <cyphermox> yeah, I'm just saying that I'll write down that I'll go bug him some this week and the next about either completing these actions or asking for help/delegating
[19:14] <rbasak> +1, thanks
[19:14] <cyphermox> #action cyphermox to bug vorlon about TB tasks
[19:14] <meetingology> ACTION: cyphermox to bug vorlon about TB tasks
[19:15] <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:15] <cyphermox> sil2100 isn't around it seems, and we haven't seen that summary
[19:16] <cyphermox> so that would probably be a carry unless  I missed something last meeting?
[19:16] <rbasak> Yes, carry I think please.
[19:16] <cyphermox> #subtopic vorlon to update the list for Thunderbird update (https://irclogs.ubuntu.com/2021/01/26/%23ubuntu-meeting.html#t20:22)
[19:17] <cyphermox> I think that's also a carry
[19:17] <rbasak> Yup
[19:17] <cyphermox> #topic Other agenda items
[19:17] <cyphermox> There was nothing else on the wiki
[19:17] <cyphermox> #topic Pending mailing list items
[19:17] <cyphermox> As far as I could tell, we're not missing anything, last messages in mailing list are just meeting absence notifications.
[19:17] <cyphermox> #topic Community bugs
[19:18] <cyphermox> There were no open bugs when I checked about an hour ago
[19:18] <cyphermox> yeah, still the case
[19:18] <cyphermox> #topic Chair for next meeting
[19:19] <cyphermox> #agreed Next chair rbasak, backup would be vorlon.
[19:19] <meetingology> AGREED: Next chair rbasak, backup would be vorlon.
[19:19] <rbasak> ack
[19:19] <cyphermox> Just going by the team members...
[19:19] <cyphermox> #topic AOB?
[19:19] <rbasak> None from me, thanks.
[19:20] <cyphermox> I'm going to apologize for missing last meeting; I did shamefully get mixed up with DST :/
[19:21] <cyphermox> mdeslaur: anything from you?
[19:21] <mdeslaur> nope nothing for me
[19:21] <cyphermox> cool
[19:21] <cyphermox> #endmeeting
[19:21] <meetingology> Meeting ended at 19:21:17 UTC.  Minutes at https://new.ubottu.com/meetingology/logs/ubuntu-meeting/2021/ubuntu-meeting.2021-04-06-19.02.moin.txt
[19:21] <cyphermox> thanks everyone
[19:29] <mdeslaur> thanks cyphermox!
[19:29] <sil2100> o/ I have no idea what's wrong with my internal clock...
[19:30] <sil2100> Apologies for missing the meeting, I feel terrible
[19:31] <mdeslaur> sil2100: no worries