=== heis2201 is now known as heis2201_ === FJKong is now known as BH1SCW === BH1SCW is now known as FJKong === JanC is now known as Guest42627 === JanC_ is now known as JanC [14:59] o/ [14:59] o/ [15:00] o/ [15:00] o/ [15:00] o/ [15:01] We need one more for quorum [15:02] Who's turn is it for chairing? Is the agenda up-to-date with that? [15:02] The chair rotation doesn't really work at all since some DMB members rarely manage to make a meeting. [15:03] I'm supposed to be on vacation this week though, so I'd appreciate if somebody else could take care of chairing/actions. [15:03] I have a meeting at 15:30, so unless we want to race through the meeting, I can't do it [15:03] sil2100: ? [15:04] Let's see if anyone else will appear, I can chair if needed but I already chaired a few times as a substitute [15:04] Not a big thing though [15:05] Still, I'd appreciate if we'd have quorum [15:05] * micahg wonders what happened with the election [15:06] I thought we had an action for that. Did it not get carried forward? [15:06] I don't think the agenda got properly updated [15:06] I didn't see a call for nomincations [15:06] I saw something in the meeting logs, but not on the agenda [15:07] s/nomications/nominations/ [15:07] ACTION: bdmurray to sort out votes and related items in respect of the two upcoming expiring DMB memberships (rbasak, 20:41) [15:07] This was from the last meeting, but not present on the agenda [15:07] Ok, I'll chair today and try to get it up to date after the meeting [15:07] Thanks! [15:08] We need one more member for quorum though - should we start without 4 people now anyway? [15:08] I'm getting pretty fed up with this tbh. [15:08] IMHO, the DMB members who repeatedly can't make it either need to sort out changing the meeting times, or step down and be replaced. [15:09] Yeah, I'm a bit annoyed too, although I must admit that I had some missed meetings myself [15:10] Trying to work around it by having a non-quorate meeting and then catching up on the ML doesn't seem to work effectively either. Whichever way applications get dragged out for far too long. [15:10] Let's start, maybe people will appear during the meeting, since if micahg will be away in 20 minutes than it's good if we get his votes at least [15:10] I'll still be here, just a little distracted ;) [15:11] Ah, ok [15:11] And it creates work for those who *do* make it. [15:11] So IMHO, we should just not have a non-quorate meeting and instead spend that time larting those who don't show up and fix the problem properly in whatever form that needs to take. [15:12] I'm hear but may need to leave suddenly. [15:12] \o/ [15:12] #startmeeting DMB [15:12] Meeting started Mon Mar 13 15:12:24 2017 UTC. The chair is sil2100. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [15:12] 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: [15:12] #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 [15:12] Ok, checking previous action items from the logs [15:13] my item is not done [15:13] Do I need to contact the whole TB or just a member regarding the extension? [15:13] Has the addition of rosco2 to the contributing developer team been made and announced? [15:13] one more unfinished item (not on the agenda) is handling fossfreedom's application for upload rights for budgie pkgs [15:15] jbicha: ok, we'll discuss that during AOB, since I guess this one was very tricky [15:15] wasn't fossfreedom supposed to come back with endorsements after a period of time [15:15] I think it was hard since he was applying for a non-existing packageset too [15:15] Since the packageset wasn't created yet [15:15] Anyway, we'll get back to it [15:15] ok [15:15] rbasak: did you add and announce Rosco2? [15:16] I see that was set for you [15:16] I don't recall. [15:16] ACTION: rbasak to add Rosco2 to the contributing developer team (rbasak, 19:32) [15:16] * rbasak works off the agenda page [15:16] ACTION: rbasak to announce Rosco2's new contributing developer team membership (rbasak, 19:32) [15:16] http://ubottu.com/meetingology/logs/ubuntu-meeting/2017/ubuntu-meeting.2017-02-27-19.15.html [15:16] OK give those actions to me again please. [15:16] Ok [15:17] #action rbasak to add Rosco2 to the contributing developer team (carried-over) [15:17] ACTION: rbasak to add Rosco2 to the contributing developer team (carried-over) [15:17] #action rbasak to announce Rosco2's new contributing developer team membership (carried over) [15:17] ACTION: rbasak to announce Rosco2's new contributing developer team membership (carried over) [15:17] bdmurray: as for your thing, I think DMB memberships are handled by the DMB, right? [15:17] Thanks! Sorry, I checked only the agenda page earlier today, and assumed I had no actions. [15:18] DMB memberships are handled by the TB [15:18] I'll fix that up today [15:18] micahg: ah, hm, ok [15:18] oh, membership in DMB owned teams, yeah, we can do those [15:18] I thought you meant actually DMB team membership [15:18] It's about DMB membership extension [15:19] yeah, TB then [15:19] ACTION: bdmurray to sort out votes and related items in respect of the two upcoming expiring DMB memberships (rbasak, 20:41) [15:19] micahg: do you know if one TB member is enough? [15:19] Or does it have to involve a vote? [15:19] in the past 1 person has just done it I think [15:20] I'll start with one then. [15:20] micahg: thanks! [15:20] bdmurray: ok, I'll carry it over then as well [15:20] #action bdmurray to sort out votes and related items in respect of the two upcoming expiring DMB memberships (carried over) [15:20] ACTION: bdmurray to sort out votes and related items in respect of the two upcoming expiring DMB memberships (carried over) [15:21] ACTION: rbasak to sort out the SRU uploaders team (rbasak, 20:41) [15:21] rbasak: that's done I think? ^ [15:21] I think so. I deferred actually creating the team in Launchpad until we had one member. [15:21] Makes sense, we might have one today! [15:21] I did announce it. [15:22] (and invite applications) [15:22] Yes :) [15:22] Ok, so one action item finished, woot! [15:23] There are also two other action items from cyphermox regarding chiluk's application - I added him to the team and announced in cyphermox's stead [15:23] Since he was busy [15:23] So this is done as well [15:23] Ok, let's move on [15:24] #topic Ubuntu Contributing 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: Ubuntu Contributing Developer Applications [15:24] #subtopic Dan Streetman (ddstreet) [15:24] o/ [15:24] ddstreet: please introduce yourself o/ [15:24] hi guys, I'm Dan [15:25] I'm applying for contributing developer [15:25] my application page is https://wiki.ubuntu.com/ddstreet/UbuntuContributingDeveloperApplication [15:26] Any questions? [15:27] I reviewed ddstreet's application when he asked me to endorse him. I have no questions. [15:27] no questions [15:28] I have a question [15:28] what happened this cycle [15:28] what do you mean? [15:28] or is that q not for me? [15:28] I see uploads through the end of yakkety [15:29] ah ok [15:29] a lot of the work i do is in the kernel [15:29] so, for the last several months i've been doing kernel work [15:29] and haven't had any userspace package uploads [15:29] is there a reason there's no endorseement from kernel devs? [15:30] oversight by me...i can ask them [15:30] i thought the endorsements needed to be from userspace pkg uploaders [15:30] any around that can vouch in IRC for you? [15:31] userspace pkg uploaders> I think any and all Ubuntu development work qualifies :) [15:31] well, contributing dev is a little different, it's overall dev effort that is reflected in the archive (and I assume your work makes it in eventually) [15:31] sure kamal probably can [15:32] Not sure if he's around yet though [15:32] (it's around 8:30 am at his place I think) [15:33] I'm seeing if I can see what I want to see in LP [15:33] * bdmurray place too [15:34] micahg: ok, give me a sign once your doubts are cleared [15:34] ddstreet: are those private repos? [15:34] are which private repos? [15:34] my lp git repos? [15:35] the kernel work [15:35] yeah [15:35] those are for customer kernel bugs i've worked [15:35] oh, sorry, I think I see it now [15:35] While he's doing that, I have a policy question. I consider ddstreet's work "significant and sustained" as it was in October 2016 - sustained until then. So I was a +1 on that basis, regardless of whether he's "sustained" since or not. [15:36] If an applicant reached "signifiant and sustained" in the past in our view, but applies after further contributions are no longer "sustained", should that still be a +1. I had assumed yes, but I'm curious what others think. [15:36] ok, I think I'm good, I assume this work was merged in [15:36] or most of it at least [15:37] sil2100: I'm good [15:38] I guess my question is moot then. Feel free to skip it and move on :) [15:38] rbasak: I personally like to think sustained means 'sustained and still continuing', but in this case it doesn't only mean archive uploads [15:38] yeah, I agree with sil2100 [15:38] So it's good [15:38] Ok then, let's vote! [15:38] Interesting, thanks. [15:38] kamal is here if you guys want to ask him [15:38] (it's not my main language so remember it's just my intepretation) [15:38] about my kernel work [15:38] kamal o/ [15:39] hi o/ [15:39] micahg: want to ask about kernel work still, or should we start voting? [15:39] rbasak: I think it depends on the period of time between last upload and application. [15:39] oh, if kamal wants to endorse, by all means :0 [15:39] :) [15:40] kamal have i done some satisfactory kernel work in the past? [15:40] I'm happy to endorse ddstreet ... he has certainly contributed to the Ubuntu kernel (and our in-the-works custom kernels for clouds) ... [15:40] in your experience? :) [15:40] thnx [15:40] I've found ddstreet to be easy to work with, and his work is of high quality. [15:40] from the Ubuntu Kernel team's perspective, ddstreet is a good kernel contributor and a quality developer. [15:40] .. [15:41] kamal: thanks! [15:41] Ok, I think we're good to start the vote [15:41] #vote Grant ddstreet Contributing Developer [15:41] Please vote on: Grant ddstreet Contributing Developer [15:41] 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) [15:41] +1 [15:41] +1 received from rbasak [15:41] +1 [15:41] +1 received from sil2100 [15:41] +1 [15:41] +1 received from micahg [15:42] +1 [15:42] +1 received from bdmurray [15:42] +1 [15:42] +1 received from cyphermox [15:42] #endvote [15:42] +1 [15:42] Voting ended on: Grant ddstreet Contributing Developer [15:42] Votes for:5 Votes against:0 Abstentions:0 [15:42] Motion carried [15:42] \o/ [15:42] ddstreet: congratulations! [15:42] ddstreet, congrats! [15:42] Who wants to take care of adding and announcing? [15:43] I'll assign it to me [15:43] #action sil2100 to add ddstreet to the contributing developer team [15:43] ACTION: sil2100 to add ddstreet to the contributing developer team [15:44] #action sil2100 to announce ddstreet's new membership [15:44] ACTION: sil2100 to announce ddstreet's new membership [15:44] Ok, moving on [15:44] #topic SRU-UPLOADER 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-UPLOADER Applications [15:44] #subtopic Eric Desrochers (slashd) [15:44] #link https://wiki.ubuntu.com/slashd/sru-uploader [15:44] slashd: hello! Please introduce yourself :) [15:45] My name is Eric (Ubuntu Member/Contributing Developer) working for Canonical for about 3 years now. I'm a Software Engineer in the Sustaining Engineering Group (Canonical STS) help in driving Ubuntu Advantage customer and community bugs into resolution by troubleshooting, fixing bugs, providing guidance & workarounds, for different areas of expertise which may cover areas such as: kernel, drivers, virtualization, network, [15:45] cloud, storage setups, ... I'm working on various packaging aspects including hotfix/testfix and of course : SRU, ... [15:45] Wiki SRU Uploader Application : https://wiki.ubuntu.com/slashd/sru-uploader [15:45] LP : https://launchpad.net/~slashd [15:45] Sponsored Uploads : http://ubuntu-dev.alioth.debian.org/cgi-bin/ubuntu-sponsorships.cgi?render=html&sponsor=&sponsor_search=name&sponsoree=Eric+Desrochers&sponsoree_search=name [15:45] Questions please [15:46] * rbasak is reading [15:48] hm, you have a strange (interesting?) style of formatting changelog entries I noticed [15:48] Can you talk about bug 1579609? It looks like it took a couple of uploads to fix it. [15:48] bug 1579609 in os-prober (Ubuntu Xenial) "os-prober bug resulting in possible FS corruption" [Critical,Fix released] https://launchpad.net/bugs/1579609 [15:49] bdmurray, yeah, I was working with cyphermox on this (joint work) and cjwatson was also working on his side separately, so we did a few upload in -proposed but decided to set them verification-failed as we found new bugs, and new thing to add based on the joint effort [15:49] but we have now a release that addresses everything in -update now [15:50] version 3.3 IIRC [15:50] ...3.3 [15:50] Did all those changes also make it into zesty? [15:50] I don't think anyone can be blamed for it taking a few goes to get os-prober stuff right at the moment FWIW [15:50] there's a different and much more invasive approach in zesty [15:51] bdmurray, there is some bit missing in zesty still, cyphermox prefer to keep the re-work form cjwatson for Zesty only. [15:51] (er, sorry, I just saw the highlight of my name, since this is a DMB meeting I should probably butt out) [15:51] cjwatson: nah, it's good your input is welcome [15:51] cjwatson, thanks for jumping on the discussion ;) [15:52] Okay, that's all I had. [15:52] slashd: can you tell me what sort of things you expect to put in the "Regression Potential" section of the SRU paperwork? [15:53] rbasak, just to make sure we are on the same page, are you referring to the SRU justification ? [15:53] template [15:53] Right [15:53] slashd: Do you envision yourself sponsoring other SRU uploads? [15:54] I'm expecting someone doing the SRU or myself, to evaluate all possible scenarios of failure, or note any potential risk (major or minor) or behavoural changes (if any) [15:55] bdmurray, I'm expecting to do it yes for help other in my team eventually [15:55] slashd: for the SRU uploads you prepared so far, were you also preparing all the SRU paperwork (the SRU template in the description)? [15:55] or wider (depending on the needs and how I can help) [15:56] sil21000, yes + debdiff for all affected releases [15:56] * rbasak puts on his ~ubuntu-sru hat for a moment [15:56] slashd: Not specifically related to your application but why is bug 1670696 worth fixing? [15:56] bug 1670696 in makedumpfile (Ubuntu Zesty) "Typo in error msg when no crashkernel memory reservation is set" [Medium,In progress] https://launchpad.net/bugs/1670696 [15:57] s/fixing/SRUing/ [15:57] bdmurray, in a specific release or in general ? [15:57] Looking at the paperwork in 1593378, 1452202, 1648901, 1579609 and 1579609, I think the regression potential sections are all missing the "it's important to make the effort to think about what could happen in the event of a regression" part. [15:58] I'm relatively new on ~ubuntu-sru and I understand that I push harder on this than the others. [15:58] slashd: Why is there a xenial task? [15:58] And this is the first SRU uploader application, so I'm not sure it's right to hold you to a higher standard than others, for example existing core devs. [15:59] I'd say yes [15:59] rbasak, I see it in #1593378, havent' check them all, but I normally pay really good attention to it, by reading one than once and updating several time until I find the justification good enought in my point of view [15:59] (not because of him specifically) [15:59] but in general, we should push for what's best for the archive/distro, not necessarily based on what's happened before [16:00] IMHO of course [16:00] So I think I'm +1 on this currently, but I also think it's appropriate to call out. [16:00] And I think that future applicants for this new team would be the ones who should hold the standard up for SRU process quality. [16:00] looking at 1593378 it might help to also say how long the patch has been in place e.g. 10 months or whatever [16:01] Any other questions? [16:01] I hope this application is being watched closely by potential future applicants. [16:01] rbasak: yep [16:02] slashd: I'm still curious about the X task for 1670696... [16:02] So I'd like to say that I'll expect the SRUs provided as examples against future applications to only increase in quality to the (new) higher standard I'd like to see. [16:03] But for slashd, I appreciate that he's the first and that he's only what existing uploaders do, so I don't think it'd productive to decline this application. [16:03] Thank you for reading. I have no further questions. [16:04] bdmurray: are you still waiting for an answer? [16:04] bdmurray, sure well I agree that it's not affecting the functionnality of the software, but this is a typo that can confuse ppl ("kenrel" instead of "kernel") not technical enough with kernel term [16:05] Its not relevant to my vote, but I'd reject that SRU unless it was bundled with other real fixes. [16:05] bdmurray noted [16:06] Ok, let's vote [16:06] Its some amount of work to update the archive etc.. and it doesn't seem warranted in the case of a typo. [16:06] bdmurray, ack [16:06] Also, there's *always* a regression risk. [16:07] That patch itself may not introduce a regression. [16:07] #vote Grant slashd SRU-UPLOADER [16:07] Please vote on: Grant slashd SRU-UPLOADER [16:07] 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) [16:07] But a rebuild might if the build is accidentally non-deterministic, or if dependencies have changed. [16:07] make sense [16:08] Or a user could be parsing error messages in some script somewhere. [16:08] +1 [16:08] +1 received from rbasak [16:08] +1 [16:08] +1 received from bdmurray [16:08] +1 [16:08] +1 received from sil2100 [16:08] +1 [16:08] +1 received from cyphermox [16:09] +1 [16:09] +1 received from micahg [16:09] #endvote [16:09] Voting ended on: Grant slashd SRU-UPLOADER [16:09] Votes for:5 Votes against:0 Abstentions:0 [16:09] Motion carried [16:09] slashd: congratulations as well! \o/ [16:09] Congratulations on the first member of a team that hasn't been created yet :-) [16:09] \o/ thanks guys [16:09] rbasak: will you take care of this? [16:10] Since this requires creation of the team as well [16:10] Yes, but as I'm on vacation I'd like to do it when I'm back on Monday, if that's OK slashd? [16:10] rbasak, sure [16:10] #action rbasak to create and add slashd to the new SRU-UPLOADERS team [16:10] ACTION: rbasak to create and add slashd to the new SRU-UPLOADERS team [16:10] * rbasak will not be using all-caps :-P [16:10] #action rbasak to announce slashd's new SRU-UPLOADERS team membership [16:10] ACTION: rbasak to announce slashd's new SRU-UPLOADERS team membership [16:10] Hey, I'm just using what's in the agenda! [16:11] I realise that ;) [16:11] I thought that was official or something ;p [16:11] It should be SRU-uploaders though! [16:11] #topic Any other business === 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: Any other business [16:11] Ok, final topic [16:11] When we rename to ~ubuntu-SRU perhaps? :-P [16:11] fossfreedom's budgie application [16:11] don't tempt me [16:12] So it seems his application is stalled with not everyone voting yet [16:12] But his case is a very difficult one [16:12] I think I did vote, did that get lost like chiluks? [16:12] micahg: late comment: fossfreedom wasn't told that he needed to come back with more endorsements on the mailing list or at the December meeting [16:12] We need to resolve it and inform him of our decision [16:13] Ah [16:13] bdmurray: indeed I see your vote in my inbox, why didn't I see it before? [16:13] Magic [16:14] Ok, so I think during the IRC meeting we had: Votes for:3 Votes against:1 Abstentions:1 [16:14] And then bdmurray's -1 [16:14] So his application has been rejected [16:15] I think we need to just announce that properly, this has somehow been very troublesome [16:15] So it stands at 3:2:1? [16:15] Yeah, not sure if we'll ever get infinity's vote [16:15] If so, then theoretically if he received a +1 from infinity then he could still be approved. [16:16] Right [16:16] Technically he is so far "not carried" rather then "rejected" then. [16:16] Ok, I'll put this on my plate then, I'll poke infinity directly and if not, just send out the current result [16:17] #action sil2100 to finalize fossfreedom's application vote situation [16:17] ACTION: sil2100 to finalize fossfreedom's application vote situation [16:17] Sounds good. Thanks sil2100 [16:17] thanks [16:17] Ok, I think we're a bit overdue already [16:17] Anything else? [16:18] I'll update the agenda in a bit with all what happened today [16:18] #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:18] Meeting ended Mon Mar 13 16:18:18 2017 UTC. [16:18] Minutes: http://ubottu.com/meetingology/logs/ubuntu-meeting/2017/ubuntu-meeting.2017-03-13-15.12.moin.txt [16:18] Thanks everyone o/ [16:18] o/ [16:18] Thank you for chairing! [16:18] * rbasak gets back to his vacation :-) [16:19] rbasak: have a nice rest! Thanks for appearing anyway :) [16:31] \o [16:31] hello [16:31] #startmeeting [16:31] Meeting started Mon Mar 13 16:31:17 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] The meeting agenda can be found at: [16:31] [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting [16:31] [TOPIC] Weekly stand-up report === meetingology changed the topic of #ubuntu-meeting to: Weekly stand-up report [16:31] mdeslaur: you're up [16:31] I'm in the happy place this week [16:32] I have a bunch of updates that I'll be publishing in a few minutes [16:32] after that, I'll work on more updates [16:32] lather, rinse, repeat [16:32] sbeattie: you're up [16:32] I'm also in the happy place [16:32] I have glibc updates to finish testing and publish [16:33] I need to investigate some qa-r-t regressions/issues for the kernel team, around some of the new kernels they're publishing, as well as for arm64/trusty, which I don't think they'd been testing consistently in the past. [16:33] after that, I'll look for more updates to pick up. [16:34] that's it for me, tyhicks? [16:34] i'm on community this week [16:34] I'm also working on an embargoed issue [16:35] I am still trying to get back to my seccomp development work [16:35] that should happen early this week [16:35] and I see that I still have a design review on my todo list [16:35] that's it for me [16:35] jjohansen: you're up [16:35] ah, I also have a snapd PR to review [16:37] I'll be continuinng work on apparmor upstreaming, dconf/gsettings FFE, and fixing bugs eg. I still have to figure out the regression that resulted in a couple of patches being reverted from the sru kernel [16:38] hrmm, I think that is it for me sarnold you're up [16:38] I'm on bug triage this week; I'm still working on shadow and the mellon MIR; /me is dreaming of a bug-free week.. ;) [16:38] just a sec [16:39] jjohansen: what's still needed for the FFE? [16:40] tyhicks: mostly doing the paper work, putting the lastest stuff in the ppa for people to use [16:40] oh and I was adding a couple more regression tests [16:40] jjohansen: are there any more revisions for you to work on? [16:40] ok [16:41] sarnold: sorry; go ahead [16:41] tyhicks: heh, afaik that's the entire report :) [16:42] no worries :) [16:42] daylight saving time is a hell of a thing [16:42] chrisccoulson: you're up [16:43] Sorry, was afk briefly [16:43] I need to do a firefox update this week to fix a regression. I've also got thunderbird to update [16:44] There was a Chromium release next week, so I'll be preparing the corresponding Oxide release [16:44] I've also got an embargoed update [16:45] Fingers crossed I'll be able to get firefox building with rustc / cargo this week - all of the bits are in place now [16:45] Other than that, I'll be catching up on Oxide work / reviews this week [16:45] That's me done [16:45] I'm on CVE triage this week [16:45] I'm still poking at the notification script and other CVE tools [16:46] I have to prep for a webinar and do other internal work items [16:46] If I have additional time, I'll work on updates for vivid for core and touch [16:46] back to you tyhicks [16:46] thanks [16:46] [TOPIC] Highlighted packages === meetingology changed the topic of #ubuntu-meeting to: Highlighted packages [16:47] 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:47] 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:47] http://people.canonical.com/~ubuntu-security/cve/pkg/citadel.html [16:47] http://people.canonical.com/~ubuntu-security/cve/pkg/undertow.html [16:47] http://people.canonical.com/~ubuntu-security/cve/pkg/duck.html [16:47] http://people.canonical.com/~ubuntu-security/cve/pkg/lshell.html [16:47] http://people.canonical.com/~ubuntu-security/cve/pkg/libemail-address-perl.html [16:47] [TOPIC] Miscellaneous and Questions === meetingology changed the topic of #ubuntu-meeting to: Miscellaneous and Questions [16:47] Does anyone have any other questions or items to discuss? [16:48] mdeslaur, sbeattie, jjohansen, sarnold, ChrisCoulson, ratliff: Thanks! [16:48] #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:48] Meeting ended Mon Mar 13 16:48:16 2017 UTC. [16:48] Minutes: http://ubottu.com/meetingology/logs/ubuntu-meeting/2017/ubuntu-meeting.2017-03-13-16.31.moin.txt [16:48] thank you, tyhicks! [16:48] thanks tyhicks! [16:48] thanks tyhicks [16:51] thanks tyhicks [16:51] tyhicks: thanks!