/srv/irclogs.ubuntu.com/2014/04/14/#ubuntu-meeting.txt

=== maclin__ is now known as maclin
=== vladk|offline is now known as vladk
=== maclin_ is now known as maclin
=== czajkows1i is now known as czajkowski
=== maclin__ is now known as maclin
=== psivaa is now known as psivaa-lunch
=== psivaa-lunch is now known as psivaa
=== tyhicks` is now known as tyhicks
=== WebbyIT is now known as rpadovani
=== chuck_ is now known as zul
mdeslaur\o16:33
jjohanseno/16:33
jdstrandhi!16:33
chrisccoulsono/16:34
* sbeattie waves16:34
jdstrand#startmeeting16:34
meetingologyMeeting started Mon Apr 14 16:34:34 2014 UTC.  The chair is jdstrand. Information about MeetBot at http://wiki.ubuntu.com/meetingology.16:34
meetingologyAvailable commands: action commands idea info link nick16:34
jdstrandThe meeting agenda can be found at:16:34
jdstrand[LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting16:34
jdstrand[TOPIC] Announcements16:34
=== meetingology changed the topic of #ubuntu-meeting to: Announcements
jdstrandThanks 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
ubottuLaunchpad bug 1305807 in openafs (Ubuntu) "DSA-2899-1 openafs -- security update" [Undecided,Fix released] https://launchpad.net/bugs/130580716:34
jdstrand[TOPIC] Weekly stand-up report16:34
=== meetingology changed the topic of #ubuntu-meeting to: Weekly stand-up report
jdstrandI'll go first16:35
jdstrandI've got a short week this week (off friday) and next (off monday)16:35
jdstrandI'm on triage this week16:35
jdstrandI'd like to finish up install testing. I did desktop and server already and filed a couple of bugs16:35
jdstrandstill going through touch16:36
jdstrandI'd like to take a look at scopes confinement16:36
jdstrandand get to some updates16:36
jdstrandmdeslaur: you're up16:36
mdeslaurI'm on community this week16:36
mdeslaurI'm off on monday also16:36
mdeslaurI'm working on the usual CVE updates16:36
mdeslaurthat's pretty much it for me, sbeattie, you're up16:37
sbeattieI'm focused on apparmor again this week.16:37
sbeattieI'm still trying to wrap up my review of jjohansen's patches16:37
sbeattieas well as writing and doing some additional tests16:37
sbeattieI need to shave some yaks and upgrade a couple of my secondary systems to trusty16:38
sbeattieThat's pretty much it for me; tyhicks, you're up16:39
tyhicksI didn't get to iterate on the aa.py patches last week, so I've still got to do that16:40
tyhicksI was just reminded that I need to respin the patches in the upstream dbus-daemon AA mediation bug after some feedback I received16:41
tyhicksafter that, I need to take a look at my work items and sync up w/ mdeslaur16:41
jdstrandwasn't there kdbus stuff from a bit back?16:41
tyhicksjdstrand: ah, yes! that'll be what I focus on16:42
tyhicksthanks16:42
tyhicksthat's it for me16:42
tyhicksjjohansen: you're up16:42
jjohansenI'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 review16:44
jdstrandjjohansen: which kernels are you doing?16:44
jjohansenjdstrand: for the backport?16:45
jdstrandyeah16:45
jjohansenjdstrand: atm 3.4 mako/manta but will also need to do flo16:45
jjohansenafter that we can see16:45
jdstrandgrouper might be interesting since several people on the team have it16:46
jjohansenyeah16:46
jdstrandunity 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 apports16:46
jdstrandnot saying it is a high priority though. it isn't for me know that I have flo16:47
jdstrandjjohansen: oh, goldfish too-- that probably is a high priority16:48
jdstrands/know/now/16:48
jjohansenjdstrand: your the only one on the team16:48
jdstrandwith flo?16:48
jjohansenjdstrand: yeah goldfish too16:48
jdstrand(fyi, my flo is my personal device that I dual boot)16:48
jjohansenjdstrand: basically those 4 are all the same backport for apparmor16:49
jdstrandoh goldfish is with the others?16:49
jdstrandI either forgot or never knew that :)16:49
mdeslaurwhat's goldfish?16:49
jjohansenemulator16:49
jdstrandemulator16:49
mdeslauroh16:49
sarnolddo we have a handy table somewhere to convert these names into what they actually are?16:50
mdeslaursarnold: I'm making one right now16:51
jjohansensarnold: hrmm, I'm not sure we do for all of them, there is https://wiki.ubuntu.com/Touch/Devices for the earlier ones16:51
tyhickshttps://wiki.ubuntu.com/Touch/Install#Supported_devices_and_codenames16:51
mdeslaursarnold: before insanity sets in16:51
sarnoldyay16:51
mdeslauroh, well, there you go16:52
mdeslaurexcept for goldfish they're all there16:52
jjohansenanyways thats it for me sarnold you are up16:52
sarnoldI'm in my happy place this week16:52
sarnoldwhich this week means apparmor patch review16:52
sarnoldI'm finished with all the MIRs for trusty :)16:52
mdeslaur\o/16:53
sbeattieyay16:53
* jjohansen is not sure that is such a happy place, but is glad sarnold is a masochist16:53
sarnoldyeah :) \o/ indeed :)16:53
sarnoldbut it'll be nice to reduce the number of not-checked-in patches for apparmor, so hooray16:53
sarnoldthat's me done, chrisccoulson?16:54
chrisccoulsonhi :)16:54
chrisccoulsonthis week, i've got a chromium update16:54
chrisccoulsonand i'm also currently investigating getting hangouts working in oxide (requires support for ppapi plugins)16:55
chrisccoulsonother than that, it's business as usual :)16:56
jdstrandchrisccoulson: we already have those security updates in oxide 501, correct?16:56
chrisccoulsonjdstrand, 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 channel16:57
jdstrandchrisccoulson: yeah, you've got the plan to get there though. I forget when you said we'd be on stable...16:57
chrisccoulsoni'm going to aim to branch for beta at the next chromium release. i think that's realistic now16:58
chrisccoulsonso that would mean we'd be on stable within the next 2 releases16:58
chrisccoulsonie, by chromium 3616:58
chrisccoulson(we're on 34 now)16:58
jdstrandis that ~4 weeks?16:59
chrisccoulsonit's a bit longer than that. the releases seem to be ~6 weeks17:00
chrisccoulsonwhen do we do 14.04.1?17:00
jdstrandah17:01
jdstrandok17:01
jdstrandI couldn't remember if the major release was 2 weeks or 617:01
chrisccoulsonso, 12.04.1 was in august17:02
jdstrandthat's fine17:02
chrisccoulsonwe can be on a stable channel quite a way before then :)17:02
* jdstrand nods17:03
jdstrandI'm not worried, I just couldn't remember the timing17:03
mdeslaurwhat's special about 14.04.1?17:03
chrisccoulsoni'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
jdstrandmdeslaur: its when precise users get the update-manager recommendation to upgrade17:03
mdeslaurjdstrand: I know what it is, I just don't know why that has anything to do with oxide17:04
jdstrandwebapp-container is used on the desktop17:04
jdstrandinstalled by default and uses oxide17:04
mdeslauro_O?17:04
mdeslaurwhere?17:04
jdstrandwebapps17:05
jdstrandthis is so we don't need all the special code in firefox and chromium that was so brittle and either broke or blocked the updates17:05
mdeslaurwow17:05
jdstrand(this was the webapps' team plan for the 14.04 dev cycle all along)17:05
jdstrandit's in an image near you right now :)17:06
mdeslaurok, hah, well it instantly segfaults for me in 14.0417:06
jdstranduh17:06
chrisccoulsonoh :/17:06
jdstrandit should not. are you up to date? please file a bug17:06
jdstrand1.0.0~bzr501-0ubuntu1 is the latest17:06
mdeslaurdoes it require 3d?17:07
mdeslaurit explodes in a vm, but not on my main desktop17:07
chrisccoulsonaha, qtquick requires a GL api17:08
mdeslaurah, ok, it segfaults because it doesn't have enough ram17:08
mdeslaurbumping up the ram in the vm fixed it17:08
mdeslaurjdstrand, chrisccoulson: sorry for interrupting, please continue17:11
chrisccoulsonoh, I think I'm done now anyway :)17:11
jdstrand[TOPIC] Highlighted packages17:11
=== meetingology changed the topic of #ubuntu-meeting to: Highlighted packages
jdstrandThe 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
jdstrandSee 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:11
jdstrandhttp://people.canonical.com/~ubuntu-security/cve/pkg/pywbem.html17:12
jdstrandhttp://people.canonical.com/~ubuntu-security/cve/pkg/php-radius.html17:12
jdstrandhttp://people.canonical.com/~ubuntu-security/cve/pkg/ibm-3270.html17:12
jdstrandhttp://people.canonical.com/~ubuntu-security/cve/pkg/tpp.html17:12
jdstrandhttp://people.canonical.com/~ubuntu-security/cve/pkg/ltp.html17:12
jdstrand[TOPIC] Miscellaneous and Questions17:12
=== meetingology changed the topic of #ubuntu-meeting to: Miscellaneous and Questions
jdstrandDoes anyone have any other questions or items to discuss?17:12
jdstrandmdeslaur, sbeattie, tyhicks, jjohansen, sarnold, ChrisCoulson: thanks!17:25
jdstrand#endmeeting17:25
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Mon Apr 14 17:25:36 2014 UTC.17:25
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2014/ubuntu-meeting.2014-04-14-16.34.moin.txt17:25
mdeslaurthanks jdstrand!17:25
sarnoldthanks jdstrand :)17:25
jjohansenthanks jdstrand17:25
sbeattiejdstrand: thanks17:26
tyhicksthanks!17:27
mdeslaur\o20:00
* slangasek waves20:00
slangasekhttps://wiki.ubuntu.com/TechnicalBoardAgenda claims pitti is chairing?20:01
slangasekkees, stgraber: ?20:01
infinityo/20:03
* slangasek waves to infinity 20:03
mdeslaurhi infinity20:03
stgraberI'm around20:03
infinityAm I fashionably late?20:03
slangasekyou are20:03
mdeslaurheh20:03
slangasekpitti isn't here; not sure if https://wiki.ubuntu.com/TechnicalBoardAgenda is accurate that he was supposed to be chairing20:04
slangasekif so, does that mean it falls through to me?20:04
slangasek#startmeeting20:04
meetingologyMeeting started Mon Apr 14 20:04:48 2014 UTC.  The chair is slangasek. Information about MeetBot at http://wiki.ubuntu.com/meetingology.20:04
meetingologyAvailable commands: action commands idea info link nick20:04
* slangasek takes action!20:04
* mdeslaur cheers slangasek on20:05
slangasek[TOPIC] next meeting20:05
=== meetingology changed the topic of #ubuntu-meeting to: next meeting
slangasekaccording to my calendar, next meeting should be Apr 28, 20:00 UTC20:05
slangasek... with pitti as the next chair?20:06
infinityYeah.20:06
mdeslaursounds right20:06
slangasek[AGREED] Next meeting Apr 28, 20:00 UTC, pitti to chair20:06
slangasek[TOPIC] Apologies20:06
=== meetingology changed the topic of #ubuntu-meeting to: Apologies
slangasekI don't think we had anyone say ahead of time that they wouldn't make it20:07
slangasekbut it looks like kees, sabdfl, pitti are absent without regrets, and the rest of us are here20:07
stgraberwe actually had pitti say ahead of time that he'd make it for sure ;)20:08
slangasekright :)20:08
slangasek[TOPIC] Action review20:08
=== meetingology changed the topic of #ubuntu-meeting to: Action review
mdeslaurhi stgraber20:08
slangasekwere there any actions from last time?  they're not noted in the agenda20:08
* slangasek checks https://wiki.ubuntu.com/TechnicalBoard/TeamReports/Current20:08
slangaseknot updated from the previous meeting, so...20:09
slangasek[TOPIC] Review our current "provisional" Micro Release Exceptions20:09
=== meetingology changed the topic of #ubuntu-meeting to: Review our current "provisional" Micro Release Exceptions
slangasekthis one needs to turn into something other than a perpetually carried-over item20:09
slangasekinfinity: I recall that you asked kees about it last time, but I don't remember a decision being taken20:10
mdeslaurkees isn't here for that one, so I guess we skip for now20:10
keesI'm here. carry please20:10
mdeslaurhi kees20:10
keeshola20:10
slangasekkees: how do we help turn this into something other than a 'carry'?20:10
keessorry I'm late!20:10
infinityI 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
slangasekok20:10
slangasekhow about if I explicitly [action] that?20:10
keesslangasek: so, I think we to generate a report showing which MREs have happened, and which haven't.20:11
keesattempting to analyze bug counts didn't work; it's way too complex.20:11
slangasekkees: 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:11
keesslangasek: 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
slangasekkees: I think I'd rather tag someone on the SRU team to help out with getting us a general report20:12
slangasek(I think I know just the person)20:12
slangasekso let me take the action to get us the report, and then we can go from there on list?20:12
keesokay20:13
infinityslangasek: 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 used20:13
meetingologyACTION: slangasek to work with SRU team to get a list of how the provisional MREs have/haven't been used20:13
slangasekinfinity: bdmurray, the grand master launchpad miner20:13
infinityslangasek: Seems sensible.20:14
infinityYou should get him a hat with a light on.20:14
mdeslaurhehe20:14
slangasekand a canary icon for his lp profile20:14
slangasekso there are no other explicit agenda items in the wiki20:14
slangasek[TOPIC] Scan the mailing list archive for anything we missed20:14
=== meetingology changed the topic of #ubuntu-meeting to: Scan the mailing list archive for anything we missed
slangasekhttps://lists.ubuntu.com/archives/technical-board/2014-April/ shows the Ubuntu Kylin discussions, and MRE requests for lxc, juju-core, iscsitarget20:15
slangasekI do want to discuss the kylin one here (sorry for not putting it on the agenda explicitly)20:16
slangasekdo the MREs need discussion here/now?20:16
slangasekfor 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 list20:17
mdeslaurI think we can continue them on the list20:17
slangasekiscsitarget 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:17
slangasekand the juju-core one seems to still be in discussion on list20:18
slangasek(iscsitarget MRE added to the wiki)20:20
slangasek[TOPIC] UbuntuKylin archive20:20
=== meetingology changed the topic of #ubuntu-meeting to: UbuntuKylin archive
slangasek[LINK] https://wiki.ubuntu.com/Ubuntu%20Kylin/Ubuntu%20Kylin%20Archive20:20
slangasekwe have a draft that I believe captures the TB consensus on the mailing list so far20:21
slangasekbut I think we only have 3 explicit +1s on this (stgraber, myself, mdeslaur)20:21
slangasekkees, 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 ack20:21
infinityslangasek: Right, let me quickly review the wiki page again.20:22
slangasekthanks20:22
infinityslangasek: Does ~ubuntu-archive get r/w access to the repo to force removal issues, or do we just ask nicely?20:23
slangasekinfinity: at present I'm expecting that we request removal of the kylin team rather than being hands-on with archive access20:24
infinityslangasek: Otherwise, looks fine.20:24
infinityslangasek: 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
slangasekinfinity: 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 list20:25
infinityslangasek: I don't think it would block my +1 on the proposal.20:25
slangasekok20:25
slangasekoh hey, we could do an actual explicit vote here20:26
infinityslangasek: 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. :P20:26
slangasek[VOTE] ratification of https://wiki.ubuntu.com/Ubuntu%20Kylin/Ubuntu%20Kylin%20Archive20:26
meetingologyPlease vote on: ratification of https://wiki.ubuntu.com/Ubuntu%20Kylin/Ubuntu%20Kylin%20Archive20:26
meetingologyPublic 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+120:26
meetingology+1 received from slangasek20:26
infinity+120:26
meetingology+1 received from infinity20:26
mdeslaur+120:26
meetingology+1 received from mdeslaur20:26
infinityHah.  You got a new vote and lost an old one. ;)20:27
slangasekstgraber, kees:20:27
stgraber+120:27
meetingology+1 received from stgraber20:27
slangasekkees: do you need more time to review/consider?20:28
slangasek[ENDVOTE]20:30
meetingologyVoting ended on: ratification of https://wiki.ubuntu.com/Ubuntu%20Kylin/Ubuntu%20Kylin%20Archive20:30
meetingologyVotes for:4 Votes against:0 Abstentions:020:30
meetingologyMotion carried20:30
slangasekalways room for more feedback on the list :)20:30
slangasek[TOPIC] Check up on community bugs20:30
=== meetingology changed the topic of #ubuntu-meeting to: Check up on community bugs
slangasekhttps://bugs.launchpad.net/ubuntu-community/+bugs?field.assignee=techboard is quite empty20:31
slangasekso... done20:31
slangasekand that leaves selecting a chair, which I believe we did at the beginning20:31
slangasekanything I've missed?20:31
mdeslaurnope20:32
slangasekcool20:33
slangasek#endmeeting20:33
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
slangasekthanks, all!20:33
mdeslaurthanks slangasek!20:33
=== marrusl is now known as marrusl_afk
=== vladk is now known as vladk|offline
=== chuck_ is now known as zul
=== marrusl_afk is now known as marrusl

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