[16:31] #startmeeting [16:31] Meeting started Mon Sep 11 16:31:46 2017 UTC. The chair is tyhicks. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [16:31] Available commands: action commands idea info link nick [16:31] \o [16:31] The meeting agenda can be found at: [16:31] [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting [16:32] [TOPIC] Announcements === meetingology changed the topic of #ubuntu-meeting to: Announcements [16:32] Gianfranco Costamagna provided a debdiff for xenial for check-all-the-things (LP: #1597245) [16:32] Launchpad bug 1597245 in check-all-the-things (Ubuntu Xenial) "[SRU] update check-all-the-things to xenial" [Undecided,Fix released] https://launchpad.net/bugs/1597245 [16:32] Simon Quigley (tsimonq2) provided a debdiff for xenial for karchive (LP: #1712948) [16:32] Launchpad bug 1712948 in karchive (Ubuntu Xenial) "[CVE] KNewstuff downloads can install files outside the extraction directory" [Medium,Fix released] https://launchpad.net/bugs/1712948 [16:32] James Cowgill (jcowgill) provided debdiffs for xenial and zesty for mbedtls (LP: #1714640) [16:32] Launchpad bug 1714640 in mbedtls (Ubuntu Artful) "CVE-2017-14032 - certificate authentication bypass" [Medium,Fix released] https://launchpad.net/bugs/1714640 [16:32] Thank you for your assistance in keeping Ubuntu users secure! :) [16:32] [TOPIC] Weekly stand-up report === meetingology changed the topic of #ubuntu-meeting to: Weekly stand-up report [16:32] jdstrand: you're up [16:32] This week I plan to work on: [16:32] * updating the review tools for new license yaml, better error reporting and a few smaller fixes [16:32] * continuing reviews in support of snapd layouts feature (PR 3621) [16:32] * investigate device cgroup issues in snapd [16:32] * miscellaneous policy updates for snapd as have time [16:32] * start next steps of my parts of uid/gid work in snapd as have time [16:32] that's it from me. mdeslaur, you're up [16:33] I'm just back from vacation, so I'll be catching up on email [16:33] I think I have qemu packages to publish tomorow [16:33] and I'll be going down the list after that [16:33] that's it, sbeattie, you're up [16:33] I'm in the happy place this week. [16:33] I have a couple of embargoed issues I'm looking at [16:34] I'm also working on a libxml2 update [16:35] I'll have the usual kernel triage bits to go through. [16:35] I have some apparmor stuff to review, and I think a couple of qrt tasks to investigate [16:36] that's probably it for me. [16:36] tyhicks: you're up [16:36] I'm in the happy place this week [16:37] I'm here for the first half of the week and then I'll be traveling to and attending the Linux Security Summit in the last half [16:37] I'll be working on packaging/testing fscrypt 0.2.1 [16:37] I'll test the latest LSM stacking patches prior to LSS [16:38] (I quickly reviewed the patches a week or two ago) [16:38] tyhicks: I have a tree with them on artful 4.13 I'll point you at [16:38] and I'll see if I can fit any libseccomp backports/uploads in if the PR gets an ack [16:38] that's it for me [16:38] jjohansen: thanks, that'll be helpful [16:38] jjohansen: you're up [16:39] I am at Linux plumbers and the linux security conference this week, today I am prepping for presentations and discussions around apparmor, LSM stacking, and LSM namespacing [16:40] if you want any reviewers, please let us know, jjohansen [16:40] that is it for me I haven't seen sarnold so back to you tyhicks [16:40] ratliff: ah, thanks that would be good [16:42] chrisccoulson: are you back around? [16:42] tyhicks: i'm finally in :) [16:42] sarnold: hey - go ahead [16:42] I'm on bug triage this week [16:43] i'm helping jj with apparmor patch reviews as he generates them [16:43] working on nghttp2 mir ATM and moving on to the python elftools one once that's finished [16:44] that'll probably account for the week, so token back to chrisccoulson or ratliff? [16:44] I'll give chrisccoulson a minute to pipe up, then I'll go [16:45] he had to step away for an errand and was iffy on returning in time [16:45] you can go ahead [16:45] I'm on community this week. [16:45] I have a number of organizational and technical documentation tasks to do. [16:46] I also need to start doing sprint prep for the two upcoming sprints. [16:46] leosilva: on to you [16:46] I'm in CVE triage this week. [16:47] Soon I finish it for today I'm planning to get gdk-pixbuf and retest the issues to see if it can or not patched [16:47] also planning to hunting more pkgs to update. [16:47] that is for me. [16:47] tyhicks: it's back to you [16:48] thanks [16:48] [TOPIC] Highlighted packages === meetingology changed the topic of #ubuntu-meeting to: Highlighted packages [16:48] The Ubuntu Security team will highlight some community-supported packages that might be good candidates for updating and or triaging. If you would like to help Ubuntu and not sure where to start, this is a great way to do so. [16:48] See https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures for details and if you have any questions, feel free to ask in #ubuntu-security. To find out other ways of helping out, please see https://wiki.ubuntu.com/SecurityTeam/GettingInvolved. [16:48] http://people.canonical.com/~ubuntu-security/cve/pkg/python-jwcrypto.html [16:48] http://people.canonical.com/~ubuntu-security/cve/pkg/libid3tag.html [16:48] [TOPIC] Miscellaneous and Questions === meetingology changed the topic of #ubuntu-meeting to: Miscellaneous and Questions [16:48] http://people.canonical.com/~ubuntu-security/cve/pkg/atheme-services.html [16:48] http://people.canonical.com/~ubuntu-security/cve/pkg/golang-github-appc-docker2aci.html [16:48] http://people.canonical.com/~ubuntu-security/cve/pkg/mxml.html [16:48] Does anyone have any other questions or items to discuss? [16:49] I'll give a quick summary of Chris' plans for the week and then we'll end the meeting: [16:49] * finish updating rustc to 1.19 [16:49] * start on updating rustc to 1.20 [16:49] * thunderbird update [16:49] * sponsor chromium-browser update [16:49] * fix bugs for Firefox 56 [16:49] * menubar [16:49] * FTBFS on Trusty [16:50] * armhf issue [16:50] jdstrand, mdeslaur, sbeattie, jjohansen, sarnold, ratliff, leosilva: Thanks! [16:50] thank you, tyhicks! [16:50] #endmeeting === meetingology 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 [16:50] Meeting ended Mon Sep 11 16:50:17 2017 UTC. [16:50] Minutes: http://ubottu.com/meetingology/logs/ubuntu-meeting/2017/ubuntu-meeting.2017-09-11-16.31.moin.txt [16:50] tyhicks: thanks! [16:50] tks tyhicks ! [16:50] thanks tyhicks [16:50] thanks tyhicks! [16:50] thanks tyhicks === JanC_ is now known as JanC === nacc_ is now known as nacc [18:49] 0 [18:50] typo [19:01] o/ [19:01] hi sil2100 [19:02] o/ [19:02] Hello dear applicants! [19:02] I wonder if we'll get quorum [19:02] o/ [19:02] hi, I am a bit distracted today because of Irma but I'll see what I can do :) [19:03] o/ [19:03] even if we don't get quorum we have some things to discuss [19:03] jbicha hope you're ok! i'm in NC, and surprisingly it seems we'll miss the worst of it [19:04] I'm south of Tampa and it seems we missed the worst of it too (except for the power outages) [19:04] I guess we have quorum already [19:04] Looks like we have 4 members present [19:05] Who wants to chair? [19:05] well, we still need to certify the election results and have the TB do the same [19:06] So we need BenC? [19:06] yeah, would be good [19:06] I’m here [19:06] o/ [19:06] \o/ [19:07] or rbasak [19:07] sil2100: Do you mind chairing? [19:07] I could [19:08] #startmeeting DMB [19:08] Meeting started Mon Sep 11 19:08:10 2017 UTC. The chair is sil2100. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [19:08] Available commands: action commands idea info link nick === meetingology 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 | DMB Meeting | Current topic: [19:08] #topic Review of previous action items === meetingology 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 | DMB Meeting | Current topic: Review of previous action items [19:08] I guess all the action items are done [19:08] Since the vote finished, we'd just need to announce the results + contact the TB [19:08] Should we talk about the vote now or during AOB? [19:08] But that's a separate task [19:09] Let's talk afterwards, since application handling I'd prefer prioritized [19:09] Okay. [19:09] #topic SRU Developer applications === meetingology 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 | DMB Meeting | Current topic: SRU Developer applications [19:10] #subtopic Dan Streetman [19:10] ddstreet: o/ Could you introduce yourself? [19:10] hello o/ [19:10] https://wiki.ubuntu.com/ddstreet/UbuntuSRUDeveloperApplication <- application link [19:10] hi, i'm dan streetman, as indicated, and applying for the 'SRU developer' role [19:10] sil2100 thanks, that's my application link [19:11] i work closely with slashd, who is currently the only other SRU devel [19:11] any questions for me? [19:12] Look at the sponsorship miner I don't see very many SRU uploads. Maybe 8 is that right? [19:12] yes, not too many, around 8 is probably right [19:13] i have spent a lot of time working on kernel patches also [19:13] and my last upload, for pylint, was artful only, no SRU [19:13] That's interesting but I'm not certain its relevant to an SRU application. [19:14] no, kernel and devel uploads are not relevant [19:14] ddstreet: a 'technical' question from my side - when submitting an SRU application, what info would you include in the Regression Potential field? [19:15] What is the purpose of this field? [19:15] i would include any possible side-effects of the change [19:16] e.g. what area of the code does this change touch, and if that code area breaks, what would that look like? [19:18] Thanks [19:19] an example of what i've put in regression potential before, from my last vlan sru: "Any modifications to ifupdown or the scripts it uses may cause wider problems with network configuration. Specifically, this could cause problems when using vlan interfaces, as it forces every vlan's raw device interface to be fully ifup'ed before the vlan interface can finish its ifup." [19:19] What prompted applying for SRU uploads today? Is not having access blocking your work even though your last SRU was in June? [19:19] ddstreet: a more theoretical question - what do you think, does the lack of upload rights block your work? Will you do more uploads when having the permissions? [19:20] bdmurray mainly my application is so i can help move along sru applications into the queue to be reviewed [19:20] i.e., speed up sru's that are needed [19:21] sil2100 yes i will likely do more uploads, but probably i'll be uploading other's work [19:21] ddstreet: so it'd allow you to sponsor other SRUs? [19:21] yes [19:21] i do not think i will personally create more patches that i apply for sru's for, but i do think i will review and upload other people's sru's [19:21] obviously more than i do now, since i can't do that now ;-) [19:22] and of course, it will help me when i do have a sru to upload [19:22] personally-authored sru, that is [19:23] That's different than what *I'd* expected this application or other SRU developer applications to look like. [19:23] bdmurray what do you expect is the intention of people applying for SRU devel? [19:23] I'd expected applicants to uploading their own work not sponsoring stuff for others. [19:23] is that what you expect of core devs? [19:23] one of the for granting rights is significant and sustained uploads/contributions except in cases where that doesn't make sense (PPU for a mature package that needs very infrequent updates) [19:23] mainly upload their own patches? [19:24] *one of the criteria [19:24] ddstreet: How would you evaluate whether or not an upload is SRU ready? [19:25] bdmurray there's 2 parts to that: 1) technical change to whatever codebase it is, and 2) sru metadata like changelog format, version number, etc [19:26] for #1, the change depends on the package, and i would review the patch(es) and existing code to see how the code works, what the author is changing, if it makes sense and is done correctly, and mostly if it's upstream [19:26] if it's not accepted in the upstream code, that's a big red flag for deinal [19:26] assuming it's upstream, make sure it's in the devel release first [19:26] if upstream accepted it, and it's in devel, and the code looks good, then check #2 [19:27] which involves making sure the changelog has no trailing whitespace, line length is right, includes LP: #NNN, right changelog text, author name/email [19:27] check the patch e.g. patch -p1, quilt import/push/refresh, builds ok, autpkgtest [19:28] version number is correct based on current version [19:29] rather a lot of meta-data checks (i've thought about adding a tool to ubuntu-dev-tools to automate some of that, like scripts/checkpatch.pl for the kernel) [19:30] any other q's for me? [19:31] Any questions? Or should we proceed to voting? [19:31] I'm ready to vote. [19:31] BenC? micahg? [19:32] ready [19:32] I guess we're good then [19:32] #vote Grant ddstreet SRU Developer [19:32] Please vote on: Grant ddstreet SRU Developer [19:32] Public votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname) [19:34] -1 I'd like to see more involvement in the SRU process before granting you upload rights. [19:34] -1 I'd like to see more involvement in the SRU process before granting you upload rights. received from bdmurray [19:34] +0 , while the quality of work is good so far, it's a bit sporadic, also, I applaud your desire to sponsor uploads, but I don't feel that in and of itself is a reason to grant upload rights, I look forward to seeing you back soon with more SRUs completed when we can hopefully grant you SRU upload permissions [19:34] +0 , while the quality of work is good so far, it's a bit sporadic, also, I applaud your desire to sponsor uploads, but I don't feel that in and of itself is a reason to grant upload rights, I look forward to seeing you back soon with more SRUs completed when we can hopefully grant you SRU upload permissions received from micahg [19:34] Perhaps one way to do that is looking at some things in the SRU queue and then getting an SRU team member endorsement. [19:36] +0, all good skill-wise but I also think it's a bit too soon, certainly a passing vote after a short while of more uploads + endorsements [19:36] +0, all good skill-wise but I also think it's a bit too soon, certainly a passing vote after a short while of more uploads + endorsements received from sil2100 [19:36] bdmurray micahg sil2100 sounds good, i'm happy to reapply after adding some more sponsored sru uploads...you guys don't mind me bugging you to sponsor my uploads right? ;-) [19:37] ddstreet: not at all! It would be a pleasure - I'd say keep up on uploading through sponsors and we'd gladly review you again in a month or so [19:37] Or whenever you're ready [19:37] awesome. thnx all [19:38] ddstreet: thanks! [19:38] #topic PPU Applications === meetingology 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 | DMB Meeting | Current topic: PPU Applications [19:38] #subtopic David Mohammed (fossfreedom) [19:38] fossfreedom: o/ [19:39] :) [19:39] fossfreedom: could you introduce yourself? Since some of us might not know you yet! [19:39] https://wiki.ubuntu.com/fossfreedom/UbuntuBudgieDevApplication <- application [19:39] hi - my name is david mohammed - I am the project lead of ubuntu budgie [19:39] I am applying for PPU for the packages listed in my application [19:40] my work crosses both debian and ubuntu [19:40] the packages I have either created myself and maintain [19:40] or the package I have a direct interest due to Ubuntu Budgie [19:41] Sorry for the interruption, but I just got reminded that we need to close the previous vote [19:41] #endvote [19:41] Voting ended on: Grant ddstreet SRU Developer [19:41] Votes for:0 Votes against:1 Abstentions:2 [19:41] Motion denied [19:41] Ok, please continue ;p [19:41] ok - sorry - any Q's for me? [19:42] I've sponsored some packages for you already and I remember not having any issues as to their contents, which is good [19:42] I only see one endorsement on your application, is there a reason for this? [19:43] bdmurray: I see 4 [19:43] bdmurray: yeah, there's 4 [19:44] I strongly endorse his application. I haven't updated my endorsement since his last application in December [19:45] I think LocutusOfBorg's endorsement might be old too? [19:45] Sorry I thought the rest were comments. [19:46] right ,just one new endorsement since December [19:47] Well, it's all good [19:48] fossfreedom: tell me, when would be the usual cut-off 'date' after which you cannot upload NEW packages (by new I mean not-existing in the Ubuntu archive yet)? [19:49] freeze date - little late this cycle - just past in late august [19:49] idea would be to work with debian preferably [19:49] Which freeze that would be? [19:49] but definitely a couple of months before hand [19:50] Since there's a lot of different freezes in the archive ;) [19:50] debian freeze [19:50] the auto sync with debian to ubuntu [19:52] And what would you do if Ubuntu is in Feature Freeze already and need such a brand new package released to Ubuntu? [19:52] feature freeze is tied to debian freeze this cycle [19:52] By need I mean, suddenly really need it for good reasons [19:52] question very hard if it is really needed first of all [19:52] usually not [19:52] but if necessary FFE - feature freeze exception [19:52] But let's assume it's really needed, can you still get it in? [19:52] Yeah [19:54] BenC, bdmurray, micahg: any questions? [19:55] Not from me. [19:55] fossfreedom: I seem to recall Budgie was mainly going through Debian and there were mostly syncs happening, did something change? [19:56] in terms of budgie-desktop - upstream pull a rabbit out of their hat. It came late this cycle [19:56] debian also had lots of issues with the new queue [19:56] so the sync would not occur before debian freeze [19:57] is Ubuntu the upstream for the budgie packages?? [19:57] the ones not in Debian I mean [19:57] upstream - budgie-desktop github.com/budgie-desktop/budgie-desktop [19:57] in a way, I think Ubuntu is the upstream for the Debian packages too ;) [19:58] right, but what about packages like budgie-welcome, budgie-desktop-environment [19:59] those two are specific to ubuntu - they are at the heart of ubuntu budgie. They are written specifically for us and would not work with Debian [20:01] Any other questions? [20:01] I'm poking since we're again over our scheduled time here [20:02] I’m good [20:02] micahg: you have any more questions? [20:03] I assume not in this case, let's vote [20:03] #vote Grant fossfreedom PPU permissions for the listed package set [20:03] Please vote on: Grant fossfreedom PPU permissions for the listed package set [20:03] Public votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname) [20:04] Packageset list: budgie-desktop, budgie-desktop-environment, budgie-artwork, budgie-welcome, budgie-wallpapers, arc-theme, moka-icon-theme, faba-icon-theme, rhythmbox-plugin-alternative-toolbar, budgie-indicator-applet, slick-greeter and ubuntu-budgie-meta [20:04] (so it's in the logs) [20:04] +1 [20:04] +1 received from sil2100 [20:05] +1 [20:05] +1 received from bdmurray [20:07] BenC, micahg: ? [20:08] +1 [20:08] +1 received from BenC [20:08] +1 [20:08] +1 received from micahg [20:09] #endvote [20:09] Voting ended on: Grant fossfreedom PPU permissions for the listed package set [20:09] Votes for:4 Votes against:0 Abstentions:0 [20:09] Motion carried [20:09] fossfreedom: congratulations! [20:10] cheers all - much appreciated! [20:10] Who will take care of creating the packageset etc.? [20:11] a personal package set might be useful,, needs to be a TB member to create, but then we can maintain [20:13] Any volunteers to drive this? ;) [20:13] I think I'll be emailing them anyway re the election so could get it setup [20:13] bdmurray: thanks! [20:13] #action bdmurray to handle the PPU role for fossfreedom [20:13] ACTION: bdmurray to handle the PPU role for fossfreedom [20:14] #endvote [20:14] No vote in progress [20:14] Eh, stupid copy-paste [20:14] #topic AOB === meetingology 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 | DMB Meeting | Current topic: AOB [20:15] bdmurray: ok, you wanted to discuss the vote results? [20:15] micahg: What did you mean by certify the election? [20:15] vote to acknowledge the results of the election [20:15] The TB? [20:15] both [20:15] Why would I not vote +1? [20:15] it's usually a formality [20:16] Is that always been like that? [20:16] yeah [20:16] Okay, just wondering. [20:16] it's just a safeguard [20:16] So let's vote then [20:16] Guess what mine is! [20:16] #vote Vote to acknowledge the results of the election [20:16] Please vote on: Vote to acknowledge the results of the election [20:16] Public votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname) [20:16] +1 [20:16] +1 received from sil2100 [20:16] +1 [20:16] +1 received from micahg [20:16] +1 [20:16] +1 received from bdmurray [20:17] * sil2100 looks at BenC [20:17] *stare* [20:18] BenC: (some clients only highlight on the nick in the first token) [20:19] micahg: hmm, but how is this vote counted then? [20:19] +1 [20:19] +1 received from BenC [20:19] #endvote [20:19] Voting ended on: Vote to acknowledge the results of the election [20:19] Votes for:4 Votes against:0 Abstentions:0 [20:19] Motion carried [20:19] BenC: thanks! [20:19] Sorry, I’m doing my best to stay focused for quorum [20:20] micahg: since we don't actually need 4 + anyway, since there's only 5 people potentially that could vote [20:20] So 3 + were anyway sufficient I suppose [20:20] Anyway, all good === ubott2 is now known as ubottu [20:20] Now just the TB and we can officially welcome jbicha and cyphermox at the DMB [20:20] Ok, final thing from me [20:21] sil2100: I think we'd still need +4 since the board is 7 members [20:21] BenC, micahg, bdmurray: there's an ongoing application of rbalint through e-mail [20:21] micahg: yeah but how can we expect 7 peolpe to vote [20:21] right, I'll try to get to that later today [20:21] micahg: since we're voting for the 2 people that we're missing [20:21] Me too [20:21] sil2100: we can't, but I don' t think that changes quorum [20:21] micahg: this would be a bit absurd IMO [20:21] But anyway [20:22] Not a problem this time I guess! [20:22] micahg, BenC: thanks! [20:22] IMHO it's the equivalent of 2 members on extended vacation [20:22] So two actions more for me? [20:22] email TB re election then announce the results? [20:22] #action bdmurray to contact TB regarding the election [20:22] ACTION: bdmurray to contact TB regarding the election [20:23] bdmurray: if you want, we can share some of those tasks [20:23] Want me to send out the result announcement? [20:23] sil2100: Sure, I'll let you know when I hear from the TB [20:24] congrats! yes my advocacy was a little bit old, but it was still valid :) === tdaitx_ is now known as tdaitx === dkessel_ is now known as dkessel === PotatoGim_ is now known as PotatoGim [20:24] #action sil2100 to send out the results announcement after the TB decision is known [20:24] ACTION: sil2100 to send out the results announcement after the TB decision is known [20:25] Any other business? [20:25] LocutusO-: ;) [20:25] Nope === LocutusO- is now known as LocutusOfBorg [20:25] Ok, let's assume we're all good now [20:25] o/ [20:25] #endmeeting === meetingology 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 [20:25] Meeting ended Mon Sep 11 20:25:54 2017 UTC. [20:25] Minutes: http://ubottu.com/meetingology/logs/ubuntu-meeting/2017/ubuntu-meeting.2017-09-11-19.08.moin.txt [20:25] Thanks everyone!