/srv/irclogs.ubuntu.com/2023/06/27/#ubuntu-meeting.txt

slyonseb128: I'm currently re-considering the libcamera MIR (looking mostly good, bug #1997560). Is it still true that you only need the libcamera0.0.5 package promoted and none of the (new/splitted) libcamera-{ipa,tools,v4l2} or gstreamer1.0-libcamera packages?10:36
-ubottu:#ubuntu-meeting- Bug 1997560 in libcamera (Ubuntu) "[MIR] libcamera" [Undecided, New] https://launchpad.net/bugs/199756010:36
slyonWell... I guess those split packages are fine anyways (except -tools). So nevermind.11:06
cpaelzer_o/14:30
=== cpaelzer_ is now known as cpaelzer
slyon\o14:30
eslermo/14:30
dviererbeo/14:30
cpaelzer#startmeeting Weekly Main Inclusion Requests status14:30
meetingologyMeeting started at 14:30:40 UTC.  The chair is cpaelzer.  Information about MeetBot at https://wiki.ubuntu.com/meetingology14:30
meetingologyAvailable commands: action, commands, idea, info, link, nick14:30
cpaelzerPing for MIR meeting - didrocks joalif slyon sarnold cpaelzer jamespage ( eslerm dviererbe )14:30
cpaelzerHello everyone14:30
cpaelzerglad to see so many waiting14:30
cpaelzerso without further ado, jumping on agenda point 114:31
cpaelzer#topic current component mismatches14:31
cpaelzerMission: Identify required actions and spread the load among the teams14: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
cpaelzerbryce is still working on that spamassassin case14:31
cpaelzerit seems we will need it14:31
cpaelzerand he preps the paperwork14:31
cpaelzerbut as in the past, those perl libs are just structural wrappers around the source14:31
didrockso/14:32
cpaelzerso we have been - and here for efficiency - do some less deep checks14:32
cpaelzermostly "is this really such a simple case"14:32
cpaelzerbut, not open for review yet14:32
cpaelzerjust a heads up14:32
joalifo/14:32
cpaelzerjamespage: the other never ending story is yourd - jaraco.text14:32
cpaelzerwhen you read this later, let us know what the state and expectation on this should be14:33
cpaelzerwe have a new cycle, so everything might be different now :-)14:33
cpaelzerruby has gotten stub bugs14:33
cpaelzerexisting, but not yet ready14:33
sarnoldgood morning14:33
cpaelzerI see nothing else new in those files14:33
cpaelzerhello also to didrocks joalif and sarnold14:34
cpaelzerand to slyon eslerm and dviererbe who were here before logging started :-)14:34
cpaelzerok, going on14:34
cpaelzer#topic New MIRs14:34
cpaelzerMission: ensure to assign all incoming reviews for fast processing14: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
sarnoldoof, good luck to bryce14:35
cpaelzerhehe14:35
cpaelzeras i said, ruby isn't really ready yet14:35
cpaelzerso we can ignore that for this week14:35
cpaelzerI'll mark them incomplete for now14:35
cpaelzerthat leaves https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/202353114:36
-ubottu:#ubuntu-meeting- Launchpad bug 2023531 in dotnet6 (Ubuntu) "[MIR] dotnet6" [Undecided, New]14:36
dviererbeI filed an MIR for dotnet6. Its a large and complex package but there is no time pressure to get it into main this cycle14:36
cpaelzerdviererbe: dare you, how could you brind this14:36
cpaelzerit is huge for sure14:36
slyondviererbe: I guess foundations would be the owning team. I can see it subscribed.. do you want me to do that?14:36
slyoncan't*14:36
cpaelzerdviererbe: any reason to start with dotnet6 and not 7 ?14:37
cpaelzeror is 7 already up and in some interim state?14:37
dviererbeWe only want to MIR LTS versions14:37
cpaelzer(maybe I should read the bug)14:37
sarnold  - This MIR exists in parralel to the MIR for dotnet714:37
dviererbecpaelzer: Waht does "brind mean"14:37
cpaelzerbring + a typo14:38
cpaelzerAs I understood, dotnet7 is not an LTS, so no MIR for it14:38
dviererbeohh... I'm sorry14:38
dviererbecorrect14:38
cpaelzerdviererbe: what are the target releases for this - only mantic or later?14:38
cpaelzerdviererbe: or will this be going back in time, as you backport all of it all the time anyway14:38
dviererbeIncluding all, back until jammy would be preferred14:39
sarnoldwill we have both dotnet6 and dotnet8 in 24.04 LTS ? https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core14:39
cpaelzeror will you make a choice14:39
dviererbedotnet8 will be there in 24.0414:39
cpaelzerwhich dotnet matches which Ubuntu LTSes14:39
sarnold"Even numbered releases are LTS releases that get free support and patches for three years." oof that's long, eh? :(14:39
cpaelzerso will it be dotnet6 18-04->23.10 and then dotnet8 24.04->future ?14:40
dviererbeonly since jammy14:40
cpaelzer?14:41
dviererbeThe actual support strategy is a little bit complicated. I will add a comment to the bug14:41
sarnoldthanks14:41
cpaelzerdotnet8 on >=jammy - is that it14:41
cpaelzerappreciate that14:41
sarnoldwhat's our plan for after the end of upstream support?14:41
dviererbeIf I recall correctly dotnet8 will only be needed in >= 24.04 and dotnet6 in >= 22.0414:42
dviererbeThe plan is to provide a transitional package that deinstalls dotnet when it reaches EOL14:42
sarnoldaha, interesting14:42
dviererbeWe already talked with security about that14:42
cpaelzerwow14:42
cpaelzerumm, yeah please outline that on the bug :-)14:43
sarnoldit does sound familiar. sigh :( my memory isn't what it was :(14:43
dviererbeno worries you have a lot to do14:43
cpaelzerok, I made a post on the bug14:43
cpaelzerand I'm waiting for dviererbe to add more details later14:43
cpaelzerin any case, we need to start a review on it14:43
cpaelzerand that isn't as special in this case14:44
cpaelzeras things with daemons and ports are often more complex to review14:44
sarnolddo we have such strong feelings about 'no generated objects / sources' the same way debian does?14:44
cpaelzerthis is more pain for security later on I guess14:44
cpaelzersarnold: we do have the opinion to avoid whenever possible, but not strictly forbid them AFAIK14:44
sarnoldthis feels likely to be supported via the 'big blog from MS' model14:44
sarnolds/blog/blob/'14:44
cpaelzers/blog/blob/ ?14:44
cpaelzeryeah :-)14:45
cpaelzerok, counting slyon out as he is in the requesting team14:45
sarnoldwhich I have to say isn't very pleasing when applied to eg mysql14:45
dviererbesarnold: Maybe you can talk with Ian about the dotnet package. we work with him for security releases14:45
* slyon nods14:45
cpaelzerthat leaves joalif didrocks or me to review14:45
cpaelzervolunteers or should I roll a dice14:45
joalifroll a dice :p14:46
didrocksif there is no time constraints, I can take it, but we can make it fun too with a dice roll :)14:46
cpaelzer1-2 me, 3-4 joalif, 5-6 didrocks14:46
cpaelzer114:46
cpaelzer= me14:46
sarnoldsnake eyes!14:46
dviererbeI'm sorry :/14:46
cpaelzerthere goes my automation of statistics ... o/14:46
didrockssorry too for you :/ wonder how you did your dice roll though!14:47
cpaelzerall fine dviererbe14:47
cpaelzerdidrocks: I have literally dices on my desk for planning and situations like this14:47
sarnold:D14:47
cpaelzerbenefit of old role players I can cover any team size14:47
cpaelzerok, going on14:47
didrockswaow, that’s orgnanization! :)14:47
cpaelzer#topic Incomplete bugs / questions14:47
cpaelzerMission: Identify required actions and spread the load among the teams14:47
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:47
sarnoldI wanna see that three-sided die14:47
cpaelzersarnold: you do realize thet is a D6/214:47
cpaelzerprimes are hard14:48
sarnoldoh. that's less fun.14:48
cpaelzerbut as manager we can be creative14:48
cpaelzertwo of the recent cases are in here14:48
cpaelzerhttps://bugs.launchpad.net/ubuntu/+source/cairomm1.16/+bug/202027314:48
-ubottu:#ubuntu-meeting- Launchpad bug 2020273 in cairomm1.16 (Ubuntu) "[MIR] cairomm1.16" [Undecided, Incomplete]14:48
cpaelzertasks of slyon for4 jbicha14:48
slyonI had a question about the symbols handling on this one ^14:48
sarnold"This does not need a security review"  <3 :)14:48
cpaelzerstate ok for now14:48
slyonas discussed on the mailinglist14:48
cpaelzerso we are coming back to symbosl14:49
cpaelzersymbols14:49
cpaelzerI haven't seen that, do you have a link slyon?14:49
cpaelzeris that the continuation of the discussion seb opened a while ago?14:50
sarnoldyeah14:50
slyonhttps://bugs.launchpad.net/ubuntu/+source/cairomm1.16/+bug/2020273/comments/2 - my normal MIR review14:50
-ubottu:#ubuntu-meeting- Launchpad bug 2020273 in cairomm1.16 (Ubuntu) "[MIR] cairomm1.16" [Undecided, Incomplete]14:50
cpaelzerIIRC last week we said he is writing a PR to clarify the "one should try"14:50
joaliftalking about symbols in my review this week https://bugs.launchpad.net/ubuntu/+source/gtkmm4.0/+bug/2020472 , symbols were missing as well for gtkmm4.0 but I wrote it is ok since gtkmm3.0 are also missing and is already in universe14:50
-ubottu:#ubuntu-meeting- Launchpad bug 2020472 in gtkmm4.0 (Ubuntu) "[MIR] gtkmm4.0" [Undecided, In Progress]14:50
slyonessentially, I couldn't find a previous MIR (seems this has been in main forever). So I did a full review14:50
cpaelzerslyon: yeah, that happened to me as well14:50
slyoncairomm[1.16] does not ship any .symbols files and I could not find any other attempt at ABI compatibilty testing. Therefore, I asked the questions why it should be skipped for this package (cc jbicha)14:51
cpaelzeryeah14:51
cpaelzerand as discussed we want to see it tried and given up for a reason14:51
cpaelzerinstead of giving up generally14:51
didrocksagreed14:51
slyonright.14:51
cpaelzerok for now14:51
cpaelzerlet us wait what the answer is14:52
cpaelzerto close out this agenda item - https://bugs.launchpad.net/ubuntu/+source/libhttp-cookiejar-perl/+bug/2024245 - has an open question and therefore is ok to be incomplete for now14:52
-ubottu:#ubuntu-meeting- Launchpad bug 2024245 in libhttp-cookiejar-perl (Ubuntu) "[MIR] libhttp-cookiejar-perl" [Undecided, Incomplete]14:52
slyonAnd accepting it just because it has been bad before (without any reasoning given) isn't good14:52
slyonIMHO14:52
cpaelzeryep14:52
cpaelzerthere is some balance to strike, but yes14:52
cpaelzerwe can keep it at that for now14:52
cpaelzer#topic Process/Documentation improvements14:52
cpaelzerMission: Review pending process/documentation pull-requests or issues14:52
cpaelzer#link https://github.com/canonical/ubuntu-mir/pulls14:52
cpaelzer#link https://github.com/canonical/ubuntu-mir/issues14:52
jbicha.14:52
cpaelzeroh, hi jbicha14:53
cpaelzerdo you want to immediately discuss/report about that?14:53
cpaelzeror only seen the highlights so far14:53
jbichafor glibmm2.68, I have a draft to force symbols tracking for amd64 on Ubuntu only https://salsa.debian.org/gnome-team/glibmm2.68/-/merge_requests/214:53
-ubottu:#ubuntu-meeting- Merge 2 in gnome-team/glibmm2.68 "Draft: Add symbols tracking" [Opened]14:53
cpaelzerawesome14:53
cpaelzerthanks jbicha14:53
jbichaI can investigate cairomm1.16 then too14:53
cpaelzerlet us know via an update in the bug if you think this lands in time or if you expect this to take ages (more thna you can wait with promotion)14:54
slyonthat'd be great, thanks jbicha14:54
cpaelzerwhile we are at it - here we have the aforementioned PR about symbols14:54
cpaelzerhttps://github.com/canonical/ubuntu-mir/pull/2714:54
-ubottu:#ubuntu-meeting- Pull 27 in canonical/ubuntu-mir "Document a possible symbols exception for c++ libraries" [Open]14:54
cpaelzerI think slyon and I commented14:56
jbichaI'm curious to see how difficult it is to update the symbols for glibmm for the next major release. The Desktop Team may come back to the MIR team if it's just too much of a headache14:56
cpaelzerwe can wait for an answer14:56
cpaelzerjbicha: that sounds fair to me14:56
jbichaI expect to have an update for cairomm by next week's meeting14:56
joalifjbicha: symbols are missing for gtkmm4.0 too could you also take a look at it ?14:56
joalifhttps://bugs.launchpad.net/ubuntu/+source/gtkmm4.0/+bug/202047214:57
-ubottu:#ubuntu-meeting- Launchpad bug 2020472 in gtkmm4.0 (Ubuntu) "[MIR] gtkmm4.0" [Undecided, Incomplete]14:57
sarnoldjbicha: I really like the sound of that salsa merge request14:57
cpaelzerwhile making progress - the other PR up is https://github.com/canonical/ubuntu-mir/pull/2814:57
-ubottu:#ubuntu-meeting- Pull 28 in canonical/ubuntu-mir "Explicitly state that reviews are about source packages" [Open]14:57
jbichagtkmm will be like glibmm so I'll aim to complete by next meeting too14:57
cpaelzerslyon: that is simple enough and I'm +114:57
cpaelzerif no one objects I'd merge it as-is14:58
cpaelzerany -1 here?14:58
sarnold+114:58
joalif+114:58
cpaelzerenough for me as it is trivial14:58
cpaelzerthanks14:58
didrocksanswered +1 on the PR, unsure how useful this is, but ok :)14:58
cpaelzerthe other cases are open14:58
cpaelzerbut not ready14:58
cpaelzerthe only issue worth is https://github.com/canonical/ubuntu-mir/issues/2614:59
-ubottu:#ubuntu-meeting- Issue 26 in canonical/ubuntu-mir "Decide if we get enough value from c++ symbols tracking to keep doing it" [Open]14:59
cpaelzersarnold:  given the changes, can we close this now?14:59
cpaelzerif you are ok, please do so sarnold14:59
cpaelzerand keeping time in mind, I'm going on ...14:59
sarnoldcpaelzer: I figured we'd close it when we merge in https://github.com/canonical/ubuntu-mir/pull/2714:59
-ubottu:#ubuntu-meeting- Pull 27 in canonical/ubuntu-mir "Document a possible symbols exception for c++ libraries" [Open]14:59
cpaelzerack @sarnold14:59
cpaelzer#topic MIR related Security Review Queue14:59
cpaelzerMission: Check on progress, do deadlines seem doable?14:59
cpaelzerSome clients can only work with one, some with the other escaping - the URLs point to the same place.14:59
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-mir14:59
cpaelzer#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:00
cpaelzerInternal link15:00
cpaelzer- ensure your teams items are prioritized among each other as you'd expect15:00
cpaelzer- ensure community requests do not get stomped by teams calling for favors too much15:00
cpaelzer#link https://warthogs.atlassian.net/jira/software/c/projects/SEC/boards/59415:00
cpaelzerThat LGTM - any concerns from your side sarnold ?15:00
sarnoldthat big pile of perl is worrying ..15:00
sarnoldbut right now, things feel pretty good15:00
cpaelzerit is coming15:00
cpaelzerbut usually those go by mostly without security15:00
cpaelzerwe will see15:00
cpaelzerthanks sarnold15:00
cpaelzer#topic Any other business?15:00
cpaelzerplease mind that your other meetings might start now15:00
didrocksnothing here15:00
cpaelzerthis is done any minute ...15:01
eslermcargo and rust dependencies15:01
sarnoldhttps://launchpad.net/ubuntu/+source/dh-builtusing ...15:01
cpaelzeryeah you wanted to bring those up last time15:01
cpaelzerwe might lose qorum, but you should bring up the question for awareness15:01
slyonI think we'd need didrocks opinion on https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1993819/comments/5 to move forward the cargo MIR15:01
-ubottu:#ubuntu-meeting- Launchpad bug 1993819 in dh-cargo (Ubuntu) "MIR: cargo, dh-cargo" [High, In Progress]15:01
sarnoldis ^^ this thing Good Enough? please skim it :)15:01
cpaelzerand if we can not close it out bring it up as first item next time15:01
didrocksyeah, as I didn’t "win" any MIR this week, I can have another look at this15:02
cpaelzerthank you didrocks15:02
eslermat the Rust Support in Main meeting in Prague, other teams agreed to define a policy for tracking rebuild-dependencies15:02
eslermthis is important to the Security Team, as we need to rebuild Rust packages when vulnerabilities in their dependencies are patched15:02
eslermi.e., patching a package should trigger rebuilding all statically linked reverse-dependencies, and rebuilds of their reverse-dependencies, and so on15:02
cpaelzeryeah, that is driven by foundations IIRC15:02
eslermat the meeting we agreed that this new policy should apply to all packages, not just Rust15:02
didrocksI think as foundation has toolchains maintainer, this is rather something between security and them, no?15:03
cpaelzeryes didrocks15:03
didrocks(I'm happy to give a hand on Go, and explaining how this works out for it as I think I might be the one with the most awareness of govulncheck and so on…)15:03
cpaelzerslyon: would you chase down internally if this was lost or net even meant to be on foundations plate?15:03
slyonYes, will do15:04
cpaelzerthanks15:04
cpaelzerwe are good for today15:04
cpaelzersorry to have kept you so long15:04
cpaelzerbut it is important, all the time15:04
cpaelzero/15:04
sarnoldthanks cpaelzer, all15:04
cpaelzer#endmeeting15:04
eslermthanks everyone15:04
meetingologyMeeting ended at 15:04:45 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2023/ubuntu-meeting.2023-06-27-14.30.moin.txt15:04
eslermo/15:04
didrocksthanks!15:04
dviererbeThanks!15:04
slyonthanks. I'll try to get back to eslerm about the rebuild-tracking policy15:05
eslermthank you slyon15:07
sil2100o/19:00
rbasako/19:00
amurrayo/19:00
rbasakI don't have any progress to report this meeting unfortunately. But I'm around now.19:00
seb128hey19:00
sil2100Hello!19:00
sil2100#startmeeting Technical Board Meeting19:01
meetingologyMeeting started at 19:01:26 UTC.  The chair is sil2100.  Information about MeetBot at https://wiki.ubuntu.com/meetingology19:01
meetingologyAvailable commands: action, commands, idea, info, link, nick19:01
sil2100#topic Apologies19:01
sil2100I don't think there were any explicit apologies sent beforehand19:01
sil2100#topic Action review19:02
sil2100Since rbasak said there's no progress on his tasks, I'll carry them over. It's sadly the same for me, so I'll do that as well19:03
sil2100#action rbasak to get agreed backporter charter https://lists.ubuntu.com/archives/technical-board/2023-June/002740.html documented under https://wiki.ubuntu.com/TechnicalBoard/19:03
meetingologyACTION: rbasak to get agreed backporter charter https://lists.ubuntu.com/archives/technical-board/2023-June/002740.html documented under https://wiki.ubuntu.com/TechnicalBoard/19:03
* sil2100 seb128/amurray/sil200 to help drafting the snap-store Ubuntu-specific tracks usage19:03
sil2100amurray, seb128: any news on this from your side?19:03
amurrayI had proposed something a while ago but I think the doc still shows it as a suggestion - so I guess that is awaiting feedback?19:04
amurrayoh I see - seb128 and ken provided some comments - i guess I need to go read those - righto - let me take that as a carry-over then19:05
sil2100amurray: thanks!19:05
sil2100#action seb128/amurray/sil200 to help drafting the snap-store Ubuntu-specific tracks usage19:06
meetingologyACTION: seb128/amurray/sil200 to help drafting the snap-store Ubuntu-specific tracks usage19:06
sil2100Ok, mine is carry-over19:06
sil2100#action 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 step19:06
meetingologyACTION: 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 step19:06
sil2100#action rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification19:06
meetingologyACTION: rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification19:06
sil2100#action rbasak to follow up on finding consensus on question of test plans for third party apps19:06
meetingologyACTION: rbasak to follow up on finding consensus on question of test plans for third party apps19:06
sil2100#action rbasak to restructure the third-party repo doc to make the status clearer19:06
meetingologyACTION: rbasak to restructure the third-party repo doc to make the status clearer19:06
sil2100#action rbasak to open wider discussion on third-party repo policy19:07
meetingologyACTION: rbasak to open wider discussion on third-party repo policy19:07
sil2100Now it's this one:19:07
* sil2100 rbasak, vorlon, amurray to replay their responses to Key Ubuntu teams discussion19:07
seb128sil2100, we are missing your input on that discussion! :-)19:07
sil2100seb128: I know! I think I need an action item for that too :(19:08
seb128but the 'reply' part is done19:08
seb128replay19:08
sil2100Ok, so I'll add this as done and add an action item for me19:08
seb128though I think my main concern wasn't address and there was no reply to my most recent email19:08
sil2100#done rbasak, vorlon, amurray to replay their responses to Key Ubuntu teams discussion19:08
seb128but maybe others aren't interested in addressing that part, hard to say19:08
sil2100#action sil2100 to follow up on the Key Ubuntu teams discussion19:09
meetingologyACTION: sil2100 to follow up on the Key Ubuntu teams discussion19:09
sil2100seb128: I'll really try hard to find a slot to address this, maybe my reply will help things moving forward19:10
sil2100Anyway, let's move on19:10
sil2100#topic Scan the mailing list archive for anything we missed (standing item)19:10
sil2100#link https://lists.ubuntu.com/archives/technical-board/2023-June/thread.html19:10
sil2100Nothing here, just the Key Ubuntu teams discussion which I'm really bad at following up on...19:11
sil2100#topic Check up on community bugs and techboard bugs19:11
sil2100#link https://bugs.launchpad.net/ubuntu-community/+bugs?field.assignee=techboard19:11
sil2100#link https://bugs.launchpad.net/techboard19:11
sil2100No new bugs open besides the ones we already know about19:11
sil2100#topic Select a chair for the next meeting (next from https://launchpad.net/~techboard/+members)19:12
sil2100#agreed next meeting chair: amurray, backup: rbasak19:12
meetingologyAGREED: next meeting chair: amurray, backup: rbasak19:12
sil2100#topic AOB19:12
sil2100Any other business?19:12
sil2100The floor is open19:12
seb128not from me19:12
amurraynothing from me19:13
sil2100There was a potential new item via the ML re: the adsys MRE, but I think that was resolved without requiring input from the TB19:13
rbasakYeah I think that's now an SRU team item to figure out.19:14
sil2100Okay then, it's a quick meeting then. Maybe I can find time to start gathering time for the Key Ubuntu teams discussion for the reminder of the meeting19:14
seb128that would be nice indeed :)19:14
sil2100#endmeeting19:14
meetingologyMeeting ended at 19:14:32 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2023/ubuntu-meeting.2023-06-27-19.01.moin.txt19:14
sil2100Thank you everyone o/19:14
amurraythanks sil210019:14
seb128thanks sil2100 for chairing!19:14
seb128efficient meetings are the best :p19:14

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