/srv/irclogs.ubuntu.com/2024/02/27/#ubuntu-meeting.txt

=== JanC is now known as Guest5782
=== JanC_ is now known as JanC
=== pushkarnk1 is now known as pushkarnk
=== pushkarnk1 is now known as pushkarnk
=== pushkarnk1 is now known as pushkarnk
=== pushkarnk1 is now known as pushkarnk
=== pushkarnk1 is now known as pushkarnk
=== pushkarnk1 is now known as pushkarnk
jbichao/15:28
eslermo/15:30
cpaelzerarrr15:30
cpaelzerI have a meeting running over15:30
cpaelzerI can read but might not be able to lead15:30
cpaelzeranyone up to jump in?15:30
cpaelzerpretty please?15:30
sarnoldgood morning15:30
slyonhey!15:30
slyonI can I guess...15:30
slyonlet me prepare some tabs15:30
joalifo/15:30
jamespageo/15:31
slyon#startmeeting Weekly Main Inclusion Requests status15:31
meetingologyMeeting started at 15:31:20 UTC.  The chair is slyon.  Information about MeetBot at https://wiki.ubuntu.com/meetingology15:31
meetingologyAvailable commands: action, commands, idea, info, link, nick15:31
slyonPing for MIR meeting - didrocks joalif slyon sarnold cpaelzer jamespage ( eslerm dviererbe )15:31
slyon#topic current component mismatches15:31
slyonMission: Identify required actions and spread the load among the teams15:31
slyon#link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg15:31
slyon#link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg15:31
slyonnon-proposed looking clean15:31
slyon-proposed is known AFAICT, except for openjdk-2115:32
slyonFor openjdk-21 we need to demote the -doc binary. cpaelzer could you do that (later)?15:32
slyonThat's how it had been handled in the past15:32
slyon#topic New MIRs15:33
slyonMission: ensure to assign all incoming reviews for fast processing15:33
slyon#link https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-date_last_updated&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&assignee_option=none&field.assignee=&field.subscriber=ubuntu-mir15:33
slyonbug #205448015:33
-ubottu:#ubuntu-meeting- Bug 2054480 in nbd (Ubuntu) "[MIR] nbd-client" [Undecided, New] https://launchpad.net/bugs/205448015:33
didrocks(I’m around today, but in meetings)15:33
slyonAny volunteers to review ^ ?15:34
didrocksI’m happy to take any MIRs, I can’t sign off they will be done next week though, I’ll aim for the next next one15:34
didrocksof*15:34
joalifi can take the simple-perl15:34
slyonsimple-perl is done already AFAIC.15:35
didrocksit doesn’t seem there is due date for ndb, so I can it15:35
didrockstake*15:35
slyonthanks, assigning to didrocks15:35
jamespagethat ndb one is odd - its a binary only promotion for a package already in main15:35
jamespageso that might be super-easy!15:35
jamespagenbd rather...15:36
jamespageI also typo that15:36
slyonindeed. it's well written too, so let's see what remarks are given15:36
slyonmoving on... bug #205448015:36
-ubottu:#ubuntu-meeting- Bug 2054480 in nbd (Ubuntu) "[MIR] nbd-client" [Undecided, New] https://launchpad.net/bugs/205448015:36
slyonopps.15:36
slyonbug #202937915:36
-ubottu:#ubuntu-meeting- Bug 2029379 in libdbd-sqlite3-perl (Ubuntu) "[MIR] promote libdbd-sqlite3-perl (libmail-dmarc-perl dependency)" [Undecided, New] https://launchpad.net/bugs/202937915:37
joalifthat also has a review15:37
slyonit seems ready, except for the team subscription. Can you confirm this joalif ?15:38
slyonSo I'd move it to "In Progress"15:38
joalifyup that's correct15:38
slyonbug #203149115:39
cpaelzerI can fix the subscription right now15:39
-ubottu:#ubuntu-meeting- Bug 2031491 in libemail-simple-perl (Ubuntu) "[MIR] libemail-simple-perl ( libemail-mime-perl dependency as libmail-dmarc-perl dependency)" [Undecided, New] https://launchpad.net/bugs/203149115:39
slyonsame here, we have the condicinal ACK and the duplication concern was addressed15:40
slyonalready subscribed, too15:40
slyonlet's move it forward15:40
slyonbug #205516515:41
-ubottu:#ubuntu-meeting- Bug 2055165 in gcr4 (Ubuntu) "Move gcr4 to main" [Undecided, New] https://launchpad.net/bugs/205516515:41
jbichahi15:41
jbichawe're wondering if we can avoid the whole MIR process for gcr415:42
slyonjbicha: hey! Are there major code changes between gcr and gcr4? Or should it be considered a "versioned package upgrade", that does not need MIR, but just AA approval?15:42
cpaelzerFYI: subscription on libdbd-sqlite3-perl added15:43
sarnoldI don't understand quite what that first paragraph is saying; if gcr doesn't include gui widgets, why do we need a separate version for gtk4?15:43
jbichagtk4 apps couldn't use libgcr-ui-3-1 anyway because of its gtk3 dependency. gcr devs also chose to make some other api changes at the same time15:45
slyonjbicha: is gcr4 a continuation of the gcr codebase?15:45
jbichaslyon: yes!15:45
jbichait's still https://gitlab.gnome.org/GNOME/gcr15:46
cpaelzerusually versioned transitions can have some overlap, but eventually resolve. Is this expected to only have gcr4 at some point, if so when?15:46
slyonI'd assume that depends on GTK3 usage in main..?15:46
jbichaI can't give you an exact time since seahorse & shotwell are undermaintained & porting to gtk4 is a lot for big apps15:47
cpaelzerI see, so it really is once all GTK3 in main are gone some day15:47
jbichathe old gcr will be in universe for a long time15:47
jbichayes15:47
seb128hey there, sorry I wanted to join but I've another call at the same time and forgot to /j on IRC15:47
cpaelzerI'm personally fine with that TBH15:48
seb128jbicha, thanks for covering for desktop :)15:48
slyonConsidering it's a versioned transition and we have precedence for parallel GTK3 & GTK4 I'm +1 on promoting this. But I'd like to defer to cpaelzer and/or didrocks for a final decision, with their AA hats on15:48
cpaelzerI'm +1 as well, with a twist (not too bad one, let me write ...)15:48
didrocksI don’t think that’s much different from gtk3 -> gtk4. It would have been a good time for reviewing the package and how we can improve it, but I don’t think this is doable in a realistic timeframe15:49
cpaelzerI haven't had a look, but is it reasonable to ask for improved testing and quality15:49
cpaelzerotherwise we have to wait for GTK5  :-)15:49
cpaelzerOTOH I totally see hwo time runs out for that15:49
cpaelzergiven that it is the same as before but newer I'm +1 even without, but couldn't resist asking for some QA and testing eyes15:50
slyonLet's make improved/non-superficial autopkgtest a recommendation, then?15:50
cpaelzerslyon: yeah, that15:50
seb128+1, we can card that on our backlog, not going to happen for feature freeze though :)15:50
cpaelzerthat is ok as a compromise - if it is before final freeze (vs the backlog being 234235346345 items long)15:51
slyonI updated the case on LP. status: Fix Committed15:51
cpaelzerthanks15:51
slyon#topic Incomplete bugs / questions15:52
slyonMission: Identify required actions and spread the load among the teams15:52
slyon#link https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-date_last_updated&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.subscriber=ubuntu-mir15:52
slyonbug #202397115:52
-ubottu:#ubuntu-meeting- Bug 2023971 in libmail-dmarc-perl (Ubuntu) "[MIR] libmail-dmarc-perl" [High, Incomplete] https://launchpad.net/bugs/202397115:52
slyonseems to be a tracking update (cc joalif)15:53
slyonbug #205185015:53
-ubottu:#ubuntu-meeting- Bug 2051850 in trace-cmd (Ubuntu) "[MIR] trace-cmd" [Undecided, Incomplete] https://launchpad.net/bugs/205185015:53
slyonhere we're waiting on implementation of required TODOs by foundations15:54
slyonbug #205191615:54
-ubottu:#ubuntu-meeting- Bug 2051916 in libtraceevent (Ubuntu) "[MIR] promote libtraceevent as a trace-cmd dependency" [Undecided, Incomplete] https://launchpad.net/bugs/205191615:54
eslerm(I'm planning to do the trace-cmd audit early)15:54
slyonI've been working with upils actively to move this forward. There are still some issues with testing on s390x. To be resolved soon15:54
slyonthanks eslerm15:54
slyonbug #205192515:55
-ubottu:#ubuntu-meeting- Bug 2051925 in libtracefs (Ubuntu) "[MIR] promote libtracefs as a trace-cmd dependency" [Undecided, Incomplete] https://launchpad.net/bugs/205192515:55
slyonsimilar to the previous bug. We have a patch that needs review and sponsoring. not actionable for MIR team15:55
slyonbug #204878115:56
-ubottu:#ubuntu-meeting- Bug 2048781 in authd (Ubuntu) "[MIR] authd" [Undecided, Incomplete] https://launchpad.net/bugs/204878115:56
cpaelzeron this very topic of the production-tools related MIRs15:56
cpaelzerI have ruled out two cases with  a pre-review, they will never hit the MIR queue15:56
slyonyes, there's overall quite some frustration about the perf tools MIRs, as the packages are not in very good shape15:56
cpaelzerthey are in much better shape than those I eliminated upfront15:57
slyonok15:57
cpaelzerTL;DR: I've drawn a line for some to be ok to match what common documentation mentioned, but need to stay in universe15:57
cpaelzerso meta package cahnges to get them easy : yes - full main approval - no15:57
cpaelzersorry to distract, keep goin15:57
cpaelzerg15:57
slyonjoalif: should bug #2048781 be status: New to make it into the security-review list?15:58
-ubottu:#ubuntu-meeting- Bug 2048781 in authd (Ubuntu) "[MIR] authd" [Undecided, Incomplete] https://launchpad.net/bugs/204878115:58
joalifslyon: sorry in 2 meetings checking15:58
slyonI see no required TODOs there15:58
slyonmoving on in parallel, feel free to give your comment later on15:59
slyon#topic Process/Documentation improvements15:59
slyonMission: Review pending process/documentation pull-requests or issues15:59
joalifslyon I think it's already in securitiy-review list15:59
slyon#link https://github.com/canonical/ubuntu-mir/pulls15:59
slyon#link https://github.com/canonical/ubuntu-mir/issues15:59
slyonjoalif: OK, setting to "Confirmed" then15:59
slyonSimple typo fix https://github.com/canonical/ubuntu-mir/pull/5015:59
-ubottu:#ubuntu-meeting- Pull 50 in canonical/ubuntu-mir "fix(typo) external endpoint exposed case" [Open]15:59
cpaelzerfeel free to merge16:00
eslermone issue to raise within the base-sets issue also16:00
slyonWill double-check and merege after the meeting.16:00
eslermwithin the authd MIR, there are comments about windows crates being vendored16:00
slyoneslerm: your comment from December?16:00
eslermthis is related to https://github.com/canonical/ubuntu-mir/issues/35#issuecomment-185932567116:00
-ubottu:#ubuntu-meeting- Issue 35 in canonical/ubuntu-mir "RFC: Introduce 'base-sets' for vendored dependencies" [Open]16:00
eslermyes16:01
eslermplease see comment #11 from authd as well16:01
eslermI'm not sure where to take this issue beyond here16:01
slyonI guess there are some hints in https://wiki.ubuntu.com/RustCodeInMain how to mangle the unneeded crates manually..16:02
sarnoldthat's for mangling, does it also work for deleting?16:03
eslermin the best case, that is manual work for each package16:04
eslermI'm not sure how well rerunning `crate vendor` works16:04
slyonYes, I think it's manual work. The package should have some script to drop unneeded stuff and mangle the manifest accordingly16:04
eslermand it would be ongoing manual work16:05
slyonI think longer term we'd need upstream toolchain support to vendor only the necessary deps16:05
slyonbut that's not something that we have right now.16:06
eslermI have links to upstream comments16:06
didrocksyeah, I think that should be done centrally, at worst, in the packaging tooling then16:06
eslermin the MIR and issue thread16:06
didrocksotherwise, everyone will have different ways of doing it, hard to update and so on16:06
eslermthis is out of scope for cargo upstream, a thirdparty lint is likely needed16:06
slyonI can put it into the Foundations/Toolchain squad's backlog for review during next roadmap planning16:07
sarnoldthanks16:07
eslermthank you !16:07
slyon#topic MIR related Security Review Queue16:07
slyonMission: Check on progress, do deadlines seem doable?16:08
slyonSome clients can only work with one, some with the other escaping - the URLs point to the same place.16:08
didrockssounds perfect!16:08
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-mir16:08
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-mir16:08
slyonInternal link16:08
slyon#link https://warthogs.atlassian.net/jira/software/c/projects/SEC/boards/59416:08
slyonsarnold: eslerm: what are the security-review updates?16:08
sarnoldprogress is progressing :)16:08
eslermwe're fairly caught up. we're expecting MIRs for tracing and perl to land in our queue soon16:09
slyonsounds good. Let's move on as we're already overtime. All pending/ready MIRs seem to be in the queue16:09
slyon#topic Any other business?16:10
eslermdbus-broker is very close16:10
slyonIs there still a change to do the dbus-broker switch in noble (cc seb128)?16:10
slyonchance*16:10
slyonI mean, it would be great the have the MIR and security review ready anyway16:11
slyonso we can to the change whenever needed16:11
slyonDo we have anything else?16:11
eslermnot from me16:12
slyonsorry for running late! o/16:12
slyon#endmeeting16:12
meetingologyMeeting ended at 16:12:44 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2024/ubuntu-meeting.2024-02-27-15.31.moin.txt16:12
sarnoldnothing here16:12
joalifthanks slyon, all :)16:12
sarnoldthanks slyon, all :)16:12
eslermthanks everyone o/16:13
slyoncpaelzer: maybe you could look into demoting openjdk-21-doc?16:14
seb128slyon, sorry, I was off for one week and struggling to catchup/get things in Noble for feature freeze atm16:22
seb128slyon, I don't really understand what changed of dbus-broker, the dbus-run-session equivalent feature is being worked by someone upstream but doesn't seem at the point of being merged yet16:24
seb128of->for16:24
seb128which means we can't demote src:dbus16:24
seb128which is what is the basis on which the MIR team nacked the request previous cycles16:24
slyonseb128: sure, I can fully understand that. Considering that things are moving in the right direction (security review progressing, upstream work on the dbus-run-session equivalent), I was just wondering if there are any plans to make that switch for 24.04?16:25
seb128I would love to see that happen but it doesn't seem like things align enough for it?16:26
slyonseb128: I think most recent discussions (from last week? https://bugs.launchpad.net/ubuntu/+source/dbus-broker/+bug/2015538/comments/19) revealed that we'd be willing to have it split into individual binary packages. So that src:dbus and src:dbus-broker could be in main at the same time, but only with the relevant binary packages (dbus-broker daemon + dbus policy)16:26
-ubottu:#ubuntu-meeting- Launchpad bug 2015538 in dbus-broker (Ubuntu) "[MIR] dbus-broker" [Undecided, Incomplete]16:26
seb128slyon, we had that discussion at the time we had the first review round iirc, but someone pointed out (mdeslaur?) back then that dbus-run-session depends on the dbus service16:28
seb128I didn't have the free slots to read the code to see if that's true16:28
seb128but assuming that's a true fact it means we can't do the split/demote dbus service thing16:28
seb128if I understand correctly what you want to split (dbus-session-run in main, dbus in universe, right?)16:29
slyonI think the idea was to get the upstream dbus-broker dbus-run-session equivalent integrated, so that we could demote dbus and dbus-run-session to universe, while keeping the src:dbus policy bits, which are not shipped by dbus-broker on purpose.16:31
slyonBut doing that split and integration work would need somebody with capacity to drive it16:31
slyoncomment #17 also suggest that there is no such hard dependency, which would give even more options: "In Debian we just keep both, dbus-run-session from the src:dbus package works just fine, and it can be installed in parallel without any issues when somebody needs it. So it doesn't seem to me that you need that separate implementation?"16:33
slyonBut it needs checking the details16:33
seb128slyon, ack, thanks for the details16:35
seb128it's on my backlog, I doubt I will get to it this week though but I'm still interested, maybe we manage to squeeze a ffe next week for it if things turn out to not be too complicated16:35
seb128the fact that the new binary is written in rust is annoying it means it's not a simple patch to drop it16:36
cpaelzerslyon: I could demote it, but this needs an extra exclude or it would come just back17:35
cpaelzerslyon: it only has https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/tree/supported#n21417:36
slyoncpaelzer: good catch! I'll work on that18:05
sil2100o/20:00
rbasako/20:00
vorlontime_t, everybody20:00
vorlontime_t?20:00
vorlonoh sorry, where am I again20:00
sil2100Ahahah20:00
sil2100Okay, I see I'm the chair20:00
sil2100Let me start this one then, give me 1 minute20:01
sil2100#startmeeting Ubuntu Technical Board20:01
meetingologyMeeting started at 20:01:39 UTC.  The chair is sil2100.  Information about MeetBot at https://wiki.ubuntu.com/meetingology20:01
meetingologyAvailable commands: action, commands, idea, info, link, nick20:01
sil2100#topic Apologies20:01
sil2100amurray sent his apologies for having to miss the meeting20:02
sil2100#topic Action review20:02
sil2100ACTION: seb128/amurray/sil2100 to help drafting the snap-store Ubuntu-specific tracks usage20:02
sil2100There's no update from me here, not sure about seb128 or amurray, so let's just carry over for now20:02
rbasakI've been ill so haven't made any progress list last time, sorry.20:03
rbasakI was going to try and set up a higher bandwidth meeting to try to catch up on the third party repo req. stuff20:03
sil2100Let me carry over those then, no worries!20:03
sil2100#action seb128/amurray/sil2100 to help drafting the snap-store Ubuntu-specific tracks usage20:03
meetingologyACTION: seb128/amurray/sil2100 to help drafting the snap-store Ubuntu-specific tracks usage20:03
sil2100#action seb128 to organize a meeting to unblock the draft of the tracks usage section20:03
meetingologyACTION: seb128 to organize a meeting to unblock the draft of the tracks usage section20:03
sil2100#action rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification20:03
meetingologyACTION: rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification20:03
sil2100#action rbasak to follow up on finding consensus on question of test plans for third party apps20:04
meetingologyACTION: rbasak to follow up on finding consensus on question of test plans for third party apps20:04
sil2100#action rbasak to open wider discussion on third-party repo policy20:04
meetingologyACTION: rbasak to open wider discussion on third-party repo policy20:04
sil2100#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:04
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:04
sil2100So, regarding this one:20:04
sil2100ACTION: seb128 to follow-up with ubuntu cinnamon on 24.04 request20:04
sil2100Does anyone remember if that happened?20:04
* sil2100 looks at the ML20:04
sil2100I guess not20:05
seb128hey, sorry for being late, evening rush time here20:05
tsimonq2Eickmeyer and I have been interfacing with ItzSwirlz on this front.20:05
sil2100seb128: o/20:05
seb128sil2100, no, none of my action moved, sorry20:05
seb128I was on holidays one week and now it's feature freeze coming20:05
seb128I will try to catch up next week and get things moving by the next meeting20:05
sil2100seb128: do you need help with that one? I could also take a look at it, since I know many teams might be at capacity due to FF20:05
sil2100Either way, for now carrying over!20:06
sil2100#action seb128 to follow-up with ubuntu cinnamon on 24.04 request20:07
meetingologyACTION: seb128 to follow-up with ubuntu cinnamon on 24.04 request20:07
sil2100ACTION: vorlon to look into scripting for packages in flavor-specific overlays20:07
sil2100vorlon: ^ ?20:07
vorlonsorry, not yet done20:07
sil2100I guess time_t..?20:07
vorlonyeah ;)20:07
sil2100time_t ;)20:07
seb128sil2100, no it's fine but thanks, I will catch up next week :)20:07
sil2100#action vorlon to look into scripting for packages in flavor-specific overlays20:07
meetingologyACTION: vorlon to look into scripting for packages in flavor-specific overlays20:07
sil2100seb128: excellent!20:07
sil2100ACTION: vorlon to follow up on xnox's request to set noble.publish_i18n_index to False20:07
vorlondone20:08
sil2100vorlon: didn't follow that one too closly - I guess it happened?20:08
sil2100\o/20:08
sil2100Okay, that's all action items from our list for now20:08
sil2100#topic Scan the mailing list archive for anything we missed (standing item)20:08
sil2100I don't see anything really20:09
sil2100Can someone else confirm that I didn't miss anything?20:09
sgmooreIs this the right place to ask about Kubuntu LTS requalification?20:09
sil2100sgmoore: sure! Let me just move to AOB20:10
sil2100#topic Check up on community bugs and techboard bugs20:10
sil2100...none!20:10
sil2100#topic AOB20:10
sil2100sgmoore: the floor is yours o/20:10
vorlonI'm not sure whether kubuntu LTS qualification is blocked on me providing scripts for a saner view of the "what packages is kubuntu committing to support" question20:10
tsimonq2I think given the scale of the Kubuntu packageset, if the TB is wanting to block on a more concise packageset list, then yes. :)20:11
rbasakML thread "Upload of translation files" -> I just replied to redirect them to ubuntu-translators@. Hopefully that's helpful, though with Gunnar gone I'm not sure who's left :-(20:11
vorlonthe thread had gone in that direction but maybe we just need to have that information available and don't need to consider it a blocker?20:11
sgmooreI know we need a proper packageset, but other than that, how are we looking :) I am working hard on getting a spectacular release ready :)20:11
vorlonrbasak: :/20:11
seb128rbasak, I think I'm the only standing member left to deal with some of those translations things :/20:13
seb128I need to sort that out somehow and find other people to involve20:14
seb128if anyone is reading and want to help with translations please msg me20:14
vorlonsgmoore: so I guess amurray who isn't here today was on point for driving the Kubuntu discussion.  I'll work on getting my action item sorted one way or the other so we can have a sane conversation about a packageset. From my perspective personally, that shouldn't be a blocker for LTS qualification but amurray will need to call the vote20:15
sil2100The only thing I can commit to, sadly, is operating the machinery20:15
rbasakseb128: IMHO, you should "close" those MLs and venues and bring everything into one place - ubuntu-devel@, or Discourse. It's not like we're going to be swarmed by traffic. Otherwise everyone assumes that there's a team somewhere that's running just fine.20:15
sgmoorevorlon: Fair enough :)20:15
seb128rbasak, the issue is that those lists are contact point for role-accounts on launchpad20:16
sil2100sgmoore: out of curiosity, maybe composing a list of packages that you and your team worked on in the last 6 months when working on Kubuntu would be a start20:17
sgmooreI only just started back with Kubuntu a few weeks ago.20:17
seb128rbasak, I could set e.g devel but that doesn't resolve the issue than in practice the only admin in the team able to do the action is me20:17
seb128(or maybe launchpad admins or some other admin groups, I don't remember the details and didn't go check)20:18
tsimonq2sgmoore: I'll happily walk through UDD with you if you find it helpful :)20:18
sgmooreI find any new knowledge helpful lol20:18
tsimonq2Okay, will follow up with you after the meeting20:19
sgmooresounds good thanks!20:19
sil2100Okay, any other business?20:20
sil2100Out of curiosity, with part of my release team hat on...20:21
seb128nothing from me20:22
sil2100Does anyone have contact with the Ubuntu Mate developers?20:22
seb128sort of20:22
vorlonit doesn't appear they've applied yet for 24.04 LTS qual20:23
sil2100Just asking since I noticed they were a bit absent from .420:23
sil2100Anyway, guess that's not a TB-topic per-se20:23
sil2100#topic Select a chair for the next meeting20:24
seb128I will give a ping to Martin just to ask20:24
sil2100...okay, how is this chair selection working20:25
sil2100Since none of the sorting of TB members results in the current order for me20:25
vorlonhttps://launchpad.net/~techboard/+members lists you last and Alex next after wrapping around20:25
seb128sil2100, you got rescheduled for missing your previous chair so that confused the logical order20:26
sil2100Yes, so how come rbasak was the backup today20:26
sil2100Aaah20:26
seb128:)20:26
sil2100Okay, so next chair will be amurray, backup rbasak20:26
sil2100Thank you everyone!20:27
sil2100#endmeeting20:27
meetingologyMeeting ended at 20:27:16 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2024/ubuntu-meeting.2024-02-27-20.01.moin.txt20:27
vorlonthanks!20:27
seb128thanks sil2100 for the chairing and doing in an efficient way, always good to not spend longer that needed in meetings during the rush times :)20:28
sil2100yw!21:29
amurraysgmoore: re Kubuntu LTS - I agree with vorlon, resolving the packageset is not a blocker for LTS qualification, so will call for a vote via the mailing list today - let me know though how you go with manually defining the packageset as suggested by sil2100 / tsimonq223:11

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