[16:50] <Fujisan> its my party and i parallel park if i want to with Hobbsee D:
[16:51] <Hobbsee> gah.
[16:51]  * Hobbsee goes to hunt for some staff
[16:51] <kiko-afk> Hobbsee, the queue page working for you?
[16:51] <Hobbsee> kiko-afk: sec, going and hunting for stafff.
[16:52] <Fujisan> i will tell you everyday for the rest of my life what Hobbsee did to me
[16:52] <Fujisan> i will make sure you will be reported Hobbsee
[16:52] <Fujisan> let them review this
[16:52] <Fujisan> what you did to me
[16:52] <Hobbsee> i knew i liked having ops here.
[16:53] <kiko-afk> what's parallel parking?
[16:54] <Hobbsee> he's whinging because he got banned for trolling
[16:54] <kiko-afk> I wish I could ban trolls on launchpad
[16:55] <Hobbsee> i wish i could get freenode to do what htey say they will, too.
[17:01] <Hobbsee> man, i hate being a woman in tech sometimes.
[17:03] <kiko-afk> Hobbsee, there's a long series of articles on CACM about this recently
[17:03] <Hobbsee> kiko-afk: oh?
[17:03] <kiko-afk> yeah, are you a subscriber?
[17:04] <Hobbsee> nope - no idea what it is
[17:05] <kiko-afk> the communications of the acm?
[17:21] <Hobbsee> kiko: i haven't, no.
[17:22] <Hobbsee> kiko: and i can't test the queue stuff now, we've released.
[17:22] <Hobbsee> presumably i'll be able to test toolchain-ey bits, if someone leaves it for me
[17:22] <kiko> Hobbsee, well, you will be able to soon, anyway. :)
[17:22] <Hobbsee> kiko: neat :)
[17:22] <Hobbsee> kiko: why?
[17:22] <kiko> because II will open, I'm hoping? :)
[17:24] <Hobbsee> oh right
[17:24] <Hobbsee> sure, and hopefully i won't have gone mad by then.
[17:27] <Hobbsee> kiko: anywya, where would i find the cacm?
[17:27] <Hobbsee> oh, my bad.
[17:28] <kiko> Hobbsee, check out acm.org
[17:28] <Hobbsee> kiko: yeah, found that much, sorry
[17:28] <kiko> Hobbsee, didn't you do compsci?
[17:29] <Hobbsee> kiko: i'm doing computing, yes.  not compsci as such.
[18:57]  * Rinchen checks for mootbot
[18:58]  * Rinchen gets a drink
[18:59] <kiko> AND ACTION!
[18:59] <kiko> me
[18:59] <sinzui> my
[18:59] <statik> me
[19:00] <Rinchen> \#startmeeting
[19:00] <Rinchen> #startmeeting
[19:00] <MootBot> Meeting started at 20:00. The chair is Rinchen.
[19:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[19:00] <Rinchen> Welcome to this week's Launchpad development meeting. For the next 45 minutes or so, we'll be coordinating Launchpad development.
[19:00] <leonardr> me
[19:00] <Rinchen> [TOPIC] Roll Call
[19:00] <MootBot> New Topic:  Roll Call
[19:00] <sinzui> me
[19:00] <mrevell> me
[19:00] <gmb> e
[19:00] <rockstar_> me
[19:00] <bac> me
[19:00] <Rinchen> moo
[19:00] <abentley> me
[19:00] <intellectronica> me
[19:00] <sinzui> me
[19:00] <gmb> me
[19:00] <leonardr> me
[19:00] <statik> m e
[19:00] <barry> me
[19:00] <kiko> moink
[19:00] <mpt> me
[19:00] <matsubara> me
[19:00] <EdwinGrubb> me
[19:00] <stub> me
[19:00] <salgado> me
[19:00] <BjornT> me
[19:00] <al-maisan> me
[19:00] <allenap> me
[19:00] <flacoste> me
[19:01] <Rinchen> releases team is here... others?
[19:01] <Rinchen> thumper?
[19:01] <adeuring> me
[19:01] <herb> me
[19:01] <danilos> me
[19:01] <rockstar_> I believe thumper has a holiday today
[19:01] <Rinchen> mthaddon ?
[19:01] <mars> me
[19:01] <Rinchen> ah right
[19:01] <danilos> jtv?
[19:01] <Rinchen> so it is
[19:01] <mthaddon> me
[19:01] <bigjools> me
[19:01] <jtv> me
[19:01] <rockstar_> So I think the remainder of bzrlp (all two of us) are here
[19:01] <Rinchen> barry?
[19:02] <schwuk_> me
[19:02] <Rinchen> oh sorry
[19:02]  * barry already me'd
[19:02] <SteveA> me
[19:02] <Rinchen> ok then
[19:02] <carlos> me
[19:02] <Rinchen> [TOPIC] Agenda
[19:02] <MootBot> New Topic:  Agenda
[19:02] <Rinchen>  * Next meeting
[19:02] <Rinchen>  * Actions from last meeting
[19:02] <Rinchen>  * Oops report (Matsubara)
[19:02] <Rinchen>  * Critical Bugs (Rinchen)
[19:02] <Rinchen>  * Bug tags
[19:02] <Rinchen>  * Operations report (mthaddon/herb)
[19:02] <Rinchen>  * DBA report (stub)
[19:02] <Rinchen>  * Sysadmin requests (Rinchen)
[19:02] <Rinchen>  * New packages required (salgado)
[19:02] <Rinchen>  * A top user-affecting issue (mrevell)
[19:02] <Rinchen>  * Doc Team report (mrevell)
[19:02] <Rinchen>  * Community procedure for unplanned downtime (mpt)
[19:02] <cpro1> me
[19:02] <Rinchen> * some interesting topic (kiko)
[19:03]  * kiko chuckles
[19:03] <Rinchen> [TOPIC]  * Next meeting
[19:03] <MootBot> New Topic:   * Next meeting
[19:03] <Rinchen> same time, same place, next week
[19:03] <kiko> yeah, let's have a next meeting.
[19:03] <Rinchen> any obstacles present with that? :-)
[19:03] <matsubara> next thursday is a brazilian national holiday, btw
[19:04] <kiko> those are the best meeting days!!
[19:04] <BjornT> there's a public holiday next thursday for me
[19:04] <matsubara> but I think I'll be around. thinking about swapping it
[19:04] <Rinchen> ok then..
[19:04] <cpro1> I won't be here too.
[19:04] <al-maisan> same here ..
[19:05] <al-maisan> it's May 1st .. a public holiday in germany
[19:05] <Rinchen> [AGREED] meeting next week, same time, station - apologies: brazil, BjornT, al-maisan
[19:05] <MootBot> AGREED received:  meeting next week, same time, station - apologies: brazil, BjornT, al-maisan
[19:05] <carlos> I will not be here either. This is my last meeting as a Launchpad member
[19:05] <statik> carlos: we will miss you!
[19:05] <adeuring> it's a holiyday for me too (thanks al-mainsan :)
[19:05] <cpro1> Rinchen: I'm not in br ;)
[19:06] <flacoste> actually, i think May 1st is a national holiday everywhere except for Canada, US (UK?)
[19:06] <barry> carlos: !
[19:06] <jtv> statik: "next time, don't miss"
[19:06]  * mpt hugs carlos 
[19:06]  * carlos will miss working with you too...
[19:06]  * Rinchen sniffles.
[19:06] <kiko> cpro1, it doesn't matter -- you follow brazilian holidays unless you explicitly request to change
[19:06] <gmb> May 1st is not a UK holiday.
[19:06] <Rinchen> carlos, you'll have to joins us for the meeting
[19:06] <mrevell> flacoste: Not for UK We have it 5th May
[19:06]  * barry will take a holiday if flacoste will
[19:06] <Rinchen> [AGREED] germany off too
[19:06] <MootBot> AGREED received:  germany off too
[19:06] <intellectronica> gmb: i think the uk moves it to the next monday
[19:06] <Rinchen> [TOPIC]  Actions from last meeting
[19:06] <MootBot> New Topic:   Actions from last meeting
[19:06] <gmb> intellectronica: Yep.
[19:06] <Rinchen> all of my actions from last week were completed.
[19:06] <Rinchen> [TOPIC] Oops report (Matsubara)
[19:06] <MootBot> New Topic:  Oops report (Matsubara)
[19:06] <carlos> Rinchen: I will try to ;-) but will miss the funny 'me' part :-)
[19:07] <Rinchen> carlos, you can still "me" :-)
[19:07] <matsubara> Today's oops report is about bugs 220251, 221072, 221047
[19:07] <cprov> kiko: I've changed my address, it should be enough to follow local holidays, isn't it obvious ?
[19:07] <carlos> Rinchen: thanks :-P
[19:07] <ubotu> Launchpad bug 220251 in malone "Calculating subscribers for bugs with multiple tasks is expensive" [High,Fix committed] https://launchpad.net/bugs/220251
[19:07] <ubotu> Bug 221072 on http://launchpad.net/bugs/221072 is private
[19:07] <matsubara> salgado, should #220251 importance be higher? is it not causing inconvenience for marilize?
[19:07] <kiko> cprov, nope
[19:07] <matsubara> The project group milestone is broken on edge. abel already fixed and the branch is on the pqm queue. (#221047)
[19:07] <salgado> matsubara, the actual bug fix won't help marilize
[19:07] <mpt> Rinchen, next you'll be saying he can still fix bugs ;-)
[19:07] <matsubara> Thanks BjornT and kiko for fixing the timeouts on the bug page (#220251)
[19:07] <salgado> matsubara, what we need to do is run a couple DELETES in production
[19:08] <kiko> cprov, you need to explicitly say you want to change to observe other holidays
[19:08] <intellectronica> matsubara: a fix for 220251 has landed (and another fix to that too)
[19:08] <Rinchen> mpt, I'm glad you caught  that ;-)
[19:08] <SteveA> cprov: watch out for queens day next week.  depending how centrally you live, it may be impossible to work.
[19:08] <SteveA> cprov: it's basically like carnival.
[19:08] <cprov> kiko: it's not time to discuss it.
[19:08] <matsubara> intellectronica: right, this is more like a thank you notice :-)
[19:08] <cprov> SteveA: yes, I was warned :)
[19:09] <matsubara> salgado: is that the db query in the LPProductionStatus page?
[19:09] <cprov> SteveA: to not go to Amsterdam, basically.
[19:09] <salgado> matsubara, it is
[19:09] <matsubara> salgado: ok, thanks then.
[19:09] <matsubara> Rinchen: I'm done here.
[19:09] <Rinchen> thanks matsubara
[19:09] <matsubara> thanks everyone
[19:09] <Rinchen> [TOPIC] Critical Bugs (Rinchen)
[19:09] <MootBot> New Topic:  Critical Bugs (Rinchen)
[19:10] <Rinchen> same two
[19:10] <Rinchen> [LINK] https://bugs.edge.launchpad.net/launchpad/+bug/206654
[19:10] <Rinchen> This is the memory issue. flacoste, SteveA.  Any updated status?
[19:10] <MootBot> LINK received:  https://bugs.edge.launchpad.net/launchpad/+bug/206654
[19:10] <flacoste> Rinchen: yes
[19:10] <Rinchen> the other is for thumper and mhw who are not here
[19:10] <Rinchen> [LINK] https://bugs.edge.launchpad.net/launchpad-bazaar/+bug/118625
[19:10] <MootBot> LINK received:  https://bugs.edge.launchpad.net/launchpad-bazaar/+bug/118625
[19:10] <flacoste> the issue is with +bugs-text
[19:10] <ubotu> Launchpad bug 118625 in launchpad-bazaar "codebrowse sometimes hangs" [Critical,Confirmed]
[19:10] <Rinchen> so I'll skp that
[19:10] <flacoste> and I'm working on a work-around
[19:10] <flacoste> ultimately, this view should be rewritten to not use SQLObject
[19:11] <flacoste> but raw SQL
[19:11] <SteveA> let's not mention particular URLs here :-)
[19:11] <flacoste> or this funcitonality moved to API where everything will be batched
[19:11] <flacoste> that's it
[19:12] <SteveA> Rinchen: the result, operationally, is that from tomorrow or so, we should be back to having reliably stable app servers
[19:12] <Rinchen> flacoste, great thanks. Looking forward to seeing the results.
[19:12] <Rinchen> fantastic, thanks.
[19:12] <Rinchen> [TOPIC] Bug tags
[19:12] <MootBot> New Topic:  Bug tags
[19:12] <Rinchen> there are no proposed bug tags
[19:12] <Rinchen> [TOPIC] Operations report (mthaddon/herb)
[19:12] <MootBot> New Topic:  Operations report (mthaddon/herb)
[19:12] <herb> Cherry picks since last meeting: 2008-04-18: r6113 & r6110, 2008-04-21: loggerhead r156, launchpad-loggerhead r29 and r6141
[19:12] <herb> Currently two cherry picks pending. Barring any objections we'll hold off until tomorrow at the earliest for them due to hardy.
[19:12] <herb> Bug #206654 continues to be an issue, though it appears that flacoste has had a breakthrough.
[19:12] <herb> That's it from me and Tom unless there are any questions.
[19:12] <ubotu> Bug 206654 on http://launchpad.net/bugs/206654 is private
[19:13] <Rinchen> thanks herb
[19:13] <Rinchen> [TOPIC] DBA report (stub)
[19:13] <MootBot> New Topic:  DBA report (stub)
[19:13] <stub> I think all the DB reviews are done finally for this cycle. If you are not sure of the status of your patch, email me. I need to talk with bigjools re: archive permissions because I can't understand his email...
[19:13] <stub> The DB server seems to be coping quite happily with the current load. This is good. This should also be the highest load we see for quite some time as we work on ways of distributing the load (unless someone manages to remove bottlenecks in the other systems ;) )
[19:13] <stub> Done.
[19:13] <salgado> herb, there are actually 3 cherry picks pending, no?
[19:14] <bigjools> stub: talk to me after this meeting
[19:14] <herb> salgado, well the 3rd hasn't been approved
[19:14] <herb> salgado, sorry, I should have clarified.
[19:14] <salgado> herb, right, good point.  can you approve it kiko?
[19:14] <Rinchen> thanks stub
[19:14] <Rinchen> any questions for stub before I move on?
[19:15] <kiko> salgado, yeah, mats just asked me
[19:15] <kiko> salgado, I thought I had approved it. maybe my wiki edit conflicted and I didn't see that happen. it's approved.
[19:15] <salgado> kiko, he asked for approval for the pending SQL.  there's a cherry pick there as well
[19:15] <Rinchen> [TOPIC] Sysadmin requests (Rinchen)
[19:15] <MootBot> New Topic:  Sysadmin requests (Rinchen)
[19:15] <Rinchen> Hi! Is anyone blocked on an RT or have any that are becoming urgent? I'm aware of the usual ones.
[19:16] <kiko> salgado, that I hadn't seen
[19:16]  * Rinchen waves at bigjools.
[19:16]  * bigjools waves back
[19:16] <kiko> BjornT, question for you: does mthaddon know that we did a CB yesterday?
[19:16] <mthaddon> I do, yes
[19:17] <Rinchen> [TOPIC] New packages required (salgado)
[19:17] <MootBot> New Topic:  New packages required (salgado)
[19:17] <herb> kiko, BjornT I sent an email to losas yesterday after the CB
[19:17] <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:17] <Rinchen> jtv, hows that xmlproc code change coming?
[19:17] <jtv> Rinchen: I was just trying to squeeze it into PQM, thanks
[19:17]  * Rinchen wants to know when he can unpin that package
[19:17] <kiko> herb, one concern I have is that BjornT hasn't landed the fix on RF yet?
[19:17] <Rinchen> jtv, awesome, thanks.
[19:18] <BjornT> kiko: i haven't?
[19:18] <mthaddon> kiko, I think it's in process, or landing...
[19:18] <kiko> BjornT, okay, need to refresh that mailbox then :)
[19:18] <BjornT> kiko: r6151
[19:18] <Rinchen> [TOPIC] A top user-affecting issue (mrevell)
[19:18] <MootBot> New Topic:  A top user-affecting issue (mrevell)
[19:18] <mrevell> hi
[19:18] <mrevell>  Happy Hardy release day!
[19:18] <mrevell> The user-affecting issue I'd like to highlight today is that impact that interest in the new Ubuntu release appears to have had on sites that rely on Launchpad for authentication.
[19:18] <mrevell>  I know this happens only twice a year but I'd like to acknowledge the slow-down in a post to lp-users and explain its cause. Is there some good news I can offer in that message?
[19:19] <BjornT> kiko: i had to resubmit it, since the first one failed due to a spurious test failure...
[19:19] <kiko> BjornT, known spurious test failure? :)
[19:19] <SteveA> mrevell: the cause is some old software written when launchpad and ubuntu had far fewer users
[19:19] <SteveA> mrevell: the good news is that we're replacing it with new software that works much better
[19:20] <mrevell> thanks SteveA :)
[19:20] <SteveA> so this will be the last such slow-down
[19:20] <mrevell> great to hear, thanks for that.
[19:20] <mrevell> Thanks Rinchen
[19:20] <Rinchen> [TOPIC] Doc Team report (mrevell)
[19:20] <MootBot> New Topic:  Doc Team report (mrevell)
[19:20] <mrevell> This week please give me your feedback on the proposed tour layouts. I've posted new drafts to the list today.
[19:21] <mrevell> I know not everyone is directly interested in this sort of thing but I'm interested in everyone's view.
[19:21] <Rinchen> mrevell, has the community members of the doc team been active lately?
[19:21] <Rinchen> s/has/have
[19:22] <mrevell> Rinchen: We haven't had much interest lately and I need to restoke interest after our 1.2.4 release (i.e. when I'm clear to do that)
[19:22] <mrevell> s/clear/more free
[19:22] <Rinchen> ok, thanks
[19:22] <mrevell> I'd also be grateful if you could give a few moments thought on the podcast idea.
[19:22] <mrevell> thanks Rinchen
[19:22] <Rinchen> [TOPIC] Community procedure for unplanned downtime (mpt)
[19:22] <MootBot> New Topic:  Community procedure for unplanned downtime (mpt)
[19:22] <mpt> hi
[19:22] <kiko> mrevell, I really like the new tour layouts, btw
[19:22] <mpt> Last Sunday, Launchpad had major availability problems for an extended period
[19:23] <mrevell> kiko: That's great to hear. If you have any specific feedback I'll give it to Gavin in my call with him tomorrow
[19:23] <mpt> There were non-Canonical people in #launchpad who noticed, but they didn't know what to do.
[19:23] <mpt> I started a mailing list thread about this on Sunday, but it hasn't come to any conclusion
[19:23] <kiko> mrevell, I'll try getting email before I trvel
[19:23] <mrevell> thanks kiko
[19:23] <mpt> So we still need to decide:
[19:24] <mpt> * Is it necessary for us to publish some way of getting in touch with admins when Launchpad is down?
[19:24] <mpt> - If so, what should that be?
[19:24] <mpt> - And if not, how will we prevent such downtime happening in future?
[19:24] <stub> Is there anyone in Montreal accessible by our users?
[19:24] <kiko> mpt, when we were down, what happened when loading the site?
[19:24] <mrevell> mpt: Presumably help.lp.net was down as well?
[19:24] <gmb> kiko: HTTP Timeouts
[19:24] <SteveA> kiko: basically, the site was totally unresponsive
[19:24] <SteveA> not even a 503 page
[19:25] <kiko> zaz a bummer
[19:25] <SteveA> or 50x page
[19:25] <SteveA> yeah
[19:25] <mpt> kiko, as I understand it, pages were *occasionally* available, but extremely slowly if at all.
[19:25] <kiko> put something on the #launchpad topic
[19:25] <SteveA> it was caused by the problem we just fixed
[19:25] <kiko> or on help.launchpad.net
[19:25] <kiko> ken
[19:25] <SteveA> or are about to fix
[19:25] <mpt> kiko, who are you suggesting do this?
[19:25] <SteveA> however, I don't think we need to set up anything special about this
[19:25] <mrevell> Is there anything fancy we can do DNS-wise that would redirect people to an off-site holding page in the case of this sort of outage?
[19:25] <SteveA> mrevell: no
[19:26] <kiko> mpt, well, that's my questions for you
[19:26] <SteveA> the issue is this
[19:26] <kiko> I'm not suggesting much
[19:26] <SteveA> we have monitoring systems
[19:26] <kiko> think it's a bit of a non-issue
[19:26] <kiko> tbh
[19:26] <SteveA> and they tell us when launchpad is not functioning
[19:26] <mpt> kiko, people in #launchpad did change the /topic, but that's all they *could* do.
[19:26] <SteveA> on Sunday, no one was available to respond to the monitoring systems
[19:26] <kiko> mpt, I mean put in the /topic "call 1800LAUNCHPAD" etc
[19:26] <SteveA> the solution is that we have people available to respond to the monitoring systems
[19:27] <SteveA> and I'm talking to the information systems people in Canonical about that.
[19:27] <SteveA> the monitoring systems detected the outage at the same time that people on the channel did.
[19:28] <Rinchen> As a normal user, if the service went down, I'd like the warm fuzzies to know someone was looking at it.  I believe we should have weekend response to monitoring alerts.
[19:28] <Rinchen> I would also be very thankful if someone posted a time when they think the problem might be fixed
[19:28] <Rinchen> (as a normal user)
[19:28] <matsubara> Rinchen: perhaps we should add that to the DealingwithCrisis policy/doc
[19:28] <kiko> Rinchen, posted /where/?
[19:29] <SteveA> Rinchen: if the monitoring system had been responded to on Sunday, the problem would have been fixed within 5 mins.
[19:29] <Rinchen> kiko, dunno. Somewhere where I would naturally see it.
[19:29] <kiko> the issue as I see it is that the site is down and there's no fallback place to look
[19:29] <matsubara> Rinchen: I mean, we should add that the part of the procedure is to notify in public places that people are looking at the issue
[19:29] <Rinchen> kiko, right
[19:29] <kiko> Rinchen, that's the key problem, so unless we can answer that, all bets are off
[19:29] <Rinchen> kiko, that rarely happens though
[19:29] <SteveA> stop, please
[19:29] <SteveA> we're talking about a problem that was fixed within minutes of an appropriate person looking into it
[19:29] <mpt> SteveA, will you post to launchpad@ when your discussions with IS have a conclusion?
[19:30] <SteveA> the issue was the lack of appropriate people on that sunday
[19:30] <SteveA> and I'm talking with people about how we address that.
[19:30] <SteveA> enough with 1800LAUNCHPAD ;-)
[19:30] <kiko> SteveA, it was a non-proposal, in case you missed that :)
[19:30] <Rinchen> hmmm
[19:31] <Rinchen> I have more to say about this but I won't now.  Moving on...
[19:31] <mpt> We have UI for planned extended downtime. We don't have UI for unplanned extended downtime, but we may not need it.
[19:31] <Rinchen> SteveA, if you could post the results of that IS discussion please as mpt suggested
[19:31] <SteveA> sure
[19:31] <Rinchen> thanks SteveA
[19:31] <mpt> thanks SteveA
[19:31] <Rinchen> mpt, ok to move on?
[19:31] <mpt> yep
[19:31] <Rinchen> [TOPIC] kiko on vacation (Kiko)
[19:31] <MootBot> New Topic:  kiko on vacation (Kiko)
[19:32] <kiko> ah, right.
[19:32] <Rinchen> someone call guiness
[19:32] <kiko> I'm on vacation tomorrow through tuesday
[19:32] <kiko> you can call me and I might have phone coverage
[19:32] <kiko> but look to steve and joey for RCs
[19:32] <stub> 2 days!
[19:32] <mthaddon> Rinchen, to order beer, or break a record?
[19:32] <kiko> I've looked at the PQM queue
[19:32] <Rinchen> mthaddon, in this case, both :-)
[19:32] <kiko> and there doesn't seem to be much at risk there
[19:32] <kiko> does anyone have a high-risk, important or otherwise urgent landing that can't miss this rollout?
[19:32] <Rinchen> I'd like to remind folks to clear out the pending-reviews queue if you haven't already
[19:33]  * mthaddon calls guinness
[19:33] <Rinchen> besides flacoste
[19:33] <bigjools> kiko: yes, I am waiting for flacoste to land his restricted librarian stuff so I can land my P3A stuff
[19:33] <kiko> and his libby patch for julian
[19:33] <kiko> so I hear
[19:33] <kiko> P<3A
[19:34] <Rinchen> silence. that's a good thing I think
[19:34] <kiko> okay
[19:34] <Rinchen> thanks kiko
[19:34] <kiko> you didn't speak
[19:34] <kiko> so I won't make any exception for your branch!
[19:34] <kiko> :)
[19:35] <Rinchen> er right. mrevell where's what's new? :-)
[19:35]  * Rinchen laughs.
[19:35] <mrevell> Rinchen: Need to speak to you about that.
[19:35] <Rinchen> sure, let's do it right after this if you can
[19:35] <Rinchen> thanks all
[19:35] <Rinchen> Thank you all for attending this week's Launchpad Developer Meeting. See the channel topic for the location of the logs.
[19:35] <mrevell> yep, np
[19:35] <Rinchen> #endmeeting
[19:35] <MootBot> Meeting finished at 20:35.
[19:35] <barry> Rinchen: thanks!
[19:35] <SteveA> thanks Rinchen !
[19:35] <carlos> this one was fast!
[19:35] <kiko> thanks thanks
[19:35] <intellectronica> thanks Rinchen
[19:35] <jtv> We're early!
[19:35] <Rinchen> we're setting records here bub
[19:35] <carlos> thanks !
[19:36] <Rinchen> more meat, less fat
[19:36] <bigjools> call Guinness again