[16:33] <mdeslaur> \o
[16:33] <jjohansen> o/
[16:33] <jdstrand> hi!
[16:34] <chrisccoulson> o/
[16:34]  * sbeattie waves
[16:34] <jdstrand> #startmeeting
[16:34] <meetingology> Meeting started Mon Apr 14 16:34:34 2014 UTC.  The chair is jdstrand. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:34] <meetingology> Available commands: action commands idea info link nick
[16:34] <jdstrand> The meeting agenda can be found at:
[16:34] <jdstrand> [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting
[16:34] <jdstrand> [TOPIC] Announcements
[16:34] <jdstrand> Thanks to Patrik Lundin (patrik-lundin) provided debdiffs for lucid-precise for OpenAFS (LP: #1305807). Your work is very much appreciated and will keep Ubuntu users secure. Great job! :)
[16:34] <jdstrand> [TOPIC] Weekly stand-up report
[16:35] <jdstrand> I'll go first
[16:35] <jdstrand> I've got a short week this week (off friday) and next (off monday)
[16:35] <jdstrand> I'm on triage this week
[16:35] <jdstrand> I'd like to finish up install testing. I did desktop and server already and filed a couple of bugs
[16:36] <jdstrand> still going through touch
[16:36] <jdstrand> I'd like to take a look at scopes confinement
[16:36] <jdstrand> and get to some updates
[16:36] <jdstrand> mdeslaur: you're up
[16:36] <mdeslaur> I'm on community this week
[16:36] <mdeslaur> I'm off on monday also
[16:36] <mdeslaur> I'm working on the usual CVE updates
[16:37] <mdeslaur> that's pretty much it for me, sbeattie, you're up
[16:37] <sbeattie> I'm focused on apparmor again this week.
[16:37] <sbeattie> I'm still trying to wrap up my review of jjohansen's patches
[16:37] <sbeattie> as well as writing and doing some additional tests
[16:38] <sbeattie> I need to shave some yaks and upgrade a couple of my secondary systems to trusty
[16:39] <sbeattie> That's pretty much it for me; tyhicks, you're up
[16:40] <tyhicks> I didn't get to iterate on the aa.py patches last week, so I've still got to do that
[16:41] <tyhicks> I was just reminded that I need to respin the patches in the upstream dbus-daemon AA mediation bug after some feedback I received
[16:41] <tyhicks> after that, I need to take a look at my work items and sync up w/ mdeslaur
[16:41] <jdstrand> wasn't there kdbus stuff from a bit back?
[16:42] <tyhicks> jdstrand: ah, yes! that'll be what I focus on
[16:42] <tyhicks> thanks
[16:42] <tyhicks> that's it for me
[16:42] <tyhicks> jjohansen: you're up
[16:44] <jjohansen> I'm working on apparmor this week. I need to finish up the backport kernels for ubuntu touch, and finish up with several bugs lp1306804, two refcount bugs, a pivot_root bug, as well as kick out a new iteration of patches for review
[16:44] <jdstrand> jjohansen: which kernels are you doing?
[16:45] <jjohansen> jdstrand: for the backport?
[16:45] <jdstrand> yeah
[16:45] <jjohansen> jdstrand: atm 3.4 mako/manta but will also need to do flo
[16:45] <jjohansen> after that we can see
[16:46] <jdstrand> grouper might be interesting since several people on the team have it
[16:46] <jjohansen> yeah
[16:46] <jdstrand> unity hasn't run super great on it, but I noticed that is is actually useful if you clear out /var/crash/* and kill any running apports
[16:47] <jdstrand> not saying it is a high priority though. it isn't for me know that I have flo
[16:48] <jdstrand> jjohansen: oh, goldfish too-- that probably is a high priority
[16:48] <jdstrand> s/know/now/
[16:48] <jjohansen> jdstrand: your the only one on the team
[16:48] <jdstrand> with flo?
[16:48] <jjohansen> jdstrand: yeah goldfish too
[16:48] <jdstrand> (fyi, my flo is my personal device that I dual boot)
[16:49] <jjohansen> jdstrand: basically those 4 are all the same backport for apparmor
[16:49] <jdstrand> oh goldfish is with the others?
[16:49] <jdstrand> I either forgot or never knew that :)
[16:49] <mdeslaur> what's goldfish?
[16:49] <jjohansen> emulator
[16:49] <jdstrand> emulator
[16:49] <mdeslaur> oh
[16:50] <sarnold> do we have a handy table somewhere to convert these names into what they actually are?
[16:51] <mdeslaur> sarnold: I'm making one right now
[16:51] <jjohansen> sarnold: hrmm, I'm not sure we do for all of them, there is https://wiki.ubuntu.com/Touch/Devices for the earlier ones
[16:51] <tyhicks> https://wiki.ubuntu.com/Touch/Install#Supported_devices_and_codenames
[16:51] <mdeslaur> sarnold: before insanity sets in
[16:51] <sarnold> yay
[16:52] <mdeslaur> oh, well, there you go
[16:52] <mdeslaur> except for goldfish they're all there
[16:52] <jjohansen> anyways thats it for me sarnold you are up
[16:52] <sarnold> I'm in my happy place this week
[16:52] <sarnold> which this week means apparmor patch review
[16:52] <sarnold> I'm finished with all the MIRs for trusty :)
[16:53] <mdeslaur> \o/
[16:53] <sbeattie> yay
[16:53]  * jjohansen is not sure that is such a happy place, but is glad sarnold is a masochist
[16:53] <sarnold> yeah :) \o/ indeed :)
[16:53] <sarnold> but it'll be nice to reduce the number of not-checked-in patches for apparmor, so hooray
[16:54] <sarnold> that's me done, chrisccoulson?
[16:54] <chrisccoulson> hi :)
[16:54] <chrisccoulson> this week, i've got a chromium update
[16:55] <chrisccoulson> and i'm also currently investigating getting hangouts working in oxide (requires support for ppapi plugins)
[16:56] <chrisccoulson> other than that, it's business as usual :)
[16:56] <jdstrand> chrisccoulson: we already have those security updates in oxide 501, correct?
[16:57] <chrisccoulson> jdstrand, we're based on the dev channel, so I guess so. things are going to be a bit confusing until we're on the stable channel
[16:57] <jdstrand> chrisccoulson: yeah, you've got the plan to get there though. I forget when you said we'd be on stable...
[16:58] <chrisccoulson> i'm going to aim to branch for beta at the next chromium release. i think that's realistic now
[16:58] <chrisccoulson> so that would mean we'd be on stable within the next 2 releases
[16:58] <chrisccoulson> ie, by chromium 36
[16:58] <chrisccoulson> (we're on 34 now)
[16:59] <jdstrand> is that ~4 weeks?
[17:00] <chrisccoulson> it's a bit longer than that. the releases seem to be ~6 weeks
[17:00] <chrisccoulson> when do we do 14.04.1?
[17:01] <jdstrand> ah
[17:01] <jdstrand> ok
[17:01] <jdstrand> I couldn't remember if the major release was 2 weeks or 6
[17:02] <chrisccoulson> so, 12.04.1 was in august
[17:02] <jdstrand> that's fine
[17:02] <chrisccoulson> we can be on a stable channel quite a way before then :)
[17:03]  * jdstrand nods
[17:03] <jdstrand> I'm not worried, I just couldn't remember the timing
[17:03] <mdeslaur> what's special about 14.04.1?
[17:03] <chrisccoulson> i'll send an e-mail later so everybody is aware, but I think the aim should be that we branch on the next chromium release (~5-6 weeks from now)
[17:03] <jdstrand> mdeslaur: its when precise users get the update-manager recommendation to upgrade
[17:04] <mdeslaur> jdstrand: I know what it is, I just don't know why that has anything to do with oxide
[17:04] <jdstrand> webapp-container is used on the desktop
[17:04] <jdstrand> installed by default and uses oxide
[17:04] <mdeslaur> o_O?
[17:04] <mdeslaur> where?
[17:05] <jdstrand> webapps
[17:05] <jdstrand> this is so we don't need all the special code in firefox and chromium that was so brittle and either broke or blocked the updates
[17:05] <mdeslaur> wow
[17:05] <jdstrand> (this was the webapps' team plan for the 14.04 dev cycle all along)
[17:06] <jdstrand> it's in an image near you right now :)
[17:06] <mdeslaur> ok, hah, well it instantly segfaults for me in 14.04
[17:06] <jdstrand> uh
[17:06] <chrisccoulson> oh :/
[17:06] <jdstrand> it should not. are you up to date? please file a bug
[17:06] <jdstrand> 1.0.0~bzr501-0ubuntu1 is the latest
[17:07] <mdeslaur> does it require 3d?
[17:07] <mdeslaur> it explodes in a vm, but not on my main desktop
[17:08] <chrisccoulson> aha, qtquick requires a GL api
[17:08] <mdeslaur> ah, ok, it segfaults because it doesn't have enough ram
[17:08] <mdeslaur> bumping up the ram in the vm fixed it
[17:11] <mdeslaur> jdstrand, chrisccoulson: sorry for interrupting, please continue
[17:11] <chrisccoulson> oh, I think I'm done now anyway :)
[17:11] <jdstrand> [TOPIC] Highlighted packages
[17:11] <jdstrand> 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.
[17:11] <jdstrand> 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.
[17:12] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/pywbem.html
[17:12] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/php-radius.html
[17:12] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/ibm-3270.html
[17:12] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/tpp.html
[17:12] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/ltp.html
[17:12] <jdstrand> [TOPIC] Miscellaneous and Questions
[17:12] <jdstrand> Does anyone have any other questions or items to discuss?
[17:25] <jdstrand> mdeslaur, sbeattie, tyhicks, jjohansen, sarnold, ChrisCoulson: thanks!
[17:25] <jdstrand> #endmeeting
[17:25] <meetingology> Meeting ended Mon Apr 14 17:25:36 2014 UTC.
[17:25] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2014/ubuntu-meeting.2014-04-14-16.34.moin.txt
[17:25] <mdeslaur> thanks jdstrand!
[17:25] <sarnold> thanks jdstrand :)
[17:25] <jjohansen> thanks jdstrand
[17:26] <sbeattie> jdstrand: thanks
[17:27] <tyhicks> thanks!
[20:00] <mdeslaur> \o
[20:00]  * slangasek waves
[20:01] <slangasek> https://wiki.ubuntu.com/TechnicalBoardAgenda claims pitti is chairing?
[20:01] <slangasek> kees, stgraber: ?
[20:03] <infinity> o/
[20:03]  * slangasek waves to infinity 
[20:03] <mdeslaur> hi infinity
[20:03] <stgraber> I'm around
[20:03] <infinity> Am I fashionably late?
[20:03] <slangasek> you are
[20:03] <mdeslaur> heh
[20:04] <slangasek> pitti isn't here; not sure if https://wiki.ubuntu.com/TechnicalBoardAgenda is accurate that he was supposed to be chairing
[20:04] <slangasek> if so, does that mean it falls through to me?
[20:04] <slangasek> #startmeeting
[20:04] <meetingology> Meeting started Mon Apr 14 20:04:48 2014 UTC.  The chair is slangasek. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[20:04] <meetingology> Available commands: action commands idea info link nick
[20:04]  * slangasek takes action!
[20:05]  * mdeslaur cheers slangasek on
[20:05] <slangasek> [TOPIC] next meeting
[20:05] <slangasek> according to my calendar, next meeting should be Apr 28, 20:00 UTC
[20:06] <slangasek> ... with pitti as the next chair?
[20:06] <infinity> Yeah.
[20:06] <mdeslaur> sounds right
[20:06] <slangasek> [AGREED] Next meeting Apr 28, 20:00 UTC, pitti to chair
[20:06] <slangasek> [TOPIC] Apologies
[20:07] <slangasek> I don't think we had anyone say ahead of time that they wouldn't make it
[20:07] <slangasek> but it looks like kees, sabdfl, pitti are absent without regrets, and the rest of us are here
[20:08] <stgraber> we actually had pitti say ahead of time that he'd make it for sure ;)
[20:08] <slangasek> right :)
[20:08] <slangasek> [TOPIC] Action review
[20:08] <mdeslaur> hi stgraber
[20:08] <slangasek> were there any actions from last time?  they're not noted in the agenda
[20:08]  * slangasek checks https://wiki.ubuntu.com/TechnicalBoard/TeamReports/Current
[20:09] <slangasek> not updated from the previous meeting, so...
[20:09] <slangasek> [TOPIC] Review our current "provisional" Micro Release Exceptions
[20:09] <slangasek> this one needs to turn into something other than a perpetually carried-over item
[20:10] <slangasek> infinity: I recall that you asked kees about it last time, but I don't remember a decision being taken
[20:10] <mdeslaur> kees isn't here for that one, so I guess we skip for now
[20:10] <kees> I'm here. carry please
[20:10] <mdeslaur> hi kees
[20:10] <kees> hola
[20:10] <slangasek> kees: how do we help turn this into something other than a 'carry'?
[20:10] <kees> sorry I'm late!
[20:10] <infinity> I think last time, I asked kees to provide enough detail to the list of his intent and proposed strategy that maybe some people could take some load off.
[20:10] <slangasek> ok
[20:10] <slangasek> how about if I explicitly [action] that?
[20:11] <kees> slangasek: so, I think we to generate a report showing which MREs have happened, and which haven't.
[20:11] <kees> attempting to analyze bug counts didn't work; it's way too complex.
[20:11] <slangasek> kees: is that something you want to still drive, or is it just defaulting to you and we should try to find someone else to do it?
[20:12] <kees> slangasek: I've made no head way, so I probably shouldn't own it. one option would be to assign out chunks of MREs to check.
[20:12] <slangasek> kees: I think I'd rather tag someone on the SRU team to help out with getting us a general report
[20:12] <slangasek> (I think I know just the person)
[20:12] <slangasek> so let me take the action to get us the report, and then we can go from there on list?
[20:13] <kees> okay
[20:13] <infinity> slangasek: Which person did you have in mind?
[20:13] <slangasek> [ACTION] slangasek to work with SRU team to get a list of how the provisional MREs have/haven't been used
[20:13] <meetingology> ACTION: slangasek to work with SRU team to get a list of how the provisional MREs have/haven't been used
[20:13] <slangasek> infinity: bdmurray, the grand master launchpad miner
[20:14] <infinity> slangasek: Seems sensible.
[20:14] <infinity> You should get him a hat with a light on.
[20:14] <mdeslaur> hehe
[20:14] <slangasek> and a canary icon for his lp profile
[20:14] <slangasek> so there are no other explicit agenda items in the wiki
[20:14] <slangasek> [TOPIC] Scan the mailing list archive for anything we missed
[20:15] <slangasek> https://lists.ubuntu.com/archives/technical-board/2014-April/ shows the Ubuntu Kylin discussions, and MRE requests for lxc, juju-core, iscsitarget
[20:16] <slangasek> I do want to discuss the kylin one here (sorry for not putting it on the agenda explicitly)
[20:16] <slangasek> do the MREs need discussion here/now?
[20:17] <slangasek> for the lxc one, stgraber has answered pitti's questions; since pitti has already looked at it, it's probably sensible to let him continue driving that one on list
[20:17] <mdeslaur> I think we can continue them on the list
[20:17] <slangasek> iscsitarget had a +1 from pitti but has not yet been added to https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions - can someone take care of that?
[20:17] <slangasek> (the rule for MREs is still 'a single +1', right?)
[20:18] <slangasek> and the juju-core one seems to still be in discussion on list
[20:20] <slangasek> (iscsitarget MRE added to the wiki)
[20:20] <slangasek> [TOPIC] UbuntuKylin archive
[20:20] <slangasek> [LINK] https://wiki.ubuntu.com/Ubuntu%20Kylin/Ubuntu%20Kylin%20Archive
[20:21] <slangasek> we have a draft that I believe captures the TB consensus on the mailing list so far
[20:21] <slangasek> but I think we only have 3 explicit +1s on this (stgraber, myself, mdeslaur)
[20:21] <slangasek> kees, infinity: I've been assuming there's nothing too controversial there at this point, and so have been proceeding with the implementation, but would appreciate an explicit ack
[20:22] <infinity> slangasek: Right, let me quickly review the wiki page again.
[20:22] <slangasek> thanks
[20:23] <infinity> slangasek: Does ~ubuntu-archive get r/w access to the repo to force removal issues, or do we just ask nicely?
[20:24] <slangasek> infinity: at present I'm expecting that we request removal of the kylin team rather than being hands-on with archive access
[20:24] <infinity> slangasek: Otherwise, looks fine.
[20:25] <infinity> slangasek: I'm okay with us asking nicely in the general case anyway, just thinking that an explicit ACL serves better than polite process if we ever find them unresponsive for too long about a severe issue or whatever.
[20:25] <slangasek> infinity: I have no opinion on the mechanics of the oversight; if you think it's important to have direct access, I suggest proposing this to Jack on the list
[20:25] <infinity> slangasek: I don't think it would block my +1 on the proposal.
[20:25] <slangasek> ok
[20:26] <slangasek> oh hey, we could do an actual explicit vote here
[20:26] <infinity> slangasek: It's about on par with "core-devs should be able to commit to all your *&!% packaging branches", which is never as true as it should be. :P
[20:26] <slangasek> [VOTE] ratification of https://wiki.ubuntu.com/Ubuntu%20Kylin/Ubuntu%20Kylin%20Archive
[20:26] <meetingology> Please vote on: ratification of https://wiki.ubuntu.com/Ubuntu%20Kylin/Ubuntu%20Kylin%20Archive
[20:26] <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)
[20:26] <slangasek> +1
[20:26] <meetingology> +1 received from slangasek
[20:26] <infinity> +1
[20:26] <meetingology> +1 received from infinity
[20:26] <mdeslaur> +1
[20:26] <meetingology> +1 received from mdeslaur
[20:27] <infinity> Hah.  You got a new vote and lost an old one. ;)
[20:27] <slangasek> stgraber, kees:
[20:27] <stgraber> +1
[20:27] <meetingology> +1 received from stgraber
[20:28] <slangasek> kees: do you need more time to review/consider?
[20:30] <slangasek> [ENDVOTE]
[20:30] <meetingology> Voting ended on: ratification of https://wiki.ubuntu.com/Ubuntu%20Kylin/Ubuntu%20Kylin%20Archive
[20:30] <meetingology> Votes for:4 Votes against:0 Abstentions:0
[20:30] <meetingology> Motion carried
[20:30] <slangasek> always room for more feedback on the list :)
[20:30] <slangasek> [TOPIC] Check up on community bugs
[20:31] <slangasek> https://bugs.launchpad.net/ubuntu-community/+bugs?field.assignee=techboard is quite empty
[20:31] <slangasek> so... done
[20:31] <slangasek> and that leaves selecting a chair, which I believe we did at the beginning
[20:31] <slangasek> anything I've missed?
[20:32] <mdeslaur> nope
[20:33] <slangasek> cool
[20:33] <slangasek> #endmeeting
[20:33] <slangasek> thanks, all!
[20:33] <mdeslaur> thanks slangasek!