/srv/irclogs.ubuntu.com/2024/09/24/#ubuntu-meeting.txt

* slyon lightning the MIR camp fire o/14:30
sarnoldgood morninig14:30
slyonc_paelzer is busy today. So let me run the meeting.14:31
slyon#startmeeting Weekly Main Inclusion Requests status14:31
meetingologyMeeting started at 14:31:14 UTC.  The chair is slyon.  Information about MeetBot at https://wiki.ubuntu.com/meetingology14:31
meetingologyAvailable commands: action, commands, idea, info, link, nick14:31
slyonPing for MIR meeting - didrocks joalif slyon sarnold c_paelzer jamespage ( eslerm dviererbe )14:31
slyon#topic current component mismatches14:31
slyonMission: Identify required actions and spread the load among the teams14:31
slyon#link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg14:31
slyon#link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg14:31
slyonthe component-mismatches report is still outdated. Last run was about a week ago. sil2100 is coordinating with IS to get it resolved.14:32
jamespageo/14:32
slyonThere's not much we can do. No news in the old reports.14:32
slyon#topic New MIRs14:32
slyonMission: ensure to assign all incoming reviews for fast processing14:32
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-mir14:32
slyonthe review queue is empty.14:32
slyon#topic Incomplete bugs / questions14:32
slyonMission: Identify required actions and spread the load among the teams14:33
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-mir14:33
slyonbug #2080965 is basically ready14:33
-ubottu:#ubuntu-meeting- Bug 2080965 in architecture-properties (Ubuntu) "[MIR] architecture-properties" [Low, Incomplete] https://launchpad.net/bugs/208096514:33
slyonbut waiting for some -dev packages exclusion discussion (more on that later)14:33
slyon(no security review needed)14:34
slyonbug #205819214:34
-ubottu:#ubuntu-meeting- Bug 2058192 in OEM Priority Project "[MIR] lenovo-wwan-unlock" [Critical, Confirmed] https://launchpad.net/bugs/205819214:34
slyoneslerm suggested this package should move to the OEM archive. I talked to sil2100 but he couldn't help a lot. We need to coordinate with the OEM team directly, then he can drop it from multiverse/restricted (if desired).14:35
slyonThe updates on the LP bug suggest that the OEM team might be interested in keeping it in the primary archive, still.14:35
cpaelzerhey, sorry for all the roadmap to blast over MIR meetings14:36
cpaelzerBTW I've followed up on wsdd as you pinged me last week - thanks14:36
sarnoldwsdd https://bugs.launchpad.net/ubuntu/+source/wsdd/+bug/207002514:37
-ubottu:#ubuntu-meeting- Launchpad bug 2070025 in wsdd (Ubuntu) "[MIR] wsdd" [Undecided, In Progress]14:37
slyonlet me ask them to address the comments made by didrocks on the bug report, as that would be a minimal requirement for main/restricted inclusion14:37
didrocksthanks slyon :)14:39
slyoncomment added.14:40
slyonthanks for moving wsdd forward, cpaelzer !14:40
slyonI also moved this one forward, which is now ready for a seed change https://bugs.launchpad.net/ubuntu/+source/xdg-terminal-exec/+bug/2069308 (cc jbicha)14:41
-ubottu:#ubuntu-meeting- Launchpad bug 2069308 in xdg-terminal-exec (Ubuntu) "MIR xdg-terminal-exec" [Undecided, In Progress]14:41
slyon#topic Process/Documentation improvements14:41
slyonMission: Review pending process/documentation pull-requests or issues14:41
slyon#link https://github.com/canonical/ubuntu-mir/pulls14:41
slyon#link https://github.com/canonical/ubuntu-mir/issues14:41
slyonsarnold: could you confirm this is working for you? https://github.com/canonical/ubuntu-mir/pull/68 then we could merge it14:42
-ubottu:#ubuntu-meeting- Pull 68 in canonical/ubuntu-mir "Fix visually broken flowchart (#67)" [Open]14:42
sarnoldoo moment..14:42
slyonI wasn't able to continue on the Rust docs, https://github.com/canonical/ubuntu-mir/pull/66 – would love to adopt/recommend the s390-tools way of doing it, but didn't get to it this week between all the other stuff14:42
-ubottu:#ubuntu-meeting- Pull 66 in canonical/ubuntu-mir "Import Rust vendoring document" [Open]14:42
slyonwhich leaves us with only one (new) issue: https://github.com/canonical/ubuntu-mir/issues/69 and I'd love to see senior MIR people chime in on this (cc cpaelzer didrocks jamespage)14:44
-ubottu:#ubuntu-meeting- Issue 69 in canonical/ubuntu-mir "Do we benefit from having the dev binary packages promoted?" [Open]14:44
slyonI had some discussions about this with seb128 today, after the architecture-properties MIR in https://launchpad.net/bugs/208096514:44
-ubottu:#ubuntu-meeting- Launchpad bug 2080965 in architecture-properties (Ubuntu) "[MIR] architecture-properties" [Low, Incomplete]14:44
cpaelzerwhy is that even a big problem?14:45
cpaelzerthe "by default" is only the auto-include meant to cover things that are usually not picked up by direct dependencies14:45
cpaelzerthat is the set of -doc and -dev14:45
cpaelzerbut AFAIK it was always ok to opt-out by adding an extra-exclude14:45
slyonwe have a case of libglib2.0-dev depending on a new "architectures-properties" tool that mostly a helper script for cross-building14:46
cpaelzerSurely this comes from a time when the support on universe was not yet as good, community not as mature and pro did not yet exist to cover universe14:46
cpaelzerback than it was more important to move those to main if it was possible14:46
cpaelzerbut if there are conflicts and problems, and really the only thing that puts the -dev/-doc into main is the auto-incliude14:47
cpaelzerthen just go for adding an exclude14:47
cpaelzerIf I understand correctly, the question is "do we still want to try to promote these by default" right?14:47
slyonright. I guess that's true for "normal" packages. But "Demoting libglib2.0-dev isn't easy because it's a low level libraries that most other desktop dev libraries depends on." So the desktop team would need to maintain a long-tail of -dev exclusions14:48
slyonor get their -dev dependencies included in "main"14:48
slyoncorrect cpaelzer14:48
cpaelzerIf other things "really" depend on it (not just the auto-inclusion), then yes it should stay in main IMHO14:48
cpaelzerabout the issue of maintaining long tails14:49
cpaelzerwe faced similar issues in server when some packages had too much content in a few packages14:49
cpaelzerlike 50 plugins of which only 2 really were prime time14:49
cpaelzerthere we ended up splitting the package14:49
cpaelzerand the one that stayed in main has much more reasonable dependencies than the former huge super-package14:50
cpaelzerI do not know the libglib2.0-dev situation, but could something like that help there too?14:50
didrockscpaelzer: smell like a similar story than gstreamer plugins :)14:50
slyonI need to check the germinate output to see what exactly is pulling in libglib2.0-dev.14:50
didrocksslyon: I’m afraid you will end up with a long list of -dev packages depending on libglib2.0-dev14:51
didrocksgtk being one, for instance14:51
slyonBut do I understand correctly, that you suggest instead of doing the MIR for a new build-tool dependency we should rather work with Extra-Excludes?14:51
cpaelzerthe one that is accoutned for in germinate is libaccountsservice-dev  , but there might be more than that as didrocks says14:52
didrocksyeah, germinate will only points to the "first" one that it founds IIRC14:52
cpaelzercorrect14:52
didrocksyou "fix" it, then goes to the next…14:52
slyonright.14:52
cpaelzerslyon: If that -dev package has no deep purpose or reason on it's own to be in main - AND only is in for auto-include. Then an auto-exclude is ok AFAIK14:53
cpaelzerthere are -dev which contain tools that are needed, others are actually always linked in so they are actually active code, ... - these would not qualify14:53
cpaelzerbut if it really is a normal -dev mostly having headers but not more14:53
cpaelzerthen an exclude if it causes pain might be ok14:53
didrocksand agreed14:54
cpaelzerbut one would need to work back the chain e.g. the aforementioned libaccountsservice-dev14:54
cpaelzerand add them all14:54
cpaelzerensuring that NONE of them has a deeper purpose14:54
cpaelzer-doc is a similar story BTW14:54
cpaelzeroften pulling in weird tools to build yet another special markdown language14:55
didrocksanother approach is to patch so that architectures-properties can be downgraded to a suggests14:55
slyonYes... https://bugs.launchpad.net/ubuntu/+source/architecture-properties/+bug/2080965 might have a deeper purpose potentially, it provides the "architecture-is-64bit" or "architecture-is-big-endian" meta packages. but OTOH we didn't need it in main up to now14:55
-ubottu:#ubuntu-meeting- Launchpad bug 2080965 in architecture-properties (Ubuntu) "[MIR] architecture-properties" [Low, Incomplete]14:55
didrocksas it’s "only" for cross-arch builds from what you discussed?14:55
jbichahttps://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=4c41750b is an approximation of the number of excludes you would need14:55
-ubottu:#ubuntu-meeting- Commit 4c41750 in ~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu "Extra-Exclude: drop the sysprof exclusions"14:55
slyonit also provides a wrapper around qemu-user to execute cross-architecture tests for example14:56
jbichait's incomplete because it would take me a few rounds with an archive admin to ensure we got everything14:56
sarnoldthe "Build-Dependencies not necessarily in main" thing was kinda intended to help us keep sphinx and the like from getting messy14:56
slyonOkay. ovearll it seems like there's no consensus for changing the defaults to exclude -dev packages. And we should rather work out the issues case-by-case. Do we want to vote on this?14:58
slyonMaybe we can do that on Github, so we can move on with the meeting.14:59
slyon#topic MIR related Security Review Queue14:59
slyonMission: Check on progress, do deadlines seem doable?14:59
slyonSome clients can only work with one, some with the other escaping - the URLs point to the same place.14:59
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-mir14:59
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-mir14:59
slyonInternal link14:59
slyon#link https://warthogs.atlassian.net/jira/software/c/projects/SEC/boards/59414:59
slyonsarnold: are you still keeping up the pace?14:59
sarnoldsorry, distracted ..15:01
slyonI see rpds-py is now in progress (cc jamespage)15:01
jamespage\o/15:02
sarnoldthe velocity is not what it was, but yes, progress is still being made on some packages15:02
slyonOkay. We're over time already. So do we have anything else?15:02
slyonhttps://github.com/canonical/ubuntu-mir/issues/6715:02
-ubottu:#ubuntu-meeting- Issue 67 in canonical/ubuntu-mir "Flowchart seems a bit broken" [Closed]15:02
cpaelzerat least that, thanks15:02
slyon#topic Any other business?15:03
slyon(sorry, wrong paste-buffer above)15:03
sarnoldsigh, I thought I had something, but i've gone blank. :/15:03
cpaelzernot from me15:04
slyonsarnold: next time you remember it, create an issue on the ubuntu-mir github. so you don't have to remember it :)15:04
cpaelzerlol15:04
sarnoldlol15:04
slyon:P15:05
cpaelzerthanks slyon for driging in these roadmappy times15:05
cpaelzerumm "driving"15:05
slyonif nothing else, thats all, folks!15:05
sarnoldthanks slyon, all :)15:05
slyon#endmeeting15:05
meetingologyMeeting ended at 15:05:24 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2024/ubuntu-meeting.2024-09-24-14.31.moin.txt15:05
sil2100o/19:00
amurrayo/19:00
seb128o/19:01
sil2100Looks like amurray is to chair today according to the Agenda?19:01
amurray#startmeeting Ubuntu Technical Board19:02
meetingologyMeeting started at 19:02:00 UTC.  The chair is amurray.  Information about MeetBot at https://wiki.ubuntu.com/meetingology19:02
meetingologyAvailable commands: action, commands, idea, info, link, nick19:02
amurray#topic Apologies19:02
sil2100I would like to apologize for my absence last time19:02
rbasako/19:02
sil2100I was supposed to appear, but somehow I ended up distracted enough to miss it...19:02
amurraythanks sil2100 - no worries19:02
amurrayno apologies that I can see for todays meeting19:03
amurray#topic Action review19:03
amurrayACTION: vorlon to look into scripting for packages in flavor-specific overlays19:03
amurraylooks like vorlon is not around - will carry-over19:04
amurray#action vorlon to look into scripting for packages in flavor-specific overlays19:04
meetingologyACTION: vorlon to look into scripting for packages in flavor-specific overlays19:04
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_Delegations19:04
seb128carry-over please19:04
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_Delegations19:05
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_Delegations19:05
rbasakOn the above...19:05
rbasakNote that the SRU team documentation now includes a section on that, so I think this is done for the SRU team.19:05
rbasakI guess I should link to it from the wiki19:05
amurraySimilarly I have documented the process for the Security team as well and linked to it from the TB page on the wiki19:06
amurray#undo19:06
meetingologyRemoving item from minutes: ACTION19:06
sil2100I think we need to do the same for the Release team. I have a general draft of Release membership onboarding that I could extend to that, but we still need to define all of it from the Release team19:06
sil2100The onboarding document for now is internal for internal onboarding processes, but there's actually no reason for it to not become public19:06
seb128I need to do  the same for the archive admins19:06
amurrayok lets keep the Release Team and AA teams on the action item them19:07
sil2100Let me add it to the next release meeting agenda19:07
sil2100Ok done, I'll discuss it with the team19:07
amurray#action seb128 to continue working with AA and Release teams to document their membership process and link to it from https://wiki.ubuntu.com/TechnicalBoard#Team_Delegations19:07
meetingologyACTION: seb128 to continue working with AA and Release teams to document their membership process and link to it from https://wiki.ubuntu.com/TechnicalBoard#Team_Delegations19:07
seb128thanks19:07
amurrayACTION: sil2100 to follow up on the Cinnamon 24.04 LTS Qualification re the number of contacts listed for the flavor19:08
seb128nice to see some change on that item, it has been carried over for ever :)19:08
sil2100I have a question regarding that one19:08
sil2100So when I started drafting an e-mail, I actually wanted to find some context of this one, but I guess I didn't search well enough19:08
sil2100https://wiki.ubuntu.com/UbuntuCinnamon/24.04/LTS-Proposal19:09
sil2100Is the problem we're trying to ask about that there's too many contacts listed?19:09
sil2100Because originally I thought the problem was that there were not enough19:09
sil2100What is the original ask here, apologies for asking19:10
amurrayhmm I am not sure either - am trying to see if I can find anything but so far am coming up blank19:10
seb128https://irclogs.ubuntu.com/2024/04/09/%23ubuntu-meeting.html#t19:1219:12
seb128it's coming from here19:12
sil2100To be fair, the Cinnamon situation is a bit weird. Basically during Beta we had trouble getting in touch with the main flavor lead, but indeed the rest of listed people were able to act on the flavor19:12
sil2100Okay, so it is the fact of 'too many contacts'. The list doesn't include 10 people though, just 4 through name19:13
sil2100And I think mentioning 'members of ubuntucinnamon-dev' is a natural thing to say?19:13
sil2100But okay, let's carry over my item. What I'll do is send a message to Cinnamon asking them about current contact information19:14
sil2100And making sure that all the contacts that are listed can action on the actual flavor19:14
amurraythanks sil210019:14
sil2100And can be made accountable19:14
sil2100Thank you for the context o/19:14
seb128it seems reasonable to me as well, I'm unsure to understand the original concern, maybe just dropping the reference to the team would be enough?19:14
seb128thanks!19:15
amurray#action sil2100 to follow up on the Cinnamon 24.04 LTS Qualification to ensure the listed contacts can action the flavor19:15
meetingologyACTION: sil2100 to follow up on the Cinnamon 24.04 LTS Qualification to ensure the listed contacts can action the flavor19:15
amurrayACTION: rbasak to document the third party software sources policy somewhere appropriate19:15
rbasako/19:16
rbasakI created https://launchpad.net/ubuntu-governance-docs19:16
rbasakGetting some help from a technical author within Canonical for the infrastructure pieces19:16
rbasakBut this is still in progress19:16
rbasakPlease carry over19:16
sil2100\o/19:16
amurraynice - thanks rbasak19:16
amurray#action rbasak to document the third party software sources policy somewhere appropriate19:17
meetingologyACTION: rbasak to document the third party software sources policy somewhere appropriate19:17
amurray#topic Scan the mailing list archive for anything we missed (standing item)19:17
amurray#link https://lists.ubuntu.com/archives/technical-board/2024-September/thread.html19:17
amurraynothing there19:17
amurray#topic Check up on community bugs and techboard bugs19:17
amurray#link https://bugs.launchpad.net/ubuntu-community/+bugs?field.assignee=techboard19:17
amurray#link https://bugs.launchpad.net/techboard19:18
amurrayLP: #2015920 can probably be closed out soon rbasak19:18
-ubottu:#ubuntu-meeting- Launchpad bug 2015920 in techboard "Third party repository policy is not well defined" [Undecided, Triaged] https://launchpad.net/bugs/201592019:18
rbasakAgreed. I was going to get it documented first so was just waiting on that so I could post a link in the bug on closing it.19:19
amurraysounds good19:19
amurray#topic Select a chair for the next meeting (next from https://launchpad.net/~techboard/+members)19:19
amurraylooks like rbasak  and seb12819:20
amurray#agreed next meeting chair: rbasak, backup: seb12819:20
meetingologyAGREED: next meeting chair: rbasak, backup: seb12819:20
rbasakack19:20
amurray#topic AOB19:20
sil2100Nothing from me19:20
seb128not from me19:21
amurraynor from me19:21
amurraylooks like we are done then - thanks folks19:21
amurray#endmeeting19:21
meetingologyMeeting ended at 19:21:56 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2024/ubuntu-meeting.2024-09-24-19.02.moin.txt19:21
sil2100Thank you o/19:21
seb128thanks!19:22
rbasakThanks!19:22
=== nicoz_ is now known as nicoz

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