/srv/irclogs.ubuntu.com/2021/09/14/#ubuntu-meeting.txt

=== genii is now known as genii-core
=== genii-core is now known as genii
slyono/14:31
cpaelzeromw14:31
cpaelzergive me 2 min to start14:31
didrockshey14:32
sarnoldgood morning14:32
slyonhey! It's going to be my first MIR meeting, as I want to join the team for foundations.14:33
didrockswelcome slyon :)14:33
slyon:)14:33
cpaelzerok let me get this started14:33
cpaelzer#startmeeting Weekly Main Inclusion Requests status14:33
meetingologyMeeting started at 14:33:47 UTC.  The chair is cpaelzer.  Information about MeetBot at https://wiki.ubuntu.com/meetingology14:33
meetingologyAvailable commands: action, commands, idea, info, link, nick14:33
ddstreeto/14:33
cpaelzerping for MIR ddstreet didrocks doko slyon sarnold jamespage14:34
cpaelzer#topic Review of previous action items14:34
cpaelzerI have sent around some thoughts about rust, but that isn't an "action" yet14:34
cpaelzerI'd love if all of you could give that a review or if you are ok just an "ack" on the mail itself14:34
sarnoldthanks for the reminder14:34
slyonwill do14:35
cpaelzerif you want an open discussion about it please let us do so at the end in the "any other business" section14:35
didrockswill do14:35
cpaelzerok14:35
cpaelzerthen heads up and for the log file now14:35
cpaelzerslyon:  here will be our new MIr team member from foundations14:35
cpaelzerhe will help out where doko couldn't make it14:35
sarnoldwelcome slyon :)14:35
cpaelzerand he will start with adsys which shall make didrocks happy I hope14:35
didrocks\o/14:35
slyono/ yes. I already prepared the adsys MIR, which I'd like to get reviewed/approved by some of you folks..14:36
slyonhttps://paste.ubuntu.com/p/HhTKzRJSDQ/14:36
cpaelzerbut first of all (there isn't that much of a process, but I need to ask) - any objections that we include him14:36
sarnoldwfm14:36
didrocksno objection either14:36
cpaelzerslyon: In can give your MIR-review a review tomorrow morning and let you know if I'd change anything14:36
cpaelzerI've taken a TODO for it14:37
slyonthanks14:37
cpaelzerin general to all of you, you know how it works - initially slyon will do reviews like each of us, but probably ask one of us if it is ok. Give him the favor of checking his work14:37
cpaelzerthat way he can fully grow into the team14:37
cpaelzerabout rust - once we have some discussions / acks in place I can (as promised) go further with it as suggestes by Steve14:38
cpaelzernow let us start the actual MIR content for today ...14:38
cpaelzer#topic current component mismatches14:38
cpaelzer#link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg14:38
cpaelzer#link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg14:38
cpaelzermostly known false positives14:38
cpaelzersarnold: weekly question for fence-agents review?14:39
sarnoldcpaelzer: weekly answer, slightly more positive this time :)14:39
cpaelzerjust FYI we updated the documentation already that talks about the package split and the promotion to main happening14:39
cpaelzerso the docs say you have done and hopefully ack'ed it in time :-)14:39
cpaelzerpython-oslo ?14:39
cpaelzerI think I remember we talked about it, let me check the referenced MIR bugs14:40
cpaelzerHmm14:40
cpaelzerno opend 5 days ago14:40
cpaelzerit is new and will be assigned in a later stage of the meeting as usual14:40
cpaelzerjamespage: or did you plan to review them anyway?14:40
cpaelzerthat is https://bugs.launchpad.net/ubuntu/+source/python-oslo.metrics/+bug/194314314:40
ubottuLaunchpad bug 1943143 in python-prometheus-client (Ubuntu) "[MIR] python-oslo.metrics, python-prometheus-client" [Undecided, New]14:41
cpaelzerand python-cheroot was added to https://bugs.launchpad.net/ubuntu/+source/python-cheroot/+bug/193011114:41
ubottuLaunchpad bug 1930111 in cherrypy3 (Ubuntu) "[MIR] new dependencies of cherrypy3: jaraco.collections, jaraco.classes, jaraco.text, python-cheroot, python-jaraco.functools, python-tempora, python-portend, zc.lockfile" [Undecided, In Progress]14:41
cpaelzerbut that already is on security14:41
cpaelzersarnold: is this tracked wherever you track the incoming reviews14:41
cpaelzerand BTW nothing else in mismatches to be concerned about14:42
sarnoldcpaelzer: python-chroot yes, python-oslo.* no14:42
cpaelzerslyon: remind me on monday to tell you the story behind false-positives14:42
sarnoldpython-cheroot rather. silly name.14:42
slyonack14:42
cpaelzersarnold: that is ok then, oslo needs to go through MIR review first14:42
cpaelzer#topic New MIRs14:42
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-mir14:42
cpaelzer3 (kind of) bugs to review14:43
cpaelzerwe have oslo (actually two packages)14:43
cpaelzerin14:43
cpaelzerin14:43
cpaelzerhttps://bugs.launchpad.net/ubuntu/+source/python-oslo.metrics/+bug/194314314:43
ubottuLaunchpad bug 1943143 in python-prometheus-client (Ubuntu) "[MIR] python-oslo.metrics, python-prometheus-client" [Undecided, New]14:43
cpaelzeranyone wants to take that?14:43
cpaelzerand we have libportal in14:43
cpaelzerhttps://bugs.launchpad.net/ubuntu/+source/libportal/+bug/193248514:43
ubottuLaunchpad bug 1932485 in libportal (Ubuntu) "[MIR] libportal" [Low, New]14:43
cpaelzerthat needs a review as well14:43
didrocksI think libportal is desktopish, I can take that14:44
cpaelzerit is indeed14:44
cpaelzeryour experience there is appreciated14:44
cpaelzerjamespage: did you intend to deal with oslo yourself14:44
sarnold"Note that there is a question on whether the API is stable at this point" .. is this really a candidate for 22.04 main?14:44
cpaelzerjamespage: and is thie urgent (21.10) or has time (22.04) ?14:44
cpaelzerindeed sarnold14:45
cpaelzerdidrocks: please give some extra scrutiny to how maintainable that seems14:45
cpaelzerif it has only one user, maybe - but if many components use it and it is unstable I'm not sure ...14:45
didrockswill do14:45
sarnoldgood point14:45
cpaelzerassigned - thanks14:46
cpaelzeroslo then14:46
cpaelzerthat should be fast, depsite being two libs14:46
cpaelzerI can have a look14:46
cpaelzer#topic Incomplete bugs / questions14:46
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-mir14:46
cpaelzeregl-wayland we did last week14:47
cpaelzerand rust is the bug for the discussion that is in your mail inbox already14:47
cpaelzernothing else newly incomplete that  needs our action14:47
cpaelzer#topic Any other business?14:47
cpaelzerok, open stage this is your chance if you have to adress anything14:47
slyonCan we change the assignee of https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1936907 to myself? I do not seem to have sufficient permission14:48
ubottuLaunchpad bug 1936907 in adsys (Ubuntu) "[MIR] ADSys" [Undecided, New]14:48
didrocksslyon: mind if we take 5 minutes post-meeting so that we address the first comments?14:48
cpaelzerdoko added you to the team, so you should14:48
cpaelzerbit I can in any case14:48
cpaelzerdone slyon14:49
slyonthanks cpaelzer14:49
slyonsure didrocks14:49
cpaelzergood suggestion I'll close for the logs to finish14:49
cpaelzerand then we can do a quick read of the RFC he linked14:49
cpaelzeranything else?14:49
sarnoldnothing from me14:49
didrocksnothing either14:49
slyonnothing14:49
cpaelzerok already thanks to all of you14:49
cpaelzer#endmeeting14:49
meetingologyMeeting ended at 14:49:58 UTC.  Minutes at https://new.ubottu.com/meetingology/logs/ubuntu-meeting/2021/ubuntu-meeting.2021-09-14-14.33.moin.txt14:49
didrocksthanks!14:50
sarnoldthanks cpaelzer, all :)14:50
slyono/14:50
cpaelzernow let us have a look at the pastebin I guess14:50
schopinis the discussion about rust public?14:50
cpaelzerschopin: not yet in detail14:50
cpaelzeronyl that it happens14:50
schopinOK, I'll wait for the movie then :)14:50
cpaelzerwe need to ensure we are sort of in sync before anything goes public yet14:50
cpaelzeror we will discuss-rip apart each other without much benefit for anyone14:50
cpaelzerother than movie like entertainment14:51
schopinOh I was just thinking public as in read-only.14:51
cpaelzersorry schopin the show will happen at a later point in time :-)14:51
didrocksslyon: ok, so, let’s go in order, some are good recommendations/required, some needs more comments :)14:51
didrocksrequired TODOS:14:51
didrocks-> Please add a team subscription (~desktop-bugs?). This has been amended and there is a check before promotion by archive admins14:52
didrocks(it’s desktop-packages btw for desktop)14:52
cpaelzerit is still recommended to subscribe upfront but no more strictly required14:52
didrocksindeed14:52
didrocks-> dh-apport build-dependency needs to be promoted to main (src:apport already in main)14:52
slyonoh i see, I wasn't aware of this14:52
slyonI wasn't sure about dh-apport either, are build-depends required to be in main?14:53
didrocksthis is a build-dep and for a few cycles, we don’t require build-deps to be in main. The only exception is when you staticalliy compile ofc, as the code will be in main14:53
cpaelzerslyon: re-read our ruls, if it is unclear propose a change next week - ok ?14:53
cpaelzerwe all might do it from memory14:53
didrocks(and as the code will be executed)14:53
slyoncpaelzer: will do14:53
slyonmakes sense, didrocks14:53
cpaelzerack to the build-dep only being in main when static linking14:53
didrocks3rd Required TODO: ack, is it in the wiki? (my bad), I really like the wording :)14:54
didrocksif it’s not in the Wiki, we should definively write it there to be explictely stated14:54
slyonit is in the wiki14:54
cpaelzerit is there14:54
didrocksshould take back from a fresh template sometimes, my bad then. I’ll add it in the initial comment14:54
cpaelzerthis does not ahve to go to main "adsys-dbgsym"14:55
didrocksyeah, that was my final one, spoiled!14:55
cpaelzerunless there is an explicit dependency to it14:55
didrocks:)14:55
cpaelzersorry didrocks14:55
didrocks:p14:55
didrocksRecommended TODOs:14:55
slyonOK14:55
didrocks- Make autopkgtests pass (it's not a regression as the autopkgtests passed never before)14:55
didrockswell spotted, my bad, it’s working on 10 machines, on VM and on CI in docker and non docker14:55
didrocksI never thought autopkgtest wouldn’t pass, it seems some issues with the filesystem, I will check14:56
didrocks- Add debian/watch file14:56
slyonyeah... autopkgtest infrastructure can provide a funny environment sometimes :)14:56
sarnoldheh :)14:56
cpaelzerdidrocks: maybe the nrew rule applies that if tests won't work at buld/autopkgtest time that you link and show examples of regular tests in other places?14:56
didrockscpaelzer: well, I would prefer really that we fix them14:56
cpaelzeroh yeah I'd "prefer" that as well14:56
didrocksit helps to have others not breaking you also14:56
didrockslike a new Go :)14:57
cpaelzerjust saying if it can't be fixed there, do not end up saying "no" but consider another place to run them14:57
didrocksyeah14:57
didrockswe can relax that, it’s recommended anyway, not required, which is okish IMHO. But not how I like to approach it for my projects :)14:57
didrockson d/watch -> this is where I have to disagree, this is a native package, built from the upstream VCS. There is then no such thing as "upstream tarballs"14:58
didrocksso nothing to download from14:58
cpaelzerone thing - the sudo rule "use of sudo, gksu, pkexec, or LD_LIBRARY_PATH" is meant for the delivered packages14:58
slyonugh, you're right! good spot14:58
cpaelzernot the tests14:58
didrocksyes, that one as well ^14:59
cpaelzerit isn't a problem if the tests internally sudo (still your hint at needs_root is great)14:59
cpaelzerbut in terms of "rules" having it in the tests isn't a problem14:59
slyonack14:59
cpaelzera silend sudo or setuid in what we install OTOH would be a problem14:59
didrocks(anyway, the package is using policykit, have a daemon running as root, listening on unix socket, the security review is still needed)14:59
cpaelzerI have to run for a meeting, sorry14:59
cpaelzero/14:59
didrocksthanks cpaelzer, we will finish up and if you want to scrollback then… :)15:00
didrockswell, last one is special for golang:15:00
didrocksmissing-notice-file-for-apache-license15:00
didrocks-> this is in vendor/15:00
didrockswhat go mod vendor does it vendoring dependencies (btw, it’s better at eliminates uneeded deps in 1.17, which we don’t have yet)15:00
didrocksand by design, it’s not copying LICENSE file, just code15:00
didrocksI think a lintian warning is needed there15:01
sarnoldeww15:01
didrockssarnold: my debian/copyright is fun to complete, as you can guess :p15:01
sarnolddidrocks: yeah :/15:01
didrockshardening-no-pie -> I think this is something general in Go packages15:02
sarnolddidrocks: is it common in goland to use spdx headers in files to describe licenses?15:02
didrocksI prefer to not override it in a lintian warnings15:02
slyonI need to double check in vendor/. as that hint was provided by lintian when doing a test build15:02
sarnoldyeah, I think golang is just funny there and doesn't emit pie with any amount of effort :(15:02
didrockssarnold: I don’t think so, some have headers, some will never use them15:02
slyonok15:02
didrockssarnold: should I keep the lintian warning in, or is it something we will never be able to do?15:02
didrocksI think upstream is not interested in support PIE?15:02
didrockssupporting*15:03
sarnolddidrocks: bummer. at some point I wouldn't be surprised if supplying to the US govt requires far more "software bill of material" things, and having those all throughout might make that approachable.15:03
didrocksyes15:03
slyonIMO you can keep the lintian warning in15:03
slyonas I saw that as a recommendation only15:04
didrocksI don’t like too many warnings either, because when they start piling up…15:04
didrocks:)15:04
sarnolddidrocks: if we do silence it, a TODO or XXX nearby to ask it to be reviewed every year or two would be nice ;)15:04
didrocksbut yeah, let’s do that for now15:04
didrocksok, let’s not silence it15:04
* sarnold <-- always the optimist15:04
didrocksjust the license one15:04
didrockshehe, I will blame you if I still see it in a couple of years15:04
didrockspersonnally ofc :)15:04
sarnold:)15:04
sarnoldnaturally :)15:04
didrocks(and if I remember!)15:04
didrocksslyon: I guess that’s mostly it? Did I forget anything?15:05
slyonnope. that's it.15:05
didrocks(I think the bigger task is the autopkgtest one, I’ll do an upload in a week with fixes anyway)15:05
slyonThank you so much for your feedback! I will update the RFC accordingly and wait for cpaelzer's feedback, before sending it to LP15:05
didrocksand thanks for spotting because, as it was never blocked and the tests are running in so many places, I never even double-guess this was always failing15:05
didrocksthanks!15:06
didrocksyeah, double check with cpaelzer, as I’m part of it, better for him to be around so that I don’t try to bend it my way too much :p15:06
slyonheh15:06
didrocks(I think the autopkgtests are chmod that don’t work, like when we try to trigger errors with unable to write to a file and in setup(), we chmod the file to make it RO first )15:08
didrocksis it something known? It rings a bell but I’m not sure I haven’t dreamt it15:08
slyondoesn't ring a bell here15:09
didrocksyeah, all failing tests are FHS related when we try to trigger edge error cases with chmoding file to make them RO, I will try in autopkgtests VM15:11
mdeslaur\o18:58
rbasako/18:58
sil2100o/18:59
rbasak#startmeeting Technical Board19:01
meetingologyMeeting started at 19:01:04 UTC.  The chair is rbasak.  Information about MeetBot at https://wiki.ubuntu.com/meetingology19:01
meetingologyAvailable commands: action, commands, idea, info, link, nick19:01
rbasak#topic Action review19:01
rbasakACTION: Wimpress To follow-up on-list with design review to address MATE Boutique security/consent concerns.19:01
rbasakPrevious discussion here19:02
rbasakIs there anything actually actionable by the TB any more here?19:03
mdeslaurwe need to figure out who's in charge of MATE I guess19:03
rbasakI'd like for the TB to either drop this, or specify exactly what the TB needs to do :-/19:03
* vorlon waves19:03
rbasako/19:03
mdeslauras I recall, the MATE boutique enables a PPA?19:04
vorlonI don't remember if it's a ppa or an archive external to LP; but it's not under Ubuntu governance19:04
rbasakRight, and I think it's agreed that this will be fixed, and how, but there's been no movement or ETA in many months/years AIUI.19:04
vorlonright19:05
rbasakI'm not sure if we want to actually do this, but the only way I can see to get this to move is for the TB to mandate a deadline after which MATE cannot ship as an official flavour unless/until this is fixed. Either that, or we drop the matter and let MATE continue as they wish.19:06
vorlonwell, I was going to say either a deadline for not being a flavor, or an upload to remove this behavior19:06
mdeslaurI don't think we should let them continue19:06
vorlonI agree19:06
mdeslaura deadline sounds appropriate19:07
rbasakWith Impish imminent, how about we set the requirement for J?19:07
sil2100I would be +1 on removing the behavior, but I still hope we'll get some news back from Wimpy19:07
rbasakSo let Impish slide, but it's a hard requirement that this isn't a problem in J, otherwise it doesn't ship officially.19:07
mdeslaurI agree to that19:08
rbasakIf flavour leads object, I'd be opening to them discussing alternatives with us. But setting the default position will help get some conclusion on this I think.19:09
rbasaksil2100: opinion?19:09
rbasakAs in, are you +1 also?19:09
sil2100I'm +1, just was trying to read some backlog to figure out - is this behavior with the boutique in impish right now?19:09
rbasakThat's the impression I have. If not, then there should be no problem :)19:10
vorlonif it's changed, no one has told us19:10
vorlonI think there was a vague sense that it might migrate to snaps but I haven't heard that this had happened19:10
rbasakYes that was discussed (very briefly) at https://irclogs.ubuntu.com/2021/05/28/%23ubuntu-desktop.html#t10:4219:11
sil2100This is the problem when there's no active communication...19:11
rbasak#agreed MATE is required to resolve the PPA situation by the J release. Otherwise, MATE will not be an official flavour in J.19:11
meetingologyAGREED: MATE is required to resolve the PPA situation by the J release. Otherwise, MATE will not be an official flavour in J.19:11
rbasak#action rbasak to communicate the TB's MATE resolution to the MATE flavour leads.19:12
meetingologyACTION: rbasak to communicate the TB's MATE resolution to the MATE flavour leads.19:12
rbasakACTION: formal ratification of third party seeded snap security policy, depends on:19:12
rbasakACTION: vorlon to circle around with store, snapcraft, et all, and revise the snap source revision policy to be more clear with regards to rebuildability and GPL compliance.19:12
vorlonfwiw I have more capacity this month than I have recently and think I will be able to make progress on this soon19:12
rbasakThanks - let's carry.19:13
rbasak#action formal ratification of third party seeded snap security policy, depends on:19:13
meetingologyACTION: formal ratification of third party seeded snap security policy, depends on:19:13
rbasak#action vorlon to circle around with store, snapcraft, et all, and revise the snap source revision policy to be more clear with regards to rebuildability and GPL compliance.19:13
meetingologyACTION: vorlon to circle around with store, snapcraft, et all, and revise the snap source revision policy to be more clear with regards to rebuildability and GPL compliance.19:13
rbasakACTION: vorlon to reply to seeded snap upload permissions question on list19:13
vorlonlikewise :)19:13
rbasak#action vorlon to reply to seeded snap upload permissions question on list19:13
meetingologyACTION: vorlon to reply to seeded snap upload permissions question on list19:13
rbasakACTION: sil2100 to start a draft summarizing the OEM archive portion of the meeting which xnox and TB will review, edit, and ratify before we move on to figuring out the next step19:13
sil2100Yes, sadly that's still in progress, didn't progress much since the last meeting: https://wiki.ubuntu.com/OEMArchive <- the page is started, I have a few more drafted words but nothing much more19:16
rbasakOK thanks. Carried then.19:16
rbasak#action sil2100 to start a draft summarizing the OEM archive portion of the meeting which xnox and TB will review, edit, and ratify before we move on to figuring out the next step19:16
meetingologyACTION: sil2100 to start a draft summarizing the OEM archive portion of the meeting which xnox and TB will review, edit, and ratify before we move on to figuring out the next step19:16
rbasakThe next item wasn't updated on the agenda, but based on the logs from last time:19:16
rbasakACTION: mdeslaur to follow-up/respond for security team on advice for the flatpak TB request19:17
mdeslaurI asked seth to file a bug: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/194348019:17
ubottuLaunchpad bug 1943480 in flatpak (Ubuntu) "flatpak installation permission requirements different from ubuntu software" [Undecided, New]19:17
rbasakThanks mdeslaur and sarnold!19:17
mdeslaurthough I now see that the bug doesn't specifically state the security team position on the matter, I'll make sure that is fixed19:17
rbasakIs there anything further for the TB here?19:17
sarnoldmdeslaur: heh, yeah, I wasn't 100% sure we'd reached a consensus yet :(19:18
rbasakOK how about I leave that action with mdeslaur for now? Or can you relay the security team position now for discussion?19:18
rbasakI think the TB opinion is likely to follow the security team's opinion, and then the TB part could be concluded/closed and it'll just be a bug to implement.19:19
mdeslaurI'm not sure there's anything more for the TB here19:19
mdeslaurThe TB deferred to the security team19:19
rbasakOK thanks let's consider the TB part done then, and no further action for the TB.19:20
mdeslaurIt would just circle back is someone disagreed with the security team's decision19:20
mdeslaur*if19:20
rbasakACTION: all TB members to "vote" or explain what they do not like of a proposal on https://pad.ubuntu.com/third-party-repository-requirements (cyphermox, 19:25)19:20
rbasakI hope everyone did their homework?19:20
mdeslaurI did spend some time on that page, but I still need to think about it some more19:20
mdeslaurCan the others go through it before the next meeting, please?19:22
* vorlon nods19:22
sil2100Will do o/19:22
rbasakYep, thanks. And also that might mean that the rest of us need to circle round again to continue discussion / clarify any further questions.19:22
rbasakSo I'll leave the action for everyone. I certainly need to read mdeslaur's comments in detail.19:23
rbasak#action all TB members to "vote" or explain what they do not like of a proposal on https://pad.ubuntu.com/third-party-repository-requirements19:23
meetingologyACTION: all TB members to "vote" or explain what they do not like of a proposal on https://pad.ubuntu.com/third-party-repository-requirements19:23
rbasak#topic Erich Eickmeyer via the mailing list: DisplayCAL in the archive as a deb that pulls in a Flatpak, and its inclusion in Ubuntu Studio by default. See https://lists.ubuntu.com/archives/technical-board/2021-July/002562.html and https://pad.ubuntu.com/third-party-repository-requirements19:23
rbasakI think this is deferred for now, until the previous item is completed.19:23
rbasakAny further discussion on this topic?19:23
mdeslaurnope19:24
=== rbasak changed the topic of #ubuntu-meeting to: Scan the mailing list archive for anything we missed (standing item)
rbasak#topic Scan the mailing list archive for anything we missed (standing item)19:24
rbasakI screwed that up. Wrong magic symbol :-/19:24
rbasakAnyway19:25
vorlon:(19:25
vorlon:)19:25
vorlon(also wrong magic symbol)19:25
rbasakI don't see anything on the ML.19:25
rbasak#info Nothing spotted on the ML.19:25
rbasak#topic Check up on community bugs (standing item)19:25
rbasak#info No currently open community bugs19:26
rbasak#topic Select a chair for the next meeting (next from https://launchpad.net/~techboard/+members)19:26
rbasakNext chair will be vorlon. Backup: sil210019:26
rbasak#topic AOB19:26
rbasakAOB?19:26
mdeslaurI've got none19:26
vorlonnothing here19:26
rbasak#endmeeting19:27
meetingologyMeeting ended at 19:27:14 UTC.  Minutes at https://new.ubottu.com/meetingology/logs/ubuntu-meeting/2021/ubuntu-meeting.2021-09-14-19.01.moin.txt19:27
rbasakThanks all!19:27
mdeslaurthanks everyone19:27
* rbasak wonders what the previous topci was19:27
sil2100o/19:27
=== sil2100 changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
sil2100I think this is it?19:28
rbasakThank you!19:28

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