sarnoldgood morning15:30
cpaelzerjust a sec15:31
cpaelzernow I'm ready15:32
cpaelzersorry for the delay15:32
cpaelzer#startmeeting Weekly Main Inclusion Requests status15:32
meetingologyMeeting started at 15:32:47 UTC.  The chair is cpaelzer.  Information about MeetBot at https://wiki.ubuntu.com/meetingology15:32
didrocksjust in time after my IRC timed out o/15:32
meetingologyAvailable commands: action, commands, idea, info, link, nick15:32
cpaelzer#topic Review of previous action items15:32
cpaelzerno items other than the reviews assigned to MIR and security team15:33
cpaelzer#topic current component mismatches15:33
cpaelzerMission: Identify required actions and spread the load among the teams15:33
cpaelzer#link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg15:33
cpaelzer#link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg15:33
cpaelzerlet us start with the -release report15:33
cpaelzerI see updates (two weeks ago) on https://bugs.launchpad.net/ubuntu/+source/glade/+bug/196102315:33
ubottuLaunchpad bug 1961023 in glade (Ubuntu) "[MIR] glade" [Undecided, Incomplete]15:33
cpaelzerdidrocks: seb128: does that need further action by you?15:34
didrockslibhandy-1 -> glade: seb128 told me he was going to look at it (false positive, but let’s ensure)15:34
cpaelzerok, let us know if we need to memorize another false positive15:34
cpaelzernothing else new in this list15:34
didrocksyeah, I want us to be sure before claiming this15:34
cpaelzergoing to -proposed now15:34
slyonpython-consul looks new to me15:34
cpaelzeron https://bugs.launchpad.net/ubuntu/+source/python-cheroot/+bug/193011115:34
ubottuLaunchpad bug 1930111 in cherrypy3 (Ubuntu) "[MIR] new dependencies of cherrypy3: jaraco.collections, jaraco.classes, jaraco.text, python-cheroot, python-jaraco.functools, python-tempora, python-portend, zc.lockfile" [Undecided, In Progress]15:34
cpaelzerthere was an update15:35
cpaelzerIMHO this is in wrong state, needs to go back to openstack Team15:35
cpaelzerjamespage: I'll assign you and set incomplete for your awareness15:35
didrocksanother update: libqmi -> libqtrglib. The dep will be dropped soon rather than MIRing, it’s an optional dep that we don’t really need now15:36
sarnoldyay :)15:36
cpaelzerthanks didrocks, I think I have read about this somewhere15:36
cpaelzerso let us ignore libqmi15:36
didrocksand gnome-shell -> libhandy1, I started it but I will need more time to finish it and too much urgent things right now (still aiming before EOW)15:36
cpaelzerbut I hear this is on you and we should not bother about it atm15:37
cpaelzerpython-xmlschema - I have the feeling we had this for a while ...15:37
cpaelzeranother false positive15:37
cpaelzerno no alternative15:38
cpaelzerpython-pysaml2 -> python3-xmlschema seems legit, and by the uploader names on openstack15:38
cpaelzerjamespage: ^^15:38
cpaelzerbug exists and is15:39
ubottuLaunchpad bug 1953363 in python-xmlschema (Ubuntu) "[MIR] python-xmlschema, elementpath, importlib-resources" [High, New]15:39
cpaelzerok so right now this one is actually on security AFAICS15:39
cpaelzerok for me15:39
cpaelzerit is flagged as 22.04 material15:39
cpaelzersarnold: can you check if this is on your list/queue ?15:39
cpaelzeryour teams list I should say?15:39
sarnoldcpaelzer: it is15:39
cpaelzernext case then ...15:40
cpaelzerhttps://bugs.launchpad.net/ubuntu/+source/libadwaita-1/+bug/1962568 is new but already assigned15:40
ubottuLaunchpad bug 1962568 in libadwaita-1 (Ubuntu) "[MIR] libadwaita-1" [Undecided, New]15:40
cpaelzerdidrocks:  is busy these days15:40
cpaelzerbut this one us openstack and not handled yet15:40
didrocksconsider it in a perfect world not be in the list next week :)15:40
cpaelzerhttps://launchpad.net/ubuntu/+source/masakari-monitors -> python-consul15:40
cpaelzerjamespage: ^^15:41
cpaelzerwe  see the new upload held back by this15:41
cpaelzercoreycb: ^^ your upload15:41
cpaelzerthe rest in this list looks known to me15:41
coreycbcpaelzer: thanks, I'll take a look15:41
cpaelzerdidrocks: final check on libreoffice -> epiphany?15:41
cpaelzerIIRC that dep was meant to be dropped15:42
cpaelzeris that task assigned to someone?15:42
didrockscpaelzer: definitively false positive15:42
didrocksthe alternative has firefox as first15:42
didrockswhich is seeded15:42
cpaelzeroh ok - then just keep reminding me until I have learned15:42
cpaelzerthanks in advance15:42
didrocksso another one for the list :/15:42
cpaelzer#topic New MIRs15:42
cpaelzerMission: ensure to assign all incoming reviews for fast processing15:42
slyonwe should have a deny-list at some point..15:42
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-mir15:42
cpaelzerslyon: yeah we all agree15:42
cpaelzerthe first to get to code one has is allowed to skip one review15:43
cpaelzernew MIRs list is empty15:43
didrocksone only? :)15:43
cpaelzer#topic Incomplete bugs / questions15:43
cpaelzerMission: Identify required actions and spread the load among the teams15:43
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-mir15:43
cpaelzersarnold: I have to go by the market, only if no one implements it for one the price increases15:44
sarnoldHODL HODL HODL!15:44
cpaelzerwe have four updates since last week in the list of incompletes15:44
cpaelzerchecking them one by one15:44
ubottuLaunchpad bug 1854362 in ceph-iscsi (Ubuntu) "[MIR] ceph-iscsi, tcmu, python-configshell-fb, python-rtslib-fb, urwid, targetcli-fb" [Undecided, In Progress]15:45
cpaelzerthat is ok, openstack can use this now15:45
cpaelzerI found it forgotten and updated the case, they are aware15:45
cpaelzerto be extra sure coreycb jamespage ^^ FYI15:45
ubottuLaunchpad bug 1963707 in libqrtr-glib (Ubuntu) "[MIR] libqrtr-glib" [Low, Incomplete]15:45
cpaelzerfiled by desktop, related to qmi, which we were told the dependency will be dropped15:45
didrocksdiscussed above, the dep will be dropped as soon as seb128 has a sec15:45
cpaelzerso action15:45
ubottuLaunchpad bug 1957932 in rustc (Ubuntu) "[MIR] rustc, cargo" [Critical, Incomplete]15:46
cpaelzerthat is documentation of what was discussed at the sprint15:46
cpaelzerno action yet15:46
ubottuLaunchpad bug 1930111 in cherrypy3 (Ubuntu) "[MIR] new dependencies of cherrypy3: jaraco.collections, jaraco.classes, jaraco.text, python-cheroot, python-jaraco.functools, python-tempora, python-portend, zc.lockfile" [Undecided, In Progress]15:46
cpaelzerthat was unblocked by security (thanks) and is back on openstack15:47
cpaelzerjamespage: ^^ FYI15:47
cpaelzerI have already updated the case to reflect that15:47
cpaelzer#topic MIR related Security Review Queue15:47
cpaelzerMission: Check on progress, do deadlines seem doable?15:47
cpaelzer#link https://bugs.launchpad.net/~ubuntu-security/+bugs?field.searchtext=%5BMIR%5D&assignee_option=choose&field.assignee=ubuntu-security&field.bug_reporter=&field.bug_commenter=&field.subscriber=ubuntu-mir15:47
sarnoldwe recently finished plocate https://bugs.launchpad.net/ubuntu/+source/plocate/+bug/1960864 -- and glusterfs is in progress https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1950321 -- swtpm is also in-progress of a sort, no progress in the last few days https://bugs.launchpad.net/ubuntu/+source/swtpm/+bug/194874815:48
cpaelzera few are left15:48
ubottuLaunchpad bug 1960864 in Release Notes for Ubuntu "[MIR] plocate" [Undecided, New]15:48
ubottuLaunchpad bug 1950321 in glusterfs (Ubuntu) "[MIR] glusterfs" [Critical, Confirmed]15:48
ubottuLaunchpad bug 1948748 in swtpm (Ubuntu) "[MIR] swtpm" [High, New]15:48
cpaelzeryes sarnold I've seen and updated the bug15:48
cpaelzerthank you15:48
sarnoldglusterfs sounds like it's still pretty gronky code15:48
cpaelzerwhy isn't gluster in this list anymore ?15:48
sarnold'assigned to sbeat tie'15:48
cpaelzeroh reassigned15:49
cpaelzerthe list still shringks every week15:49
* sbeattie is trying to get through it, but it'd help if people'd stop finding security issues in other software.15:49
sbeattieit == glusterfs15:49
cpaelzerso again thank you sarnold and sbeattie and all the reviewer you train up15:49
cpaelzersbeattie: can we stop other people finding other issues somehow?15:49
sarnoldwe can beg people to run coverity and cppcheck and ..  :)15:50
cpaelzerso to sum it up, progress is made on the security reviews, that makes people happy, we still might be able to complete all 22.04 material in time15:50
cpaelzer#topic Any other business?15:50
ubottuLaunchpad bug 1887187 in nftables (Ubuntu) "[MIR] nftables" [Critical, New]15:50
cpaelzerright that is recent as well slyon15:51
slyonjoalif and myself finished the MIR review on that one today15:51
slyonnot sure why it didn't show up in the new MIRs queue15:51
joalifthanks slyon again!15:51
slyonbasically it is back to the security team for security review and a small packaging change (missing .symbols file)15:51
cpaelzerslyon: does it have required todos?15:51
cpaelzeryes it has some15:51
cpaelzerso I'll set incomplete15:52
slyoncpaelzer: yes it does have two small required TODOs15:52
cpaelzerthen it would have shown15:52
slyonthank you15:52
cpaelzerAnd this is on security twice now - for review and for driving the case (IIUC)15:52
sarnold*very* secure15:52
ubottuPull 9 in cpaelzer/ubuntu-mir "RFC: ensure package built in most recent archive test rebuild" [Open]15:53
cpaelzerI updated https://bugs.launchpad.net/ubuntu/+source/nftables/+bug/188718715:53
ubottuLaunchpad bug 1887187 in nftables (Ubuntu) "[MIR] nftables" [Critical, Incomplete]15:53
cpaelzerlet us look at the PR15:53
cpaelzersorry for bug handling not being present sbeattie15:53
cpaelzerreading the case15:53
sbeattieno problem15:53
cpaelzerI'd plus one this suggestion15:54
cpaelzercould we vote on this please, if we are overall +1 I can add it right away15:55
slyon+1, maybe we could suggest doing a local build, too?15:55
sbeattieI'd like to avoid the issue found in the python-cheroot security review, feel free to wordsmith, bikeshed, etc.15:55
didrocks+1 as well15:55
slyonlike running sbuild on the package locally. This would be even newer than the latest archive rebuild15:56
cpaelzerslyon: I can add that as C15:56
cpaelzerthat or a proposed PPA rebuild15:56
cpaelzerthis suggestion is better than nothing, wordsmithing can happen if this ever is a pain to someone15:56
cpaelzerI'd add it right now15:56
slyoncpaelzer: that'd be nice15:56
cpaelzerthat seems to be all we have15:56
cpaelzerok closing then15:57
meetingologyMeeting ended at 15:57:27 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2022/ubuntu-meeting.2022-03-08-15.32.moin.txt15:57
sarnoldthanks cpaelzer, all :)15:57
didrocksthanks everyone!15:57
slyonthanks cpaelzer, all!15:57
joalifthanks all o/15:57
=== chiluk_ is now known as chiluk
sil2100oh, I see cyphermox on the channel \o/ But I guess he might be AFK or busy20:00
cyphermoxnope, I'm there20:00
cyphermoxdouble-booked though20:00
sil2100cyphermox: will you be able to chair in that case? Since I think it's your turn, but rbasak is set as the backup20:01
* vorlon waves20:01
cyphermoxyeah, I should be able to chair20:02
vorloncyphermox: double-booked> I hadn't had a chance to email, would it help you if we changed the meeting time?20:02
cyphermoxnot really, I'll adapt20:02
rbasakDid I fail to update the agenda after the last meeting? Sorry.20:02
rbasakhttps://irclogs.ubuntu.com/2022/02/22/%23ubuntu-meeting.html has the previous log20:03
cyphermoxlet's start?20:03
rbasakhttps://new.ubottu.com/meetingology/logs/ubuntu-meeting/2022/ubuntu-meeting.2022-02-22-20.05.html has the summary20:03
cyphermox#startmeeting Ubuntu Technical Board20:03
meetingologyMeeting started at 20:03:47 UTC.  The chair is cyphermox.  Information about MeetBot at https://wiki.ubuntu.com/meetingology20:03
meetingologyAvailable commands: action, commands, idea, info, link, nick20:03
rbasakI was just looking up previous action items20:03
cyphermox#chairs cyphermox rbasak20:04
rbasakI think everything was carried20:04
rbasakAnd I also had "20:04
rbasak    rbasak will send out the private removal emails20:04
rbasakwhich I've done20:04
cyphermoxthanks :)20:04
cyphermox#topic Action Review20:04
cyphermoxACTION: formal ratification of third party seeded snap security policy, depends on: (rbasak, 19:06)20:05
rbasakI think we were going to collapse this all into the ongoing (pad) discussion on seeded snap requirements, but I failed to update the agenda20:05
cyphermoxso carry?20:08
cyphermoxno longer double-booked.20:09
sil2100I'd say yes20:09
cyphermoxACTION: 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. (rbasak, 19:06)20:09
vorlon(I think at this point it makes sense for the above to be dependent on finalizing the ratification of the policy)20:10
cyphermoxI agree, I'll update the agenda to that effect20:10
cyphermoxACTION: sil2100 to start a draft summarizing the OEM archive portion of the meeting which x-nox and TB will review, edit, and ratify before we move on to figuring out the next step (rbasak, 19:08)20:10
sil2100Yes, so the draft is started, but still not finished!20:10
cyphermoxalright, thanks sil2100 :)20:11
sil2100So carry over please ;)20:11
sil2100(https://wiki.ubuntu.com/OEMArchive for the record)20:11
cyphermoxACTION: Review and leave feedback on the first version of the preamble and three first requirements https://pad.ubuntu.com/third-party-repository-requirements (all of the TB) (sil2100, 20:09)20:11
cyphermoxI had left my feedback months ago20:12
sil2100hmmm, yeah, I didn't leave my comment on the actual preamble20:13
sil2100Well, it's about the formal preamble, that's quite new20:13
cyphermoxI'll re-review for myself too20:13
cyphermoxACTION: Discuss DMB inactivity expiration policy (all of the TB) (sil2100, 20:27)20:13
rbasakcyphermox: yes, but I'd like more feedback please now that I've actually started drafting the proposed final wording after having gathered everyone's opinions20:13
sil2100We were working on the rules themselves, but then rbasak started working on the actual wording - I need to sit down on that20:13
cyphermoxoops sorry20:13
vorlonarewe continuing on using a pad for this, vs perhaps moving it to a google doc?20:13
cyphermox+1 for a Google doc, if we're doing final wording20:14
rbasakI'm happy to move it to a Google Doc if you all think it's worth doing that. I used the pad because I thought it'd be more open, but it turns out to be really hard to use the pad effectively20:14
rbasakOK I'll do that thanks20:14
cyphermoxok, what about the DMB inactivity policy?20:15
cyphermoxand perhaps, TB inactivity, since I was so kind to just disappear for three months myself :/20:15
rbasakThat's resolved for the current situation, but longer term I think the TB needs to decide what to do if the situation recurs20:16
rbasakThat's not urgent though.20:16
cyphermoxshould we discuss it now, or take that back to the mL?20:18
rbasakWe need someone to drive it on the ML :-/20:18
rbasakOr, it gets left until it actually comes up I guess.20:22
cyphermoxalright. that's a drop then, for all intents and purposes20:26
sil2100I still think the retention policy is a good idea20:26
cyphermoxpostpone until it comes up20:26
rbasakFTR, I basically agree with what the DMB wants to do. I think we just need to refine the detail about the interaction between the DMB and the TB to actually do the removal, and communicate with the DMB members being removed, etc.20:27
vorlonsil2100: does that mean you want to drive the discussion on the list?20:27
sil2100vorlon: eh, I'm worried that I have so many DMB + the TB action that it might not be driven to completion20:27
sil2100I would love to, since I think this policy will be helpful20:27
vorlonI agree that it would be helpful but am wary of committing myself to driving it20:28
rbasakI think, given recent events, it would be best if I didn't drive this one.20:28
rbasak(but I will provide input, etc)20:28
sil2100Ok, so maybe please assign it to me and if I can't make it by the next meeting, we'll try finding someone else20:28
sil2100Thanks o/20:31
cyphermox(sil2100) Discuss if the membership to ~ubuntu-archive should be managed by the Technical Board, and if yes: consider new timezone-diverse additions to the team (i.e. bdmurray).20:31
rbasakI thought ~ubuntu-archive managed their own membership, and various existing members were added that way?20:32
sil2100Yeah, I think that's correct, I think the action item is invalid!20:33
cyphermoxerr okay :P20:33
sil2100Sorry about that ;p20:33
cyphermoxmoving on20:33
cyphermoxDefinition of our third party repository policy. See https://lists.ubuntu.com/archives/technical-board/2021-July/002562.html and https://pad.ubuntu.com/third-party-repository-requirements20:33
rbasakTo be clear, if members of ~ubuntu-archive want to change things, then consulting with the TB is probably worthwhile.20:34
rbasakBut unless there's some reason we'd probably leave it as-is20:34
sil2100Sure, but I think that's all up to the ubuntu-archive admins - I think as of right now there is no actions required20:34
rbasakOn the pad, I'll take the action to move it to a Google Doc then, update everyone on the TB with the link and ask for further feedback there.20:36
rbasakI don't think there's anything else on this, except to say that I really want to make progress on this and need to know that you're happy with the direction it's going in since I'll need the final wording to be agreed later.20:37
cyphermox#topic Mailing list review20:39
sil2100Not sure if this is the right moment to bring this up:20:39
cyphermoxthere was only one email there, not sure if it had been actioned yet, DMB allow20:39
sil2100But there was the e-mail from Marc?20:40
sil2100Should we think about starting an election?20:41
cyphermoxyeah, I suppose there is that too20:41
rbasakWe need the CC to do that I think.20:41
vorloncyphermox: do you want to give us a gmail address for you to use for the google doc?  I think that will make comment etc. tracking saner so it's not accidentally "anonymous"20:41
rbasakAt least that's what's happened in the past.20:41
cyphermoxvorlon: I will share it, yes20:41
rbasakUnless you want to do like the DMB and have us run the TB election admin ourselves20:41
sil2100I guess someone will have to take the AI to contact the CC in that case20:42
vorlonhistorically it's been the CC20:42
cyphermoxI will take that action20:42
vorlonI'm doing the best I can to refer election management either up or down so I don't have to do it ;-)20:42
cyphermoxI will contact the CC to trigger the election20:42
rbasakNow that I've done the DMB one twice I've got the process in my head and don't mind doing it. But it'd probably be better if the CC can.20:43
cyphermox#topic Check up on community bugs20:43
cyphermoxthere are no open bugs20:43
cyphermox#topic Select a chair for the next meeting20:43
rbasakOne AOB item please20:43
cyphermoxrbasak, it's your turn next to chair I think?20:44
rbasakI chaired last week! But sure.20:44
rbasakUh, last time - two weeks ago.20:44
cyphermoxunless someone wants to save you20:44
rbasakI don't mind.20:44
cyphermoxif I'm not double-booked I can do it again20:44
cyphermoxokay, moving on20:44
cyphermox#topic AOB20:44
rbasakIs everyone happy with my response on the question of DMB nomination eligibility?20:45
rbasakIt wasn't my intention to speak for the TB but it seems to have been taken that way.20:45
rbasak(I also fail to see how asking the TB for a vote is any different to asking the DMB for a vote in terms of "formality" but there you go)20:46
vorlonI'm trying to skim the mailing list thread quickly, since I don't remember this20:48
rbasakToday on ubuntu-devel@20:48
vorlonthe old one on tech-board20:48
rbasakOh right sorry20:48
vorlongiving the timing I can well understand why I personally didn't reply to it :)20:49
vorlonI agree that ~ubuntu-sru-developers is narrower than what we expect DMB to assess and therefore isn't a good fit20:50
vorlonalso wonder why anyone on the ~ubuntu-sru-developers team who was actually interested in running for DMB wouldn't also just get core-dev first20:50
vorlonI would be fine to vote on this if necessary20:51
sil2100btw. do we have this documented somewhere besides the ML?20:51
sil2100Like, who can actually be nominated for a seat for the DMB20:51
rbasakFollowing that ML post, I put it in my call for nominations20:52
rbasakAdditionally I wrote it up in https://wiki.ubuntu.com/DeveloperMembershipBoard/KnowledgeBase#Running_a_DMB_election - not specifically the rule, but it does link to my call for nomination email as an example to use as a basis.20:53
sil2100Ah, ok!20:53
sil2100Noted ;)20:53
rbasakI can document the rule explicitly there if you think it'd be helpful.20:53
rbasakvorlon: thanks, but also, are you happy with the position that it's for the TB to decide eligbility and not the DMB? That's what ddstreet seems to be complaining about as "all this formality". I don't see any other reasonable option though.20:55
rbasak(and same question to the others)20:55
vorlonrbasak: yes, TB should decide this, not DMB20:57
rbasakDoes anyone on the TB want to support any change to the status quo?20:58
rbasakIf not then I'm done - thank you for clarifying.20:58
sil2100hm, it's hard to say from my POV, I don't have a strong opinion. But I think that since the TB does manage the DMB membership (besides the fact of startin elections), I think it makes sense to assume that the TB is the one setting the base rules20:58
rbasakI wanted to make sure that this is handled openly since I'm dancing a fine line of ensuring that the election is done properly :-/20:58
sil2100But as said, I'm of no strong opinion here20:59
cyphermoxokay, so do we need a vote or do we already have consensus on the topic?21:06
rbasakI don't think anyone has called for a vote here.21:07
rbasakSo I think we're good. Thanks!21:07
rbasakDoes that mean "I'd like to raise something" or "bye"? :)21:08
sil2100...that is a bit confusing, yes! But the latter ;)21:08
cyphermoxalrighty then, any other other business?21:09
meetingologyMeeting ended at 21:09:48 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2022/ubuntu-meeting.2022-03-08-20.03.moin.txt21:09
rbasakThanks all, and cyphermox for chairing!21:10
cyphermoxthanks all o/21:11
sil2100Thanks all! cyphermox thank you for chairing!21:13

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