=== astechgeek is now known as the_r0cker
[07:18] <ara> morning all!
[08:19]  * ara goes to grab a coffee
[10:47] <czajkowski> aloha folks
[10:50] <ara> hey czajkowski
[10:52] <czajkowski> ara: good weekend?
[10:53] <ara> czajkowski, yes, I met an old friend I hadn't seen in a while
[10:53] <ara> czajkowski, yours?
[10:54] <czajkowski> ara: nice, watched rugby on Saturday and then finally got around to going through all the gobby docs and writing out my to do list.
[10:54] <ara> czajkowski, nice :)
[12:45]  * ara -> lunch
=== fader|away is now known as fader_
[13:23] <fader_> Morning all
[14:22] <moustafa> fader_, cr3: Baguette!
[14:25] <davmor3> hello everybody
[14:25] <moustafa> hello davmor3
[14:25] <fagan> davmor3: hello
[14:26] <davmor3> back is finally on the mend
[14:27] <cr3> moustafa: tour eiffel
[14:27] <cr3> davmor3: welcome "back"! :)
[14:28] <fader_> moustafa, davmor3: hey dudes
[14:28]  * fagan feels like chopped liver 
[14:29] <fagan> hey fader_ :)
[14:29] <moustafa> Since I can't find any decent "back" puns, I'll divert attention with this: http://www.collegehumor.com/video:1919599
[14:29] <fader_> fagan: Howdy!
[14:29] <fader_> :)
[14:29]  * fader_ spreads some fagan on a cracker.
[14:30] <fagan> haha
[14:47] <fagan> oh can someone help me traige a bug
[14:47] <fagan> its with gwibber
[14:48] <fagan> I dont know if its specific to my computer's config or a bug with gwibber
[15:01] <ara> hey jsalisbury
[15:02] <jsalisbury> ara:  Good morning, or afternoon ;-)
[15:04] <ara> jsalisbury, :)
[15:06] <fader_> fagan: I'm not much of a gwibber power-user or anything but I might be able to help; what are you seeing?
=== Ubot-Tn is now known as MaWaLe
[17:07] <fagan> fader_: Could you set up a facebook account on gwibber and then close it then open gwibber again via the messaging menu does it ask you to add verify the facebook account again?
=== jdstrand_ is now known as jdstrand
[20:34] <fader_> fagan: FYI, I wasn't able to reproduce the facebook/gwibber behavior you described
[20:34] <fagan> Hmmmm must be a config problem
[20:34] <fagan> ill try to delete the cache of it and see if that helps
[20:36] <fader_> I seem to recall having seen something similar to it a couple of weeks back but I can't reproduce it now.
[21:28] <soren> cr3: So, https://blueprints.edge.launchpad.net/ubuntu/+spec/server-lucid-automated-testing has my name on it, but you suggested you guys were going to do some of it?
[21:31] <cr3> soren: after looking it, I seem comfortable with everything except: Multi-system environements: documentation.
[21:32] <cr3> soren: I think I should be the assignee though
[21:32] <soren> cr3: Are we talking about the same thing?
[21:32] <cr3> marjo: ^^^ shouldn't I be the assignee for the above spec?
[21:33] <soren> cr3: There's a list of work items at the bottom.
[21:33] <soren> cr3: Of that page. Not of the spec on the wiki.
[21:33] <cr3> soren: I was looking at the wiki page
[21:33] <marjo> cr3: i don't think you should be the assignee on that one
[21:34] <soren> cr3: If you were to grab all the stuff that matches /qa-regression-tests.*checkbox/, I'd be a happy camper.
[21:34] <soren> cr3: ..and I'd be happy to help out.
[21:34] <marjo> it's really for someone like the "Server QA Engineer"
[21:34] <cr3> soren: sounds good to me, if you remind me to do them at some point
[21:34] <soren> cr3: Like now?
[21:35] <marjo> soren: yes, that makes more sense; we need one assignee but the work might be done by others
[21:35] <cr3> marjo: should I volunteer to do that kind of work or should I sit back and relax until we find a server qa engineer?
[21:36] <soren> cr3: Tell you what... If you can do one or two of them this week, I can look at what you did and we can just tag team on the rest of them?
[21:36] <cr3> soren: that list of TODO doesn't cover the ServerWhole tests mentionned on the wiki page
[21:36] <marjo> cr3: you're welcome to volunteer and i can reassign it later
[21:36] <soren> cr3: I'm going to be doing a /lot/ of qa work this cycle. I'd be happy to work together with you on this and make it a joint effort.
[21:37] <soren> cr3: Right you are. I wasn't sure how to make the ServerWhole stuff fit into this.
[21:37] <marjo> soren: thx for the offer; that makes a lot of sense; we appreciate it
[21:37] <cr3> soren: I'm probably the last person to ask about task management
[21:37] <soren> hey, stuff like this makes me sleep better at night. It'd be my pleasure :)
[21:37] <soren> cr3: Heheh :)
[21:38] <cr3> marjo: question from soren: the wiki page for the above blueprint mentions integrating the ServerWhole testcases wiki page, so how to we express that as TODO list?
[21:38] <marjo> cr3: just state it like you just said and put an owner to it using the "workitem: TODO" syntax
[21:39] <marjo> i would treat that as a deliverable within the larger blueprint project
[21:39] <soren> IIUIC, ServerWhole is a reference to the whole set of ISO test cases, right? The ones that are currently all manual?
[21:40] <cr3> soren: yes, the ones that mathiaz usually runs himself at the cost of his sanity
[21:40] <marjo> only other way to do it is to create a separate blueprint (too much overhead, i think)
[21:41] <soren> cr3: Ok, gotcha. Yeah, that would be interesting to automate as much as possible. Even more than Mathiaz already does. kvm has some interesting tidbits for that.
[22:00] <moustafa> cr3, fader_: I'm off for the night, later!"
[22:00] <fader_> moustafa: ciao!
=== fader_ is now known as fader|away
[22:23] <soren> cr3: Can you ping me when you've integrated the first couple of things from q-r-t into checkbox? That would give me a really good starting point for learning the process.
[22:23] <cr3> soren: I'll try to find some time for this tomorrow, does that sound reasonable?
[22:24] <soren> cr3: Sounds perfect.
[22:49] <sbeattie> soren|cr3: from what I recall, it'd be fairly trivial to incorporate the elements of mathiaz' tests into qa-r-t
[22:59] <cr3> sbeattie: qrt is almost 500 megs to branch, I'd rather leave actual regression tests in that suite. we can talk about it tomorrow, I'm outa here