/srv/irclogs.ubuntu.com/2024/04/09/#ubuntu-meeting.txt

=== Droid is now known as Maik
cpaelzersarnold: slyon: eslerm_: joalif: didrocks:  today is the Ubuntu stakeholder meeting to discuss the coming cycle, I won't be able to attend :-/ Could either of you drive the meeting please?10:37
slyoncpaelzer: I can.12:49
cpaelzerthank you slyon12:51
slyon#startmeeting Weekly Main Inclusion Requests status14:29
meetingologyMeeting started at 14:29:08 UTC.  The chair is slyon.  Information about MeetBot at https://wiki.ubuntu.com/meetingology14:29
meetingologyAvailable commands: action, commands, idea, info, link, nick14:29
slyonPing for MIR meeting - didrocks joalif slyon sarnold cpaelzer jamespage ( eslerm dviererbe )14:29
dviererbeo/14:29
slyonStill a bit early. Let's give it a minute or two14:29
slyon#topic current component mismatches14:30
joalifo/14:30
slyonMission: Identify required actions and spread the load among the teams14:30
slyon#link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg14:31
slyon#link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg14:31
slyonThis is looking very good. *bpf* got promoted. *trace* is making nice progress, just pending some work on libtracefs14:31
slyon#topic New MIRs14:31
slyonMission: ensure to assign all incoming reviews for fast processing14:31
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-mir14:32
cpaelzerI managed to be free - hello (keep going slyon and thank you!)14:32
slyonjust bug #2060056 from dviererbe14:32
-ubottu:#ubuntu-meeting- Bug 2060056 in dotnet8 (Ubuntu) "[MIR] dotnet8" [Undecided, New] https://launchpad.net/bugs/206005614:32
slyonjust-in-time cpaelzer :)14:32
slyonI'd like to ask cpaelzer to check this ^ as I think you have the most context.14:32
cpaelzerack on bpf, I resolved that14:32
cpaelzertrace-cmd ack on looking good but needing a bit14:32
slyonIt should be a quick "versioned package" upgrade, I assume. Correct, dviererbe?14:32
dviererbeYes14:33
cpaelzeron dotnet8 I didn't feel there was much open other than asking "do we need a full process again"14:33
cpaelzerreading ...14:33
cpaelzerspoiler: the answer is no - not full again14:33
cpaelzerOh I see, that is the new bug14:33
sarnoldgood morning14:33
cpaelzerI can give this a review tomorrow morning, expect this to be 99% a yes14:33
dviererbeThanks! :)14:34
slyoncool, thanks!14:34
slyonassigned14:34
slyon#topic Incomplete bugs / questions14:34
slyonMission: Identify required actions and spread the load among the teams14:34
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-mir14:34
cpaelzerso many recent updates14:36
cpaelzershould we go top to bottom?14:36
slyonok. bug #200451614:36
-ubottu:#ubuntu-meeting- Bug 2004516 in libyuv (Ubuntu) "[MIR] libyuv (transitive dependency of libheif)" [Undecided, Incomplete] https://launchpad.net/bugs/200451614:36
cpaelzerok, that says escalate to have a chance14:36
cpaelzerwhich I think is reasonable14:36
slyonThis is blocked on security-review. but it's too late. I think it's not high priority and not necessarily needed for 24.04. So probably no need for escalation. I'll double check with ravikant_14:37
slyonbug #205192514:37
cpaelzeryes14:37
-ubottu:#ubuntu-meeting- Bug 2051925 in libtracefs (Ubuntu) "[MIR] promote libtracefs as a trace-cmd dependency" [Undecided, Incomplete] https://launchpad.net/bugs/205192514:37
cpaelzerand update the case either way14:37
slyonwill do14:37
cpaelzerpart of the bigger "perf tools for ubuntu by default" movement14:37
cpaelzer"I'm working on this and mostly finishing the changes." sounds good14:38
slyonright. that should be the last missing piece for trace-cmd14:38
cpaelzerok, wait for the final update14:38
slyonbug #200444914:38
-ubottu:#ubuntu-meeting- Bug 2004449 in libde265 (Ubuntu) "[MIR] libde265 (dependency of libheif)" [Undecided, Incomplete] https://launchpad.net/bugs/200444914:38
slyoncpaelzer: you were the original reviewer. This is part of the libgd2 -> libheif -> ... chain, which is moving closer to completion14:38
cpaelzersame as libyuv - although I'd love to have that in next LTS14:38
slyonVladimir told me he did the work on this in Debian an it's sync'ed, can you double-check the requirements, cpaelzer ?14:39
cpaelzeroh no, security has passed that already14:39
cpaelzeryeah I can check against my requests from the review14:39
slyonthanks14:39
sarnoldcan this move forward if libyuv doesn't?14:39
slyonno it can't14:39
slyonwell... it could probably, but doesn't make a lot of sense I think14:40
cpaelzerwell,  libde265 could - but there is no point for the final use case without the other14:40
adrienfor libtracefs, I think I'm only left waiting on test results (I think I triggered the tests too early and it didn't pick the version in the PPA sadly)14:40
slyonexactly14:40
slyonthanks adrien! please re-ping the MIR bug once it's ready14:41
slyonbug #197761414:41
-ubottu:#ubuntu-meeting- Bug 1977614 in fdk-aac-free (Ubuntu) "[MIR] fdk-aac-free" [Undecided, Incomplete] https://launchpad.net/bugs/197761414:41
adriensure14:41
slyontracking update from security team. Nothing to do for us14:41
cpaelzerack14:41
slyonbug #205819214:41
-ubottu:#ubuntu-meeting- Bug 2058192 in OEM Priority Project "[MIR][needs-packaging] lenovo-wwan-unlock" [Undecided, Confirmed] https://launchpad.net/bugs/205819214:41
cpaelzernot yet ready14:41
slyonack14:42
slyonbug #205448014:42
-ubottu:#ubuntu-meeting- Bug 2054480 in nbd (Ubuntu) "[MIR] nbd-client" [Undecided, Incomplete] https://launchpad.net/bugs/205448014:42
slyonthis is a case of "to re-review security" or "not to re-review security"14:43
cpaelzer+1 vote on should-be-reviewed14:43
slyonIt would be useful, but we're past the point where we can make it happen for 24.04 I assume? I'll double-check with waveform to see how critical this is14:43
cpaelzeror is this "needs to be in noble in main asap" panic (still review but later then)?14:43
slyonI'll try to find out14:44
cpaelzerand if you need it14:44
cpaelzergo the "escalate with security" path14:44
waveformslyon, it's one of the items on my roadmap but it's not going to "break the image" if it has to go red14:44
cpaelzerSee the update by Seth on the other bug14:44
cpaelzerif you (and mclemenceau_) think we should have it14:44
cpaelzerescalate it now14:44
cpaelzerand we might14:44
cpaelzerwaveform: can this be "added to main later" ?14:45
cpaelzerwe have done component moves after the release, that isn't impossible14:45
cpaelzerso could it be ready for 24.04.1 ?14:45
waveformwell, the idea of including it in the image was to enable netboot of the release image, so if we add it to main later it'll only really benefit .1 onwards14:45
cpaelzeror is - after that is approved - a "major revamp how everything works" needed?14:45
cpaelzerI'm mostly, is this a "safe addition" later or is this "to be used break the world" change14:46
cpaelzerif it is the former, we can make it happen toward 24.04.1 and that should be our goal then IMHO14:46
waveformoh, safe addition -- it's basically just enabling the initramfs to support nbd boot (assuming the necessary kernel param is present)14:46
cpaelzerok, how about that - not giving up on the item but timing it towards that?14:46
eslerm_o/14:46
sarnoldgiven that this package had been in main itself, it's 'just'a binary package move, and I don't recall seeing it as a source of work, and that the attack surface is largely in the kernel, I think I'd encourage this to go to main in time for 24.04 release14:46
cpaelzerupdate the bug in that case and security can review without panic-priority14:47
waveformI'm fine with that (enabling for .1)14:47
adrienI do have a question for libtracefs btw: I've addressed comments; does the MIR team still needs to be involved or could a regular review before upload do it? (sorry to come back late to this)14:47
cpaelzersarnold: sure, if you consider this a quick security review - let us make the change for 24.0414:47
cpaelzerI'm sure waveform will be happy14:47
waveformI would love it to go into 24.04 but if it has to be shunted, I'm okay with that too14:47
cpaelzerhow about this - sarnold spends 20 minutes, and gives a shallow security review based on this being in main in the past kind of alreay14:47
cpaelzerif that outcome is good, get it into 24.0414:48
sarnoldwfm14:48
cpaelzerif not, see former plan for 24.04.114:48
cpaelzergreat14:48
waveformsure14:48
slyonvery nice! thanks14:48
cpaelzerwaveform: sarnold: work together and make my Pi NBD boot!14:48
sarnold:D14:48
waveformo714:48
slyonI guess that's all for MIR updates. dbus-broker is stuck for now and needs some additional (upstream) work14:48
slyon#topic Process/Documentation improvements14:49
slyonMission: Review pending process/documentation pull-requests or issues14:49
slyon#link https://github.com/canonical/ubuntu-mir/pulls14:49
slyon#link https://github.com/canonical/ubuntu-mir/issues14:49
slyonno updates as of last week AFAICT14:49
slyon#topic MIR related Security Review Queue14:49
slyonMission: Check on progress, do deadlines seem doable?14:49
slyonSome clients can only work with one, some with the other escaping - the URLs point to the same place.14:49
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-mir14:49
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-mir14:49
slyonInternal link14:49
slyon#link https://warthogs.atlassian.net/jira/software/c/projects/SEC/boards/59414:49
cpaelzerno more looks front-loaded which is good given the time we are in the cycle14:50
slyonbug #2004516 was discussed above and should not get a sec-* tag for now14:50
-ubottu:#ubuntu-meeting- Bug 2004516 in libyuv (Ubuntu) "[MIR] libyuv (transitive dependency of libheif)" [Undecided, Incomplete] https://launchpad.net/bugs/200451614:50
cpaelzerslyon: it should14:50
slyonbug #2060035 is targeted for 24.04.114:51
-ubottu:#ubuntu-meeting- Bug 2060035 in msgraph (Ubuntu) "[MIR] msgraph" [Undecided, Confirmed] https://launchpad.net/bugs/206003514:51
cpaelzerjust not an urgent one14:51
slyonwfm14:51
cpaelzerBTW - I know we all feel pressure atm, please all remember how bad this often was in the past, and be happy. Then take a breath and thank security for making it happen!14:51
sarnold<314:51
eslerm_<314:51
cpaelzerthanks sarnold and eslerm_ - pass the thanks to all that helped please14:51
slyonYes.. we have enough fires in other places this cycle :)14:51
* slyon looking at t64 & xz14:51
cpaelzeroh so true slyon14:51
sarnoldyes14:51
slyonsarnold: eslerm_: OK so can we get msgraph and libyuv imported in Jira?14:52
eslerm_can do14:52
slyonfor non-urgent processing14:52
slyon#topic Any other business?14:53
dviererbeA follow up question to the dotnet6 MIR: Do I need to find an Archive Admin to do the promotion or will someone take care of this eventually before 24.04 GA?14:53
slyonadrien: can you please repeat your question from above?14:53
slyondviererbe: AAs usually pick it up from the report, once the MIR status is "Fix Committed"14:53
slyonand it is seeded/pulled as a dependency14:54
sarnolddviererbe: the last comment from cpaelzer is "ready for you to change seeds" -- do know if this step has been done yet?14:54
cpaelzerI do not see it in component mismatches14:54
slyonneither do I14:54
dviererbeNo, I don't think so14:54
mirespaceo/ for the DMARC perl, do you need anything from me to decide about libmime-tools vs libemail-mime ?14:55
cpaelzerHi mirespace -  who are you asking in particular?14:55
cpaelzersecurity, MIR in general, ... ?14:55
slyonmirespace: did you see this update? https://github.com/rjbs/Email-MIME/issues/66#issuecomment-2024085120 (cc eslerm_)14:55
-ubottu:#ubuntu-meeting- Issue 66 in rjbs/Email-MIME "DoS on excessive or deeply nested parts" [Open]14:55
cpaelzerthere is so much context that sadly left my memory14:55
adrienslyon: my question is whether the MIR team expects to have further MIR-specific comments for libtracefs or if any uploader/reviewer could check the open items effectively14:55
cpaelzerdviererbe: for your case, do you know what is expected from you to change seeds for this?14:56
mirespace_checking that link_14:56
dviererbecpaelzer: not really, I have never done this so far14:56
adrienI've been addressing all the open comments and I'm almost done (it looks like something still isn't ready but it shouldn't take much longer)14:56
cpaelzerdviererbe: and you can be bold, and do it for dotnet6 and dotnet8 (for noble) to make them supported (but do not pre-install them anywhere)14:56
slyonadrien: you get the upload done and then a MIR team member needs to approve the bug report by changing to the relevant status14:56
cpaelzerslyon: can you teach dviererbe or organize that someone else does?14:56
cpaelzerfoundations internal I mean14:57
slyonsure dviererbe. I can help with that. please reach out to me on MM14:57
adrienslyon: hmmm, right, the question is mostly moot indeed14:57
dviererbeslyon: ack14:57
cpaelzeradrien: once you think it is ready, update the case. And for urgency get in touch with me or slyon (to not wait for next Tue)14:57
mirespace:O ... so the MIME DoS issue is not toatally resolved...14:57
adriencpaelzer: thanks14:57
mirespacecpaelzer: I was worried that the debate between mime-tools and email-mime could make the MIR being stuck14:58
eslerm_I would like to see rjbs/Email-MIME in 24.04, the upstream devs do great work at fastmail14:59
cpaelzerI'm worried as well, but too far from it to have a good understanding atm14:59
slyonmirespace: can you remind us of the LP bug number?14:59
slyonit didn't show up in today's lists14:59
cpaelzeralso collision and I need to leave for the next meeting14:59
cpaelzerslyon: it is an older incomplete somewhere14:59
mirespacehttps://bugs.launchpad.net/ubuntu/+source/libmail-dmarc-perl/+bug/202397114:59
-ubottu:#ubuntu-meeting- Launchpad bug 2023971 in libmail-dmarc-perl (Ubuntu) "[MIR] libmail-dmarc-perl" [High, In Progress]14:59
slyoncpaelzer: I have one question for you, regarding libgoa-* depdency14:59
slyoncpaelzer: see https://bugs.launchpad.net/ubuntu/+source/msgraph/+bug/2060035 (you can reply on that bug later)15:00
-ubottu:#ubuntu-meeting- Launchpad bug 2060035 in msgraph (Ubuntu) "[MIR] msgraph" [Undecided, Confirmed]15:00
slyonNot sure what to do about the libgoa-* dependency or why we check for it during the MIR review. It's been there for historical reasons. But we need it in this case15:00
cpaelzereslerm_: to what extend it rjibs/Email-MIME and similar good wishes for the future but no blockers for now15:01
cpaelzerafter all time for 24.04 runs out and I understand mirespace getting concerned15:01
cpaelzermirespace:  what are the options we have there15:01
cpaelzeris it:15:01
eslerm_libmail-dmarc-perl does have an ack, the open issue needs to be solved, but *might* not be a blocker (Seth?)15:01
cpaelzerI fail to summarize it :-/15:02
mclemenceau_thanks cpaelzer sarnold, I'm ok with the plan w.r.t netboot with a preference for addition in 24.04 :)15:02
eslerm_I don't mind contacting upstream and asking if they can make a plan15:02
mirespaceuse the change we did to use libmime-tools-perl, diverging from upstream15:02
cpaelzerok, consider ^^ option (a)15:02
cpaelzerwhat is option (b)15:03
cpaelzerslyon: for libgoa - it can be a build dependency, just not a runtime dependency (and not part of the final code, no static linking tricks)15:03
mirespaceif (a) is libemail-mime contacting upstream, option (b)is  use libmime-tools, diverging upstream15:03
slyoncpaelzer: ACK. thanks I'll update the case15:04
cpaelzerslyon: but if it is used at build to get stuff done (like test tools, binary mangling helpers, ...) then it does not need to be in main15:04
sarnold(or 'it's not a library it's just a .h file tricks :)15:04
cpaelzerslyon: >Trusty, before it had to be15:04
cpaelzersarnold: yes, that I count as "static code active in the final binary" which would need to be in main15:04
cpaelzersarnold: just as much as any other similar trick15:05
cpaelzerback to mime15:05
cpaelzereslerm_: mirespace: what is the way forward15:05
cpaelzereslerm_: you said the open issue might (tm) not be a blocker15:05
slyonlibgoa being gnome-online-accounts, right? I.e. https://packages.ubuntu.com/noble/libgoa-1.0-0b15:05
cpaelzerjust an important "we want to work thazt out in the long run"15:05
cpaelzerif it is really that, can we go on with the promotion of that stack then?15:06
cpaelzeras-is I mean15:06
mirespacethe promotion form my PPA uses libmime-tools by the moment15:06
eslerm_since these are ack'd I am okay with pushing through if Seth agrees. If so, I can contact upstream and try to settle issues.15:06
mirespacebecause emailñ-mime introduced duplicity15:06
cpaelzersounds like a good plan compromise, unblock now, do not give up on making it better15:07
cpaelzerand thanks for the offer to contact upstream15:07
sarnoldI'm a bit worried that comment #27 on https://bugs.launchpad.net/ubuntu/+source/libmail-dmarc-perl/+bug/2023971 suggests that there's even MORE packages to MIR in order to "just ship what debian ships"15:07
-ubottu:#ubuntu-meeting- Launchpad bug 2023971 in libmail-dmarc-perl (Ubuntu) "[MIR] libmail-dmarc-perl" [High, Incomplete]15:07
eslerm_(I'll message upstream today)15:07
sarnoldbut I have to admit that this is a twisty maze of package names that all collide into one single mental hashbucket and I've long ago lost the plot15:07
cpaelzersarnold: well, we can slowly sort that out one by one >24.0415:07
cpaelzerthe question is can we take the current approved set for 24.04 and resolve it here?15:08
cpaelzerif yes, then I'd ask mirespace to work with bryce to prepare the seed/dependency changes and prepare a session telling me what would need to be promoted and why. I could check one by one - if all good mass promotion15:09
cpaelzermirespace: will work on several follow up items anyway, like the elliptic curve lib wrapper and such15:09
mirespacefor me it's ok15:10
slyon+115:11
cpaelzerso to summarize, eslerm_ contacts upstreams for a better path forward. mirespace will prep and lay out what we have ready and can land for 24.0415:12
cpaelzershort: get what we have to noble, mid term make it better15:12
eslerm_I can do that :)15:12
mirespacesounds like a plan :)15:13
cpaelzermirespace: can you work with bryce to get all in line (probably some blocks by the beta freeze) and then get in touch15:13
cpaelzerit is work, but better than the unclear state before15:13
cpaelzerok, we are way over time15:13
mirespaceyes, I do.. thank you all for unblocking this15:13
cpaelzerslyon: time to get to the end :-) ?15:13
sarnoldi'm probably not going to come to a good udnerstanding of the whole problem space and the options quickly .. so here's a few of my general thoughts: (a) I'd prefer to not diverge from debian and the upstreams if we can (b) i'm fine with shipping mirespace's "lets change packages to meet our existing main requirements" but I'm not wedded to it (c) I'm not too worried about a 1 meg --> 2 gigs of ram15:13
sarnoldDOS, that'd probably be tolerable enough to fix post-release if upstream doesn't get to it sooner15:13
sarnold(doesn't every mail server have 100 gigs ram? :)15:14
cpaelzeralmost15:14
slyonthanks for the summary!15:14
cpaelzeror 640k15:14
sarnold:D15:14
slyondo we have anything else?15:14
slyon#endmeeting15:14
meetingologyMeeting ended at 15:14:55 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2024/ubuntu-meeting.2024-04-09-14.29.moin.txt15:14
cpaelzerexhaustion everywhere15:14
cpaelzerthank you all15:15
sarnoldnothing from me besidews thanks to everyone :)15:15
slyonoops, too quick :)15:15
cpaelzerhehe15:15
slyonanway, thanks all!15:15
eslerm_thanks all o/15:15
mirespacethanks all o/15:15
dviererbeThanks everyone! o/15:15
=== JanC is now known as Guest3202
=== JanC_ is now known as JanC
amurrayo/18:59
rbasako/19:00
* vorlon waves19:00
seb128hey19:01
vorlonseb128: hi! I believe you're on for chairing19:01
seb128yes, sorry for being late!19:01
seb128#startmeeting19:02
meetingologyMeeting started at 19:02:26 UTC.  The chair is seb128.  Information about MeetBot at https://wiki.ubuntu.com/meetingology19:02
meetingologyAvailable commands: action, commands, idea, info, link, nick19:02
seb128#topic Apologies19:02
amurrayapologies folks but I have a hard stop in 30 mins so I may have to drop early19:02
seb128k, let's try to keep going, no apologies for this meeting I can see19:03
seb128#topic Action review19:03
seb128ACTION: rbasak to update third party repo draft with outcomes from our recent out-of-band meeting19:03
rbasakI've made progress on this...19:03
amurrayit looks really good rbasak, thanks for that19:04
rbasakThe doc is updated. Could all TB members please check what I've updated (highlighted in green), and raise any comments within a week?19:04
seb128+119:04
rbasakThis time next week I'll publish the initial consultation to Discourse for Ubuntu developers at large.19:04
vorlonyes19:04
rbasakThanks amurray!19:04
rbasakFTR, I intend to edit heavily to clean up the documentation generally, resolve outstanding Google Doc comments, etc. But I don't intend to change anything substantial at this stage.19:05
rbasak(nothing about intent, I mean)19:05
seb128#action everyone to review the third party repo draft within a week and raise any comments they have, after that Robie will post to discourse19:06
meetingologyACTION: everyone to review the third party repo draft within a week and raise any comments they have, after that Robie will post to discourse19:06
rbasakGreat. Thanks!19:06
seb128ACTION: rbasak to open wider discussion on third-party repo policy19:06
seb128I guess that's what is happening in a week so carrying over?19:06
rbasakYep19:06
rbasakSo carry over that one please19:06
seb128#action rbasak to open wider discussion on third-party repo policy19:06
meetingologyACTION: rbasak to open wider discussion on third-party repo policy19:06
rbasakNearly there!19:06
seb128ACTION: rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification19:07
rbasakCarry over my DMB action please19:07
seb128#action rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification19:07
meetingologyACTION: rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification19:07
seb128ACTION: vorlon to look into scripting for packages in flavor-specific overlays19:07
vorlonstill outstanding sorry19:07
seb128#action vorlon to look into scripting for packages in flavor-specific overlays19:07
meetingologyACTION: vorlon to look into scripting for packages in flavor-specific overlays19:07
rbasakI also need to get the DMB election going19:07
seb128do you want an action item for that?19:07
rbasakSure19:07
seb128#action rbasak to get the DMB election going19:08
meetingologyACTION: rbasak to get the DMB election going19:08
seb128ACTION: 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_Delegations19:08
seb128still carrying that one over19:08
seb128#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_Delegations19: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_Delegations19:08
seb128#topic Scan the mailing list archive for anything we missed (standing item)19:08
seb128there is https://lists.ubuntu.com/archives/technical-board/2024-March/002913.html but that doesn't really seem to be a TB topic19:09
teward*raises hand briefly*19:09
seb128teward, yes?19:09
tewardregarding that, there was one sent to the CC and other teams as well as Canonical's teams.19:10
tewardCC hasn't addressed it yet, but Canonical (Fallen, etc.) were starting to investigate best approaches19:10
tewardjust wanted to have that on the record.19:10
teward(expected it to show up here)19:10
rbasakIt sounds like something the nearest Loco could take up perhaps?19:10
teward^^ that19:10
rbasakHappy to hear that it's being looked at. Thank you!19:10
teward*returns to the shadowy void from whence he came*19:11
seb128thanks teward!19:11
seb128other list topic19:11
seb128https://lists.ubuntu.com/archives/technical-board/2024-March/002905.html (Call for vote: Ubuntu Cinnamon 24.04 LTS Qualification)19:11
seb128afaik only amurray and me voted19:12
seb128can we get some other members to also vote?19:12
vorlonI have a concern about the "contact" being a list of ~10 people19:12
vorlonI've raised similar concerns with other flavor applications before19:12
vorlonbut I haven't had time to respond to the list about this19:13
seb128can you follow up on the list with that concern?19:13
vorlonyes19:13
seb128thanks19:13
seb128want an action item for it?19:13
vorlonbut mentioning here this is what's blocked me from +1'ing19:13
vorlonI'll accept an action item :)19:13
seb128#action vorlon to follow up on the Cinnamon 24.04 LTS Qualification re the number of contacts listed for the flavor19:14
meetingologyACTION: vorlon to follow up on the Cinnamon 24.04 LTS Qualification re the number of contacts listed for the flavor19:14
seb128no other topic on the list that I can see (outside of the DMB election which we discussed earlier)19:14
seb128#topic Check up on community bugs and techboard bugs19:15
seb128#info No open community bugs19:15
seb128#info No new techboard bugs19:15
seb128#topic Select a chair for the next meeting (next from https://launchpad.net/~techboard/+members)19:15
seb128#info Next chair will be vorlon, with sil2100 as backup19:16
seb128#topic AOB19:16
vorlonack19:16
seb128AOB?19:16
vorlonnothing from me19:16
amurrayneither from me19:16
seb128nor from me19:17
seb128ok, that's a wrap then, thanks everyone!19:17
seb128#endmeeting19:17
meetingologyMeeting ended at 19:17:09 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2024/ubuntu-meeting.2024-04-09-19.02.moin.txt19:17
vorlonthanks!19:17
amurraythanks folks - thanks seb128 for chairing19:17
rbasakThanks all!19:17

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