[14:59] <slashd> o/
[14:59] <sil2100> o/
[15:00] <rbasak> o/
[15:00] <ddstreet> o/
[15:00] <micahg> o/
[15:01] <sil2100> We need one more for quorum
[15:02] <sil2100> Who's turn is it for chairing? Is the agenda up-to-date with that?
[15:02] <rbasak> The chair rotation doesn't really work at all since some DMB members rarely manage to make a meeting.
[15:03] <rbasak> 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] <micahg> I have a meeting at 15:30, so unless we want to race through the meeting, I can't do it
[15:03] <micahg> sil2100: ?
[15:04] <sil2100> 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] <sil2100> Not a big thing though
[15:05] <sil2100> Still, I'd appreciate if we'd have quorum
[15:05]  * micahg wonders what happened with the election
[15:06] <rbasak> I thought we had an action for that. Did it not get carried forward?
[15:06] <sil2100> I don't think the agenda got properly updated
[15:06] <micahg> I didn't see a call for nomincations
[15:06] <sil2100> I saw something in the meeting logs, but not on the agenda
[15:07] <micahg> s/nomications/nominations/
[15:07] <sil2100> ACTION: bdmurray to sort out votes and related items in respect of the two upcoming expiring DMB memberships (rbasak, 20:41)
[15:07] <sil2100> This was from the last meeting, but not present on the agenda
[15:07] <sil2100> Ok, I'll chair today and try to get it up to date after the meeting
[15:07] <rbasak> Thanks!
[15:08] <sil2100> We need one more member for quorum though - should we start without 4 people now anyway?
[15:08] <rbasak> I'm getting pretty fed up with this tbh.
[15:08] <rbasak> 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] <sil2100> Yeah, I'm a bit annoyed too, although I must admit that I had some missed meetings myself
[15:10] <rbasak> 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] <sil2100> 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] <micahg> I'll still be here, just a little distracted ;)
[15:11] <sil2100> Ah, ok
[15:11] <rbasak> And it creates work for those who *do* make it.
[15:11] <rbasak> 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] <bdmurray> I'm hear but may need to leave suddenly.
[15:12] <sil2100> \o/
[15:12] <sil2100> #startmeeting DMB
[15:12] <meetingology> 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] <meetingology> Available commands: action commands idea info link nick
[15:12] <sil2100> #topic Review of previous action items
[15:12] <sil2100> Ok, checking previous action items from the logs
[15:13] <bdmurray> my item is not done
[15:13] <bdmurray> Do I need to contact the whole TB or just a member regarding the extension?
[15:13] <sil2100> Has the addition of rosco2 to the contributing developer team been made and announced?
[15:13] <jbicha> one more unfinished item (not on the agenda) is handling fossfreedom's application for upload rights for budgie pkgs
[15:15] <sil2100> jbicha: ok, we'll discuss that during AOB, since I guess this one was very tricky
[15:15] <micahg> wasn't fossfreedom supposed to come back with endorsements after a period of time
[15:15] <sil2100> I think it was hard since he was applying for a non-existing packageset too
[15:15] <sil2100> Since the packageset wasn't created yet
[15:15] <sil2100> Anyway, we'll get back to it
[15:15] <micahg> ok
[15:15] <sil2100> rbasak: did you add and announce Rosco2?
[15:16] <sil2100> I see that was set for you
[15:16] <rbasak> I don't recall.
[15:16] <sil2100> ACTION: rbasak to add Rosco2 to the contributing developer team (rbasak, 19:32)
[15:16]  * rbasak works off the agenda page
[15:16] <sil2100> ACTION: rbasak to announce Rosco2's new contributing developer team membership (rbasak, 19:32)
[15:16] <sil2100> http://ubottu.com/meetingology/logs/ubuntu-meeting/2017/ubuntu-meeting.2017-02-27-19.15.html
[15:16] <rbasak> OK give those actions to me again please.
[15:16] <sil2100> Ok
[15:17] <sil2100> #action rbasak to add Rosco2 to the contributing developer team (carried-over)
[15:17] <meetingology> ACTION: rbasak to add Rosco2 to the contributing developer team (carried-over)
[15:17] <sil2100> #action rbasak to announce Rosco2's new contributing developer team membership (carried over)
[15:17] <meetingology> ACTION: rbasak to announce Rosco2's new contributing developer team membership (carried over)
[15:17] <sil2100> bdmurray: as for your thing, I think DMB memberships are handled by the DMB, right?
[15:17] <rbasak> Thanks! Sorry, I checked only the agenda page earlier today, and assumed I had no actions.
[15:18] <micahg> DMB memberships are handled by the TB
[15:18] <sil2100> I'll fix that up today
[15:18] <sil2100> micahg: ah, hm, ok
[15:18] <micahg> oh, membership in DMB owned teams, yeah, we can do those
[15:18] <micahg> I thought you meant actually DMB team membership
[15:18] <sil2100> It's about DMB membership extension
[15:19] <micahg> yeah, TB then
[15:19] <sil2100> ACTION: bdmurray to sort out votes and related items in respect of the two upcoming expiring DMB memberships (rbasak, 20:41)
[15:19] <sil2100> micahg: do you know if one TB member is enough?
[15:19] <sil2100> Or does it have to involve a vote?
[15:19] <micahg> in the past 1 person has just done it I think
[15:20] <bdmurray> I'll start with one then.
[15:20] <sil2100> micahg: thanks!
[15:20] <sil2100> bdmurray: ok, I'll carry it over then as well
[15:20] <sil2100> #action bdmurray to sort out votes and related items in respect of the two upcoming expiring DMB memberships (carried over)
[15:20] <meetingology> ACTION: bdmurray to sort out votes and related items in respect of the two upcoming expiring DMB memberships (carried over)
[15:21] <sil2100> ACTION: rbasak to sort out the SRU uploaders team (rbasak, 20:41)
[15:21] <sil2100> rbasak: that's done I think? ^
[15:21] <rbasak> I think so. I deferred actually creating the team in Launchpad until we had one member.
[15:21] <sil2100> Makes sense, we might have one today!
[15:21] <rbasak> I did announce it.
[15:22] <rbasak> (and invite applications)
[15:22] <rbasak> Yes :)
[15:22] <sil2100> Ok, so one action item finished, woot!
[15:23] <sil2100> 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] <sil2100> Since he was busy
[15:23] <sil2100> So this is done as well
[15:23] <sil2100> Ok, let's move on
[15:24] <sil2100> #topic Ubuntu Contributing Developer Applications
[15:24] <sil2100> #subtopic Dan Streetman (ddstreet)
[15:24] <ddstreet> o/
[15:24] <sil2100> ddstreet: please introduce yourself o/
[15:24] <ddstreet> hi guys, I'm Dan
[15:25] <ddstreet> I'm applying for contributing developer
[15:25] <ddstreet> my application page is https://wiki.ubuntu.com/ddstreet/UbuntuContributingDeveloperApplication
[15:26] <sil2100> Any questions?
[15:27] <rbasak> I reviewed ddstreet's application when he asked me to endorse him. I have no questions.
[15:27] <cyphermox> no questions
[15:28] <micahg> I have a question
[15:28] <micahg> what happened this cycle
[15:28] <ddstreet> what do you mean?
[15:28] <ddstreet> or is that q not for me?
[15:28] <micahg> I see uploads through the end of yakkety
[15:29] <ddstreet> ah ok
[15:29] <ddstreet> a lot of the work i do is in the kernel
[15:29] <ddstreet> so, for the last several months i've been doing kernel work
[15:29] <ddstreet> and haven't had any userspace package uploads
[15:29] <micahg> is there a reason there's no endorseement from kernel devs?
[15:30] <ddstreet> oversight by me...i can ask them
[15:30] <ddstreet> i thought the endorsements needed to be from userspace pkg uploaders
[15:30] <micahg> any around that can vouch in IRC for you?
[15:31] <rbasak> userspace pkg uploaders> I think any and all Ubuntu development work qualifies :)
[15:31] <micahg> 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] <ddstreet> sure kamal probably can
[15:32] <sil2100> Not sure if he's around yet though
[15:32] <sil2100> (it's around 8:30 am at his place I think)
[15:33] <micahg> I'm seeing if I can see what I want to see in LP
[15:33]  * bdmurray place too
[15:34] <sil2100> micahg: ok, give me a sign once your doubts are cleared
[15:34] <micahg> ddstreet: are those private repos?
[15:34] <ddstreet> are which private repos?
[15:34] <ddstreet> my lp git repos?
[15:35] <micahg> the kernel work
[15:35] <micahg> yeah
[15:35] <ddstreet> those are for customer kernel bugs i've worked
[15:35] <micahg> oh, sorry, I think I see it now
[15:35] <rbasak> 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] <rbasak> 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] <micahg> ok, I think I'm good, I assume this work was merged in
[15:36] <micahg> or most of it at least
[15:37] <micahg> sil2100: I'm good
[15:38] <rbasak> I guess my question is moot then. Feel free to skip it and move on :)
[15:38] <sil2100> 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] <micahg> yeah, I agree with sil2100
[15:38] <sil2100> So it's good
[15:38] <sil2100> Ok then, let's vote!
[15:38] <rbasak> Interesting, thanks.
[15:38] <ddstreet> kamal is here if you guys want to ask him
[15:38] <sil2100> (it's not my main language so remember it's just my intepretation)
[15:38] <ddstreet> about my kernel work
[15:38] <ddstreet> kamal o/
[15:39] <kamal> hi o/
[15:39] <sil2100> micahg: want to ask about kernel work still, or should we start voting?
[15:39] <bdmurray> rbasak: I think it depends on the period of time between last upload and application.
[15:39] <micahg> oh, if kamal wants to endorse, by all means :0
[15:39] <micahg> :)
[15:40] <ddstreet> kamal have i done some satisfactory kernel work in the past?
[15:40] <kamal> 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] <ddstreet> in your experience? :)
[15:40] <ddstreet> thnx
[15:40] <kamal> I've found ddstreet to be easy to work with, and his work is of high quality.
[15:40] <kamal> from the Ubuntu Kernel team's perspective, ddstreet is a good kernel contributor and a quality developer.
[15:40] <kamal> ..
[15:41] <sil2100> kamal: thanks!
[15:41] <sil2100> Ok, I think we're good to start the vote
[15:41] <sil2100> #vote Grant ddstreet Contributing Developer
[15:41] <meetingology> Please vote on: Grant ddstreet Contributing Developer
[15:41] <meetingology> 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] <rbasak> +1
[15:41] <meetingology> +1 received from rbasak
[15:41] <sil2100> +1
[15:41] <meetingology> +1 received from sil2100
[15:41] <micahg> +1
[15:41] <meetingology> +1 received from micahg
[15:42] <bdmurray> +1
[15:42] <meetingology> +1 received from bdmurray
[15:42] <cyphermox> +1
[15:42] <meetingology> +1 received from cyphermox
[15:42] <sil2100> #endvote
[15:42] <kamal> +1
[15:42] <meetingology> Voting ended on: Grant ddstreet Contributing Developer
[15:42] <meetingology> Votes for:5 Votes against:0 Abstentions:0
[15:42] <meetingology> Motion carried
[15:42] <ddstreet> \o/
[15:42] <sil2100> ddstreet: congratulations!
[15:42] <kamal> ddstreet, congrats!
[15:42] <sil2100> Who wants to take care of adding and announcing?
[15:43] <sil2100> I'll assign it to me
[15:43] <sil2100> #action sil2100 to add ddstreet to the contributing developer team
[15:43] <meetingology> ACTION: sil2100 to add ddstreet to the contributing developer team
[15:44] <sil2100> #action sil2100 to announce ddstreet's new membership
[15:44] <meetingology> ACTION: sil2100 to announce ddstreet's new membership
[15:44] <sil2100> Ok, moving on
[15:44] <sil2100> #topic SRU-UPLOADER Applications
[15:44] <sil2100> #subtopic Eric Desrochers (slashd)
[15:44] <sil2100> #link https://wiki.ubuntu.com/slashd/sru-uploader
[15:44] <sil2100> slashd: hello! Please introduce yourself :)
[15:45] <slashd> 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] <slashd> cloud, storage setups, ... I'm working on various packaging aspects including hotfix/testfix and of course : SRU, ...
[15:45] <slashd> Wiki SRU Uploader Application : https://wiki.ubuntu.com/slashd/sru-uploader
[15:45] <slashd> LP : https://launchpad.net/~slashd
[15:45] <slashd> 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] <sil2100> Questions please
[15:46]  * rbasak is reading
[15:48] <sil2100> hm, you have a strange (interesting?) style of formatting changelog entries I noticed
[15:48] <bdmurray> Can you talk about bug 1579609? It looks like it took a couple of uploads to fix it.
[15:49] <slashd> 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] <slashd> but we have now a release that addresses everything in -update now
[15:50] <slashd> version 3.3 IIRC
[15:50] <slashd> ...3.3
[15:50] <bdmurray> Did all those changes also make it into zesty?
[15:50] <cjwatson> 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] <cjwatson> there's a different and much more invasive approach in zesty
[15:51] <slashd> bdmurray, there is some bit missing in zesty still, cyphermox prefer to keep the re-work form cjwatson for Zesty only.
[15:51] <cjwatson> (er, sorry, I just saw the highlight of my name, since this is a DMB meeting I should probably butt out)
[15:51] <cyphermox> cjwatson: nah, it's good your input is welcome
[15:51] <slashd> cjwatson, thanks for jumping on the discussion ;)
[15:52] <bdmurray> Okay, that's all I had.
[15:52] <rbasak> slashd: can you tell me what sort of things you expect to put in the "Regression Potential" section of the SRU paperwork?
[15:53] <slashd> rbasak, just to make sure we are on the same page, are you referring to the SRU justification ?
[15:53] <slashd> template
[15:53] <rbasak> Right
[15:53] <bdmurray> slashd: Do you envision yourself sponsoring other SRU uploads?
[15:54] <slashd> 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] <slashd> bdmurray, I'm expecting to do it yes for help other in my team eventually
[15:55] <sil2100> 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] <slashd> or wider (depending on the needs and how I can help)
[15:56] <slashd> sil21000, yes + debdiff for all affected releases
[15:56]  * rbasak puts on his ~ubuntu-sru hat for a moment
[15:56] <bdmurray> slashd: Not specifically related to your application but why is bug 1670696 worth fixing?
[15:57] <bdmurray> s/fixing/SRUing/
[15:57] <slashd> bdmurray, in a specific release or in general ?
[15:57] <rbasak> 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] <rbasak> I'm relatively new on ~ubuntu-sru and I understand that I push harder on this than the others.
[15:58] <bdmurray> slashd: Why is there a xenial task?
[15:58] <rbasak> 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] <micahg> I'd say yes
[15:59] <slashd> 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] <micahg> (not because of him specifically)
[15:59] <micahg> but in general, we should push for what's best for the archive/distro, not necessarily based on what's happened before
[16:00] <micahg> IMHO of course
[16:00] <rbasak> So I think I'm +1 on this currently, but I also think it's appropriate to call out.
[16:00] <rbasak> 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] <bdmurray> 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] <sil2100> Any other questions?
[16:01] <rbasak> I hope this application is being watched closely by potential future applicants.
[16:01] <tinoco> rbasak: yep
[16:02] <bdmurray> slashd: I'm still curious about the X task for 1670696...
[16:02] <rbasak> 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] <rbasak> 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] <rbasak> Thank you for reading. I have no further questions.
[16:04] <sil2100> bdmurray: are you still waiting for an answer?
[16:04] <slashd> 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] <bdmurray> Its not relevant to my vote, but I'd reject that SRU unless it was bundled with other real fixes.
[16:05] <slashd> bdmurray noted
[16:06] <sil2100> Ok, let's vote
[16:06] <bdmurray> Its some amount of work to update the archive etc.. and it doesn't seem warranted in the case of a typo.
[16:06] <slashd> bdmurray, ack
[16:06] <rbasak> Also, there's *always* a regression risk.
[16:07] <rbasak> That patch itself may not introduce a regression.
[16:07] <sil2100> #vote Grant slashd SRU-UPLOADER
[16:07] <meetingology> Please vote on: Grant slashd SRU-UPLOADER
[16:07] <meetingology> 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] <rbasak> But a rebuild might if the build is accidentally non-deterministic, or if dependencies have changed.
[16:07] <slashd> make sense
[16:08] <rbasak> Or a user could be parsing error messages in some script somewhere.
[16:08] <rbasak> +1
[16:08] <meetingology> +1 received from rbasak
[16:08] <bdmurray> +1
[16:08] <meetingology> +1 received from bdmurray
[16:08] <sil2100> +1
[16:08] <meetingology> +1 received from sil2100
[16:08] <cyphermox> +1
[16:08] <meetingology> +1 received from cyphermox
[16:09] <micahg> +1
[16:09] <meetingology> +1 received from micahg
[16:09] <sil2100> #endvote
[16:09] <meetingology> Voting ended on: Grant slashd SRU-UPLOADER
[16:09] <meetingology> Votes for:5 Votes against:0 Abstentions:0
[16:09] <meetingology> Motion carried
[16:09] <sil2100> slashd: congratulations as well! \o/
[16:09] <rbasak> Congratulations on the first member of a team that hasn't been created yet :-)
[16:09] <slashd> \o/ thanks guys
[16:09] <sil2100> rbasak: will you take care of this?
[16:10] <sil2100> Since this requires creation of the team as well
[16:10] <rbasak> 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] <slashd> rbasak, sure
[16:10] <sil2100> #action rbasak to create and add slashd to the new SRU-UPLOADERS team
[16:10] <meetingology> 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] <sil2100> #action rbasak to announce slashd's new SRU-UPLOADERS team membership
[16:10] <meetingology> ACTION: rbasak to announce slashd's new SRU-UPLOADERS team membership
[16:10] <sil2100> Hey, I'm just using what's in the agenda!
[16:11] <rbasak> I realise that ;)
[16:11] <sil2100> I thought that was official or something ;p
[16:11] <bdmurray> It should be SRU-uploaders though!
[16:11] <sil2100> #topic Any other business
[16:11] <sil2100> Ok, final topic
[16:11] <rbasak> When we rename to ~ubuntu-SRU perhaps? :-P
[16:11] <sil2100> fossfreedom's budgie application
[16:11] <bdmurray> don't tempt me
[16:12] <sil2100> So it seems his application is stalled with not everyone voting yet
[16:12] <sil2100> But his case is a very difficult one
[16:12] <bdmurray> I think I did vote, did that get lost like chiluks?
[16:12] <jbicha> 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] <sil2100> We need to resolve it and inform him of our decision
[16:13] <sil2100> Ah
[16:13] <sil2100> bdmurray: indeed I see your vote in my inbox, why didn't I see it before?
[16:13] <sil2100> Magic
[16:14] <sil2100> Ok, so I think during the IRC meeting we had: Votes for:3 Votes against:1 Abstentions:1
[16:14] <sil2100> And then bdmurray's -1
[16:14] <sil2100> So his application has been rejected
[16:15] <sil2100> I think we need to just announce that properly, this has somehow been very troublesome
[16:15] <rbasak> So it stands at 3:2:1?
[16:15] <sil2100> Yeah, not sure if we'll ever get infinity's vote
[16:15] <rbasak> If so, then theoretically if he received a +1 from infinity then he could still be approved.
[16:16] <rbasak> Right
[16:16] <rbasak> Technically he is so far "not carried" rather then "rejected" then.
[16:16] <sil2100> 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] <sil2100> #action sil2100 to finalize fossfreedom's application vote situation
[16:17] <meetingology> ACTION: sil2100 to finalize fossfreedom's application vote situation
[16:17] <rbasak> Sounds good. Thanks sil2100
[16:17] <jbicha> thanks
[16:17] <sil2100> Ok, I think we're a bit overdue already
[16:17] <sil2100> Anything else?
[16:18] <sil2100> I'll update the agenda in a bit with all what happened today
[16:18] <sil2100> #endmeeting
[16:18] <meetingology> Meeting ended Mon Mar 13 16:18:18 2017 UTC.
[16:18] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2017/ubuntu-meeting.2017-03-13-15.12.moin.txt
[16:18] <sil2100> Thanks everyone o/
[16:18] <slashd> o/
[16:18] <rbasak> Thank you for chairing!
[16:18]  * rbasak gets back to his vacation :-)
[16:19] <sil2100> rbasak: have a nice rest! Thanks for appearing anyway :)
[16:31] <mdeslaur> \o
[16:31] <tyhicks> hello
[16:31] <tyhicks> #startmeeting
[16:31] <meetingology> 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] <meetingology> Available commands: action commands idea info link nick
[16:31] <tyhicks> The meeting agenda can be found at:
[16:31] <tyhicks> [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting
[16:31] <tyhicks> [TOPIC] Weekly stand-up report
[16:31] <tyhicks> mdeslaur: you're up
[16:31] <mdeslaur> I'm in the happy place this week
[16:32] <mdeslaur> I have a bunch of updates that I'll be publishing in a few minutes
[16:32] <mdeslaur> after that, I'll work on more updates
[16:32] <mdeslaur> lather, rinse, repeat
[16:32] <mdeslaur> sbeattie: you're up
[16:32] <sbeattie> I'm also in the happy place
[16:32] <sbeattie> I have glibc updates to finish testing and publish
[16:33] <sbeattie> 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] <sbeattie> after that, I'll look for more updates to pick up.
[16:34] <sbeattie> that's it for me, tyhicks?
[16:34] <tyhicks> i'm on community this week
[16:34] <tyhicks> I'm also working on an embargoed issue
[16:35] <tyhicks> I am still trying to get back to my seccomp development work
[16:35] <tyhicks> that should happen early this week
[16:35] <tyhicks> and I see that I still have a design review on my todo list
[16:35] <tyhicks> that's it for me
[16:35] <tyhicks> jjohansen: you're up
[16:35] <tyhicks> ah, I also have a snapd PR to review
[16:37] <jjohansen> 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] <jjohansen> hrmm, I think that is it for me sarnold you're up
[16:38] <sarnold> 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] <tyhicks> just a sec
[16:39] <tyhicks> jjohansen: what's still needed for the FFE?
[16:40] <jjohansen> tyhicks: mostly doing the paper work, putting the lastest stuff in the ppa for people to use
[16:40] <jjohansen> oh and I was adding a couple more regression tests
[16:40] <tyhicks> jjohansen: are there any more revisions for you to work on?
[16:40] <tyhicks> ok
[16:41] <tyhicks> sarnold: sorry; go ahead
[16:41] <sarnold> tyhicks: heh, afaik that's the entire report :)
[16:42] <tyhicks> no worries :)
[16:42] <sarnold> daylight saving time is a hell of a thing
[16:42] <tyhicks> chrisccoulson: you're up
[16:43] <chrisccoulson> Sorry, was afk briefly
[16:43] <chrisccoulson> I need to do a firefox update this week to fix a regression. I've also got thunderbird to update
[16:44] <chrisccoulson> There was a Chromium release next week, so I'll be preparing the corresponding Oxide release
[16:44] <chrisccoulson> I've also got an embargoed update
[16:45] <chrisccoulson> 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] <chrisccoulson> Other than that, I'll be catching up on Oxide work / reviews this week
[16:45] <chrisccoulson> That's me done
[16:45] <ratliff> I'm on CVE triage this week
[16:45] <ratliff> I'm still poking at the notification script and other CVE tools
[16:46] <ratliff> I have to prep for a webinar and do other internal work items
[16:46] <ratliff> If I have additional time, I'll work on updates for vivid for core and touch
[16:46] <ratliff> back to you tyhicks
[16:46] <tyhicks> thanks
[16:46] <tyhicks> [TOPIC] Highlighted packages
[16:47] <tyhicks> 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] <tyhicks> 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] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/citadel.html
[16:47] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/undertow.html
[16:47] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/duck.html
[16:47] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/lshell.html
[16:47] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/libemail-address-perl.html
[16:47] <tyhicks> [TOPIC] Miscellaneous and Questions
[16:47] <tyhicks> Does anyone have any other questions or items to discuss?
[16:48] <tyhicks> mdeslaur, sbeattie, jjohansen, sarnold, ChrisCoulson, ratliff: Thanks!
[16:48] <tyhicks> #endmeeting
[16:48] <meetingology> Meeting ended Mon Mar 13 16:48:16 2017 UTC.
[16:48] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2017/ubuntu-meeting.2017-03-13-16.31.moin.txt
[16:48] <ratliff> thank you, tyhicks!
[16:48] <sarnold> thanks tyhicks!
[16:48] <mdeslaur> thanks tyhicks
[16:51] <jjohansen> thanks tyhicks
[16:51] <sbeattie> tyhicks: thanks!