[18:47]  * Rinchen looks around and sees MootBot and breathes a sign of relief.
[18:57] <mpt> [WC] <- sign of relief
[18:58] <intellectronica> thanks for letting us know!
[18:58] <Rinchen> heh
[18:58] <mpt> ah, intellectronica, you missed the context by ten minutes :-)
[18:58]  * thumper has coffee
[18:58] <intellectronica> i'm not sure whether i should be happy or sad about that
[18:59] <intellectronica> i'll default to happy
[19:00] <salgado> me
[19:00] <schwuk> you
[19:00] <sinzui> him
[19:00] <bac> us
[19:00] <thumper> I
[19:01] <thumper> aye
[19:01]  * allenap is feeding his daughter; 7pm is not such a good time for the meeting :)
[19:01] <carlos> me
[19:01] <bigjools> allenap: seconded
[19:01] <al-maisan> me
[19:01] <thumper> 6am ain't so hot either
[19:01] <gmb> me
[19:01] <leonardr> me
[19:01] <thumper> Rinchen: c'mon
[19:01] <Rinchen> vroom
[19:02] <allenap> thumper: granted
[19:02] <bigjools> thumper: I thought you always got up at 6am? :)
[19:02]  * schwuk waits for rollcall
[19:02] <Rinchen> geez, anxious bunch
[19:02] <flacoste> me
[19:02] <Rinchen> #startmeeting
[19:02] <MootBot> Meeting started at 20:02. The chair is Rinchen.
[19:02] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[19:02] <thumper> bigjools: almost, but not always coherent
[19:02] <Rinchen> Welcome to this week's Launchpad development meeting. For the next 45 minutes or so, we'll be coordinating Launchpad development.
[19:02] <Rinchen> [TOPIC] Roll Call
[19:02] <abentley> me
[19:02] <MootBot> New Topic:  Roll Call
[19:02] <mrevell> me
[19:02] <gmb> me
[19:02] <Rinchen> me
[19:02] <jt1> me
[19:02] <flacoste> me
[19:02] <salgado> me
[19:02] <allenap> me
[19:02] <bigjools> me
[19:02] <mars> me
[19:02] <barry> me
[19:02] <schwuk> me
[19:02] <mpt> me
[19:02] <herb> me
[19:02] <leonardr> me
[19:02] <intellectronica> me
[19:02] <matsubara> me
[19:02] <Rinchen> (and my beeps aren't working today again)
[19:02] <bac> me
[19:02] <adeuring> me
[19:02] <BjornT> me
[19:02] <sinzui> me
[19:02] <cprov> me
[19:02] <gmb> thumper: Is that a definition of bigjools? Cos that's how it reads ;)
[19:02] <thumper> me
[19:02] <jtv> me
[19:02] <SteveA> me
[19:03] <kiko-afk> me
[19:03] <statik> me
[19:03] <EdwinGrubbs> me
[19:04] <Rinchen> hmm.... ok, let's keep going!
[19:04] <Rinchen> [TOPIC] Agenda
[19:04] <MootBot> New Topic:  Agenda
[19:04] <Rinchen>  * Next meeting
[19:04] <Rinchen>  * Actions from last meeting
[19:04] <Rinchen>  * Oops report (Matsubara)
[19:04] <Rinchen>  * Critical Bugs (Rinchen)
[19:04] <Rinchen>  * Bug tags
[19:04] <Rinchen>  * Operations report (mthaddon/herb)
[19:04] <Rinchen>  * DBA report (stub)
[19:04] <Rinchen>  * Sysadmin requests (Rinchen)
[19:04] <Rinchen>  * New packages required (salgado)
[19:04] <Rinchen>  * A top user-affecting issue (mrevell)
[19:04] <Rinchen>  * Doc Team report (mrevell)
[19:04] <Rinchen>  * Blockers
[19:04] <Rinchen> [TOPIC] Next meeting
[19:04] <MootBot> New Topic:  Next meeting
[19:04] <Rinchen> same time, same channel?
[19:05] <SteveA> I'd prefer a tad earlier
[19:05] <SteveA> bit it's no biggie
[19:05] <thumper> :(
[19:05] <kiko-afk> SteveA, what about thumper?
[19:05] <kiko> well, last week we said we'd experiment rotating team leads
[19:05] <kiko> the team leads call, sorry
[19:05] <kiko> turns out we didn't agree to do that for this round
[19:06] <Rinchen> our next call is on Wednesday of next week so we can bring the topic up again
[19:06] <SteveA> so, as the meeting is late for europeans, I ask that we keep it firmly on time
[19:06] <kiko> I really want a time that works for tim and jtv
[19:06] <SteveA> and end exactly 45 minutes after starting
[19:06] <kiko> we make a serious effort to end 45 minutes after
[19:06] <SteveA> well
[19:06] <SteveA> we just end then ;-)
[19:06] <SteveA> and take the consequences
[19:06] <Rinchen> [AGREED] Same time next week
[19:06] <MootBot> AGREED received:  Same time next week
[19:06] <Rinchen> [TOPIC] Actions from last meeting
[19:06] <MootBot> New Topic:  Actions from last meeting
[19:06] <Rinchen> none
[19:06] <Rinchen> [TOPIC] Oops report (Matsubara)
[19:06] <MootBot> New Topic:  Oops report (Matsubara)
[19:06] <Rinchen> (vrooom)
[19:07] <matsubara> Today's oops report is about bugs 214843, 198368
[19:07]  * Rinchen chuckles.
[19:07] <ubotu> Launchpad bug 214843 in launchpad "Cycles in team data kill mailing lists" [Critical,Confirmed] https://launchpad.net/bugs/214843
[19:07] <ubotu> Bug 198368 on http://launchpad.net/bugs/198368 is private
[19:07] <matsubara> #214843 is already assigned do barry.
[19:07] <matsubara> to barry
[19:07] <matsubara> barry: any news about #198368?
[19:07] <barry> i think the data problem is already fixed, as is the resync issue.  we now have bug 215118 in review
[19:07] <ubotu> Launchpad bug 215118 in launchpad "Odd mailing list resync behavior" [High,Confirmed] https://launchpad.net/bugs/215118
[19:08] <barry> once that lands we should be good to go
[19:08] <barry> that's it
[19:08] <matsubara> thanks barry
[19:08] <matsubara> back to you Rinchen.
[19:08] <Rinchen> thanks!
[19:08] <Rinchen> [TOPIC] Critical Bugs (Rinchen)
[19:08] <MootBot> New Topic:  Critical Bugs (Rinchen)
[19:09] <Rinchen> [LINK] https://bugs.edge.launchpad.net/launchpad/+bug/206654
[19:09] <Rinchen> This is the memory issue. flacoste, SteveA.  Any updated status?
[19:09] <MootBot> LINK received:  https://bugs.edge.launchpad.net/launchpad/+bug/206654
[19:09] <Rinchen> [LINK] https://bugs.edge.launchpad.net/launchpad-bazaar/+bug/207558
[19:09] <Rinchen>  thumper, what's the next step with this?
[19:09] <MootBot> LINK received:  https://bugs.edge.launchpad.net/launchpad-bazaar/+bug/207558
[19:09] <kiko> I'm really unhappy about that one
[19:09] <flacoste> Rinchen: mthaddonis copying the references leak log
[19:09] <ubotu> Launchpad bug 207558 in bzr ""bzr branch http://bazaar.launchpad.net/...." fails with bzr.dev >= r3309" [Critical,Fix released]
[19:09] <thumper> I think that was just with bzr.dev
[19:09] <SteveA> kiko: what one?
[19:09] <thumper> and is fixed
[19:09] <flacoste> Rinchen: i'll investigate after that, but we are not seeing any big leak on the monitoring server, probably due to the fact that it receives a lot less requests
[19:09] <Rinchen> interesting flacoste
[19:10] <kiko> the server issue, SteveA
[19:10] <Rinchen> thumper, can you please update the bug then since there is a code hosting task assigned?
[19:10] <thumper> ah
[19:10] <kiko> we need a new strategy for dealing with it
[19:10] <SteveA> kiko: it's a tricky one, for sure
[19:10] <thumper> I recall now
[19:10] <flacoste> Rinchen: i'm hoping to correlate a small leak in the monitoring log to the big one based on the difference in number of requests
[19:10] <thumper> lifeless filed an RT to get apache config updated
[19:10] <SteveA> kiko: what are you talking about?
[19:10] <kiko> SteveA, well..
[19:10] <SteveA> kiko: we have a strategy for dealing with it, which is in progress
[19:11] <kiko> SteveA, is that strategy going to work? it seems we've made the change and the change we've made has hidden the problem from that environment.
[19:11] <SteveA> kiko: I'd appreciate a bit more support and positivity considering the work people are putting into diagnosing this
[19:11] <kiko> meanwhile, clock ticking, etc
[19:11] <thumper> Rinchen: confirmed with config that the RT has been executed
[19:11] <SteveA> we don't know that the change has hidden anything
[19:11]  * thumper updates task
[19:11] <Rinchen> thumper, thank you sir.
[19:12] <flacoste> kiko: well, since the problem now disapperaed from edge, maybe it will go away by itself in the next roll-out ;-)
[19:12] <SteveA> we are collecting data, and we need to analyze it and tweak how we're collecting it based on the analysis
[19:12] <kiko> SteveA, that's all just words to me. I haven't seen us progress to a solution after more than a week, and that's what's concerning me
[19:12] <SteveA> kiko: I have no idea what you're talking about
[19:12] <kiko> flacoste, completely? no edge instances are balooning?
[19:12]  * kiko chuckles
[19:12] <kiko> heisenbug indeed
[19:13] <flacoste> kiko: i wouldn't count on it though, because until last week, that was isolated to edge
[19:13] <flacoste> kiko: and it's not like a cherry-pick could explain it
[19:13] <Rinchen> flacoste, perhaps it time for a quick update on status to be posted to the bug. That way kiko will see the work you and others are doing.  Would you be ok with that?
[19:13] <kiko> flacoste, f*cking crazy.
[19:13] <flacoste> Rinchen: sure
[19:13] <kiko> I know what work's been done, though.
[19:14] <kiko> that's not really the issue :)
[19:14] <kiko> but go ahead, it'll be interesting
[19:14] <flacoste> what kiko wants is results!
[19:14] <SteveA> what kiko wants is a vacation somewhere sunny
[19:14] <kiko> or really good excuses :)
[19:14] <Rinchen> [LINK] https://bugs.edge.launchpad.net/launchpad/+bug/214843
[19:14] <Rinchen> barry, how is the refactoring going?
[19:14] <MootBot> LINK received:  https://bugs.edge.launchpad.net/launchpad/+bug/214843
[19:14] <ubotu> Launchpad bug 214843 in launchpad "Cycles in team data kill mailing lists" [Critical,Confirmed]
[19:14] <kiko> it's always sunny where /I/ live
[19:14] <flacoste> SteveA: he just needs a vacation then I guess, i heard it was very sunny where he lives
[19:15] <matsubara> Rinchen: barry just gave a update about that one in the oops section :-)
[19:15] <SteveA> flacoste: the memory problems have only happened when kiko's not been on vacation.  so obviously that is the solution.
[19:15] <kiko> can I not be the subject of the conversation, and instead the problem we're trying to solve?
[19:15] <barry> Rinchen: the refactoring has not been done and probably isn't critical
[19:15] <barry> Rinchen: it can be done this cycle as normal
[19:15] <kiko> flacoste, can you go on describing where we are?
[19:15] <Rinchen> barry, great...that means we can demote the bug to HIGH.  Would you mind doing the honours?
[19:16] <flacoste> kiko: i'll analyse the current data we collect and see if there is anything interesting
[19:16] <barry> Rinchen: done
[19:16] <Rinchen> barry, thank you sir
[19:16] <kiko> flacoste, okay. is there a way we could monitor across multiple threads?
[19:16] <flacoste> kiko: no
[19:17] <kiko> bummer
[19:17] <SteveA> well
[19:17] <SteveA> there are ways.  it's a lot more complicated.
[19:17] <kiko> yeah, I had that feeling
[19:17] <flacoste> kiko: we could bump up the number of requests it receives
[19:17] <kiko> that's a great idea! can we do that mthaddon?
[19:17] <SteveA> so we should only go there once we've established we can't get decent data the way we're doing it
[19:17] <kiko> right
[19:17] <SteveA> first, let's have flacoste analyze the data we have
[19:18] <mthaddon> kiko, what's that, bump up the number of requests?
[19:18] <SteveA> then we'll look at increasing the number of requests it gets
[19:18] <sinzui> I blame Schoëdinger's cat
[19:18] <mthaddon> kiko, we tried that (from 1/16 -> 1/10) and had to revert since it was timing out
[19:18] <kiko> mthaddon, make it more preferred in the server rotation I guess
[19:18] <kiko> mthaddon, hah
[19:18] <kiko> mthaddon, is there a smaller increment?
[19:18]  * kiko high 5s jtv 
[19:19] <jtv> huh?
[19:19] <mthaddon> kiko, any increment you like - 1/15 for instance... :)
[19:19] <kiko> mthaddon, yeah, we could do a smaller step to see. okay, let flacoste make that call once he's looked at the data.
[19:19] <mthaddon> kiko, sounds good
[19:19] <SteveA> from looking at the data, we may see that we want to look more closely at *particular* kinds of request
[19:20] <SteveA> so, I'm not so interested in adding shavings to the number of requests it processes
[19:20] <SteveA> but rather directing requests that matter to it
[19:20] <SteveA> we'll know soon
[19:20] <Rinchen> ok, thanks for the lively discussion....
[19:20] <Rinchen> I'm going to move on
[19:20] <Rinchen> [TOPIC] Bug tags
[19:20] <MootBot> New Topic:  Bug tags
[19:20] <Rinchen> none to be considered
[19:21] <Rinchen> [TOPIC] Operations report (mthaddon/herb)
[19:21] <MootBot> New Topic:  Operations report (mthaddon/herb)
[19:21] <herb> 2008-04-07 - Cherry pick 6013 to lpnet*
[19:21] <herb> 2008-04-09 - Cherry picks 6006, 6026, 6031 to forster, lpnet*, xmlrpc-internal, mailman
[19:21] <herb> Memory utilization issues continue, which has forced us to restart multiple lpnet instances daily.
[19:21] <herb> ... But we have a debug release in place on edge3 and lpnet6. As discussed above, it doesn't seem we're getting any real feedback because the debug instances are throttled due to running them with 1 thread. They don't seem to be getting enough traffic to create the memory leak.
[19:21] <herb> That's it from Tom and I unless there are any questions.
[19:21] <Rinchen> This is a good time to talk about cprov's item
[19:22] <cprov> yup
[19:22] <Rinchen> update-cache
[19:22] <mthaddon> what's to talk about?
[19:22] <mthaddon> sounds like looptuner (sp?) is the way to go, right?
[19:22] <cprov> mthaddon: exactly, we have to find a way to reduce the commit-rate
[19:23] <jtv> mthaddon: spelled right
[19:23] <Rinchen> cprov, so it sounds like the email threads have been updated and we can skip this topic.
[19:23] <Rinchen> ..yes?
[19:23] <mthaddon> ype
[19:23] <mthaddon> yep, even
[19:23] <kiko> I just replied to cprov and we should indeed use looptuner
[19:23] <cprov> Rinchen: yes, all sorted
[19:24] <kiko> it's easy to do
[19:24] <kiko> gmb, can you help him out?
[19:24] <Rinchen> great thanks gents
[19:24] <gmb> kiko: Will do.
[19:24] <Rinchen> [TOPIC] DBA report (stub)
[19:24] <MootBot> New Topic:  DBA report (stub)
[19:24] <kiko> i know you made that change for update-bugtargetnames
[19:24] <kiko> thanks so much
[19:24] <Rinchen> no stub
[19:24] <SteveA> on vacation
[19:24] <SteveA> or leave
[19:24] <SteveA> or whatever
[19:24] <Rinchen> ok, we'll skip the report this week.
[19:24] <SteveA> anyway, not at work today
[19:24] <Rinchen> [TOPIC] Sysadmin requests (Rinchen)
[19:24] <MootBot> New Topic:  Sysadmin requests (Rinchen)
[19:25] <Rinchen> Hi! Is anyone blocked on an RT or have any that are becoming urgent?
[19:25] <Rinchen> that I don't already know about
[19:25] <Rinchen> IS is still congested due to Hardy
[19:26] <Rinchen> ok, if you do have something, ping me later or email me please. Thanks
[19:26] <Rinchen> [TOPIC] New packages required (salgado)
[19:26] <MootBot> New Topic:  New packages required (salgado)
[19:26]  * bigjools waves at Rinchen
[19:26] <salgado> if any of the branches you're working on right now depends on any library which is not part of the launchpad-dependencies package, come talk to me ASAP.
[19:26]  * kiko looks around
[19:26] <kiko> salgado, do you know if we still require lxml?
[19:26]  * Rinchen acks bigjools and the ppa issue
[19:26] <salgado> fyi, I recently made the package depend or pgsql 8.2 or 8.3, so you don't need to keep both versions around anymore
[19:26] <salgado> kiko, I don't
[19:27] <kiko> I'm asking because I know that abel isn't using it to validate hwtest schema anylonger
[19:27] <kiko> (is that right flacoste?)
[19:27] <adeuring> salgado, kiko: I think I was the only one who used it
[19:27] <jtv> kiko: we still require xmlproc.
[19:27] <Rinchen> right and there's a bug open for this cycle to remove that dependency
[19:27] <flacoste> kiko: i want to use it for other stuff
[19:27] <Rinchen> it's the only other hardy item on my list
[19:27] <flacoste> kiko: like pagetests helpers and other general XML usage
[19:28] <bigjools> what;'s going on with python-xml in hardy now?
[19:28] <Rinchen> he newest python-xml package in hardy (uploaded April 1st) has made it impossible to run/test Launchpad because it moved its installed files to a place where we can't easily import from.
[19:28] <kiko> flacoste, yep, that's what I was trying to remember
[19:29] <Rinchen> translations has a dependency on xmlproc which, when removed, should allow LP to run/test fine on dev machines
[19:29] <Rinchen> anything further for salgado?
[19:29] <kiko> will it be removed, though?
[19:29] <Rinchen> translations has a bug open to remove the dep
[19:30] <Rinchen> the package itself will remain in hardy
[19:30] <jtv> kiko: we definitely plan to
[19:30] <Rinchen> ok, onward! (to make up for the last few meetings which overran)
[19:30] <kiko> jtv, milestone eta?
[19:30] <Rinchen> [TOPIC] A top user-affecting issue (mrevell)
[19:30] <MootBot> New Topic:  A top user-affecting issue (mrevell)
[19:30] <Rinchen> kiko, this cycle
[19:31] <mrevell> Hi. I don't have one outstanding user-affecting issue this week. However, there are a couple of issues I've seen that I think are of interest.
[19:31] <mrevell> 1. We've had a request from beeseek to import mbox files from their existing mailing lists into their Launchpad-hosted mailing lists. Barry, is this something we can/will do?
[19:31] <kiko> cool cool
[19:31] <barry> mrevell: yes.  matsubara is this the same request we're working on?
[19:31] <Rinchen> kiko, https://bugs.edge.launchpad.net/rosetta/+bug/213406
[19:31] <matsubara> barry: yes
[19:31] <barry> mrevell: ^^
[19:32] <mrevell> barry: Ah, thanks. Would you be happy to do this generally? If so, I'll update ListHelp.
[19:32]  * beuno has been holding back from using LP mailing lists due to not being able to migrate archive/subscribers from lists.ubuntu
[19:32] <matsubara> mrevell: I talked to barry about that already. we're going to do that after the meeting with mthaddon help :-)
[19:32] <mrevell> matsubara: Ah, okay :) Thanks!
[19:32] <mrevell> 2. Bug 213430 requests that "request feedback" in Blueprint should trigger an email notification.
[19:32] <ubotu> Launchpad bug 213430 in blueprint ""Request feedback" should send an e-mail to the person who is asked" [Undecided,New] https://launchpad.net/bugs/213430
[19:32] <barry> beuno: migrating subscribers isn't planned, but we can do mboxes
[19:32] <mrevell> Just thought I'd highlight that request.
[19:33] <beuno> barry, can you plan it?  :)
[19:33] <mrevell> Rinchen: Do you want to talk about bug 213406?
[19:33] <barry> beuno: let's chat after this meeting
[19:33] <mthaddon> I'd also like to mention https://answers.launchpad.net/launchpad/+question/29265 as well - registering PLD Linux as a distro
[19:33] <ubotu> Bug 213406 on http://launchpad.net/bugs/213406 is private
[19:33] <kiko> yep
[19:33] <beuno> barry, sure, thanks  :)
[19:33] <kiko> I'll do that today, mthaddon
[19:33] <Rinchen> mrevell, no, that's ok. Thanks :-)
[19:33] <mthaddon> kiko, cool, thx
[19:33] <intellectronica> mrevell: i'm aware of this, but i doubt that we'll have time to look at it for some time
[19:33] <mrevell> Rinchen: Thanks for pointing me at it.
[19:34] <mrevell> intellectronica: Thanks. It'd be cool when it arrives.
[19:34] <intellectronica> mrevell: just like many other blueprint feature requests
[19:34] <Rinchen> I'm hoping to have more time applied to Blueprint love after our currently schedule work completes.  *fingers crossed*
[19:34] <mrevell> That's it from me, thanks Rinchen.
[19:34] <Rinchen> Thank mrevell
[19:34] <Rinchen> [TOPIC] Doc Team report (mrevell)
[19:34] <MootBot> New Topic:  Doc Team report (mrevell)
[19:34] <mrevell> Ah, me again
[19:34] <mrevell> This week mpt and I met with the designers who are working on our new Launchpad tour. We spent most of the day with them, explaining the concepts behind LP and the ten primary features we want to communicate in the tour.
[19:34] <kiko> mrevell, what do you think of them?
[19:35] <mrevell> kiko: I was impressed with how quickly they "got" the concepts behind LP.
[19:35] <kiko> that's cool
[19:35] <mrevell> kiko: They had good input into how we could represent them visually, too.
[19:35] <mrevell> I'll post a report on the meeting to the list.
[19:35] <mrevell> Please, if you're a team lead, could I have a fifteen minute call with you tomorrow or early next week to go over the parts of the tour relevant to your part of LP?
[19:35] <mrevell> Ping me with some good times :)
[19:36] <Rinchen> mrevell, and grab someone from soyuz too please :-)
[19:36] <mrevell> I'll be posting a new draft of the tour content to the team list either tomorrow or Monday. The tour designers are going to give us some mock-ups next week, which I'll post to the list.
[19:36] <mrevell> Rinchen: Will do :)
[19:36]  * Rinchen loves mock-ups.
[19:36] <mrevell> Thanks, back to you Rinchen.
[19:36] <Rinchen> Thanks mrevell
[19:36] <Rinchen> wow, we're really zooming today
[19:36] <Rinchen> [TOPIC] Blockers
[19:36] <MootBot> New Topic:  Blockers
[19:36] <thumper> Code: not blocked
[19:37] <flacoste> Foundations: not blocked
[19:37] <flacoste> actually
[19:37] <mpt> I'm not blocked, but bug 214690 will make me much slower fixing anything that involves CSS
[19:37] <ubotu> Bug 214690 on http://launchpad.net/bugs/214690 is private
[19:37] <kiko> what's that bug about?
[19:37] <jtv> Translations: not blocked
[19:37] <BjornT> Bugs: not blocked
[19:37] <bigjools> Soyuz: just the usual
[19:37] <mpt> kiko, launchpad.dev using style-slimmer.css instead of style.css
[19:37] <mpt> kiko, so I think it's about launchpad.dev's config
[19:37] <Rinchen> Releases Team: Not blocked.
[19:38] <flacoste> i see nothing in the config related to that
[19:38] <flacoste> i thought that was an apache-side issue
[19:38] <SteveA> I think I kniw how that works
[19:38] <kiko> mpt, I think nobody else is aware of that problem
[19:38] <statik> lpcomm: no blocked
[19:38] <SteveA> I'll look into it shotyly
[19:38] <Rinchen> thanks SteveA
[19:38] <mpt> kiko, I discovered it only yesterday
[19:38] <mpt> thanks SteveA
[19:38] <sinzui> Does slimmer rely on devmode == False
[19:39] <flacoste> i thnk sinzui got an hypothesis here
[19:39] <schwuk> hwdb: not blocked
[19:40] <sinzui> I have not messed with that until today, and it absolutely still works in the branch that removes launchpad ZConfig.
[19:40] <BjornT> mpt: can't you run scripts/make-static.css as a workaround? if it works, it's at least better than restaring the web app
[19:40] <BjornT> s/css/py
[19:41] <mpt> I don't know -- I'll try it
[19:41] <Rinchen> Ok, I'm going to wrap up now
[19:41] <mpt> thanks for the hint
[19:41] <Rinchen> feel free to chat about this on -code :-)
[19:41] <Rinchen> Thank you all for attending this week's Launchpad Developer Meeting. See the channel topic for the location of the logs.
[19:41] <jtv> Thank you!
[19:42] <Rinchen> #endmeeting
[19:42] <MootBot> Meeting finished at 20:42.
[19:42] <thumper> \o/
[19:42] <mrevell> thanks Rinchen
[19:42] <Rinchen> yo
[19:42] <jtv> Early even.
[19:42] <Rinchen> vrooooom
[19:42] <mrevell> thanks everybody
[19:42] <Rinchen> ;-)
[19:42] <statik> thanks rinchen
[19:42] <cprov> great !
[19:42] <intellectronica> cheers Rinchen
[19:42] <gmb> Cheers Rinchen.
[19:42] <abentley> Thanks Rinchen
[19:42]  * gmb -> evening things
[19:42] <cprov> thanks everybody
[19:42] <Rinchen> thumper <-> rockstar_,  rockstar_ <-> thumper
[19:42] <al-maisan> thanks!
[19:42] <thumper> Rinchen: we know
[19:42] <Rinchen> :-)
[19:42] <rockstar_> Rinchen, yea, we've met!  :)
[19:42] <kiko> moonies
[19:43] <Rinchen> where's my bandana ?
[19:43] <thumper> Rinchen: bandana?
[19:43]  * gmb misread that as the Pascal version of thumper != rockstar
[19:43] <thumper> gmb: and that'd be right
[19:43] <bigjools> Rinchen's symbols look like an Imperial Tie Fighter

[19:43] <thumper> |-o-|
[19:44] <bigjools> !
[19:44] <bigjools> +1
[19:44] <bigjools> perfect :)
[19:44] <rockstar_> thumper, the first is an interceptor
[19:44] <Rinchen> well, I was using the vader model
[19:44] <bigjools> lol
[19:44] <rockstar_> Only Vader flew one of those until RotJ
[19:44] <Rinchen> tie interceptor maybe
[19:44] <rockstar_> Yup
[19:44]  * Rinchen has trouble remembering imperial ship names
[19:45] <rockstar_> |-oo-|  <-- TIE Bomber
[19:45] <bigjools> I'm not nearly geeky enough to remember
[19:45]  * rockstar_ played too much Rogue Squadron
[19:45] <thumper> me neither
[19:45]  * thumper hasn't played a game in ages
[19:45] <rockstar_> Those movies are all older than me.
[19:45] <bigjools> not me :(
[19:45] <rockstar_> thumper, your kids don't game?
[19:46] <thumper> rockstar_: oldest is 7
[19:46] <bigjools> Wii bowling is my limit these days
[19:46] <thumper> so they play Clifford games, and my little pony
[19:46] <thumper> not something that I get involved with
[19:46] <rockstar_> thumper, I was 4 when I started playing.  Got into computers/electronics because my dad would unhook the stuff from the TV, so I taught myself to hook it back up.
[19:46] <bigjools> come now thumper don't be shy
[19:47] <thumper> I'd be happy to get a games console later
[19:47] <thumper> I remember with fondness the an old playstation game that I can't remember the title to
[19:48] <thumper> a problem solving one where you were some skeleton
[19:48] <bigjools> Realistic Breast Physics III ?
[19:48] <rockstar_> thumper, our LUG here gets together for Warhawk pretty often (everyday lately...)
[19:48] <thumper> lol
[19:48]  * thumper has never heard of warhawk
[19:48] <rockstar_> New PS3 game.
[19:50]  * thumper wonders if we should really have a #launchpad-offtopic channel
[19:50] <rockstar_> :)
[20:05] <matsubara> COD4 ftw