/srv/irclogs.ubuntu.com/2021/10/12/#ubuntu-meeting.txt

=== ginggs_ is now known as ginggs
* cpaelzer is lighting the MIR campfire14:26
cpaelzerpre-ping sarnold didrocks slyon doko_ ddstreet jamespage14:26
ddstreeto/14:30
cpaelzerhi14:30
cpaelzer#startmeeting Weekly Main Inclusion Requests status14:30
meetingologyMeeting started at 14:30:09 UTC.  The chair is cpaelzer.  Information about MeetBot at https://wiki.ubuntu.com/meetingology14:30
meetingologyAvailable commands: action, commands, idea, info, link, nick14:30
slyono/14:30
cpaelzergiven that it is release week, we'd hope to not have any urgent MIR acticity14:30
cpaelzerbut the one for next cycle might start :-)14:30
cpaelzer#topic Review of previous action items14:30
cpaelzerAs promised I have started the unification of rules/templates on our wiki14:31
cpaelzera first suggestion is available for your review at https://github.com/cpaelzer/ubuntu-mir/pull/214:31
ubottuPull 2 in cpaelzer/ubuntu-mir "Unify rules and templates" [Open]14:31
cpaelzer#topic current component mismatches14:31
cpaelzer#link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg14:31
cpaelzer#link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg14:31
didrocks(hey)14:32
cpaelzerjamespage: with cherrypy3->python-cheroot and python-oslo.metrics not being ready they wont make it in 21.10 as it seems14:32
cpaelzeris that a problem?14:32
cpaelzerNot sure is jamespage is around to see this, as backup pinging coreycb14:33
cpaelzerwe will go on with our agenda, but if there are answers to the above please chime in and let us knows14:34
cpaelzerthe rest of the mismatches looks as-usual no new entries AFAICS14:34
cpaelzer#topic New MIRs14:34
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-mir14:34
cpaelzerThere is one new entry14:34
cpaelzerhttps://bugs.launchpad.net/ubuntu/+source/vulkan-tools/+bug/194635914:34
ubottuLaunchpad bug 1946359 in vulkan-tools (Ubuntu) "[MIR] vulkan-tools" [Undecided, New]14:34
cpaelzeranyone having the cycles to work on that (I'm on PTO soon, then planning sprint; so not me this time :-/ )14:35
coreycbcpaelzer: we need oslo.metrics but we could probably back out to an old oslo.messaging as a last resort. the security team made it through one of the two packages I think.14:35
slyonI can take on that.14:35
cpaelzerthanks slyon14:35
cpaelzerslyon: assigned14:36
cpaelzercoreycb: yes .messaging is done14:36
cpaelzercoreycb: do you know if secruity aware that the deadline for this is essentially days/hours now?14:36
cpaelzersarnold isn't here today14:36
cpaelzerI'd ask you coreycb and jamespage to get in touch with security Team to make sure this is resolved by Impish release14:36
coreycbcpaelzer: yes, I chatted with him last week - I don't think there was a guarantee14:37
coreycbcpaelzer: ok I'll touch base over there14:37
cpaelzerbecause even if you would "back out to an old oslo.messaging" that would still be uploads and migration - and we are in final freeze14:37
cpaelzerthank you coreycb14:37
cpaelzerthis isn't anything the MIR team can help, but we can push you to help youself :-)14:37
cpaelzer#topic Incomplete bugs / questions14:38
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:38
cpaelzerTwo recent updates14:38
cpaelzerhttps://bugs.launchpad.net/ubuntu/+source/opensc/+bug/1892559 seems to be re-started but not yet for us to review14:38
ubottuLaunchpad bug 1892559 in opensc (Ubuntu) "[MIR] ccid opensc pcsc-lite" [Undecided, Incomplete]14:38
cpaelzerAnd https://bugs.launchpad.net/ubuntu/+source/lua5.4/+bug/1909665 also might be 22.04 or later material (to switch to a newer lua verion some day)14:39
ubottuLaunchpad bug 1909665 in lua5.4 (Ubuntu) "[MIR] ibus-libpinyin dependencies" [Low, Incomplete]14:39
cpaelzerbut it doesn't need MIR team attention so far14:39
cpaelzer#topic Any other business?14:39
cpaelzernothing from me except asking again for review of the PR that updates the rules in the wiki14:39
didrocksyeah, will do :)14:39
sarnoldgood morning, sorry I'm late14:40
slyonI will have a look at your PR as well!14:40
slyonNothing else from my side.14:40
cpaelzerhi sarnold14:40
cpaelzernp to be late, but please see the above question on https://bugs.launchpad.net/ubuntu/+source/python-prometheus-client/+bug/194314314:41
ubottuLaunchpad bug 1943143 in python-oslo.metrics (Ubuntu) "[MIR] python-oslo.metrics, python-prometheus-client" [Undecided, In Progress]14:41
cpaelzerslyon: AFAICS that needs to happen more or less "now" since the fallback by the OS team also would take some time14:41
sarnoldcpaelzer: can you repaste the question?14:41
cpaelzersarnold: sure14:41
sarnold(it'll be half an hour or something before the logbot gets to it)14:41
cpaelzerthe package python-prometheus-client still awaits security review14:42
cpaelzerfor the MIR in https://bugs.launchpad.net/ubuntu/+source/python-prometheus-client/+bug/194314314:42
ubottuLaunchpad bug 1943143 in python-oslo.metrics (Ubuntu) "[MIR] python-oslo.metrics, python-prometheus-client" [Undecided, In Progress]14:42
cpaelzerThis is 21.10 material14:42
cpaelzerAnd release is in two days14:42
cpaelzerSo the openstack team (jamespage / coreycb) will need to know asap if this will be reviewed (and be ok)14:42
cpaelzeror if they need to do last minute changes to fall back to an alternative14:43
cpaelzerI guess that summarizes the question14:43
sarnoldcpaelzer: thanks; prometheus_client looks short enough that I can get through it asap...14:44
sarnoldI suggest we continue under the assumption it'll be fine14:44
cpaelzercoreycb: ^^14:44
cpaelzerawesome14:44
cpaelzerif the two of you sarnold + coreycb (jamespage) could sort that out today it could then be promoted tonight/tomorrow14:45
coreycbsarnold: thanks for looking!14:45
cpaelzerok, I guess that covers the "other topics"14:45
cpaelzerI'd close unless there is anything else ???14:45
sarnoldnothing from me14:45
slyonthank you o/14:46
didrocksthanks cpaelzer14:46
cpaelzerFinal FYI next week I'd be on PTO, if someone else could drive this then that would be great.14:46
sarnoldnice, enjoy :)14:46
cpaelzerOr you can all let the archive reopening ruin -proposed and idle a week until things look reasonable :-)14:47
cpaelzer#endmeeting14:47
meetingologyMeeting ended at 14:47:13 UTC.  Minutes at https://new.ubottu.com/meetingology/logs/ubuntu-meeting/2021/ubuntu-meeting.2021-10-12-14.30.moin.txt14:47
sarnoldthanks cpaelzer, all :)14:47
didrocksyeah, I don’t think there is a need for a meeting next week14:47
didrocksother opinions?14:47
cpaelzerThat is the one week I won't care since I'm off :-)14:50
=== genii-core is now known as genii
cyphermoxo/18:57
sarnoldhey cyphermox :)18:58
* vorlon waves18:58
cyphermoxhey sarnold18:59
cyphermoxI'm here, but actually currently doing maintenance in a DC, I might be slow to respond18:59
vorlonI may have failed to update the agenda after last meeting?  Checking chairs19:01
rbasako/19:01
vorlonso sil2100 is primary chair, and he may be buried under the release; mdeslaur is backup but sent regrets19:03
rbasakI can chair19:04
rbasak#startmeeting Technical Board19:04
meetingologyMeeting started at 19:04:53 UTC.  The chair is rbasak.  Information about MeetBot at https://wiki.ubuntu.com/meetingology19:04
meetingologyAvailable commands: action, commands, idea, info, link, nick19:04
rbasak#topic Apologies19:05
rbasak#info mdeslaur sends his apologies19:05
rbasak#info sil2100 may be unavailable due to the imminent Ubuntu release19:05
rbasak#topic Action review19:05
rbasakACTION: rbasak to communicate the TB's MATE resolution to the MATE flavour leads.19:05
rbasakI just did this, and Wimpy said to expect a response in a couple of weeks. Thanks Wimpy!19:06
rbasakACTION: formal ratification of third party seeded snap security policy, depends on:19:06
rbasakACTION: 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:06
vorloncarry-over19:06
rbasak#action formal ratification of third party seeded snap security policy, depends on:19:06
meetingologyACTION: formal ratification of third party seeded snap security policy, depends on:19:06
rbasak#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:06
meetingologyACTION: 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:06
rbasak#action vorlon to reply to seeded snap upload permissions question on list19:06
meetingologyACTION: vorlon to reply to seeded snap upload permissions question on list19:06
vorloncarry-over19:07
rbasak#action vorlon to reply to seeded snap upload permissions question on list19:07
meetingologyACTION: vorlon to reply to seeded snap upload permissions question on list19:07
rbasakFWIW, I'm not sure what that item is referring to exactly19:07
rbasakACTION: 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:07
rbasakI assume we will carry this as sil2100 isn't here.19:08
rbasak#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 step19:08
meetingologyACTION: 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:08
rbasakACTION: all TB members to "vote" or explain what they do not like of a proposal on https://pad.ubuntu.com/third-party-repository-requirements19:08
rbasakDoes everyone consider their input on this complete?19:09
vorlonI see there's an ongoing discussion at the bottom of the document19:10
vorlonI've given feedback on everything up to that point19:10
rbasakI have an answer for the next related action item, so let's carry this I guess.19:10
rbasak#action all members to continue discussion at https://pad.ubuntu.com/third-party-repository-requirements19:11
meetingologyACTION: all members to continue discussion at https://pad.ubuntu.com/third-party-repository-requirements19:11
rbasakACTION: rbasak to draft refined rules for the proposed "stability" requirement for third-party software repositories19:11
sil2100o/19:11
rbasakI just drafted this19:11
rbasako/19:11
rbasakLet me paste it into the pad19:11
sil2100Sorry everyone, got distracted19:11
* vorlon finds it, look for --BEGIN---19:12
vorlonrbasak: thanks.  I think we should take some time to digest this rather than trying to decide on it this meeting (at least, I need time to digest :)19:13
rbasakSure.19:14
rbasakI think the next agenda item will suffice to track the general goal of sorting this out.19:15
rbasak#topic Erich Eickmeyer via the mailing list: DisplayCAL in the archive as a deb that pulls in a Flatpak, and its inclusion in Ubuntu Studio by default. See https://lists.ubuntu.com/archives/technical-board/2021-July/002562.html and https://pad.ubuntu.com/third-party-repository-requirements19:15
rbasakAny specific next steps here? Is everyone happy to continue digesting/feedbacking?19:15
EickmeyerI don't want to crash the meeting, but can I say something about this (got a ping)?19:17
rbasakSure, please do19:18
EickmeyerOk, well, considering the feedback I got from vorlon, I'm willing to drop this and have been working on a snap.19:18
EickmeyerUnfortunately, that has been quite the struggle, so I'm going to be enlisting some help on this.19:18
EickmeyerAt the appropriate time, I hope to make it a seeded snap19:19
sil2100\o/19:19
EickmeyerHowever, I agree that the technicality of being able to include a flatpak of *something* has merit, but I'm no longer pursuing it for this particular application.19:20
rbasakOK. Thank you for the update!19:20
EickmeyerNo problem. I hope that helps. :)19:20
rbasakWhere do we want to go from here then?19:20
sil2100I think it's still good to work out an official policy for such cases19:20
cyphermox+119:21
rbasakShould we archive the current discussion until/unless it's raised again by someone else with a similarly credible request? Or as sil2100 says, should we carry on anyway?19:21
cyphermoxwell, aren't we with the third party repo requirements pad?19:21
vorlonI think archiving it carries the risk of retread the next time it comes up :)19:22
rbasakPersonally I'm in favour of solidifying this anyway, as we are continuing with seeded snaps which would I think be expected to comply with these generic requirements anyway19:22
rbasakOK, so I think we're agreed that we carry on?19:22
sil2100My apologies for not finishing my comments for that one, but I think we should be continuuing, especially that I feel it's 'close' to being all properly defined19:22
rbasak#agreed We will continue working on defining the third party repo requirements even though Eickmeyer has withdrawn his request for the DisplayCAL case, as we think it'd be useful to have anyway19:24
meetingologyAGREED: We will continue working on defining the third party repo requirements even though Eickmeyer has withdrawn his request for the DisplayCAL case, as we think it'd be useful to have anyway19:24
rbasakSo there remains an action item for everyone to continue working on the pad, so I'll leave that there, and I'll adjust the agenda item to make this request generic19:25
sil2100+119:25
rbasakAnything else for this topic for now?19:25
rbasak#topic Scan the mailing list archive for anything we missed (standing item)19:25
rbasak#info No recent communication on the public mailing list19:26
rbasakHowever there was a private communication that needs a response I think, but should probably remain private for now.19:26
rbasakIs there somewhere private the TB can go to discuss this now? Or do we need to use private email or something?19:26
vorlonprivate email is pretty much it19:26
rbasakOK. I'll start that thread after the meeting.19:27
rbasak#topic Check up on community bugs (standing item)19:27
rbasak#info No open community bugs19:27
rbasak#topic Select a chair for the next meeting (next from https://launchpad.net/~techboard/+members)19:27
sil2100Me o/19:27
sil2100Since I was supposed to be chairing today, right?19:28
rbasak#info Next chair will be sil2100 with mdeslaur as backup19:28
rbasakYup, makes sense.19:28
rbasak#endmeeting19:28
meetingologyMeeting ended at 19:28:23 UTC.  Minutes at https://new.ubottu.com/meetingology/logs/ubuntu-meeting/2021/ubuntu-meeting.2021-10-12-19.04.moin.txt19:28
vorlonthanks, all!19:28
sil2100Thank you rbasak for chairing!19:28
sil2100And thanks for the meeting o/19:28

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