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

=== JanC is now known as Guest8158
=== JanC_ is now known as JanC
=== pushkarnk1 is now known as pushkarnk
=== JanC_ is now known as JanC
=== pushkarnk1 is now known as pushkarnk
=== pushkarnk1 is now known as pushkarnk
=== cpaelzer_ is now known as cpaelzer
cpaelzerslowly lighting a MIR campfire ...15:21
* eslerm warms up15:28
jbichao/15:30
cpaelzerhehe15:30
cpaelzer#startmeeting Weekly Main Inclusion Requests status15:30
meetingologyMeeting started at 15:30:54 UTC.  The chair is cpaelzer.  Information about MeetBot at https://wiki.ubuntu.com/meetingology15:30
meetingologyAvailable commands: action, commands, idea, info, link, nick15:30
cpaelzerPing for MIR meeting - didrocks joalif slyon sarnold cpaelzer jamespage ( eslerm dviererbe )15:31
cpaelzer#topic current component mismatches15:31
slyono/15:31
cpaelzerMission: Identify required actions and spread the load among the teams15:31
cpaelzer#link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg15:31
cpaelzer#link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg15:31
jamespageo/15:31
sarnoldgood morning15:31
slyonnullboot and python-cssselect should be ready15:31
cpaelzerlet us cheeck15:31
cpaelzerthey are approved at least by the color15:32
slyonyes, that's what I did earlier today :)15:32
slyonbesides those, kexec-tools looks new to me15:32
cpaelzeryes, they can be promoted15:32
cpaelzerI'll do so tomorrow if no one beats me to it15:32
slyonthanks!15:32
sarnoldi'm surprised the kexec-tools owner is ~canonical-ubuntu-qa15:33
sarnoldI expected kernel team ;)15:33
cpaelzerit is the kernel team15:33
sarnold(maybe foundations..)15:33
slyonIt shows ~kernel-packages for me15:33
cpaelzerhttp://reqorts.qa.ubuntu.com/reports/m-r-package-team-mapping.html15:33
cpaelzersome are subscribed by multiple which breaks some checks15:33
sarnoldaha15:33
slyonbut yes, QA is subscribed, too15:34
sarnoldI was going by bug subscribers https://launchpad.net/ubuntu/+source/kexec-tools15:34
cpaelzerthis is added in kexec-tools (1:2.0.25-1)15:34
cpaelzer  * Added build dependency on libxen-dev so kexec would work on xen15:34
cpaelzer    (Closes: #1023270)15:34
cpaelzerthe merge didn't revert that change and made it Ubuntu delta kexec-tools (1:2.0.28-0ubuntu1)15:34
cpaelzerbut probably needs to15:34
cpaelzerWe lack a kernel person to ping15:35
cpaelzerlet me see who uploaded that ...15:35
cpaelzerhttps://launchpad.net/ubuntu/+source/kexec-tools/1:2.0.28-0ubuntu115:35
cpaelzerxnox: did15:35
cpaelzerhi xnox, do you think we should remove the recommends to xen from kexec-tools or do you want to pursue this in any other way?15:35
cpaelzerThe rest of the component mismatches are known cases that are being worked on or false-positives15:36
cpaelzer#topic New MIRs15:36
cpaelzerMission: ensure to assign all incoming reviews for fast processing15:36
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:36
cpaelzerThere are two more from the production/crisis-tools set15:36
cpaelzerwe last week consumed three of them, some already done some still in flight15:36
slyonI can take one of the desktop MIRs15:37
cpaelzerhanding you the snapshot15:38
slyonack15:38
cpaelzerhmm15:39
cpaelzerhard to spread the others15:40
cpaelzerjamespage: can I pass you one as well today?15:40
cpaelzerto balance the load?15:40
eslermbpf bugs mention they are WIP, but the outstanding issues seemed small enough that I encourged submitting them (missing unit tests)15:40
cpaelzerjoalif: seems not to be here yet but last week had already a second assigned - so probably full too15:40
cpaelzerI completed mine this morning (last minutes)15:41
cpaelzerThere are two ways we can do this15:41
eslermI wouldn't mind foing a review for the MIR team if that is okay15:41
eslermdoing*15:41
joalifsorry I am here but at 2 mtgs in teh same time and didnt say hi15:41
cpaelzerhehe15:41
cpaelzernp joalif, how possible or not is it to take another reivew?15:41
joalifIf you cannot find anyone else assign a bug to me but then again no promises for next week15:41
cpaelzerjoalif: as long as not all of them are piling up and are done never it is ok to take a while each15:42
jamespagecpaelzer: yep15:42
joalifok then15:42
cpaelzerI assigned langtable to joalif15:42
cpaelzerthanks jamespage - giving you bpftrace15:42
joalifack15:42
cpaelzerand myself taking bpfcc15:42
jamespageta15:43
cpaelzerThat clears the list15:43
cpaelzerto all of us, good luck in finding an efficient review time15:43
cpaelzer#topic Incomplete bugs / questions15:44
cpaelzerMission: Identify required actions and spread the load among the teams15:44
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:44
cpaelzerok we see the libtrace* things going back15:44
cpaelzermostly being great and ok actually, but missing some better QA15:45
cpaelzerone done by didrocks, one by me15:45
slyoncc upils: ^15:45
cpaelzerslyon: of the team prefers, there is the option to do autopkgtests once and awesome just on the high level15:45
cpaelzerI suggested to that in my review15:45
cpaelzerlike15:46
cpaelzera) get the build time tests to be better, seems didrocks found the same in his review15:46
cpaelzerbut also15:46
cpaelzerb) autopkgtests are weak15:46
cpaelzerbut for (b)15:46
cpaelzerthat can be done in-pkg15:46
cpaelzeror it can be done on the level that pulls it in, which here is trace-cmd15:46
cpaelzerthere is might be easier to write non trivial tests15:46
cpaelzerand if made sure that this uses both libs, that might be adressing 3-for-115:47
cpaelzerall other incomplete cases in this list are much older15:47
slyonright. This is for upils to look into. Potentially doing proper autopkgtests for trace-cmd only15:47
sarnoldtracing the autopkgtest runner kernels might be a challenge15:47
cpaelzeryeah slyon, if done right that would cover all three at once15:47
cpaelzersarnold: we have testcases which spawn VMs to have control and avoid weird effects15:47
cpaelzerthis could be another one of those15:48
cpaelzermark them big to have enough mem/cpu and set it up that way15:48
tsimonq2o/ MIR team! Sorry to butt in, I just wanted to bring this to your attention: https://tracker.debian.org/news/1493585/accepted-ubuntu-dev-tools-0198-source-into-unstable/ - I am quite happy to accept any feedback if you have it. :)15:48
cpaelzernot saing it has to be that way, but it helps to have control and avoid flakyness15:48
cpaelzerhi tsimonq2, you are totally fine to interrupt15:48
cpaelzerhaving a look ...15:48
tsimonq2Those are just some slight tweaks I found useful for check-mir. Anyone in ~ubuntu-dev is welcome to upload to ubuntu-dev-tools in Debian as a team upload.15:49
sarnoldcool :)15:49
cpaelzertsimonq2: thanks15:49
slyontsimonq2: without looking at the code, those sound like very useful additions! thanks :)15:50
tsimonq2My pleasure. :)15:50
cpaelzerok, getting to git next15:50
cpaelzerwe had landed some15:50
cpaelzerlet us look at the queues15:50
cpaelzer#topic Process/Documentation improvements15:50
cpaelzerMission: Review pending process/documentation pull-requests or issues15:50
cpaelzer#link https://github.com/canonical/ubuntu-mir/pulls15:50
cpaelzer#link https://github.com/canonical/ubuntu-mir/issues15:50
upilshi. thanks for the suggestion. This approach is new to me to I will probably ping some of you at some point for some details in the implementation. I have no idea how much work this is.15:50
upils*so I will15:51
cpaelzeronly the old "need to work on it once we have time" cases on github15:51
cpaelzerok upils, that is only fair15:51
cpaelzerthanks for driving this15:51
cpaelzeryou might look at other tests doing that, I think systemd does - any others one immediately remembers?15:51
upilsnot quite sure I will have time to work on it this week but maybe next one15:52
cpaelzersure upils, while we should try to avoid getting too late - promotions/demotions are not strictly bound by feature freeze15:53
cpaelzerbetter go slow and do it right if in doubt (as long as we do not miss noble)15:53
cpaelzer#topic MIR related Security Review Queue15:53
cpaelzerMission: Check on progress, do deadlines seem doable?15:53
cpaelzerSome clients can only work with one, some with the other escaping - the URLs point to the same place.15:53
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:53
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:53
sarnold(but due keep in mind that the MIR has to be assigned ot security before the beta freeze to avoid extra paperwork)15:54
cpaelzerInternal link15:54
cpaelzer- ensure your teams items are prioritized among each other as you'd expect15:54
cpaelzer- ensure community requests do not get stomped by teams calling for favors too much15:54
cpaelzer#link https://warthogs.atlassian.net/jira/software/c/projects/SEC/boards/59415:54
slyonbug #2052495 is ready for security review15:54
-ubottu:#ubuntu-meeting- Bug 2052495 in wsl-pro-service (Ubuntu Noble) "[MIR] wsl-pro-service" [Undecided, Confirmed] https://launchpad.net/bugs/205249515:54
sarnoldpro on wsl, interesting :)15:54
sarnoldat the moment things feel like we've got a decent handle on the list of outstanding mirs15:55
cpaelzerack sarnold, there are time limits for sure15:55
cpaelzerand pro on wsl is not only interesting it is also great :-)15:56
cpaelzerwill you add it to the jira board?15:56
upilsack cpaelzer sarnold, that should be manageable before Beta Freeze I think15:56
sarnoldyeah, we'll add it15:56
cpaelzerthanks15:57
cpaelzerthe rest on the board looks sane15:57
cpaelzerglad to see that15:57
cpaelzer#topic Any other business?15:57
cpaelzernot from me15:58
slyonnothing here15:58
cpaelzermirespace: is still on writing the wrapper for libcrpytx15:58
cpaelzeractually mirespace, I know you are unavailable now but please answer later - is the new version that does not use ed uploaded already to promote the full stack for now?15:59
cpaelzeras the rest adding it with the openssl wrapper is for "later" anyway15:59
sarnoldone small item here15:59
cpaelzergo sarnold while I check these perl libs ...15:59
sarnoldthe flowchart on https://github.com/canonical/ubuntu-mir has a lot of html formatting codes in it15:59
sarnoldthis feels new :)15:59
cpaelzerhehe16:00
sarnoldI'm hoping that this is an obvious "oh I know how to fix that" for someone around here16:00
cpaelzeryeah, it was cleaner than that for sure16:00
slyonI wonder if dviererbe can help with that... I can reach out to hin16:00
slyonhim*16:00
tsimonq2sarnold: It's being interpeted as a string, Markdown is formatted into HTML to be rendered, thus it's a matter of telling the renderer "hey, actually render this as HTML!" :)16:01
sarnoldI forgot to open an issue last time I spotted this :/16:01
sarnoldtsimonq2: if only the browsers would inspect the content they've been delivered and ignore the MIME types they were told to use, I'm sure there's no ill consequences of this choice :)16:01
tsimonq2:D16:01
tsimonq2I suspect this will help: https://mermaid.js.org/syntax/flowchart.html#markdown-formatting16:02
sarnoldanyway that was it for me16:02
cpaelzerThis is a good one16:02
tsimonq2All I have for AOB is, thank you for your work, MIR Team! :D16:02
cpaelzerlet us wait what dviererbe will say16:02
cpaelzerthanks tsimonq2, same to you and all others contributing to Ubuntu out there!16:02
cpaelzersince slyon will reach out we can consider this as "it will happen"16:03
cpaelzerthanks16:03
cpaelzerok, that seems to be a wrap16:03
cpaelzerand I'm too late to the next meeting16:03
sarnoldthanks cpaelzer, all :)16:03
cpaelzerclosing ...16:03
eslermthanks all o/16:03
slyonthakns cpaelzer, all!16:03
cpaelzer#endmeeting16:03
meetingologyMeeting ended at 16:03:45 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2024/ubuntu-meeting.2024-02-13-15.30.moin.txt16:03
rbasako/20:00
amurrayo/20:00
tsimonq2o/20:00
* vorlon waves20:02
seb128hey20:02
amurrayI can't see any apologies from sil2100 - does anyone know if he is out this week?20:03
vorlonhe's not out this week, I can't speak to where he is at the moment20:04
amurrayok, I'll jump in to chair then20:04
amurray#startmeeting Ubuntu Technical Board20:05
meetingologyMeeting started at 20:05:16 UTC.  The chair is amurray.  Information about MeetBot at https://wiki.ubuntu.com/meetingology20:05
meetingologyAvailable commands: action, commands, idea, info, link, nick20:05
amurray#topic Apologies20:05
amurraynone but seems sil2100 is unavailable20:05
amurray#topic Action review20:05
amurrayACTION: seb128/amurray/sil2100 to help drafting the snap-store Ubuntu-specific tracks usage20:06
amurrayno update on this from my side20:06
seb128neither from mine, sorry20:06
amurrayno worries - will carry over20:06
seb128and I didn't schedule the meeting20:06
amurray#action seb128/amurray/sil2100 to help drafting the snap-store Ubuntu-specific tracks usage20:06
meetingologyACTION: seb128/amurray/sil2100 to help drafting the snap-store Ubuntu-specific tracks usage20:06
amurrayACTION: seb128 to organize a meeting to unblock the draft of the tracks usage section20:07
amurraycarry over?20:07
seb128yes20:08
amurray#action seb128 to organize a meeting to unblock the draft of the tracks usage section20:08
meetingologyACTION: seb128 to organize a meeting to unblock the draft of the tracks usage section20:08
amurrayACTION: rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification20:08
rbasakCarry over please20:08
amurray#action rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification20:08
meetingologyACTION: rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification20:08
amurrayACTION: rbasak to follow up on finding consensus on question of test plans for third party apps20:08
rbasakCarry over, but this one I'd like to talk about if we have time today please20:09
amurrayok do you want to do that during AOB?20:09
rbasakYes let's do it at the end20:09
amurray#action rbasak to follow up on finding consensus on question of test plans for third party apps20:10
meetingologyACTION: rbasak to follow up on finding consensus on question of test plans for third party apps20:10
amurrayACTION: rbasak to open wider discussion on third-party repo policy20:10
rbasakIt's low priority so whatever else comes first can have the time first20:10
rbasakThis is blocked on the previous20:10
amurrayack20:10
amurray#action rbasak to open wider discussion on third-party repo policy20:10
meetingologyACTION: rbasak to open wider discussion on third-party repo policy20:10
amurrayACTION: 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:10
seb128carry over please20:10
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_Delegations20:10
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:10
amurrayACTION: vorlon to write up draft guidelines for packages in the archive that download from the Internet20:10
vorlonI suggest we drop this from here and that I track it elsewhere, since I'm the one who was arguing for it20:11
vorlonand haven't had time to follow through20:11
amurraywould it be worth filing at https://bugs.launchpad.net/techboard to track this?20:12
vorlononly if you think the TB wants to keep track of it IMHO20:12
vorlonsince it was my proposal, it's more useful for me to track the TODO elsewhere20:12
amurrayI don't think the TB needs to track it20:13
amurrayI'll drop it from the agenda then20:14
amurrayACTION: seb128 to follow-up with ubuntu cinnamon on 24.04 request20:14
seb128I did, and they replied so I need to process the details and follow up20:14
seb128let's carry over20:14
amurray#action seb128 to follow-up with ubuntu cinnamon on 24.04 request20:15
meetingologyACTION: seb128 to follow-up with ubuntu cinnamon on 24.04 request20:15
amurrayACTION: seb128 to follow-up with ubuntu budgie on 24.04 request20:15
seb128done20:15
amurrayack - https://lists.ubuntu.com/archives/technical-board/2024-January/002874.html20:15
seb128that one should have been deleted from the actions in favor of the one 3 items down20:15
seb128which is also done20:15
amurrayah ok  - I'll keep plowing through the agenda to make sure we don't miss anything20:16
amurrayACTION: amurray to send confirmation of successful LTS status for UbuntuKylin 24.0420:16
amurraydone - https://lists.ubuntu.com/archives/technical-board/2024-January/002870.html20:16
amurrayACTION: sil2100 to review the lubuntu LTS participation request and follow up as appropriate (question or call for vote)20:17
amurrayI'll put that as carry over too then20:17
amurrayoh actually I forgot we already voted via email20:18
amurrayso it just needs someone to send the confirmation email from what I can tell20:18
amurrayI can do that then20:19
seb128I guess since Lukasz was doing the review he should do the emailing?20:19
seb128or that :)20:19
amurrayI'm fine either way20:19
tsimonq2Didn't vorlon follow up giving an official ack? :)20:19
vorlonI think I did?20:19
vorlonyes20:19
seb128oh yes, I went over that email but the conclusion is several screen down and I didn't scroll all the way :p20:20
amurrayah right - sorry I wasn't looking at the right one either - https://lists.ubuntu.com/archives/technical-board/2024-February/002877.html20:20
vorlonhttps://lists.ubuntu.com/archives/technical-board/2024-February/002877.html20:20
amurraythanks vorlon20:20
vorlonyah20:20
tsimonq2<320:20
amurrayACTION: seb128 to send confirmation of successful LTS status for Ubuntu Budgie 24.0420:20
seb128that's done20:20
amurrayas seb noted above this is done already20:20
amurrayACTION: vorlon to confirm TB agreement to launchpad-buildd-admins ownership change20:21
vorlondone20:21
amurraythis was done in https://lists.ubuntu.com/archives/technical-board/2024-February/002876.html20:21
amurrayACTION: amurray to follow up with Kubuntu on 24.04 LTS request20:21
amurraythis is still ongoing20:21
tsimonq2o/ I'm a stand-in for Kubuntu today, and just wanted to provide some context (nothing actionable.) Scarlett Gately Moore has been working for the Kubuntu Council now, officially, on a contract basis. I have been tasked with guiding her through so she re-learns the ropes. There has been enough progress and energy in the Kubuntu Team where I am confident in saying we should be re-qualified. I'm20:21
tsimonq2happy to answer any specific questions if there are any today, because I have been deeply involved in this effort.20:21
tsimonq2Rik is still around and involved, providing guidance on the precedent he has set over the past few years, to be clear.20:22
amurrayhey tsimonq2 - at this stage I don't have any specific questions, I'll probably just continue to follow up via email - I did notice scarlett said they would intend to support the entire kubuntu packageset (which is great!) but I worry about whether they have the resources for this?20:23
vorlonthat all seems reasonable, and Kubuntu is established enough that I'm personally not worried about a change of lead impacting the LTS qual20:23
vorlonamurray: could you elaborate as to what's in the kubuntu packageset that's not KDE?20:24
vorlonwe do a poor job of gardening packagesets20:24
vorlonthere's probably a bunch of stuff listed that doesn't even exist in the archive anymore20:24
tsimonq2vorlon: I understand this isn't necessarily what we want to do going forward, but yes, that list has quite grown over time.20:25
vorlondoesn't have to be done here and now, anyway; this could be a mail followup20:25
vorlonbut I'd like to get into the nitty-gritty of the capacity concerns20:25
tsimonq2Not a problem :)20:26
amurrayok (fyi the packageset is quite long https://pastebin.ubuntu.com/p/jbYsvvfVgq/ so I assume the kubuntu folks might want to scope their statement of support a bit)20:26
rbasakI think a flavour packageset is a poor list to use outside of DMB managed ACLs because they are (were) automatically produced20:26
vorlonhttps://ubuntu-archive-team.ubuntu.com/packagesets/noble/kubuntu btw20:26
rbasak...and they might change arbitrarily for the same sort of reason in the future20:27
tsimonq2I'll follow up on our end to see if Rik had a particular rhyme or reason.20:27
amurrayok, we'll continue this via email then20:27
vorlonrbasak: unfortunately it's the best proxy we have for "things in this flavor that aren't also in a base seed" without additional coding that we've never bothered doing.  But I agree20:27
vorlontsimonq2: I look forward to you elaborating on your support plan for cvs20:27
rbasakThe task of fixing the scripts is years old and not taken now. The DMB currently just adjusts them manually on request.20:28
tsimonq2vorlon: lol :)20:28
rbasakSo there's no longer really any assurance that packages in there aren't in a different seed. Nobody is checking for that.20:28
vorlonuh you can give me an action to look whether we have any ubuntu-archive / ubuntu-release bits that would let me say "this bit is the flavor-specific overlay"20:28
vorlonbecause what we want to see is set(kubuntu-seeds) - set(platform-seeds)20:29
amurray#action vorlon to look into scripting for packages in flavor-specific overlays20:29
meetingologyACTION: vorlon to look into scripting for packages in flavor-specific overlays20:29
amurrayACTION: vorlon to confirm ratification of Lubuntu LTS20:30
amurrayas noted above, this was already done20:30
vorlonwell. set(kubuntu-seeds) - set(platform-seeds) - set(ubuntu-seeds)20:30
amurray#topic Scan the mailing list archive for anything we missed (standing item)20:31
rbasakxnox asked for a change in LP20:31
vorlonyes20:31
vorlonwhich he pointed out that my previous request for apt maintainer sign-off was unfortunately on a superseded mp and thus "lost" to the stream20:32
vorlonwith my AA hat on I have 0 concerns about dropping this if apt itself doesn't use it20:32
rbasakI wanted to know who would be taking responsibility for the change, dealing with any fallout, etc, and I don't think I got a clear answer to that.20:32
amurrayyep - I'm not sure how to proceed here - there is clearly some perceived risk in this change but its not clear to me who owns it20:32
vorlonI will as an AA20:33
vorlongive this to me as an action please20:33
rbasakGreat - thanks!20:33
amurraythanks vorlon20:33
vorlon(TBH I think despite the acl being owned by the TB this could have just been handled directly with the AA members of the TB rather than involving the TB as a whole)20:33
amurray#action vorlon to follow up on xnox's request to set noble.publish_i18n_index to False20:33
meetingologyACTION: vorlon to follow up on xnox's request to set noble.publish_i18n_index to False20:33
amurrayI don't see anything else on the mailing list for today20:34
amurray#topic Check up on community bugs and techboard bugs20:34
amurray#link https://bugs.launchpad.net/ubuntu-community/+bugs?field.assignee=techboard20:34
amurray#link https://bugs.launchpad.net/techboard20:34
amurraynothing here either20:35
amurray#topic Select a chair for the next meeting (next from https://launchpad.net/~techboard/+members)20:35
amurraylooks like its me and rbasak as backup20:35
rbasakack20:35
amurray#agreed next meeting chair: amurray, backup: rbasak20:35
meetingologyAGREED: next meeting chair: amurray, backup: rbasak20:35
amurray#topic AOB20:36
rbasako/20:36
vorlonthe covention is that it be sil2100 with rbasak as backup, but ok :)20:36
vorlon+n20:36
amurrayoh cool20:36
amurray#agreed next meeting chair: sil2100, backup: rbasak20:36
meetingologyAGREED: next meeting chair: sil2100, backup: rbasak20:36
vorlon(i.e. missing your chair spot doesn't get you off the hook for chairing :)20:36
amurraydoes anyone else have AOB? otherwise rbasak the floor is yours20:37
rbasakThis relates to "snap-MIRs" here: https://docs.google.com/document/d/1apUKR4gtOrfPGCWmtoebaQUhoy-fG8Cyo3VKJyhnpD0/edit#heading=h.whx7oqqnxsv020:37
rbasakOur previous discussions are summarised and linked from there. This is the only thing that might be holding up the main body text. To make progress I'd like to: 1) decide if it really needs to be general, because if we can agree that it's snap-specific then we can progress on the main body at least; 2) meet in a higher bandwidth medium (Google Meet?) with amurray and maybe seb128, sil2100, whoever20:37
rbasakelse wants to be involved to actually get something drafted that works for us.20:37
rbasakThis might be homework for you for next time to remind yourself of the previous conversation, but maybe it's worth mentioning here in public that I'd like to resolve this out-of-band and come back with a result to present in public in order to get something into the draft that's workable for everyone. I'd still expect a final vote / ratification here in public regardless so I don't think there need20:37
rbasakbe any concerns about not being public enough with the work on this.20:37
amurraysounds reasonable to me20:38
vorlon+120:38
rbasakThanks. I'll set up a meeting then. Anybody else who'd like to be involved, please contact me.20:39
amurraywe already have an action item on the agenda around this so I won't add any additional one20:40
seb128rbasak, I had that action item but I'm happy for it to grab it if you have time to move that forward20:40
rbasakseb128: I think that was on a different point - snap tracks?20:41
amurrayyeah we have 2 similar items on the agenda - one is about track usage and the other is about test plans for third-party apps - this is about the second one20:41
rbasakWe could try and combine them to make scheduling easier20:42
rbasakApproximately the same set of people need to discuss them anyway20:42
amurraysure20:42
rbasakSo you can leave it with me to schedule something20:42
amurraythanks rbasak20:42
seb128ah, right, sorry ... but yeah, might be more efficient to cover both topics in one meeting20:42
seb128rbasak, thanks!20:42
amurrayanything else for today...?20:43
vorlonnothing here20:43
rbasakNothing else from me. Thanks!20:43
seb128not from me20:44
tsimonq2Thank you all for20:44
tsimonq2...what you do :)20:44
amurraythanks folks20:44
amurray#endmeeting20:44
meetingologyMeeting ended at 20:44:15 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2024/ubuntu-meeting.2024-02-13-20.05.moin.txt20:44
seb128thanks! :)20:44
amurrayyw tsimonq2 :)20:44
tsimonq2rbasak: Happy to attend the meeting if you would find my opinion to be valuable.20:44
rbasakOK I'll add you to the invite list. Thanks!20:44
tsimonq2<320:44

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