[15:29]  * cpaelzer lights the campfire for the MIR meeting
[15:29] <dviererbe> o/
[15:29] <cpaelzer> travellers of the world back from sprints, let us ssee how much has piled up
[15:30] <cpaelzer> #startmeeting Weekly Main Inclusion Requests status
[15:30] <meetingology> Meeting started at 15:30:00 UTC.  The chair is cpaelzer.  Information about MeetBot at https://wiki.ubuntu.com/meetingology
[15:30] <meetingology> Available commands: action, commands, idea, info, link, nick
[15:30] <cpaelzer> Ping for MIR meeting - didrocks joalif slyon sarnold cpaelzer jamespage ( eslerm dviererbe )
[15:30] <cpaelzer> I'm early, you ahve time
[15:30] <jamespage> o/
[15:30] <cpaelzer> but I wanted to get the ping out early :-)
[15:30] <cpaelzer> ih dviererbe, hi jamespage
[15:30] <slyon> o/
[15:30] <cpaelzer> new release, new auto-sync surely lots of new $%&/(
[15:30] <cpaelzer> so let us get started
[15:30] <cpaelzer> #topic current component mismatches
[15:30] <cpaelzer> Mission: Identify required actions and spread the load among the teams
[15:30] <cpaelzer> #link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg
[15:30] <cpaelzer> #link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg
[15:31] <cpaelzer> the non proposed shows postgresql-16
[15:31] <cpaelzer> that is a transition being worked on by athos
[15:31] <cpaelzer> but a bit later in the cycle
[15:31] <cpaelzer> so we will see it a few more times
[15:31] <cpaelzer> Anyway, this won#t be a new MIR as it is just source rename
[15:32] <cpaelzer> so once athos asks, we can promote it under the condition it did not dramatically change
[15:32] <cpaelzer> in -proposed we have
[15:32] <mirespace> o/
[15:32] <slyon> libio-prompter-perl is assigned to a collegue in Foundations.
[15:32] <cpaelzer> a bunch of libmail-dkim-perl which is from mirespace that just logged in
[15:32] <slyon> I uploaded python-keyring earlier today, to downgrade Recommends->Suggests, so that should be resolved, soon.
[15:32] <cpaelzer> and thanks slyon for knowing that the prompter-perl is already been worked on in your team
[15:32] <cpaelzer> double thanks for that slyon
[15:33] <cpaelzer> I see llvm-toolchain-17 at the end of the postgresql tree
[15:33] <sarnold> good morning
[15:33] <cpaelzer> slyon: that is usually also all going to main as doko updates toolchains
[15:33] <cpaelzer> do you happen to know more about it?
[15:34] <cpaelzer> and finally, not new but since jamespage said hi - jaraco.text and dependencies - how will this continue?
[15:34] <slyon> cpaelzer: I saw a question about llvm-toolchain-17 being in universe recently... But I think there wasn't an answer yet from the toolchains squad.
[15:34] <jamespage> let me page that back in...
[15:36] <cpaelzer> slyon: I think we pick up the llvm set as default, hence it should be in main
[15:36] <jamespage> pydantic as some required TODO's - I'll get those sorted out
[15:36] <cpaelzer> slyon: this isn't urgent, maybe by next week you have an info what the way forward for noble shall be there
[15:36] <cpaelzer> so we can pass athos to use that or another llvm
[15:36] <cpaelzer> thanks jamespage
[15:36] <cpaelzer> that feels like there is progress everywhere
[15:36] <cpaelzer> mirespace: did you want to speak about libmail-dkim-perl ?
[15:36] <slyon> ACK
[15:37] <mirespace> no progress on that yet, sorry
[15:37] <cpaelzer> ok, but AFAIR all we reviewed so far were ok with a few small required todo's
[15:37] <cpaelzer> one question on "is this a dup" which has been answered
[15:38] <mirespace> _checking..._
[15:38] <cpaelzer> and you mentioned that you'll cut the longer dependency tree to a short one
[15:38] <cpaelzer> feel free to bring that up not or in the final AoB section
[15:38] <cpaelzer> I'm going on with the agenda for now
[15:38] <cpaelzer> #topic New MIRs
[15:38] <mirespace> but that's for libmail-dmarc-perl, not for dkim-perl
[15:38] <cpaelzer> Mission: ensure to assign all incoming reviews for fast processing
[15:38] <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-mir
[15:38] <cpaelzer> I see
[15:38] <cpaelzer> which is just what we see in the new queue right now
[15:38] <sarnold> hehe
[15:38] <mirespace> yes
[15:38] <cpaelzer> https://bugs.launchpad.net/ubuntu/+source/libemail-abstract-perl/+bug/2037405
[15:39] -ubottu:#ubuntu-meeting- Launchpad bug 2037405 in libemail-abstract-perl (Ubuntu) "[MIR] libemail-abstract-perl (libemail-sender-perl dependency as libmail-dmarc-perl dependency)" [Undecided, New]
[15:39] <cpaelzer> https://bugs.launchpad.net/ubuntu/+source/libemail-sender-perl/+bug/2037389
[15:39] -ubottu:#ubuntu-meeting- Launchpad bug 2037389 in libemail-sender-perl (Ubuntu) "[MIR] libemail-sender-perl (libmail-dmarc-perl dependency)" [Undecided, New]
[15:39] <cpaelzer> https://bugs.launchpad.net/ubuntu/+source/libthrowable-perl/+bug/2037392
[15:39] -ubottu:#ubuntu-meeting- Launchpad bug 2037392 in libthrowable-perl (Ubuntu) "[MIR] libthrowable-perl (libemail-sender-perl dependency as libmail-dmarc-perl dependency)" [Undecided, New]
[15:39] <cpaelzer> all three look for a reviewer
[15:39] <mirespace> that's three can be on hold
[15:39] <cpaelzer> or mirespace are you telling me this will be even less?
[15:39] <cpaelzer> on hold because we should be waiting for that dependency changes you mentioned?
[15:39] <mirespace> all the 11 dependencies that I narrowed for dmarc are already reviewed, except the ppal libmail-dmarc-perl itself
[15:40] <mirespace> yes
[15:40] <cpaelzer> ok
[15:40] <cpaelzer> I'll mark them incomplete for now based on that
[15:40] <cpaelzer> that removes them from the list until you'd change that
[15:40] <mirespace> I could verigy with the test on both packages (dmarc-perl and spamassasin) that we can go with 11 packages for MIR, and move the rest to suggeted
[15:40] <mirespace> thatnkyou
[15:41] <cpaelzer> we all appreciate the effort to not give us another 40 packages to review
[15:41] <mirespace> :)
[15:41] <sarnold> yes :)
[15:41] <slyon> very much so!
[15:41] <cpaelzer> the one on  libmail-dmarc-perl is ongoing - right?
[15:41] <cpaelzer> https://bugs.launchpad.net/ubuntu/+source/libmail-dmarc-perl/+bug/2023971
[15:41] -ubottu:#ubuntu-meeting- Launchpad bug 2023971 in libmail-dmarc-perl (Ubuntu) "[MIR] libmail-dmarc-perl" [High, Incomplete]
[15:41] <cpaelzer> incomplete and waiting for you
[15:42] <mirespace> yes, I have a draft for the template and working on a dep8 package to include the mnaual verification for the functionality with the 11 packages
[15:42] <cpaelzer> once you think this one is ready for us unassign yourself and set it back to NEW please
[15:42] <cpaelzer> that sounds good mirespace
[15:42] <cpaelzer> if ever unsure just come by here again
[15:42] <mirespace> ok, thanks
[15:42] <mirespace> I'll do
[15:42] <cpaelzer> this is the easiest way to coordinate on this
[15:42] <cpaelzer> ok, new bugs handled by all of that
[15:42] <cpaelzer> #topic Incomplete bugs / questions
[15:42] <cpaelzer> Mission: Identify required actions and spread the load among the teams
[15:42] <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-mir
[15:42] <dviererbe> sorry can I throw in dotnet6?
[15:43] <cpaelzer> which is exactly here
[15:43] <cpaelzer> in the incomplete list dviererbe
[15:43] <cpaelzer> the others have been mirespace stack of packages
[15:43] <dviererbe> Yes
[15:43] <cpaelzer> I've seen some dotnet updates out of the riga discussions
[15:43] <cpaelzer> for all of you https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2023531/comments/13
[15:43] -ubottu:#ubuntu-meeting- Launchpad bug 2023531 in dotnet6 (Ubuntu) "[MIR] dotnet6" [Undecided, Incomplete]
[15:44] <cpaelzer> TL;DR no more so special/weird, and therefore fitting more nicely into existing patterns
[15:44] <dviererbe> correct
[15:44] <cpaelzer> dviererbe: do you happen to know what is left open?
[15:44] <cpaelzer> and once they are supposed to be done, what steps are then the next?
[15:44] <dviererbe> As far as I am aware we only had left recommends
[15:45] <dviererbe> One strong recommends was smoke test during build time
[15:45] <cpaelzer> I remember
[15:45] <cpaelzer> https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2023531/comments/4 has the full initial list
[15:45] -ubottu:#ubuntu-meeting- Launchpad bug 2023531 in dotnet6 (Ubuntu) "[MIR] dotnet6" [Undecided, Incomplete]
[15:46] <cpaelzer> dviererbe: so without that special behavior - is your SRU exception now approved. Or are you saying you do not even need one at all anymore?
[15:47] <dviererbe> This is part of why I am here. We do not request an exception anymore.
[15:47] <dviererbe> Therefore I wanted to ask if you still want an formal ack by the SRU team?
[15:48] <cpaelzer> so you will process these under https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases - third bullet I guess
[15:48] <cpaelzer> and not an exception
[15:49] <cpaelzer> and no more "remove support later" as we ahve read
[15:49] <dviererbe> Yes
[15:49] <dviererbe> The support of dotnet packages should now behave as any other package
[15:49] <cpaelzer> I think we no more need a formal exception acked, but as a final confirmation I'd like to have one of the SRU members state on the MIR bug that this isn't a way to bypass the rules :-)
[15:49] <cpaelzer> does that make sense
[15:50] <cpaelzer> I know that everyone agreed in Riga, but the audit trail available to others lacks that
[15:50] <cpaelzer> unless we blindly believe your updates :-)
[15:50] <dviererbe> That is fine :)
[15:50] <cpaelzer> after that I think we are good
[15:50] <cpaelzer> I'll keep it open to recheck all TODO's tomorrow
[15:50] <cpaelzer> to ensure we haven't missed one
[15:50] <cpaelzer> once myself and an SRU member are good
[15:50] <cpaelzer> we can start promoting it
[15:51] <dviererbe> sounds good
[15:51] <cpaelzer> and you might want to extend this to dotnetX as the same is true for all those versions right
[15:51] <cpaelzer> ok, let us go from here and continue with the agenda ...
[15:51] <dviererbe> correct. the only exception is dotnet7 in jammy (mentioned in the bug comment)
[15:51] <cpaelzer> ack
[15:52] <cpaelzer> #topic Process/Documentation improvements
[15:52] <cpaelzer> Mission: Review pending process/documentation pull-requests or issues
[15:52] <cpaelzer> #link https://github.com/canonical/ubuntu-mir/pulls
[15:52] <cpaelzer> #link https://github.com/canonical/ubuntu-mir/issues
[15:52] <cpaelzer> nothing new
[15:52] <cpaelzer> the suggestion on defining clear deadlines has come up at the sprint
[15:53] <cpaelzer> I think everyone was fine, we are waiting for an PR by eslerm or sarnold for that I guess?
[15:53] <cpaelzer> objections?
[15:53] <slyon> I pushed the "base-sets" story a bit at the Riga sprint. Verdict: We're back to status quo. The toolchains squad won't have resources to maintain important dependencies of those ecosystems in the foreseable future.
[15:53] <cpaelzer> https://github.com/canonical/ubuntu-mir/pull/41 might be that PR ...
[15:53] -ubottu:#ubuntu-meeting- Pull 41 in canonical/ubuntu-mir "security: add timeline, contact, and priority info" [Open]
[15:54] <cpaelzer> thanks slyon
[15:54] <cpaelzer> do not give up on it though
[15:54] <sarnold> I can't recall what specific date we actually converged on, heh
[15:54] <cpaelzer> sarnold: eslerm: spelling issues left (or updates to the spelling DB)
[15:54] <cpaelzer> the PR has it all
[15:54] <cpaelzer> it LGTM except the spelling fixes that are needed
[15:54] <cpaelzer> if you can get that updated before next week we can merge it there
[15:54] <slyon> same here. +1 on the deadlines PR
[15:55] <cpaelzer> #topic MIR related Security Review Queue
[15:55] <cpaelzer> Mission: Check on progress, do deadlines seem doable?
[15:55] <cpaelzer> Some clients can only work with one, some with the other escaping - the URLs point to the same place.
[15:55] <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-mir
[15:55] <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-mir
[15:55] <cpaelzer> Internal link
[15:55] <cpaelzer> - ensure your teams items are prioritized among each other as you'd expect
[15:55] <cpaelzer> - ensure community requests do not get stomped by teams calling for favors too much
[15:55] <cpaelzer> #link https://warthogs.atlassian.net/jira/software/c/projects/SEC/boards/594
[15:56] <cpaelzer> we see all of them go through the queues one by one
[15:56] <cpaelzer> 3 plus the one expected perl packages left open then
[15:56] <cpaelzer> nothing else incoming yet
[15:56] <sarnold> this is the best this board has looked in ages :D nice
[15:57] <sarnold> alas I've been busy elsewhere, and eslerm is out recently, so our status is pretty stale :(
[15:57] <cpaelzer> fair for now
[15:57] <cpaelzer> #topic Any other business?
[15:57] <cpaelzer> nothing extra by me
[15:57] <sarnold> I'll ask around to see if anyone can pick up things, but it's a challenging time of year, heh
[15:57] <sarnold> nothing here
[15:57] <cpaelzer> sarnold: it will be more challenging in 4 weeks
[15:57] <slyon> wrt the LLVM situation: according to the Noble schedule, we're targetting LLVM18 to become the default: https://discourse.ubuntu.com/t/noble-numbat-release-schedule/35649
[15:57] <slyon> nothing else from me
[15:57] <cpaelzer> sarnold:  and it not done before that then it is suddenly close to feature freeze
[15:58] <cpaelzer> slyon: fine, but we might need 17 in main until 18 exists for dependencies to move
[15:58] <cpaelzer> time is up
[15:58] <cpaelzer> thank you all
[15:58] <cpaelzer> this was great and lots of things moved forward a little bit
[15:58] <cpaelzer> o/
[15:58] <slyon> o/
[15:58] <cpaelzer> last chance
[15:58] <cpaelzer> 4
[15:58] <cpaelzer> 3
[15:58] <cpaelzer> 2
[15:58] <slyon> thanks cpaelzer, all!
[15:58] <cpaelzer> 1
[15:58] <cpaelzer> #endmeeting
[15:58] <meetingology> Meeting ended at 15:58:45 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2023/ubuntu-meeting.2023-11-21-15.30.moin.txt
[15:59] <dviererbe> Thanks! o/
[16:01] <sarnold> thanks cpaelzer, all :)
[16:55] <cpaelzer> sarnold: thanks for silencing the non-alphanumeric warnings
[16:55] <cpaelzer> sarnold: but wasn't the issue that blocked you this
[16:55] <cpaelzer> Error: README.md:1110:174 ... 184, Error - `Mattermost` is not a recognized word. (unrecognized-spelling)
[16:56] <cpaelzer> #42 is merged, that was fine
[16:56] <cpaelzer> but it did not fix it to know about "Mattermost" AFAICS
[20:00] <amurray> o/
[20:01] <seb128> hey!
[20:01] <seb128> amurray, you are today's chair according to the wiki
[20:01] <amurray> ah yes indeed
[20:02] <seb128> Steve and Robie declined the calendar invite
[20:02] <amurray> is sil2100 around or is it just the two of us?
[20:02] <seb128> unsure if Lukasz is around
[20:03] <seb128> let me ping him on mattermost in case he's there
[20:04] <seb128> sil2100, hey
[20:04] <sil2100> hey
[20:04] <amurray> #startmeeting Ubuntu Technical Board
[20:04] <meetingology> Meeting started at 20:04:58 UTC.  The chair is amurray.  Information about MeetBot at https://wiki.ubuntu.com/meetingology
[20:04] <seb128> sorry for distracting you from the things you focus on
[20:05] <meetingology> Available commands: action, commands, idea, info, link, nick
[20:05] <amurray> hey sil2100
[20:05] <amurray> #topic Apologies
[20:05] <amurray> robie and steve both sent their apologies via the mailing list
[20:05] <amurray> #topic Action review
[20:06] <amurray> ACTION: seb128/amurray/sil200 to help drafting the snap-store Ubuntu-specific tracks usage
[20:06] <seb128> I saw you commented there and Robie discussed it with Ken in Riga
[20:06] <seb128> but I think we need to carry over still
[20:06] <amurray> yep ok no worries
[20:07] <seb128> I will try to reply to your comment this week though
[20:07] <amurray> thanks
[20:07] <amurray> #action seb128/amurray/sil200 to help drafting the snap-store Ubuntu-specific tracks usage
[20:07] <meetingology> ACTION: seb128/amurray/sil200 to help drafting the snap-store Ubuntu-specific tracks usage
[20:07] <amurray> ACTION: rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification
[20:07] <amurray> I'll carry over robie's tasks
[20:07] <amurray> #action rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification
[20:07] <meetingology> ACTION: rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification
[20:08] <amurray> ACTION: rbasak to follow up on finding consensus on question of test plans for third party apps
[20:08] <amurray> #action rbasak to follow up on finding consensus on question of test plans for third party apps
[20:08] <meetingology> ACTION: rbasak to follow up on finding consensus on question of test plans for third party apps
[20:08] <amurray> ACTION: rbasak to open wider discussion on third-party repo policy
[20:08] <amurray> #action rbasak to open wider discussion on third-party repo policy
[20:08] <meetingology> ACTION: rbasak to open wider discussion on third-party repo policy
[20: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_Delegations
[20:08] <seb128> carry over please
[20:09] <amurray> fwiw security team is almost done on this from our side - thanks for kicking this off seb128
[20:09] <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_Delegations
[20:09] <meetingology> 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_Delegations
[20:09] <seb128> ah, nice, and you're welcome!
[20:09] <amurray> ACTION: vorlon to write up draft guidelines for packages in the archive that download from the Internet
[20:09] <amurray> will carry over
[20:09] <amurray> #action vorlon to write up draft guidelines for packages in the archive that download from the Internet
[20:09] <meetingology> ACTION: vorlon to write up draft guidelines for packages in the archive that download from the Internet
[20:09] <amurray> #topic Scan the mailing list archive for anything we missed (standing item)
[20:10] <amurray> #link https://lists.ubuntu.com/archives/technical-board/2023-November/thread.html
[20:10] <amurray> so we have flavor requests for 24.04
[20:11] <amurray> excuse my ignorance but do we just usually vote on these here?
[20:11] <seb128> right, it just took me a bit to find the reference to what we need to do there since I'm new to it
[20:11] <seb128> it's documented on https://wiki.ubuntu.com/RecognizedFlavors
[20:11] <seb128> 'Guidelines for Tech Board to designate flavor image as LTS'
[20:12] <seb128> reading the guidelines I do feel like there is some investigation work to be done to answer the questions for each flavors
[20:12] <seb128> I'm not familiar enough with the work happening on those flavors to be able to vote now I think
[20:13] <seb128> amurray, sil2100, how do you feel about it?
[20:14] <seb128> I'm happy to spend some time on that this week though and follow up on the list with a summary of my 'investigation' for each though if that helps others
[20:14] <amurray> so from our side we at least have to do the "Written confirmation from IS" part
[20:14] <sil2100> I'm fine with more flavors, should we maybe assign one flavor per one TB member to perform the investigation?
[20:14] <sil2100> To spread the workload
[20:15] <seb128> I would not say no to share if others have some time to work on that
[20:15] <amurray> as far as the flavors themselves go, I am also not very familiar with any of them so I would  also be keen to ask a few more questions - particularly around the level of support offered and how big their teams are to handle it plus how many packages they are looking to support
[20:17] <amurray> I'm also happy to take a flavor or two
[20:17] <seb128> same
[20:18] <amurray> #action seb128 to follow-up with ubuntu cinnamon on 24.04 request
[20:18] <meetingology> ACTION: seb128 to follow-up with ubuntu cinnamon on 24.04 request
[20:18] <amurray> #action sil2100 to follow-up with ubuntu studio on 24.04 request
[20:18] <meetingology> ACTION: sil2100 to follow-up with ubuntu studio on 24.04 request
[20:18] <amurray> #action amurray to follow-up with edubuntu on 24.04 request
[20:18] <meetingology> ACTION: amurray to follow-up with edubuntu on 24.04 request
[20:19] <amurray> given robie and steve are out, are we happy to assign one to each of them as well in their absentia?
[20:19] <amurray> otherwise I can take another if one of you two are happy to also take a second?
[20:19] <seb128> I would rather not assign things to them without asking first, especially that Robie already said he would miss the next meeting
[20:20] <seb128> give me a second one
[20:20] <amurray> ok thanks seb128
[20:20] <seb128> I can always try to trade it with Robie or Steve if needed
[20:20] <amurray> #action seb128 to follow-up with ubuntu budgie on 24.04 request
[20:20] <meetingology> ACTION: seb128 to follow-up with ubuntu budgie on 24.04 request
[20:20] <amurray> #action amurray to follow-up with ubuntu kylin on 24.04 request
[20:20] <meetingology> ACTION: amurray to follow-up with ubuntu kylin on 24.04 request
[20:20] <seb128> but at least we have an owner who was there to accept the item meanwhile :)
[20:20] <amurray> :)
[20:21] <amurray> I don't see anything else on the mailing list
[20:21] <amurray> #topic Check up on community bugs and techboard bugs
[20:21] <amurray> #link https://bugs.launchpad.net/ubuntu-community/+bugs?field.assignee=techboard
[20:21] <amurray> #link https://bugs.launchpad.net/techboard
[20:22] <amurray> nothing new here either
[20:22] <amurray> #topic Select a chair for the next meeting (next from https://launchpad.net/~techboard/+members)
[20:22] <amurray> robie already sent his apologies for the next meeting so will skip him
[20:22] <amurray> #agreed next meeting chair: seb128, backup: vorlon
[20:22] <meetingology> AGREED: next meeting chair: seb128, backup: vorlon
[20:22] <seb128> +1
[20:23] <amurray> #topic AOB
[20:23] <seb128> none from me
[20:23] <amurray> nothing from me either
[20:24] <amurray> ok thanks folks
[20:24] <seb128> thanks amurray !
[20:24] <amurray> #endmeeting
[20:24] <meetingology> Meeting ended at 20:24:51 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2023/ubuntu-meeting.2023-11-21-20.04.moin.txt
[20:32] <sil2100> Thanks amurray, seb128  o/
[20:32] <sil2100> I go despair a bit more with security-britney
[21:18] <sarnold> cpaelzer: hah, I can't recall seeing "
[21:18] <sarnold> `Mattermost` is not a recognized word. (unrecognized-spelling)
[21:19] <sarnold> cpaelzer: sigh stupid firefox .. I can't recall seeing "`Mattermost` is not a recognized word. (unrecognized-spelling)" before! just the non-alpha ones. I'd love to know if it was there and I missed it entirely, or if that error didn't display when I viewed it!