[15:31] <mmrazik> hi everyone
[15:31] <mmrazik> Lets have a meeting introducing some of the quality stuff we are doing inside Canonical and more specific the Product Strategy department
[15:31] <mmrazik> #startmeeting
[15:31] <meetingology> Meeting started Tue Jan 24 15:31:53 2012 UTC.  The chair is mmrazik. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot.
[15:31] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[15:32] <AlanBell> hi mmrazik
[15:32] <mmrazik> We have one agenda topic and that is the introduction to testability -- a test automation framework for Qt
[15:32] <mmrazik> hi
[15:32] <gema> o/
[15:32] <greyback> Hi all
[15:32] <mmrazik> [TOPIC] Testability (aka automated testing in Qt environment)
[15:33] <mmrazik> greyback was so kind to do the introduction :-)
[15:33] <mmrazik> greyback, your turn :)
[15:33] <greyback> mmrazik: ok, thank you
[15:33] <greyback> Hey all, I'm Gerry Boland, team lead of the Unity 2D project. I'm here to talk about automated testing!
[15:34] <greyback> We all use our desktops every day. We know it is important for the desktop shell to be reliable, consistent and fast.
[15:34] <greyback> From the programmer's side, we strive to maintain these qualities. But we're human, and we make mistakes.
[15:34] <greyback> Sometimes a bugfix will break something else, and it's easy to miss these breakages.
[15:34] <AlanBell> are you using at-spi to do the testing?
[15:35] <greyback> AlanBell: hold on, I'm getting to it (short answer: no)
[15:35] <greyback> We have documents called "manual User Experience tests" where human beings follow a step-by-step procedure to verify the software is doing exactly what it should. But why not automate it!
[15:35] <greyback> In Unity 2D, we have just introduced an automated User Experience test system, based on a test framework called "Testability Driver" (I'll just call it 'Testability' from now on)
[15:35] <greyback> Testability is for Qt-based applications.
[15:36] <greyback> Its core feature is that it allows inspection of the tree of QObjects in a Qt application while it is running.
[15:36] <greyback> It can read and write object properties, call methods and slots, verify signals are emitted, as well as faking mouse/keyboard/gesture inputs, grabbing visual outputs, and measure performance.
[15:36] <greyback> And best of all, Testability is open source and maintained by Nokia!
[15:36] <greyback> To show it off, here is a screengrab of the Testability Visualizer application which allows you to dig into the QObject tree and investigate what's going on (here, the Launcher):
[15:37] <greyback> http://i.imgur.com/Kp7RA.png
[15:37] <greyback> On the left is a preview of the app, in the center is the object tree which you can navigate, and on the right is the list of properties, methods and signals you can interact with.
[15:37] <greyback> All these properties, methods, signals, etc, are scriptable via Ruby. Thus we can emulate every interaction that a user can make with the software, and measure the reaction.
[15:38] <greyback> This forms the foundation for the Unity 2D User Experience testing suite.
[15:38] <greyback> .
[15:38] <greyback> Testability works as follows:
[15:38] <greyback> - *any* Qt application using Qt4.6+ can be tested by executing it with the "-testability" switch (and any previous with a little code)
[15:39] <greyback> - a standalone server "qttasserver" runs in the background
[15:39] <greyback> - With the -testability switch, the Qt library tries to load a "libtestability.so" plugin which establishes a connection between the application and qttasserver, giving access to the root node of the object tree.
[15:39] <greyback> - qttasserver then climbs the QObject tree, reads all the info it can and converts it to an XML format. It also can receive commands and cause the application to react upon them (click here, type, etc..).
[15:40] <greyback> - A series of Ruby scripts connect to qttasserver, parse this XML and allow us to script tests and interactions with the application.
[15:40] <greyback> - from here, can use existing test frameworks like Test::Unit or Cucumber to run tests
[15:40] <greyback> .
[15:40] <greyback> The Unity 2D test framework also includes an extra helper library to control the X server, to control the mouse and keyboard, and to manipulate windows on the desktop. As far as X is concerned, you are controlling it.
[15:41] <greyback> With the ability to fake any form of user input, and directly read the output from the shell applications themselves, we can test almost every behaviour of the desktop shell. And as a result, the quality of the experience will only go up.
[15:41] <greyback> As a demo, here is a video of part of the Unity 2D test suite in action. On the right is Ubuntu Oneiric running inside VirtualBox, where the Launcher will be tested. On the left is my host machine terminal running the test suite:
[15:41] <greyback> https://wiki.ubuntu.com/Unity2DTestability?action=AttachFile&do=get&target=testability.ogv
[15:41] <greyback> (I hope you can all see it)
[15:42] <greyback> It shows various hide/show tests are being performed, with windows in the way, mouse being controlled, keyboard shotcuts being pressed etc.
[15:42] <mmrazik> greyback, is the X helper library developed by the Unity-2D team or is it something "standard"?
[15:42] <greyback> mmrazik: it's a heavily customised version of a ruby library for xdotool
[15:42] <greyback> mmrazik: it's in the unity-2d source repo as a result (but some stuff I want to push upstream)
[15:43] <greyback> Our policy is that every new feature and bug fix in Unity 2D will now be tested like this.
[15:43] <Riddell> greyback: is testability proprietary or free software?
[15:43] <greyback> Riddell: open source
[15:43] <greyback> Links: https://wiki.ubuntu.com/Unity2DTestability
[15:43] <Riddell> greyback: so we can package it for ubuntu and have other people be able to test unity 2d and expand that to other qt uses?
[15:43] <greyback> https://projects.developer.nokia.com/Testabilitydriver/wiki
[15:44] <greyback> Riddell: exactly. I've packaged it up in my PPA (see first link), and hope to get it into Ubuntu proper
[15:45] <greyback> Riddell: idea is that everyone can run the tests we do, and help add to them
[15:45] <greyback> Ok, that's my spiel. Thanks for your attention everybody. Questions welcome!
[15:45] <Riddell> I'm sure plenty of people would be happy to review the packaging if needed
[15:45] <AlanBell> greyback: it would be great to see tests for orca users too. With a dummy speech dispatcher module you can get the text orca would read out loud piped to a file, then the test can validate that non-visual users would be hearing something sensible
[15:46] <greyback> Riddell: I hope so. I'll need help to get it properly packaged (I made a few shortcuts)
[15:46] <greyback> AlanBell: I agree. Certainly we can read the accessibility text that is sent to Orca directly from the Qt application itself
[15:47] <greyback> AlanBell: but yes, test to ensure Orca is getting the right strings is important
[15:47] <AlanBell> reading the final output is sometimes more instructive than the individual strings
[15:48] <greyback> That's a good point. No certainly, that is something I will investigate more
[15:48] <greyback> There is still plenty to do
[15:48] <AlanBell> I can help you with the speech dispatcher module, I have one that just appends to /tmp/orca.out
[15:49] <greyback> That would be great
[15:49] <greyback> Unity2D is reasonable for A11Y, but can be better. Every bit helps
[15:49] <greyback> Thank you
[15:50] <AlanBell> is the HUD stuff included in this testing?
[15:50] <greyback> HUD needs to be written in Unity2D yet :) But yes, it will not be accepted unless there are tests for it
[15:50] <AlanBell> great
[15:51] <mmrazik> AlanBell, unfortunately testability is Qt specific
[15:51] <mmrazik> so unity 3D goes with custom solution - Autopilot
[15:51] <greyback> AlanBell: I'm assuming unity-core has unit tests to check HUD works at a lower level
[15:51] <mmrazik> right now the wiki is work in progress but to get some idea: https://wiki.ubuntu.com/Unity/QA/Autopilot
[15:51] <mmrazik> yes, that is exactly the case
[15:51] <gema> mmrazik: any way to create an abstraction layer so that you can reuse the test cases between both?
[15:51] <mmrazik> in matter of fact Mark even published some coverage data on his blog
[15:52] <mmrazik> gema, we were thinking of cucumber
[15:52] <mmrazik> but those are very early thoughts ATM
[15:52] <mmrazik> not real work was done yet
[15:52] <kalikiana> greyback: can it run something like xephyr to avoid fiddling with the running system?
[15:52] <gema> mmrazik: ack
[15:52] <AlanBell> greyback: yeah, I am just trying to push orca testing back in the development lifecycle as far as possible, hopefully as far as design one day!
[15:53] <greyback> kalikiana: yes. In fact, I have it set up to run tests on Ubutu inside a virtual box, but controlled by the host machine
[15:53] <greyback> kalikiana: it ensures as little changes as possible are made to the sustem being tested
[15:53] <kalikiana> ah, nice
[15:53] <greyback> kalikiana: Xephyr isn't quite a "pure" but something I have in mind to also support
[15:54] <kalikiana> greyback: I'm mainly saying xeyphr since it's less overhead and faster
[15:54] <kalikiana> not every potential tester may want to have a vm running
[15:55] <greyback> AlanBell: noted. I must admit, it's been some time since I've tested Unty2D and Orca. But we do test them manually during the bug-fixing stage of the cycle
[15:55] <AlanBell> yeah, it is harder then ;)
[15:55] <greyback> kalikiana: indeed. You can run these test on your machine too, it just mucks up your desktop a little afterwards :)
[15:55] <AlanBell> stuff like the new shortcut overlay in unity just plain doesn't work with orca as it can't be focussed
[15:56] <mmrazik> Ok.  Any other questions?
[15:56] <greyback> AlanBell: yep. Unity2D has a problem with the Dash textbox, it can't be navigated with Orca. It needs to be fixed
[15:57] <greyback> AlanBell: yes if you should share where I could get that dummy speech dispatcher, I'd be grateful
[15:58] <mmrazik> As we are running out of time -- many thanks for joining us, for good questions and thanks greyback for the talk.
[15:58] <greyback> You're welcome!
[15:58] <mmrazik> We are also blogging about our activities on http://qualityhour.wordpress.com/ :)
[15:58] <mmrazik> And we want to make these public meetings on a monthly basis.
[15:58] <mmrazik> So see you next time!
[15:58] <mmrazik> byt
[15:58] <mmrazik> bye
[15:59] <mmrazik> #endmeeting
[15:59] <meetingology> Meeting ended Tue Jan 24 15:59:01 2012 UTC.
[15:59] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-01-24-15.31.moin.txt
[15:59] <AlanBell> greyback: http://people.ubuntu.com/~alanbell/file.conf and you need to edit /etc/speech-dispatcher/speechd.conf to add AddModule "file"  "sd_generic" "file.conf"
[15:59] <greyback> AlanBell: magic, thanks
[15:59] <AlanBell> "echo $DATA>>/tmp/orca.out" is the bit that does the magic
[15:59] <mmrazik> (btw we are on #ubuntu-testing for post-discussions :-))
[16:01] <Daviey> .. meeting starting shortly.
[16:01] <Daviey> (server)
[16:03] <Daviey> Chair isn't here.. /me drives
[16:03] <Daviey> #startmeeting
[16:03] <meetingology> Meeting started Tue Jan 24 16:03:02 2012 UTC.  The chair is Daviey. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot.
[16:03] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[16:03] <Daviey> AlanBell: is the bot poorly?
[16:03] <Daviey> #startmeeting
[16:03] <meetingology> Daviey: Error: Can't start another meeting, one is in progress.
[16:03] <mmrazik> #endmeeting
[16:03] <Daviey> O_o
[16:04] <Daviey> o/
[16:04] <arosales> Hello
[16:04] <mmrazik> sorry.  Just thought I didn't finish my meeting.
[16:04] <hggdh> ~ô~
[16:04] <Daviey> Who is here for the ubuntu server meeting?
[16:04] <adam_g> o/
[16:04] <arosales> o/
[16:05] <utlemming> o/
[16:05] <zul> hi
[16:05]  * smb moves into the shadows
[16:05] <rbasak> o/
[16:05] <Daviey> #topic Review ACTION points from previous meeting
[16:05] <jamespage> o/
[16:06] <Daviey> Discuss merge of Open Discussion with Community update topics
[16:06] <SpamapS> Sorry for my lateness.. as usual, 1600 UTC is not doable for me.
[16:06] <SpamapS> but 1605 is :p
[16:06] <Daviey> Sounds like a no-brainer for me, any objections?
[16:06] <utlemming> +1
[16:06] <Daviey> #agreed merge of Open Discussion with Community update topics
[16:07] <SpamapS> :)
[16:07] <Daviey> #agree merge of Open Discussion with Community update topics
[16:07] <Daviey> #topic Precise Development
[16:07] <Daviey> Anyone else want to drive this?
[16:07] <Daviey> okay..
[16:07] <Daviey> Current Bugs pertinent to Precise Server release that we are working on http://status.qa.ubuntu.com/reports/ubuntu-server/release-bugs.html
[16:08] <Daviey> bug 883988
[16:08] <Daviey> adam_g: you wre following this?
[16:08] <adam_g> Daviey: yeah, targetted toward next essex milestone
[16:08] <Daviey> adam_g: looking on track?
[16:09] <adam_g> Daviey: honestly not sure anyone has touched it upstream but a fix has been discussed
[16:09] <Daviey> bug 893926 , assigned to mainerror who isn't here.  I'll follow up with him shortly.
[16:09] <Daviey> bug 911812, roaksoax ?
[16:10] <Daviey> adam_g: thanks, can you follow that up?
[16:10] <adam_g> Daviey: the glance bug? yes, ill ping jay this week to find out his thoughts
[16:10] <Daviey> rocking
[16:10] <SpamapS> Daviey: shouldn't we also be going over the WI tracker, since FF is coming soon?
[16:11] <Daviey> SpamapS: yes, but lets get the bugs done
[16:11] <Daviey> roaksoax: are you here?
[16:11] <Daviey> bug 913009, smoser is /away.. I believe it is still untouched, pending new upstream snapshot
[16:12] <Daviey> bug 916992, adam_g ?
[16:12] <adam_g> Daviey: patch merged upstream, should be fix released in ubuntu next snapshot (fri)
[16:12] <Daviey> SpamapS: following bug 914392 ?
[16:12] <Daviey> adam_g: great!
[16:13] <Daviey> new bug 920202, up for grabs!
[16:13] <Daviey> anyone want it?
[16:13] <SpamapS> Daviey: I am aware of 914392 but I have not been following up on it. I think the fix is fairly trivial, so perhaps I can patch it myself.
[16:13] <adam_g> Daviey: ill poke at it
[16:14] <Daviey> adam_g: you rock star!
[16:14] <zul> Daviey: i would poke lamont
[16:14] <Daviey> SpamapS: great news, do you want to take ownership
[16:14] <Daviey> zul: good thinking
[16:14] <Daviey> bug 875262 , SpamapS were you working with koolhead17 ?
[16:15] <Daviey> smb: has bug 607039 moved?
[16:15] <smb> Daviey, errr not really
[16:16] <Daviey> zul: bug 890362 ?
[16:16] <zul> Daviey: will be addressed this week
[16:16] <Daviey> bug 898840 .. roaksoax  seems absent, but i think it is blocked.
[16:16] <rbasak> SpamapS: re: bug 914392, I've just s/oneiric/precise/ as a workaround and it seems to be ok. Not fully tested thisi though.
[16:16] <Daviey> smb: Is there a path forward?
[16:17] <SpamapS> rbasak: right, but its a fairly important bug. ;)
[16:17] <Daviey> bug 904681, assigned to a slacker.. He hasn't touched it, but will do today/tomorrow.
[16:17] <rbasak> yes :)
[16:17] <smb> Daviey, If I had seen this before I may have an answer
[16:17] <SpamapS> Daviey: I will take bug 912716
[16:17] <Daviey> smb: Oh, sorry - i thought you were tracking that one?
[16:18] <smb> Daviey, Not that I can recall
[16:18] <Daviey> SpamapS: I think hggdh tentively had that one, awaiting triage/confirm
[16:18] <smb> ... though that may mean nothing
[16:18] <hggdh> this has been fixed since Maverick (by a zul patch!)
[16:18] <Daviey> smb: oh, ok - sorry.
[16:18] <smb> Daviey, Maybe SpamapS ?
[16:18] <Daviey> heh
[16:18] <hggdh> I am just waiting on the OP to clarify before closing
[16:18] <SpamapS> Daviey: yeah, it is the same bug, but the original bug wasn't actually fixed
[16:19] <Daviey> smb: I see you were on it in Nov. Are you wanting to continue on it?
[16:19] <lamont> Daviey: bah.  I'll look into that today
[16:19] <lamont> 920202 that is
[16:19] <smb> Daviey, About what do we talk exactly..?
[16:19] <Daviey> SpamapS: Sorry, i might have moved too fast.. but did you see me ask about the php bug? ^^
[16:19] <Daviey> lamont: \o/
[16:20] <Daviey> (lamont, there seems to bea  Debian bug aswell fwiw)
[16:20] <lamont> Daviey: that's because I'm consistent.
[16:20] <Daviey> smb: https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/607039/comments/19
[16:20] <Daviey> lamont: heh
[16:20] <smb> Daviey, Ah, yes. I may sure
[16:22] <Daviey> zul: bug 906654 ?
[16:22] <SpamapS> Daviey: the PHP bug is just an obsolete conffile that postinst should be removing.
[16:22] <zul> Daviey: i think openstackx might actually merged into nova proper, but other than that im still waiting for the MIR
[16:22] <Daviey> SpamapS: any closer to getting fix0rd?
[16:22] <Daviey> zul: which MIR ?
[16:23] <zul> Daviey: horizon
[16:23] <Daviey> ah, cool
[16:23] <Daviey> bug 907197, zul ?
[16:23] <zul> need to reproduce first..
[16:24] <Daviey> zul: that would seem pretty bad if it is valid.. :/
[16:24] <SpamapS> Daviey: no, somebody needs to take the action suggested by slangasek in comment #16.
[16:24] <Daviey> zul: will you be able to reproduce this week?
[16:24] <zul> Daviey: i can try it this afternoon
[16:24] <Daviey> SpamapS: Right, i thought you were working with koolhead17 to resolve that?
[16:24] <SpamapS> Daviey: have not heard from koolhead on it. Will ping him.
[16:25] <Daviey> s/i\ thought//
[16:25] <Daviey> SpamapS: rocking!
[16:25] <Daviey> bug 914257, adam_g
[16:25] <Daviey> adam_g: should that be Fix Committed?
[16:26] <adam_g> Daviey: will get to that in the next day or two
[16:26] <Daviey> adam_g: looks like it's fixed in bzr?
[16:26] <Daviey> bug 879666, rbasak
[16:26] <adam_g> Daviey: unfortunately, no
[16:26] <zul> Daviey: it has different side affects
[16:27] <adam_g> Daviey: the local_settings.py that was shipping before is no longer, so i propose we ship our own basedoff the example. ill ping zul about thi later this AM
[16:27] <Daviey> adam_g & zul: http://bazaar.launchpad.net/~ubuntu-server-dev/horizon/essex/revision/22 ?
[16:27] <rbasak> I hadn't seen your comment. I'll update the debdiff for precise.
[16:28] <adam_g> Daviey: no, that doesn't fix the bug and not sure why it was merged as such. local_settings.py is no longer part of the package, and is not installed.
[16:28] <adam_g> Daviey: and, if it was, the django app doesn't import it from /etc/openstack-dashboard
[16:29] <Daviey> lynxman: bug 916489 ?
[16:29] <Daviey> (lnxman awaiting update to merge proposal)
[16:30] <Daviey> Okay, shall we move on?
[16:31] <Daviey> http://status.ubuntu.com/ubuntu-precise/group/topic-precise-servercloud-infrastructure-deployment.html
[16:31] <Daviey> We seem to be making reasonably good progress.
[16:31] <Daviey> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-cloud-power-management is of concern.
[16:31] <Daviey> roaksoax: when you read this, can you follow up with aquette ?
[16:32] <Daviey> jjohansen: What is the status of https://blueprints.launchpad.net/ubuntu/+spec/security-p-apparmor-containers ?
[16:32] <roaksoax> Daviey: will do
[16:32] <Daviey> jdstrand: ^^, is it looking ok?
[16:33] <Daviey> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-arm-service-orchestration ... will be flushed today, with some changes.
[16:33] <Daviey> SpamapS: how is, https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-juju-charm-testing looking ?
[16:33] <SpamapS> Daviey: spec should land on the juju mailing list today, which should give way to the others falling rather rapidly
[16:34] <jdstrand> Daviey: jjohansen is continuing to work hard on this. it is an essential bp which we are committed to delivering
[16:34] <jdstrand> Daviey: he has made significant progress, but it hasn't landed yet
[16:34] <Daviey> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-ceph .. is looking a concern.
[16:34] <SpamapS> Daviey: yeah, about half of that is going to have to be postponed
[16:35] <Daviey> arosales: are you able to dig into servercloud-p-ceph ?
[16:35] <Daviey> SpamapS: \o/, GREAT news
[16:35] <Daviey> nice one.
[16:35] <SpamapS> Daviey: it should hit main, it should have a MIR, but other than that, I don't think we're going to get much further with it
[16:35] <Daviey> roaksoax: https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-powernap ?
[16:35] <Daviey> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-virtio-device-driver , is blocked on some non-Ubuntu issues.
[16:36] <Daviey> jdstrand: thanks for the update!
[16:36] <roaksoax> Daviey: well... haven't yet work on it furhter as I've been more concentrated into the cobb;er/orchestra/and now with the new stuff might gonna have to postpone work items
[16:37] <Daviey> arosales: https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-glusterfs-mir .. seems a MIR hasn't yet been raised.. that can be marked done when resolved.
[16:37] <Daviey> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-openstack-testing jamespage / adam_g ?
[16:37] <adam_g> Daviey: should be marking a couple of those DONE this week
[16:37] <Daviey> SpamapS: Ceph in main?
[16:38] <SpamapS> Daviey: Yes, since we're going to turn on qemu's ceph RBD support
[16:38] <Daviey> rbasak: https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-arm-service-orchestration anything blocking?
[16:39] <Daviey> adam_g: https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-openstack-charms how is it looking?
[16:39] <rbasak> nope, just hitting more issues though. another bug to file outstanding
[16:39] <Daviey> lynxman, still not here? https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-cfjuju
[16:40] <rbasak> I've been slowed massively by a kernel regression but a fix is on its way
[16:40] <arosales> Daviey:  re: servercloud-p-glusterfs-mir: yup, SpamapS was also going to look in to that one, not anticipating a lot of work to complete the work item.
[16:40] <Daviey> rbasak / adam_g: please comment so we can move on.
[16:40] <adam_g> Daviey: looking okay, have some of those chamrs ready for merge into charm store currently
[16:41] <Daviey> !ping
[16:42] <Daviey> Am i here?
[16:42] <smb> Daviey, Which one of you?
[16:42] <Daviey> (there seems to be lag going on?)
[16:43] <smb> Hm, did not see any lag here but it is quite quiet
[16:44] <rbasak> who is still here?
[16:44] <rbasak> o/
[16:44] <jamespage> o/
[16:44] <smb> \o
[16:44] <adam_g> o/
[16:44] <Daviey> bug 1
[16:44] <hggdh> ~ô~
[16:44] <arosales> o/
[16:44] <utlemming> o/
[16:45]  * rbasak doesn't see any lag
[16:45] <smb> He is connected
[16:45] <Daviey> roaksoax: Okay, shall we discuss it out of band?
[16:45] <SpamapS> o/
[16:45]  * SpamapS had "alt-tab" induced lag
[16:45] <roaksoax> Daviey: sure
[16:47] <Daviey> GREAT adam_g
[16:47] <Daviey> #topic Ubuntu Server Team Events
[16:47] <Daviey> FOSDEM next weekend, expect to see - jamespage, rbasak and Daviey
[16:47] <Daviey> Other events?
[16:48] <arosales> Daviey, had some pretty good interest in Juju and Server at SCALE10x this past weekend.
[16:48] <Daviey> SpamapS: ok, thanks
[16:48] <arosales> SpamapS: and jcastro gave a charmschool and talk @SCALE 10x
[16:51] <SpamapS> Nothing in the immediate horizon though.
[16:51] <Daviey> #topic Weekly Updates & Questions for the QA Team (hggdh)
[16:52] <Daviey> Problem solved... sorry!
[16:52] <hggdh> no news from me, life seems to be kludging along on the QA/server front ;-)
[16:52] <hggdh> ..
[16:53] <Daviey> ok, thanks
[16:53] <Daviey> #topic Weekly Updates & Questions for the Kernel Team (smb)
[16:53] <smb> Still working on getting cobbler up locally which is not as simple as I thought
[16:53] <Daviey> smb: do you want some pointers?
[16:53] <smb> Am able to pxeboot real and virtual machines in some way
[16:53] <smb> Daviey, Always appreciated
[16:54] <Daviey> smb: roaksoax, smoser, myself etc are always willing to jump in.... always feel free to ask in #ubuntu-serber
[16:54] <Daviey> err, server
[16:54] <Daviey> thanks smb
[16:54] <Daviey> #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)
[16:55] <rbasak> I have one openmpi question
[16:55] <rbasak> bug 889644
[16:55] <rbasak> With janimo's help I now have a version that builds on arm, and Debian have already taken it - their 1.5 is in experimental. But I'm worried about syncing this because it would pull the general archive version up from 1.4 to 1.5, and I don't know what other dependencies might break. There do seem to be a pile of rdepends. What exactly is the functionality/use case that we need to add, how would I verify existing functionality is not broken determ
[16:55] <rbasak> ine that what we need to add works? Or should I just get 1.5 synced and worry about what breaks later?
[16:55] <rbasak> Other than that ARM work is chugging away. I'm still hitting bugs trying to get juju to work, but am slowly making progress
[16:56] <Daviey> rbasak: I don't thnk anyone here has touched openmpi before, but i agree it does have plenty of rdepends.
[16:56] <Daviey> rbasak: lets take that offline...
[16:56] <rbasak> ok
[16:57] <Daviey> #topic Weekly Updates & Questions from the Ubuntu Community and Open Discussion
[16:57] <Daviey> ^^ note, new topic
[16:57] <Daviey> Firstly, sorry for my laggy connection.. I had some woes :/
[16:57] <arosales> Any objections from the server team from removing mysql-cluster-7.0 from universe?  It hasn't gotten any updates since September, no new upstream source since January 2011, and its not in Debian. It has a bunch of security vulnerabilities (with little/no upstream support from oracle) that will make maintaining it a large effort.
[16:57] <Daviey> anything from anyone?
[16:57] <Daviey> arosales: Sounds like a +1 from me, i don't think it had a high userbase anyway.
[16:57] <arosales> jdstrand had brought this up yesterday, and I wanted to check with the team
[16:58] <Daviey> Would be good to see it in Debian tho!
[16:58] <arosales> ok, I'll let jdstrand know this can be  removed from Universe
[16:58] <Daviey> moving on.... ?
[16:58] <Daviey> #topic Announce next meeting date and time
[16:59] <Daviey> same time, same place.. have fun..
[16:59] <Daviey> thanks for coming.
[16:59] <Daviey> o/
[16:59] <Daviey> #endmeeting
[16:59] <meetingology> Meeting ended Tue Jan 24 16:59:14 2012 UTC.
[16:59] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-01-24-16.03.moin.txt
[16:59] <apw> o/
[16:59] <jsalisbury> Roll Call for Ubuntu Kernel Weekly Status Meeting
[16:59] <smb> \o
[16:59] <herton> o/
[16:59] <smb> (still)
[17:00] <tgardner> o/
[17:00] <bjf> o/
[17:00] <ogasawara> o/
[17:00] <sforshee> o/
[17:00] <jsalisbury> #startmeeting
[17:00] <meetingology> Meeting started Tue Jan 24 17:00:20 2012 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot.
[17:00] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> ## This is the Ubuntu Kernel Team weekly status meeting.
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[17:00] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Precise
[17:00] <jsalisbury> # Meeting Etiquette
[17:00] <jsalisbury> #
[17:00] <jsalisbury> # NOTE: '..' indicates that you are finished with your input.
[17:00] <jsalisbury> #       'o/' indicates you have something to add (please wait until you are recognized)
[17:00] <jsalisbury> [TOPIC] ARM Status (ppisati)
[17:00] <ppisati> Nothing new to report this week.
[17:00] <ppisati> ..
[17:00] <jsalisbury> [TOPIC] Release Metrics and Incoming Bugs (jsalisbury)
[17:01] <jsalisbury> Release metrics and incomming bug data can be reviewed at the following link:
[17:01] <jsalisbury> [LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt
[17:01] <jsalisbury> ..
[17:01] <jsalisbury> [TOPIC] Milestone Targeted Work Items (ogasawara)
[17:01] <ogasawara> [LINK] http://status.ubuntu.com/ubuntu-precise/canonical-kernel-distro-team-precise-alpha-2.html
[17:01] <ogasawara> || apw        || hardware-p-kernel-boot                || 1 work item  ||
[17:01] <ogasawara> ||            || hardware-p-kernel-config-review       || 4 work items ||
[17:01] <ogasawara> ||            || hardware-p-kernel-delta-review        || 3 work items ||
[17:01] <ogasawara> ||            || foundations-p-ipv6                    || 1 work item  ||
[17:01] <ogasawara> || jsalisbury || other-p-bug-workflows                 || 1 work item  ||
[17:02] <ogasawara> || ogasawara  || hardware-p-kernel-config-review       || 3 work items ||
[17:02] <ogasawara> || tgardner   || hardware-p-kernel-delta-review        || 1 work item  ||
[17:02] <ogasawara> If your name is in the above table, please review your Alpha-2 work items.  Note that Alpha-2 is next Thurs Feb 2.
[17:02] <ogasawara> ..
[17:02] <jsalisbury> [TOPIC] Blueprint: hardware-p-kernel-power-management (cking)
[17:02] <cking> no updates this week
[17:02] <cking> ..
[17:03] <jsalisbury> [TOPIC] Status: Precise Development Kernel (ogasawara)
[17:03] <ogasawara> Last week we uploaded the linux-3.2.0-10.17 Ubuntu kernel and we have
[17:03] <ogasawara> also just uploaded linux-3.2.0-10.18.  With Alpha-2 next Thurs, Feb 2,
[17:03] <ogasawara> I'd ideally like to upload our final kernel for the Alpha-2 milestone by
[17:03] <ogasawara> this Friday.  For any patches needing to land in Alpha-2, send them out
[17:03] <ogasawara> to the kernel-team mailing list immediately.
[17:03] <ogasawara> Important Upcoming Dates:
[17:03] <ogasawara>  * Thurs Feb 2 - Alpha 2 (~1 week)
[17:03] <ogasawara> ..
[17:03] <ogasawara> ~
[17:03] <jsalisbury> [TOPIC] Status: CVE's (apw)
[17:03] <apw> [17:03] <apw>  
[17:03] <apw> [LINK] http://people.canonical.com/~kernel/cve/pkg/CVE-linux.txt
[17:03] <apw>  
[17:03] <apw> Currently open CVEs for each supported branch:
[17:03] <apw>  
[17:04] <apw> || Package                                  || Open      ||
[17:04] <apw> ||                                          ||           ||
[17:04] <apw> || linux Hardy                              ||   17 (-3) ||
[17:04] <apw> || linux Lucid                              ||   12      ||
[17:04] <apw> || linux Maverick                           ||   11 (-2) ||
[17:04] <apw> || linux Natty                              ||   10 (-3) ||
[17:04] <apw> || linux Oneiric                            ||    9      ||
[17:04] <apw> || linux Precise                            ||    7      ||
[17:04] <apw> || linux-ec2 Lucid                          ||   12      ||
[17:04] <apw> || linux-fsl-imx51 Lucid                    ||   11 (-4) ||
[17:04] <apw> || linux-mvl-dove Lucid                     ||    9 (-2) ||
[17:04] <apw> || linux-mvl-dove Maverick                  ||    9 (-2) ||
[17:04] <apw> || linux-ti-omap4 Maverick                  ||   12 (-4) ||
[17:04] <apw> || linux-ti-omap4 Natty                     ||    7 (-5) ||
[17:04] <apw> || linux-ti-omap4 Oneiric                   ||    6 (-2) ||
[17:04] <apw> || linux-ti-omap4 Precise                   ||    5 (-2) ||
[17:04] <apw> || linux-lts-backport-maverick Lucid        ||   11 (-2) ||
[17:04] <apw> || linux-lts-backport-natty Lucid           ||   10 (-3) ||
[17:04] <apw> || linux-lts-backport-oneiric Lucid         ||    9      ||
[17:04] <apw>  
[17:04] <apw> This week two new CVEs were added both of which were closed out.
[17:04] <apw> Overall we have made some progress in closing the outstanding backlog.
[17:04] <apw>  
[17:04] <apw> ..
[17:05] <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Oneiric/Natty/Maverick/Lucid/Hardy (bjf/herton)
[17:05] <bjf> Here is the status for the main kernels, until today (Jan. 24):
[17:05] <bjf>  
[17:05] <bjf>  * Hardy - 2.6.24-30.98
[17:05] <bjf>   * In updates.
[17:05] <bjf>   * Nothing new to prep, there were no new commits on master-next.
[17:05] <bjf>  
[17:05] <bjf>  * Lucid - 2.6.32-38.84
[17:05] <bjf>   * Prep'd and uploaded.
[17:05] <bjf>  
[17:05] <bjf>  * Maverick - 2.6.35-32.65
[17:05] <bjf>   * Prep'd and uploaded.
[17:05] <bjf>  
[17:05] <bjf>  * Natty - 2.6.38-13.55
[17:05] <bjf>   * Prep'd and uploaded.
[17:05] <bjf>  
[17:05] <bjf>  * Oneiric - 3.0.0-16.27
[17:05] <bjf>   * Prep'd and uploaded.
[17:05] <bjf>  
[17:05] <bjf> Current opened tracking bugs details:
[17:05] <bjf>  * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
[17:05] <bjf>  
[17:05] <bjf> For SRUs, SRU report is a good source of information:
[17:06] <bjf>  * http://people.canonical.com/~kernel/reports/sru-report.html
[17:06] <bjf>  
[17:06] <bjf> Future stable cadence cycles:
[17:06] <bjf>  * https://wiki.ubuntu.com/PrecisePangolin/ReleaseInterlock
[17:06] <bjf> ..
[17:06] <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
[17:07] <jsalisbury> If no questions/discussions, then:
[17:07] <jsalisbury> #endmeeting
[17:07] <meetingology> Meeting ended Tue Jan 24 17:07:29 2012 UTC.
[17:07] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-01-24-17.00.moin.txt
[17:07] <jsalisbury> thanks everyone