[19:14] <Linden940> there got my old name back lol
[19:27] <kees> meetin' time
[19:28] <mdeslaur> yellow!
[19:28] <Linden940> are you asking when the meeting is?
[19:28] <kees> i'm on triage this week. planning to find something to publish
[19:29] <kees> Linden940: nh, just declaring the start of one
[19:29] <Linden940> hmm i c
[19:29] <jdstrand> o/
[19:29] <Linden940> <<never been in here yet so I'm all eyes
[19:29]  * sbeattie is here, too.
[19:29] <kees> uhm, nothing else, I'm still going to be getting over travel shock :P
[19:30] <mdeslaur> ok, my turn
[19:30] <mdeslaur> I've got tomcat6 packages ready to release, and I'm currently testing moin updates
[19:31] <mdeslaur> I'll probably release them tomorrow
[19:31] <jjohansen> \o
[19:31] <mdeslaur> after that, I'll continue down the list
[19:31] <mdeslaur> that's it from me
[19:31] <jdstrand> I'll go
[19:32] <jdstrand> I plan on testing and publishing a hardy/xen regression when the kernel team is ready for me to
[19:32] <jjohansen> new test kernels are building as we speak
[19:32] <jdstrand> libvirt update got sidetracked last week, but I plan to work on that
[19:33] <kees> what's the regression issue? from this latest kernel?
[19:33] <jdstrand> I managed to find a little time to work on ufw over the weekend, so with luck I'll release 0.30 and push to debian and maverick (couple of nagging bug fixes only)
[19:33] <kees> \o/
[19:33] <jdstrand> kees: yes. dom0 would trace back
[19:34] <jdstrand> kees: -xen flavor only
[19:34] <jdstrand> I spent toda getting up to speed on using xen and can reproduce and have a testing environment
[19:34] <jjohansen> kees: its because xen tries mlocking only PART of the stack
[19:34] <jdstrand> kees: this is bug #620994
[19:35] <kees> *hold face*
[19:37] <jdstrand> that's it from me
[19:37] <sbeattie> I was on triage last week, as well as off for 1.5 days.
[19:37] <sbeattie> I'm still catching up on email today
[19:38] <sbeattie> (I'd hoped my laptop's backlight would have been repaired while I was off, but it was not to be -- backlight's on backorder)
[19:38] <jdstrand> :(
[19:38] <sbeattie> This week, I too will be looking for open issues to publish.
[19:39] <sbeattie> I also need to make progress on on getting apparmor 2.5.1 out the door, sorry jjohansen
[19:39] <jjohansen> sbeattie: np, its not like I have got the kernel patches out yet
[19:39] <sbeattie> I tracked down a pam_apparmor issue in lucid, and we need to get 2.5.1 out so we can do the omnibus lucid sru for apparmor
[19:40] <sbeattie> Umm, I think that's it for me.
[19:41] <sbeattie> Anyone else have issues they wish to discuss with the security team?
[19:43] <sbeattie> Hrm, I think that's a resounding no...
[19:43]  * kees times out
[19:43] <kees> cool, thanks everyone!
[19:43] <mdeslaur> thanks!
[19:43] <jcastro> Accouncement: http://ubuntu.stackexchange.com/questions/tagged/security
[19:44] <jcastro> feel free to participate!
[19:44] <jcastro> wow, I meant Announcement. >_>
[19:45] <kees> jcastro: neat, thanks
[19:46] <jcastro> I'm putting together a guide for existing teams on best practices
[19:51]  * Linden940 lookin for a good team to start with
[19:53] <sbeattie> jcastro: cool, thanks,
[21:53] <Nounoufle> \o/