/srv/irclogs.ubuntu.com/2024/03/12/#ubuntu-meeting.txt

=== pushkarnk1 is now known as pushkarnk
cpaelzerslyon: didrocks: RM planning makes me unavailable this and next week - would you be around to drive the meeting later?13:42
didrockscpaelzer: as usual, I have a conflict and will not be available13:56
slyoncpaelzer: I can drive it today14:12
slyono/ paelzer is no available today. I'll run the MIR meeting.15:30
slyon#startmeeting Weekly Main Inclusion Requests status15:30
meetingologyMeeting started at 15:30:34 UTC.  The chair is slyon.  Information about MeetBot at https://wiki.ubuntu.com/meetingology15:30
meetingologyAvailable commands: action, commands, idea, info, link, nick15:30
slyonPing for MIR meeting - didrocks joalif slyon sarnold cpaelzer jamespage ( eslerm dviererbe )15:30
slyon#topic current component mismatches15:30
slyonMission: Identify required actions and spread the load among the teams15:30
slyon#link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg15:30
slyon#link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg15:30
joalifo/15:30
sarnoldgood morning15:31
slyonfor c-m: We got trace-cmd seeded while the MIR is not yet fully ready. But It's beeing worked on. I linked the most recent MIRs for libtraceevent and libtracefs this morning15:32
slyonlibtraceevent is making some progress (patch adding tests needs review & sponsoring), libtracefs is stuck currently reaching out for help from the Foundations system squad15:32
slyonc-m-proposed: we have a bunch of new stuff in here..15:33
slyongst-plugins-good1.0 and roc-toolkit are desktop-packages. So I'd like to ask didrocks to investigate those (later on)15:33
slyonjaraco.text and python-openstacksdk are ubuntu-openstack packages, for jamespage to look into.15:34
slyonEverything else seems known/explained15:34
jamespagewill look15:34
slyonthx!15:34
slyon#topic New MIRs15:34
slyonMission: ensure to assign all incoming reviews for fast processing15:34
slyon#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:34
slyonbug #205609915:35
-ubottu:#ubuntu-meeting- Bug 2056099 in tree (Ubuntu) "[MIR] tree" [Undecided, New] https://launchpad.net/bugs/205609915:35
slyonwas this discussed last week? (I wasn't here)15:35
slyonlooks like foundations agreed to own the package. So it could go through MIR review.15:36
sarnoldI think last week we decided to see if foundations would accept it15:36
ahresse_Hello, this has been discussed last year and a owner was missing but foundation is actually willing to take it.15:36
sarnoldand the last comment suggests that they have :)15:36
ahresse_last week*15:36
slyondo we have any volunteers? (I'd like to abstain, as this will be foundations owned)15:36
slyonjoalif or cpaelzer maybe?15:36
joalifslyon: I can take it15:37
slyonthank you!15:37
slyonassigned.15:37
slyon#topic Incomplete bugs / questions15:37
slyonMission: Identify required actions and spread the load among the teams15:37
slyon#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:37
slyonthere are two *trace* updates (bug #2051916 & bug #2051925) that I explained earlier. Nothing actionable for the MIR team, yet.15:39
-ubottu:#ubuntu-meeting- Bug 2051916 in libtraceevent (Ubuntu) "[MIR] promote libtraceevent as a trace-cmd dependency" [Undecided, Incomplete] https://launchpad.net/bugs/205191615:39
-ubottu:#ubuntu-meeting- Bug 2051925 in libtracefs (Ubuntu) "[MIR] promote libtracefs as a trace-cmd dependency" [Undecided, Incomplete] https://launchpad.net/bugs/205192515:39
slyonFinally, bug #205448015:39
-ubottu:#ubuntu-meeting- Bug 2054480 in nbd (Ubuntu) "[MIR] nbd-client" [Undecided, Incomplete] https://launchpad.net/bugs/205448015:39
* slyon reading...15:39
slyonMIR reviewer asked for additional/improved testing. Upstream developers are involved. So this is correctly set to "Incomplete" and back to the reporter for now until resolved.15:40
slyonNothing to do for us15:40
slyon#topic Process/Documentation improvements15:41
slyonMission: Review pending process/documentation pull-requests or issues15:41
slyon#link https://github.com/canonical/ubuntu-mir/pulls15:41
slyon#link https://github.com/canonical/ubuntu-mir/issues15:41
slyonhttps://github.com/canonical/ubuntu-mir/issues/52 which is related to the `tree` MIR above15:42
-ubottu:#ubuntu-meeting- Issue 52 in canonical/ubuntu-mir "Suggested owner should provide a confirmation from the owning team" [Open]15:42
slyonbeing addressed via https://github.com/canonical/ubuntu-mir/pull/5315:42
-ubottu:#ubuntu-meeting- Pull 53 in canonical/ubuntu-mir "Rationale and ownership" [Open]15:42
slyonlet's put our +1 or suggestions for improvement on GitHub, so paelzer can mere once ready15:43
slyonmerge*15:43
slyonThen we have eslerm's https://github.com/canonical/ubuntu-mir/issues/5115:44
-ubottu:#ubuntu-meeting- Issue 51 in canonical/ubuntu-mir "cargo vendor adds unnecessary crates" [Open]15:44
slyonconsensus seems to be adding per-package hacks in debian/rules to delete unnecessary vendored crates. Which was my understanding, too.15:45
slyonThis is not nice, but probably better than shipping (and reviewing) lots of unused code.15:46
slyonI brought the cause up with the Foundations toolchaing squad. They are currently busy, so we should not expect a centralized solution soon. I'll try to push it for next cycle's roadmap, though.15:46
slyonso I guess that it's mostly for didrocks to look into fixing/cleaning up his package manually15:47
slyon#topic MIR related Security Review Queue15:47
slyonMission: Check on progress, do deadlines seem doable?15:47
slyonSome clients can only work with one, some with the other escaping - the URLs point to the same place.15:47
slyon#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
slyon#link https://bugs.launchpad.net/~ubuntu-security/+bugs?field.searchtext=[MIR]&assignee_option=choose&field.assignee=ubuntu-security&field.bug_reporter=&field.bug_commenter=&field.subscriber=ubuntu-mir15:47
slyonInternal link15:47
slyon#link https://warthogs.atlassian.net/jira/software/c/projects/SEC/boards/59415:47
slyonsarnold: what's the security-team's status?15:47
slyonbug #2055434 looks like it needs a `sec-*` tag15:49
-ubottu:#ubuntu-meeting- Bug 2055434 in pemmican (Ubuntu) "[MIR] pemmican" [Undecided, Confirmed] https://launchpad.net/bugs/205543415:49
sarnoldslyon: I belivee that we're still doing alright, but some departures from the team may impact our velocity if we have late additions in the cycle15:49
slyonThe number of new MIRs has been relatively low (or rather balanced before feature freeze) this cycle. Let's hope it stays this way and we don't get a lot of late additions.15:50
sarnoldthere we go, https://warthogs.atlassian.net/browse/SEC-397115:50
slyonsweet thanks!15:50
slyon#topic Any other business?15:51
sarnoldyeah, it's felt very calm .. a little too calm .. *harmonica music*15:51
joalifsarnold: wrt https://warthogs.atlassian.net/browse/SEC-3971 it may not need a sec review after all15:51
sarnoldnone here (well, I've got a very small nagging feeling that I've forgotten something. sigh. but if I can't remember it now...)15:51
slyonjoalif: that's because it's not a root daemon?15:53
sarnoldjoalif: it sounded a bit like it's got a root daemon and a client of some sort, but I couldn't quickly tell if non-root was supposed to be able to use it, etc ..15:53
sarnoldif non-root processes are communicating with a root daemon as part of the task, then it's probably worth a quick look15:53
joalifwell it's not a deamon, and th i spent quite some time if this needs a sec review and decided to play on safe side and put it for sec review15:54
joalifok lemme discuss it with waveform  on the bug and if need be i'll remove it from sec review15:55
slyonthanks joalif!15:55
sarnoldnice, thanks :)15:55
slyonIf nothing else, that's all for today.15:56
joalifnothing else from me15:56
slyonthanks all!15:56
slyon#endmeeting15:56
meetingologyMeeting ended at 15:56:10 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2024/ubuntu-meeting.2024-03-12-15.30.moin.txt15:56
joalifthanks slyon, all:)15:56
sarnoldthanks slyon, all :)15:56
* vorlon waves19:58
amurrayo/19:59
seb128hey20:02
amurrayhey seb12820:02
vorlonamurray: wiki says you're chair?20:02
amurrayah right - yep20:03
amurray#startmeeting Ubuntu Technical Board20:03
meetingologyMeeting started at 20:03:08 UTC.  The chair is amurray.  Information about MeetBot at https://wiki.ubuntu.com/meetingology20:03
meetingologyAvailable commands: action, commands, idea, info, link, nick20:03
amurray#topic Apologies20:03
amurrayrbasak sent his apologies earlier20:03
amurray#topic Action review20:03
amurrayACTION: seb128/amurray/sil2100 to help drafting the snap-store Ubuntu-specific tracks usage20:03
seb128carry over again I guess20:04
amurrayyep20:04
amurray#action seb128/amurray/sil2100 to help drafting the snap-store Ubuntu-specific tracks usage20:04
meetingologyACTION: seb128/amurray/sil2100 to help drafting the snap-store Ubuntu-specific tracks usage20:04
amurrayACTION: seb128 to organize a meeting to unblock the draft of the tracks usage section20:04
seb128rbasak took over this one as we planned to squeeze also that topic in the meeting he is organizing20:05
amurraywill carry-over since we will try again once rbasak is feeling better20:05
seb128which was supposed to be today but got postponed20:05
amurray#action rbasak to organize a meeting to unblock the draft of the tracks usage section20:05
meetingologyACTION: rbasak to organize a meeting to unblock the draft of the tracks usage section20:05
amurraywill carry over rbasak's items then too20:05
amurray#action rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification20:06
meetingologyACTION: rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification20:06
amurray#action rbasak to follow up on finding consensus on question of test plans for third party apps20:06
meetingologyACTION: rbasak to follow up on finding consensus on question of test plans for third party apps20:06
amurray#action rbasak to open wider discussion on third-party repo policy20:06
meetingologyACTION: rbasak to open wider discussion on third-party repo policy20:06
amurrayACTION: seb128 to continue working with SRU, AA, Release, Backporters and Security teams to document their membership process and link to it from https://wiki.ubuntu.com/TechnicalBoard#Team_Delegations20:06
seb128carry over please20:06
amurrayI wanted to ask a quick question on this - I have the process ready for the security team but just wasn't sure where to post it? any ideas? discourse / wiki?20:07
seb128either is fine I think20:07
seb128people seem to prefer discourse nowadays20:08
amurrayok - will go with that then - thanks20:08
amurrayACTION: seb128 to follow-up with ubuntu cinnamon on 24.04 request20:08
seb128great :)20:08
amurrayoops forgot to carry over the other one20:08
amurray#action seb128 to continue working with SRU, AA, Release, Backporters and Security teams to document their membership process and link to it from https://wiki.ubuntu.com/TechnicalBoard#Team_Delegations20:08
meetingologyACTION: seb128 to continue working with SRU, AA, Release, Backporters and Security teams to document their membership process and link to it from https://wiki.ubuntu.com/TechnicalBoard#Team_Delegations20:08
seb128please carry this one also over again but I will handle it tomorrow, feature freeze and proposed stated had been time sinks20:09
amurray#action seb128 to follow-up with ubuntu cinnamon on 24.04 request20:09
meetingologyACTION: seb128 to follow-up with ubuntu cinnamon on 24.04 request20:09
amurrayACTION: vorlon to look into scripting for packages in flavor-specific overlays20:09
vorlonsorry, haven't gotten to this yet20:09
vorlonI guess if we're voting yes on Kubuntu now it's not urgent?20:10
vorlonbut I would still like to keep the action, to do before 24.04, unless someone else wants to learn about this stuff from me and work on it20:10
amurraynot urgent but I would still like to see them finalise their list before the LTS goes out20:10
vorlonindeed20:10
amurrayhmm also should there be an action item on me for the kubuntu LTS request?20:11
amurrayI don20:11
amurray't see anything - will add one20:11
amurray#action amurray to follow-up with kubuntu on 24.04 LTS request20:11
meetingologyACTION: amurray to follow-up with kubuntu on 24.04 LTS request20:11
amurray#topic Scan the mailing list archive for anything we missed (standing item)20:12
amurray#link https://lists.ubuntu.com/archives/technical-board/2024-March/thread.html20:12
amurraynothing new20:12
amurray#topic Check up on community bugs and techboard bugs20:12
amurray#link https://bugs.launchpad.net/ubuntu-community/+bugs?field.assignee=techboard20:12
amurray#link https://bugs.launchpad.net/techboard20:12
amurraynothing here either20:13
amurray#topic Select a chair for the next meeting (next from https://launchpad.net/~techboard/+members)20:13
amurraylooks like its rbasak with seb128 as backup20:13
amurray#agreed next meeting chair: rabask, backup: seb12820:13
meetingologyAGREED: next meeting chair: rabask, backup: seb12820:13
seb128ack20:14
amurray#topic AOB20:14
vorlonone item for AOB20:14
vorlonI noticed when doing a "census" from the Release Team side of our LTS qualifications20:14
vorlonthat Ubuntu MATE doesn't appear to have applied yet for LTS status20:14
vorlondoes someone want to reach out to them and find out if they plan to?20:14
seb128right, that was discussed yesterday during the flavors sync call20:14
vorlon(it's fine if they don't do LTS, of course)20:14
vorlonseb128: oh ok - what's the news?20:15
seb128someone took an action item to reach to Martin to ask20:15
seb128but the few people who had feedback said that the MATE team seems mostly inactive recently20:15
vorlonok20:16
seb128ah, someone was Mauro20:16
vorlonthat's fine then20:16
seb128(just checked the meeting note)20:16
vorlonI just didn't want this to slip by unnoticed20:16
amurraythere is a topic over in their discourse but I don't see anything definitive there20:16
vorlonsince the MATE team's communications preferences seem misaligned with the Release Team's and the Tech Board's these days20:16
amurray#link https://ubuntu-mate.community/t/plans-for-24-04-lts/27110/420:16
seb128amurray, right, I think that one was used as a basis for the claim that the dev team isn't responsive/around much recently20:17
amurrayI'll ask in that thread as well and tag Martin as well20:19
seb128amurray, thanks (and maybe check first with Mauro if he already did since he took an action about it yesterday)20:19
seb128well I mean reaching out to them20:19
seb128though I guess a public post wouldn't hurt in any case20:20
vorlonMartin *did* come to the Ubuntu Summit so it's not entirely moribund?20:20
amurrayyeah I think its fine for the TB to enquire for our own purposes - it would definitely be a shame for MATE to not be part of the LTS20:20
vorlonagain, it's fine if a flavor doesn't want to do LTS support20:20
seb128right, well let's see what they reply20:21
vorlonjust don't want to make sure that's a conscious decision (or the outcome of an assessment of the flavor's capacity), not an accident of timing20:21
vorlons/don't//20:21
amurrayagreed20:21
amurraythanks for raising it vorlon20:21
amurrayanything else?20:22
vorlonnothing else here20:22
seb128nothing from me20:22
amurrayeasy - thanks folks20:22
amurray#endmeeting20:22
meetingologyMeeting ended at 20:22:59 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2024/ubuntu-meeting.2024-03-12-20.03.moin.txt20:22
seb128thanks!20:23
vorlonseb128, amurray: thank you!20:23
amurraylikewise :)20:24

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