[17:16] <jdstrand> hi!
[17:16] <jdstrand> #startmeeting
[17:16] <meetingology> Meeting started Mon Oct  6 17:16:55 2014 UTC.  The chair is jdstrand. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[17:16] <meetingology> Available commands: action commands idea info link nick
[17:16] <jdstrand> The meeting agenda can be found at:
[17:16] <jdstrand> [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting
[17:17] <jdstrand> [TOPIC] Review of any previous action items
[17:17] <jdstrand> I'll go first
[17:17] <jdstrand> I'm on community this week
[17:17] <jdstrand> quite a few apparmor related items have come up that need to land
[17:17] <jdstrand> there is a click-apparmor update for adjusting CLICK_DIR. it is ready, but it needs testing
[17:18] <jdstrand> there is apparmor-easyprof-ubuntu for a new template (ubuntu-push-helper)
[17:19] <jdstrand> and there is apparmor itself, which is mostly in sbeattie's court, but may need a couple of tweaks to the init script and bug #1377338
[17:19] <jdstrand> that creates click-reviewers-tools changes
[17:19] <jdstrand> and I still haven't updated UCT for derivative branches
[17:20] <jdstrand> mdes laur is off today
[17:20] <jdstrand> sbeattie: you're up
[17:20] <sbeattie> I'm on apparmor this week
[17:20] <jdstrand> sbeattie: (also, before you hand off to tyhicks, I'll have some questions)
[17:20] <sbeattie> jdstrand: okay
[17:20] <sbeattie> as jdstrand said, I need to poke at 1377338
[17:21] <sbeattie> and work on the landing of a bugfix update for the apparmor package.
[17:21] <sbeattie> I have a bit of upstream work I need to do around releases.
[17:22] <sbeattie> jdstrand: what did you want to ask?
[17:22] <jdstrand> first (and this may be for tyhicks as well), I was (perhaps mistakenly) thinking that the apparmor upload would fix the testsuite such that it would pass
[17:23] <jdstrand> which would be part of my justification for uploading it
[17:23] <tyhicks> there are outstanding kernel bugs
[17:23] <jdstrand> yes
[17:23] <jdstrand> but we did decide that the testsuite would be adjusted for the named path getopt (and friends) failures, correct?
[17:24] <sbeattie> tyhicks: however, the getopt on dgram before there's a bound socket isn't going to get a fix, is it?
[17:24] <tyhicks> I thought all of the getopt failures were addressed in the test suite
[17:25] <jdstrand> sbeattie, tyhicks: can you sort that ^ out after the meeting?
[17:25] <tyhicks> yes
[17:25] <jdstrand> thanks
[17:25] <sbeattie> jdstrand: yeah
[17:25] <sbeattie> jdstrand: any other questions?
[17:26] <jdstrand> so, I think that means that we should adjust QRT to not fail with the current expected failures (ie, if only those kernel bugs are making the testsuite fail, then we don't fail QRT). when our kernel bugs are fixed, we remove that
[17:26] <jdstrand> sbeattie: what do you think? QA and kt are not happy with the current state
[17:27] <jdstrand> (which you can point them to me if they are upset with you)
[17:27] <jdstrand> (that was a collective you, not sbeattie-specific :)
[17:27] <sbeattie> jdstrand: yeah, agreed.
[17:27] <jdstrand> ok
[17:27] <sbeattie> meh, KT/QA are always upset with me, it's a steady state of affairs.
[17:27] <jdstrand> heh
[17:28] <jdstrand> well, for apparmor's qrt, they can blame me
[17:28] <jdstrand> (should've thought about it before the upload that broke it)
[17:29] <jdstrand> sbeattie: so, at this point, I'm not sure that the new version of apparmor that you are working on will make it into rtm
[17:29] <jdstrand> sbeattie: however, 1377338 has to be fixed in rtm
[17:30] <jdstrand> sbeattie: so, I think priorities should be, get a patch going for 1377338, and I'll prepare an rtm upload for that and whatever else I need to do to the boot scripts
[17:30] <sbeattie> okay
[17:30] <jdstrand> sbeattie: then, get that patch into the ppa, after sorting out the testsuite
[17:30] <jdstrand> sbeattie: then I can get that to utopic
[17:31] <jdstrand> sbeattie: then someone can work on qrt
[17:31] <jdstrand> sbeattie: sound like a plan?
[17:31] <sbeattie> jdstrand: yeah, that works for me.
[17:31] <jdstrand> sbeattie: we can play the postfix one by ear once jj can comment. maybe it'll be in your upload, maybe not
[17:32] <jdstrand> sbeattie: cool, thanks
[17:32] <jdstrand> that's it from me
[17:32] <sbeattie> alright, thanks. tyhicks?
[17:32] <jdstrand> sbeattie: oh, also, for it to be in rtm, it needs to land by thursday, which basically means I need a patch by tomorrow
[17:32] <jdstrand> (bug 1377338)
[17:32] <sbeattie> jdstrand: gotcha
[17:32] <jdstrand> cool, thanks
[17:33] <tyhicks> I'm now looking at the in-tree apparmor regression test suite to make sure it is failing when expected (as discussed above)
[17:34] <tyhicks> I have a couple more eCryptfs kernel patches to review and test this week before I can send a pull request for the 3.18 merege window
[17:34] <tyhicks> they're small and shouldn't take long
[17:34] <sbeattie> tyhicks: note that the paste I sent you elsewhere were results using the apparmor package in the security-proposed ppa, which has everything that's in lp:apparmor.
[17:34] <tyhicks> I misplaced them during the big apparmor landing push and just rediscovered them :/
[17:34] <tyhicks> sbeattie: ack
[17:35] <tyhicks> then I'm switching over to the upstream dbus-daemon apparmor mediation bug feedback
[17:35] <tyhicks> that's probably all that I should commit to this week
[17:36] <tyhicks> I spent more time than I expected last week on the apparmor kernel memory bug triage (LP: #1375416) so my planned work for this week looks similar to last week
[17:36] <tyhicks> that's it for me
[17:36] <tyhicks> jj isn't here so it is sarnold's turn
[17:37] <jdstrand> I know the feeling regarding planned work looking similar...
[17:38] <sarnold> I'm in happy place this week, on MIR duty; I still have ~five outstanding MIRs to work on, one is in progress
[17:39] <sarnold> I'll try to quick-ack smallish apparmor patches this week, but longer / more involved patches just won't get any attention, sorry
[17:40] <sarnold> I think that's it for me, chrisccoulson?
[17:51] <tyhicks> maybe jjohansen should go now that he's here?
[17:51] <tyhicks> jjohansen: sarnold had passed chrisccoulson the mic just before you joined but we haven't heard from him
[17:52] <jjohansen> okay
[17:52] <jjohansen> so I am primary working on apparmor bugs this week
[17:52] <jjohansen> I need to look into 1373172, 1373174, and 1373176
[17:53] <jdstrand> the testsuite bugs. cool
[17:53] <jjohansen> and finish up with 1375417 and maybe poke at 1375416, and 1375410
[17:54] <jjohansen> jdstrand: yep
[17:54] <jdstrand> cool
[17:55] <jjohansen> we also need to decide if we want to push the fix for docker.io LP: #1371310 out to the phone kernels
[17:55]  * jdstrand pauses
[17:55] <jjohansen> and if so send the pull request
[17:55] <jdstrand> jjohansen: I wasn't thinking we would. all the phone policy seems fine atm
[17:56] <jdstrand> jjohansen: I mean, we can for utopic to keep things tidy if people want
[17:56] <jdstrand> but that bug on rtm kernels or even phablet utopic kernels doesn't bother me
[17:57] <jjohansen> yeah, I am not bothered by it eiterh
[17:57] <jdstrand> now, if we have updates for other kernel bugs, sure, we can toss it in there
[17:58] <jdstrand> alright, let's not worry about it on phablet unless we can roll it in with other bug fixes
[17:59] <jjohansen> ack
[17:59] <jdstrand> jjohansen: did you have anything else to report
[17:59] <jdstrand> ?
[17:59] <jjohansen> okay, let see I have an embargo issue to look at closer, and some apparmor patches to upstream
[18:00] <jjohansen> we also have apparmor 2.9 that we need to push out this week if there is going to be any chance of debian picking it up
[18:00] <jjohansen> that is it for me
[18:02] <jdstrand> jjohansen: I think sbeattie is close to finalizing that. those testsuite bugs you mentioned and one other bug (1377338) are the only thing holding up 2.9 aiui
[18:02] <jdstrand> things*
[18:02] <jdstrand> ok
[18:03] <jjohansen> that sounds about right
[18:03] <jdstrand> so, let's move on
[18:03] <jdstrand> [TOPIC] Highlighted packages
[18:03] <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.
[18:03] <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.
[18:03] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/fusionforge.html
[18:03] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/iodine.html
[18:03] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/pigz.html
[18:03] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/cakephp.html
[18:03] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/ekiga.html
[18:03] <jdstrand> [TOPIC] Miscellaneous and Questions
[18:03] <jdstrand> Does anyone have any other questions or items to discuss?
[18:05] <jdstrand> sbeattie, tyhicks, jjohansen, sarnold: thanks!
[18:05] <jdstrand> #endmeeting
[18:05] <meetingology> Meeting ended Mon Oct  6 18:05:36 2014 UTC.
[18:05] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2014/ubuntu-meeting.2014-10-06-17.16.moin.txt
[18:05] <sbeattie> jdstrand: thanks!
[18:06] <tyhicks> thanks
[18:07] <sarnold> thanks jdstrand
[18:08] <jjohansen> thanks jdstrand
[19:02]  * cking wonders if he's too early  or late for the meeting
[19:03] <bdmurray> !dmb-ping
[19:04]  * ScottK looks up
[19:09] <bdmurray> micahg-work: are you here for the meeting?
[19:10] <micahg-work> yes
[19:11] <bdmurray> well, that makes 3 if I am counting correctly
[19:11] <cking> is that enough?
[19:12] <bdmurray> cking: its not enough for quorum for a vote.
[19:18] <ScottK> micahg-work: Are you running the meeting?
[19:19] <micahg-work> do we have quorum?
[19:22] <ScottK> micahg-work: We can review cking's application and finish the vote via email if we don't.
[19:22]  * cking would appreciate that :-)
[19:23] <micahg-work> ok, wfm
[19:23] <micahg-work> #startmeeting Ubuntu Developer Membership Board
[19:23] <meetingology> Meeting started Mon Oct  6 19:23:28 2014 UTC.  The chair is micahg-work. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[19:23] <meetingology> Available commands: action commands idea info link nick
[19:23] <micahg-work> welcome to the fortnightly DMB meeting
[19:25] <micahg-work> #topic Colin King applying for PPU (eventstat, forkstat, health-check, idlestat, powerstat, smemstat, stress-ng, thermald and fwts)
[19:25] <micahg-work> #link https://wiki.ubuntu.com/ColinKing/PPUApplicationTools
[19:25] <micahg-work> cking, care to introduce yourself?
[19:26] <cking> hi there, I've been working with Ubuntu now for 6+ years and I work in the Ubuntu Kernel team
[19:26] <cking> I like to focus on fixing bugs and improving code quality
[19:26] <micahg-work> #chair ScottK micahg-work
[19:26] <meetingology> Current chairs: ScottK micahg-work
[19:26] <cking> I'm also a Debian Maintainer for a bunch of packages: https://qa.debian.org/developer.php?login=colin.king@canonical.com
[19:27] <cking> ..I like to develop tools that help us find bugs and identify issues than need improving
[19:28] <cking> hence I'm requesting per package upload rights for these tools as well as the firmware test suite which I developed too
[19:28] <cking> is that enough?
[19:28] <micahg-work> I think so
[19:29] <ScottK> I see Lintian wants you to do a bit of man page work.  Any plans for that?
[19:30] <ScottK> #link https://lintian.debian.org/maintainer/colin.king@canonical.com.html
[19:30] <cking> yes, I'm planning to get the packages lintian clean, some if this requires me working upstream with the developer, such as thermald
[19:31] <ScottK> In the mean time, you can write the man pages and ship them in debian/.
[19:31] <cking> ..as I like to get fixes upstream first so everyone can benefit
[19:31] <cking> indeed, with idlestat, I was waiting for the next release of the code which is coming "real soon"-ish
[19:32] <ScottK> When one of your packages is uploaded, do you track that it makes from proposed to the release pocket?  If so, how?
[19:32] <cking> that's a good question, normally I give it a few days and when I'm not sure about the status I normally ask a fellow kernel team member to see what's happened
[19:33] <cking> but I should be more familiar with the exact process so I can be more on top of the situation
[19:33] <ScottK> Fair enough.  We can talk about it after.
[19:34] <ScottK> Which of your packages are seeded in Ubuntu images?
[19:34] <cking> currently just thermald, it's tied closely to the kernel as it stops CPUs overheating now that we've enabled the intel-pstate driver in the kernel
[19:35] <ScottK> How would you tell if any of the others had been added?
[19:35] <cking> erm, I'm not sure, I'd have to research that out
[19:35] <ScottK> seeded-in-ubuntu in ubuntu-dev-tools is the usual answer.
[19:36] <cking> ok
[19:36] <ScottK> Why would you care?  How would it affect if you were going to upload a package at a given time?
[19:37] <cking> i'd care because it's a package that is automatically included.  if not seeded in ubuntu then users can opt in so it's a "less" critical  package
[19:38] <cking> it also means I need to be really careful on the release cycle so I don't rush in any changes at a late stage. normally I want to ensure it's stable very early on to get enough soak time on it
[19:38] <ScottK> If there's a freeze on for an alpha/beta milestone seeded packages don't transition from proposed to release for the images involved in the milestone.
[19:40] <cking> ok, got it
[19:40] <micahg-work> are there any times when you can't upload a package that's not seeded?
[19:41] <ScottK> For future reference, for package migration you'll want to know about http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html and http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt - the latter takes some work to comprehend.  Don't worry about it now, have a look later.
[19:42] <cking> micahg-work, i must confess, I've not consider that before now
[19:42] <cking> where would I find that policy out?
[19:43] <micahg-work> on the release schedule are links to each freeze and their respective policies: https://wiki.ubuntu.com/UtopicUnicorn/ReleaseSchedule
[19:45] <ScottK> cking: What kind of changes would be OK for upload right now?
[19:45] <cking> ScottK, only bug fixes, and generally I'd only consider ones that were show-stoppers
[19:45] <ScottK> OK.
[19:46] <cking> SRU-like fixes
[19:46] <ScottK> If you had direct upload rights today and uploaded thermald, what would happen to it first?
[19:47] <cking> wouldn't it go into -proposed?
[19:48] <cking> then only once it has passed certain tests it would go into the release pocket
[19:48] <ScottK> No, since it's seeded it goes into unapproved and is reviewed by the release team before being manually accepted.
[19:48] <ScottK> (this happens after the last beta)
[19:48] <micahg-work> are you subscribed to ubuntu-devel-announce?
[19:49] <cking> yep
[19:49] <micahg-work> FYI, https://lists.ubuntu.com/archives/ubuntu-devel-announce/2014-September/001113.html was send about 2 weeks ago
[19:50] <cking> oh, double check, I'm not 100% sure of that, I'm subscribed to quite a few, I need to look at my mail filters
[19:50] <micahg-work> since we don
[19:50]  * cking has seen that email, so I must be subscribe
[19:50] <cking> *subscribed
[19:50] <micahg-work> since we don't have quorum, we can vote, but will have to finish on the ML
[19:51] <micahg-work> #voters bdmurray ScottK micahg-work
[19:51] <meetingology> Current voters: ScottK bdmurray micahg-work
[19:51] <ScottK> +1
[19:51]  * ScottK wonders if he was too fast.
[19:51] <micahg-work> #vote Vote on Colin King getting upload rights to eventstat, forkstat, health-check, idlestat, powerstat, smemstat, stress-ng, thermald
[19:51] <meetingology> Please vote on: Vote on Colin King getting upload rights to eventstat, forkstat, health-check, idlestat, powerstat, smemstat, stress-ng, thermald
[19:51] <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)
[19:52] <ScottK> There we go.
[19:52] <ScottK> +1
[19:52] <meetingology> +1 received from ScottK
[19:52]  * micahg-work believes upload rights exist for fwts already
[19:53] <cking> oh, that's news to me, must because I was historically part of the Hardware Enablement Team
[19:53] <cking> apologies for that
[19:53] <micahg-work> sorry, I might be mis-remembering
[19:55] <micahg-work> here, let's make that more official just in case
[19:55] <micahg-work> #endvote
[19:55] <meetingology> Voting ended on: Vote on Colin King getting upload rights to eventstat, forkstat, health-check, idlestat, powerstat, smemstat, stress-ng, thermald
[19:55] <meetingology> Votes for:1 Votes against:0 Abstentions:0
[19:55] <meetingology> Motion carried
[19:55] <micahg-work> #vote Vote on Colin King getting upload rights to eventstat, forkstat, health-check, idlestat, powerstat, smemstat, stress-ng, thermald, fwts
[19:55] <meetingology> Please vote on: Vote on Colin King getting upload rights to eventstat, forkstat, health-check, idlestat, powerstat, smemstat, stress-ng, thermald, fwts
[19:55] <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)
[19:55] <micahg-work> +1
[19:55] <meetingology> +1 received from micahg-work
[19:56] <ScottK> +1
[19:56] <meetingology> +1 received from ScottK
[19:56] <micahg-work> bdmurray, did you want to vote now?
[19:58] <bdmurray> +1
[19:58] <meetingology> +1 received from bdmurray
[20:00] <Noskcaj> Is there still time for my MOTU application or should i just go and get breakfast?
[20:00] <cking> thanks
[20:00] <micahg-work> Noskcaj, I think we're out of time on this one, are you available for the next meeting?
[20:01] <ScottK> Noskcaj: You're on for next time.
[20:01] <Noskcaj> sigh, another month
[20:01] <Noskcaj> Would anyone have 5 mins to check if i've done enough? https://wiki.ubuntu.com/Noskcaj
[20:02] <micahg-work> #endvote
[20:02] <meetingology> Voting ended on: Vote on Colin King getting upload rights to eventstat, forkstat, health-check, idlestat, powerstat, smemstat, stress-ng, thermald, fwts
[20:02] <meetingology> Votes for:3 Votes against:0 Abstentions:0
[20:02] <meetingology> Motion carried
[20:02] <micahg-work> cking, we'll take the vote to the ML
[20:02] <ScottK> Noskcaj: My recollection is that when I read it, I was confused about what you were applying for and what endorsements were related.
[20:02] <micahg-work> #action micahg to follow up on ML with vote on Colin King's PPU application
[20:02] <meetingology> ACTION: micahg to follow up on ML with vote on Colin King's PPU application
[20:03] <micahg-work> #topic AOB
[20:03] <ScottK> Nothing here.
[20:03] <Noskcaj> ScottK, Applying for MOTU, Xubuntu Packageset, and whatever the recommended gnome one is (packageset or desktop-extra)
[20:03] <ScottK> Didn't you get Xubuntu last time?
[20:03]  * ScottK may misremember.
[20:04] <Noskcaj> ScottK, I got 4 packages, 1 of which was dropped from xubuntu and from my maintenance
[20:04]  * micahg-work would like to remind applicants to please send a mail to devel-permissions explaining what they're applying for per https://wiki.ubuntu.com/DeveloperMembershipBoard#Application_process
[20:04] <micahg-work> #endmeeting
[20:04] <meetingology> Meeting ended Mon Oct  6 20:04:39 2014 UTC.
[20:04] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2014/ubuntu-meeting.2014-10-06-19.23.moin.txt
[20:04] <Noskcaj> micahg-work, I think i did, although my email probably could have been better
[20:04] <ScottK> Now you have a chance to write a better one then.
[20:05] <micahg-work> Noskcaj, I didn't see it in the archive
[20:05] <Noskcaj> Oops, it went to developer-membership-board@lists.ubuntu.com
[20:05] <micahg-work> ah, that would explain it :)