/srv/irclogs.ubuntu.com/2024/01/16/#ubuntu-meeting.txt

=== pushkarnk1 is now known as pushkarnk
=== pushkarnk1 is now known as pushkarnk
cpaelzerHiho party people15:29
cpaelzer#startmeeting Weekly Main Inclusion Requests status15:29
meetingologyMeeting started at 15:29:54 UTC.  The chair is cpaelzer.  Information about MeetBot at https://wiki.ubuntu.com/meetingology15:29
meetingologyAvailable commands: action, commands, idea, info, link, nick15:29
cpaelzerPing for MIR meeting - didrocks joalif slyon sarnold cpaelzer jamespage ( eslerm dviererbe )15:29
cpaelzerI know I'm early, but wanted to get the ping out in time15:30
slyono/15:30
eslermhello o/15:30
cpaelzer#topic current component mismatches15:30
cpaelzerMission: Identify required actions and spread the load among the teams15:30
cpaelzer#link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg15:30
cpaelzer#link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg15:30
cpaelzerwow15:31
cpaelzerthe new nvidia driver is wanted a lot15:31
cpaelzerI'm not in the mood to count the lines15:31
cpaelzerbut those are normal, no new MIR needed and the team handles them well15:31
cpaelzerno action needed15:31
cpaelzerhttps://bugs.launchpad.net/ubuntu/+source/python-cssselect/+bug/2048760 is open15:31
-ubottu:#ubuntu-meeting- Launchpad bug 2048760 in python-cssselect (Ubuntu) "[MIR] python-cssselect" [Undecided, Confirmed]15:31
cpaelzerI guess we will see that later as it seems ready for review15:32
slyonyes15:32
joalifo/15:32
eslerm(just curious, how would I run mismatch on an arbitrary universe package to see its MIR requirements)15:32
cpaelzerdkim-perl is known and still worked on by mirespace15:32
sarnoldgood morning15:32
cpaelzereslerm: https://github.com/canonical/ubuntu-mir?tab=readme-ov-file#tools15:33
eslermthanks!15:33
cpaelzerIIRC I wrote my own as it wasn't doing recursive needs15:33
cpaelzernot sure anymore, it was long long ago15:33
cpaelzerit is the right start15:33
cpaelzerthe rest in mismatches is also known15:33
cpaelzerpython-infelct15:33
cpaelzerthe same cssselect15:34
cpaelzerand known logcheck->esmtp15:34
cpaelzergoing on in the agenda ...15:34
cpaelzer#topic New MIRs15:34
cpaelzerMission: ensure to assign all incoming reviews for fast processing15: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-mir15:34
cpaelzeras assumed15:34
cpaelzerhttps://bugs.launchpad.net/ubuntu/+source/python-cssselect/+bug/204876015:34
-ubottu:#ubuntu-meeting- Launchpad bug 2048760 in python-cssselect (Ubuntu) "[MIR] python-cssselect" [Undecided, Confirmed]15:34
cpaelzerand also15:34
cpaelzerhttps://bugs.launchpad.net/ubuntu/+source/libnet-idn-encode-perl/+bug/203892915:34
-ubottu:#ubuntu-meeting- Launchpad bug 2038929 in libnet-idn-encode-perl (Ubuntu) "[MIR] libnet-idn-encode-perl (as libmail-dmarc-perl dependency)" [Undecided, New]15:34
cpaelzerlet me read the discussion ont he latter15:34
slyonI assume the latter could be WONTFIX, as mirespace changed the reverse-dependency, so that it is no longer needed15:35
cpaelzeryeah that is how I read the comments too15:35
cpaelzerThe former looks for a reviewer15:36
cpaelzerhttps://bugs.launchpad.net/ubuntu/+source/python-cssselect/+bug/204876015:36
-ubottu:#ubuntu-meeting- Launchpad bug 2048760 in python-cssselect (Ubuntu) "[MIR] python-cssselect" [Undecided, Confirmed]15:37
cpaelzerwe have slyon and me and it is slyon's case ... avoiding self-review I think I have to take this one15:37
cpaelzerWhile I have more sprint things to prep that should squeeze in well (hope dies last)15:37
cpaelzer#topic Incomplete bugs / questions15:38
slyonThe MIR templated used here ^ is a bit outdated. mkukri is willing to update it if needed. But overall the package seems to be in good shape, so we should be fine reviewing as-is, IMO15:38
cpaelzerMission: Identify required actions and spread the load among the teams15:38
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:38
slyoncpaelzer: joalif was also waving above15:38
cpaelzeroh, blind me15:38
cpaelzerindeed15:38
joalifI was about to write the same :p15:38
* cpaelzer opens eyes15:38
joalifI can take one15:38
cpaelzerI've seen the security folks and slyon - sorry joalif15:38
joalifno worries15:38
slyonsqueezing it in between a sprint, might not be the best idea15:38
joalifi was abit late to the party15:38
cpaelzerpassed cssselect to you then joalif15:39
joalifok15:39
slyonthx joalif!15:39
cpaelzerI'll need to thank you in my sprint presentation somehow now ...15:39
sarnold:)15:39
cpaelzercomments on https://bugs.launchpad.net/ubuntu/+source/dbus-broker/+bug/201553815:39
-ubottu:#ubuntu-meeting- Launchpad bug 2015538 in dbus-broker (Ubuntu) "[MIR] dbus-broker" [Undecided, Incomplete]15:39
mkukrii unfortunately didnt have time to impove python3-cssselect today, but will have it done by next week15:40
cpaelzerThat is a Debian maintainer and upstream systemd contributor offering to help15:40
eslermI asked SEG and there wasn't extra capacity to take dbus-brokers wrapper15:40
cpaelzerBut it will still be O-release15:40
slyonmkukri: please coordinate with joalif about that (maybe it's not needed)15:40
cpaelzereslerm: interesting, what was the answer?15:40
cpaelzerit is kind of a very soon or in 24.10 atm right?15:41
eslermit was a favor request, they mentioned that they were tight on people but someone *might* be interested to take it on15:41
eslermadding the wrapper likely needs to go on a roadmap15:41
sarnoldyeah, and it's a large enough change that even if it were done today, I think there'd be serious questions about switching to it now15:41
cpaelzerby not finding time we are also becoming one of the few that have not yet switched :-/15:42
cpaelzerfedora changed ages ago, arch did announce the same last week15:42
sarnolderr .. the first "large change" is switching dbus implementations; the second "it were done today" was the (presumably) smallish wrapper15:42
eslermSecurity eyeballed how much work the wrapper would take during the review. There's a little bit of process state handling, but not much15:42
cpaelzermaybe the link is worth adding to second the rationale?15:42
eslermI can15:43
cpaelzerI'll add it15:43
slyondbus-broker was mostly driven by desktop. I wonder if seb128 is interested in merging v35 (even though it's in universe)? Just to keep it up to date15:44
cpaelzerI still doubt this can happen without Desktop finding and dedicating resources to it15:44
slyonadding the wrapper is another story then15:45
cpaelzerack15:45
cpaelzerin the context of the MIR meeting this is interesting but not blocking us15:45
cpaelzerwould one ping Seb and others to ensure they reconsider it again as it is kind of the last chance to do so?15:45
slyonI can15:46
cpaelzerthx15:46
cpaelzer#topic Process/Documentation improvements15:46
cpaelzerMission: Review pending process/documentation pull-requests or issues15:46
cpaelzer#link https://github.com/canonical/ubuntu-mir/pulls15:46
cpaelzer#link https://github.com/canonical/ubuntu-mir/issues15:46
cpaelzerno new entries15:46
cpaelzersome wnated to discuss offline about base-sets15:46
cpaelzerany major change already on that front?15:46
eslermsome in Foundations MM15:47
eslermnot a major roadmap item atm, but there is related work to do15:47
slyonverdict was that the Foundations toolchain squad does not have capacity to work on it this cycle, but security might start working on some relevant tooling15:47
cpaelzerok15:47
cpaelzerthanks for the update15:47
cpaelzer#topic MIR related Security Review Queue15:47
cpaelzerMission: Check on progress, do deadlines seem doable?15:47
cpaelzerSome clients can only work with one, some with the other escaping - the URLs point to the same place.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
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:47
cpaelzerInternal link15:47
cpaelzer- ensure your teams items are prioritized among each other as you'd expect15:48
cpaelzer- ensure community requests do not get stomped by teams calling for favors too much15:48
cpaelzer#link https://warthogs.atlassian.net/jira/software/c/projects/SEC/boards/59415:48
cpaelzerThere seem to be 6 in TODO+Backlog15:48
cpaelzergiven that we are closing in towards FF and with a bit more distance towards release15:48
cpaelzercould security do a spike to get those handled?15:48
eslermI'm training the certs/fips folks for MIRs after this meeting (libgssglue) and setting up similar meeting for fdk-aac-free15:49
cpaelzerwell, that is great to hear15:49
eslermthe perl ones are more or less done, it would be nice if another perl one was ready15:49
eslermlibmysofa is still in upstream's hands iiuc15:49
cpaelzerlibmail-mime-perl is in TODO15:49
eslermopenscap is a backlog security task (not for MIR)15:49
eslermI'm not aware of roc-toolkit yet15:49
* eslerm looks15:49
cpaelzerarr, that was one that was switched away15:50
cpaelzeryou might want to remove the card in your jira though15:50
slyoneslerm: I finished roc-toolkit MIR review today. It's ready for security review15:50
eslerm\o/15:50
eslermI'll try to assign it this week15:50
cpaelzerI'll ping mirespace if there are any more perl MIRs waiting to get them to us asap for you to be able to use them for training15:50
eslermthank you15:51
eslermAndrei has worked up a perl fuzzing process for those15:51
cpaelzerok, I pinged mirespace about it15:52
eslermperl turns out not to be great for training though :)15:52
mirespacecpaelzer: They all are submitted15:52
cpaelzerah15:52
cpaelzerwell, great15:52
cpaelzerafte rso many months of yet another no one thought of that to be possible :-)15:52
mirespacehehe... well, let's see how libcryptX evolves :(15:52
sarnoldmirespace: woo :) nice work working those through :)15:52
cpaelzermirespace: libcryptx was the bad one enmbedding another version of a lib right?15:53
mirespacethanks sarnold! :$15:53
mirespaceyes, that one15:53
cpaelzer*sigh*15:53
cpaelzerwhy can't things ever be easy15:53
cpaelzermirespace: hmm, reading the comment15:54
cpaelzerit seems you wait for us on this15:54
cpaelzerbut by being assigned to you it won't show up in any query15:54
cpaelzerlet me löink it here15:54
cpaelzerfor us to have a look now15:54
cpaelzerhttps://bugs.launchpad.net/ubuntu/+source/libcryptx-perl/+bug/204615415:54
-ubottu:#ubuntu-meeting- Launchpad bug 2046154 in libcryptx-perl (Ubuntu) "[MIR] libcryptx-perl (libmail-dkim-perl dependency)" [Undecided, New]15:54
cpaelzerI'd appreciate we all could have a look to conclude on ways forward15:54
cpaelzeroption #1 sounds even worse :-/15:55
cpaelzerfor #2 - sad that even that ed25519 uses the embedded tomcrypt15:56
eslermI'll bring this LP up during the fips/certs mir training15:56
slyonmaybe adrien does have an opinion on that?15:56
cpaelzerI see how #3 is the easiest, but OTOH the one taking way the function users want from this whole stack of tools15:57
eslermslyon: I'll ask15:57
mirespaceI'm  working on trying to separate ed255519 from dkim itself at putting it like recommend... there is a sodium based perl lib that that handles also ed255519, but is pretty abandoned15:57
cpaelzerI think I miss #4 - make this an optional dependency, so that some encryptions work out of the bux and others are a suggest to a universe package15:58
mirespace(sorry, I put a extra that )15:58
cpaelzerreally I'd love to see adriens and eslerm (after bringing it up) thoughts on this15:58
sarnoldI'd love to know if they're abandoned because they are working fine and don't need maintaining, or if they're so busted that the authors gave up :(15:58
cpaelzerafter all they might say "ok, while not great - using it as is is the least bad option"15:58
cpaelzerI mean I found that the embedded lib is more up to date than the lib itself15:59
sarnoldha15:59
cpaelzertime is running out15:59
mirespace(sorry, I need to drop ... thank you all)15:59
sarnoldbye mirespace :) thanks15:59
cpaelzerlooking forwadr to seeing your comment on the case later on15:59
cpaelzerwe all need to drop ...15:59
cpaelzer#topic Any other business?16:00
sarnoldnoen here16:00
cpaelzerlast minute urgent things?16:00
slyonnope16:00
cpaelzernot from me16:00
joalifnone from me16:00
eslermthanks all o/16:00
cpaelzernice, over and out16:00
slyonthanks cpaelzer, all!16:00
sarnoldthanks cpaelzer, all :)16:00
cpaelzer#endmeeting16:00
meetingologyMeeting ended at 16:00:25 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2024/ubuntu-meeting.2024-01-16-15.29.moin.txt16:00
joalifthanks cpaelzer, all :)16:00
tsimonq2o/19:58
rbasako/19:58
amurrayo/20:00
seb128o/20:02
seb128ah, according to the agenda it seems like I'm the chair today20:03
seb128sorry for being a bit late20:03
seb128#startmeeting Ubuntu Technical Board20:04
meetingologyMeeting started at 20:04:01 UTC.  The chair is seb128.  Information about MeetBot at https://wiki.ubuntu.com/meetingology20:04
meetingologyAvailable commands: action, commands, idea, info, link, nick20:04
seb128#topic Apologies20:04
seb128amurray is the only one who refused the calendar event but he seems around?20:05
seb128no email on the list from what I can see20:05
seb128#topic Action review20:05
amurrayvorlon mentioned in a private channel that he would be afk20:05
seb128ok20:05
seb128ACTION: seb128/amurray/sil2100 to help drafting the snap-store Ubuntu-specific tracks usage20:05
eslermamurray is ooo on my calendar20:06
seb128right, I said that :)20:06
amurrayi'm here ;)20:06
seb128so on the tracks usage, I replied to a comment20:07
seb128unsure what is missing for us to be able to move forward from where we are20:07
seb128amurray, any opinion on what should be the next steps there?20:07
amurrayyeah I am also a bit unsure - I wonder if we need a google meet session or similar to review the remaining comments as a group?20:08
amurrayor we need to engage the store team to figure out if they can support the requirements20:09
seb128ok, let's carry over and I will take an action item to set up a meeting specifically to discuss that topic20:10
seb128including other stakeholders if needed20:10
seb128#action: seb128/amurray/sil2100 to help drafting the snap-store Ubuntu-specific tracks usage20:10
amurraythanks20:11
seb128#action: seb128 to organize a meeting to unblock the draft of the tracks usage section20:11
sil2100Apologies, I got totally distracted20:11
seb128ACTION: rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification20:11
seb128sil2100, hey!20:11
rbasakCarry over please20:11
seb128#action rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification20:11
meetingologyACTION: rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification20:11
seb128ACTION: rbasak to follow up on finding consensus on question of test plans for third party apps20:12
rbasakAlso carry over sorry20:12
seb128#action rbasak to follow up on finding consensus on question of test plans for third party apps20:12
meetingologyACTION: rbasak to follow up on finding consensus on question of test plans for third party apps20:12
seb128ACTION: rbasak to open wider discussion on third-party repo policy20:12
rbasakSame20:12
seb128#action rbasak to open wider discussion on third-party repo policy20:12
meetingologyACTION: rbasak to open wider discussion on third-party repo policy20:12
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_Delegations20:12
seb128carrying over that one also20:12
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_Delegations20:12
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:12
seb128#action vorlon to write up draft guidelines for packages in the archive that download from the Internet20:13
meetingologyACTION: vorlon to write up draft guidelines for packages in the archive that download from the Internet20:13
seb128I'm carrying that one over since I didn't see an update and Steve is not here20:13
seb128ACTION: seb128 to follow-up with ubuntu cinnamon on 24.04 request20:13
seb128I didn't see a reply, I need to nudge them so I'm carrying it over20:14
seb128#action seb128 to follow-up with ubuntu cinnamon on 24.04 request20:14
meetingologyACTION: seb128 to follow-up with ubuntu cinnamon on 24.04 request20:14
seb128ACTION: sil2100 to send confirmation of successful LTS status for Ubuntu Studio 24.0420:14
seb128that's done, https://lists.ubuntu.com/archives/technical-board/2024-January/002846.html20:15
sil2100Done!20:15
sil2100Indeed20:15
seb128good to have one item done :)20:15
seb128ACTION: amurray to send confirmation of successful LTS status for Edubuntu 24.0420:15
seb128https://lists.ubuntu.com/archives/technical-board/2024-January/002845.html20:16
seb128done20:16
sil2100;) I think amurray did his as well!20:16
seb128indeed!20:16
amurrayyep20:16
seb128ACTION: seb128 to follow-up with ubuntu budgie on 24.04 request20:16
seb128I didn't get a reply here either so need to nudge them20:16
seb128#action seb128 to follow-up with ubuntu budgie on 24.04 request20:16
meetingologyACTION: seb128 to follow-up with ubuntu budgie on 24.04 request20:16
seb128ACTION: amurray to follow-up with ubuntu kylin on 24.04 request20:16
seb128that happened as well I think?20:17
amurraysorry I think I need to carry this over20:17
seb128https://lists.ubuntu.com/archives/technical-board/2024-January/002844.html ?20:17
seb128or was there another follow up needed?20:17
amurraygah yes I forgot20:17
seb128I overlooked that in my backlog, I will add my vote after the meeting20:18
sil2100I think I did vote, right?20:18
seb128yes, and Steve20:18
seb128I'm going to send my +1 in a bit20:19
seb128amurray, I'm giving you an action item to send the confirmation of the vote result then if that's ok?20:19
amurrayyes thats fine20:19
seb128#action amurray to send confirmation of successful LTS status for Ubuntu Kylin 24.0420:19
meetingologyACTION: amurray to send confirmation of successful LTS status for Ubuntu Kylin 24.0420:19
seb128#topic Scan the mailing list archive for anything we missed (standing item)20:20
seb128https://lists.ubuntu.com/archives/technical-board/2024-January/date.html20:20
tsimonq2o/ :)20:20
seb128we have a request from Lubuntu to be LTS20:20
seb128https://lists.ubuntu.com/archives/technical-board/2024-January/002849.html20:21
sil2100Since I finished mine, maybe I could get assigned to it then20:22
seb128sil2100, what would be the action item?20:22
seb128the request seems reasonable so maybe we just need to vote?20:22
sil2100We can, but I didn't read it! Yet20:22
seb128sil2100, but thanks, let me add an action to review and call for a vote?20:23
seb128#action sil2100 to review the lubuntu LTS participation request and follow up as appropriate (question or call for vote)20:23
meetingologyACTION: sil2100 to review the lubuntu LTS participation request and follow up as appropriate (question or call for vote)20:23
tsimonq2I'm happy to answer any questions here or at a later point about Lubuntu's application. :)20:23
seb128sil2100, ^ sounds fine?20:23
sil2100Looks fine o/ Are you and amurray ready to vote as is?20:24
amurrayyes20:24
seb128I want to read the emails again since I only glanced over them but it feels like it is ready20:24
seb128let's just do a call for vote on the list rather than trying to do it here today20:25
seb128did any of you had questions here today for tsimonq2 since he joined the meeting for us?20:25
sil2100I'm leaving it up to you. I'd like someone to do a proper review of it - if someone already did it, I'm fine with voting20:25
seb128no need to rush I would say20:26
amurrayno, his email is very detailed and covers everything I would have wanted to know20:26
seb128you have an action item20:26
seb128we can call for vote on the list once you have reviewed it20:26
seb128no question from me either20:26
sil2100Ok o/20:26
seb128tsimonq2, no question it seems but thanks for taking the time to join the meeting in case we had some20:27
seb128#topic Check up on community bugs and techboard bugs20:27
tsimonq2Hey, one more thing on this topic, briefly...20:27
seb128tsimonq2, sure?20:27
seb128(no activity on the community bugs and techboard bugs)20:28
tsimonq2Actually, two, sorry. I noted lack of cooperation generally speaking on that email, and I've seen a drastic change for the better. I still have some (genuine) questions around the SRU Team given recent events, but I'm planning a postmorteum on virtualbox anyway.20:28
tsimonq2Also, I appointed Aaron and Dan as assistant release managers, there's no direct action required from the TB, but a "hey we see this" would be great. :)20:29
rbasakWell I asked and was told that no response was expected?20:29
tsimonq2Yes :) I'm glad you saw it, just making a general point to it.20:30
tsimonq2Anyway, those are the points I have, happy to answer any questions.20:30
seb128I'm not aware the SRU team situation you are referencing to but it doesn't seem to be a TB topic at this point?20:30
seb128aware of*20:31
rbasakI'm not sure either.20:31
tsimonq2My general point is, asking for requalification is a two-way agreement. We are happy to provide support for Lubuntu, the only reason I brought it up is to ensure we have support on the other side to be able to move the needle forward.20:32
seb128tsimonq2, and I've seen the email about the assistant release managers :-)20:32
tsimonq2seb128: thanks :)20:32
seb128ok, so seems there is no question/action there but thanks for mentioning those!20:32
tsimonq2Yes of course :)20:32
seb128#topic Select a chair for the next meeting (next from https://launchpad.net/~techboard/+members)20:32
rbasakI wonder if there's an opportunity to be talking more via the flavour syncs or something similar20:33
vorlonI promise I'll be here in time for the next one so you can keep me as chair ;)20:33
seb128next in the list is Steve and Lukasz as backup20:33
rbasakBecause I'm seeing noises, but without specifics, I'm not in a position to be able to help at all.20:33
seb128vorlon, hey, and thanks!20:33
seb128rbasak, yes, the flavor syncs is a good venue for project discussions with flavor20:35
seb128flavors20:35
tsimonq2As far as I'm aware, the TB has an open invite to the Flavor Syncs. If you talk to the Community Team (specifically ilvipero_), he should be able to get you an invite.20:35
seb128#topic AOB20:35
rbasakPlease do arrange for the SRU team and/or TB to be invited if there's a specific agenda item you have in mind that you'd like to discuss20:35
tsimonq2Absolutely, just finishing with my notes on this one. Thanks :)20:36
seb128I usually try to join at least the European tz compatible meeting and I think sil2100 has been to some of those as well20:36
rbasakI'm not aware of having been invited recently20:37
tsimonq2That sounds like a mistake to me :)20:37
seb128I think it's an open venue, ask Mauro to be added to the calendar invite if you wish to join20:37
seb128I usually join as a desktop representative, afaik we didn't have any formal request to have TB members there before20:38
seb128but I think we should at least review the invite list according to the topics on the agenda20:38
seb128that's not a meeting the TB own though, but I will still try to ensure we invite the right people20:39
NotEickmeyerJust pinged the appropriate people to get you all invites. :)20:39
=== NotEickmeyer is now known as Eickmeyer
seb128:)20:39
EickmeyerMy IRC client with issues. :)20:39
rbasakThanks!20:39
seb128ok, I think that should be enough for that topic then20:39
seb128another other topic?20:40
seb128giving 3 min and if not then it's a wrap20:40
tsimonq2rbasak: I understand it's an action item, but an additional poke on the DMB inactivity stuff :)20:41
amurraynothing from me20:41
tsimonq2I did get frightened for a minute at Aaron's MOTU meeting.20:41
* tsimonq2 is good20:41
rbasaktsimonq2: I've not been focused on that because it's usually worked out recently20:42
rbasakIf people start getting near the threshold then I'll definitely prioritise that20:42
tsimonq2Okay :)20:42
seb128alright, seems we are done then20:43
rbasakAlso it was very close to the New Year and I'd expect some disruption/unavailability around then.20:43
tsimonq2Very true.20:43
seb128thanks everyone!!20:43
seb128let's wrap?20:43
rbasakThe plans won't change that since it's only sustained absence that would be actionable20:43
tsimonq2I'm okay wrapping, I believe we're on the same page.20:44
seb128ok, it's a wrap then, thanks everyone!20:44
sil2100Yeah, I need to apologize for missing out many DMB meetings lately20:44
seb128#endmeeting20:45
meetingologyMeeting ended at 20:45:05 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2024/ubuntu-meeting.2024-01-16-20.04.moin.txt20:45
sil2100It's been so many Mondays that I just haven't been around20:45
sil2100o/20:45
amurrayo/20:45
seb128sorry for being half around in that DMB meeting, I was sick on that day but still joined to be able to have quorum but I didn't manage to stick around all the time20:45
Eickmeyerseb128: You came in clutch, so you're more than forgiven from all sides, I'm sure. :D20:46
seb128:-)20:46
tsimonq2Agreed :)20:46
Eickmeyerseb128: And never apologize for being sick. I've had to say that to subordinates I've had in the past.20:47
Eickmeyer(not that you're subordinate to me, but the point still stands)20:48

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