[18:59] <kiko> harken all
[19:00] <Rinchen> well, let's see if mootbot has recovered
[19:00] <Rinchen> I think it hasn't
[19:00] <gmb> 10:1 against.
[19:00] <Rinchen> #startmeeting
[19:00] <Rinchen> right then, I know seeker's been working on it
[19:00]  * gmb wins
[19:00] <matsubara> me
[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] <abentley> me
[19:00] <mrevell> me
[19:00] <Rinchen> Roll Call
[19:00] <mrevell> me
[19:00] <gmb> me
[19:00] <sinzui> me
[19:00] <Rinchen> me
[19:00] <barry> me
[19:00] <bac_> me
[19:01] <bigjools> me
[19:01] <allenap> me
[19:01] <statik> me
[19:01] <adeuring> me
[19:01] <jt1> me
[19:01] <jtv> me
[19:01] <mthaddon> me
[19:01] <flacoste> me
[19:01] <matsubara> me
[19:01] <thumper> me
[19:01] <herb> me
[19:01] <kiko> eu
[19:01] <Rinchen> SteveA, danilos ?
[19:01] <leonardr> me
[19:01] <mpt> meme
[19:01] <Rinchen> schwuk, ?
[19:01] <jtv> Rinchen: just pinged danilos
[19:01] <mpt> me
[19:01] <schwuk> me
[19:01] <mars> me
[19:02] <Rinchen> ah mpt, are you here for the full meeting?
[19:02] <SteveA> me
[19:02] <BjornT> me
[19:02] <flacoste> salgado is on leave, Foundations is complete
[19:02] <mpt> Rinchen, I think so
[19:02] <Rinchen> k
[19:02] <Rinchen> thanks flacoste
[19:02] <Rinchen> releases is here
[19:02] <mpt> I just love you guys too much
[19:02] <Rinchen> rockstar, ?
[19:02] <rockstar> me
[19:02] <BjornT> Bugs is here as well. intellectronica is on leave
[19:02] <Rinchen> cprov-out, ?
[19:03] <Rinchen> muharem is not here today with a hall pass
[19:03] <cprov-out> me
[19:03] <Rinchen> ok, let's get going
[19:03] <Rinchen> Agenda
[19:03] <Rinchen>  * Next meeting
[19:03] <Rinchen>  * Actions from last meeting
[19:03] <Rinchen>  * Oops report (Matsubara)
[19:03] <Rinchen>  * Critical Bugs (Rinchen)
[19:03] <EdwinGrubbs> me
[19:03] <Rinchen>  * Bug tags
[19:03] <Rinchen>  * Operations report (mthaddon/herb)
[19:03] <Rinchen>  * DBA report (stub)
[19:03] <Rinchen>  * Sysadmin requests (Rinchen)
[19:03] <Rinchen>  * New packages required (salgado)
[19:03] <Rinchen>  * A top user-affecting issue (mrevell)
[19:03] <Rinchen>  * Doc Team report (mrevell
[19:03] <Rinchen> * Numbered experiments and [WWW] https://launchpad.canonical.com/Experiments (kiko)
[19:03] <Rinchen>  
[19:03] <Rinchen> Next meeting
[19:04] <Rinchen> same time, same place, June 5th?
[19:04] <kiko> +1
[19:04] <Rinchen> Anyone know they will be absent?
[19:04] <Rinchen> ok.  If you find out later, please update the agenda
[19:05] <Rinchen>  
[19:05] <Rinchen> Actions from last meeting
[19:05] <Rinchen>  
[19:05] <Rinchen> None remaining open
[19:05] <Rinchen>  
[19:05] <Rinchen> Oops report (Matsubara)
[19:05] <matsubara> Today's oops report is about bugs 235818, 200572
[19:05] <SteveA> I'll be absent
[19:05] <matsubara> danilo, #235818 is for you. Are you going to re-enable relicense translations
[19:05] <matsubara> in an RC? If not, can you disable the link for the second rollout?
[19:05] <matsubara> flacoste, any news about 200572?
[19:05] <SteveA> actually, I'll be absent for 2 meetings in a row
[19:05] <matsubara> danilos: ^
[19:06] <flacoste> matsubara: no
[19:06] <matsubara> flacoste: should I add that exception to the "User generated errors" section?
[19:06] <jtv> matsubara: danilos may be having system problems again.
[19:07] <matsubara> jtv: ok. I'll chase him after the meeting then. thanks
[19:07] <flacoste> matsubara: if you can identify them reliably, i guess so, i don't think we have time for this before 2.0
[19:07] <kiko> matsubara, the first one, for danilo, is already fixed in RF, just landed.
[19:07] <matsubara> thanks kiko
[19:08] <matsubara> flacoste: ok. I'll give it try. thanks
[19:08] <matsubara> anything else shows up in the oops report today, and I'll follow up directly with people
[19:08] <matsubara> I'm done Rinchen
[19:08] <Rinchen> Thanks matsubara
[19:08] <Rinchen>  
[19:08] <Rinchen> Critical Bugs (Rinchen)
[19:08] <Rinchen>  
[19:08] <matsubara> thanks everyone
[19:08] <kiko> matsubara, I don't see any issue with moving that into UGE
[19:09] <Rinchen> It seems that we've talked about everything on my list or it has been fixed (thanks flacoste) so I have nothing for this week.
[19:09] <matsubara> kiko: ok. I'll do that
[19:09] <Rinchen>  
[19:09] <Rinchen> Bug tags
[19:09] <Rinchen>  
[19:09] <Rinchen> We have 2
[19:09] <Rinchen> https://help.launchpad.net/TaggingLaunchpadBugs
[19:09] <Rinchen> matsubara, bughistory
[19:09] <Rinchen> we'll start with yours first
[19:10] <matsubara> hmm ok
[19:10] <matsubara> it's a tag to handle all bugs related to our +bug-activity page
[19:10] <kiko> +1
[19:10] <matsubara> actually it's +activity page
[19:10] <matsubara> and given the number of examples, I think it's worth to have it.
[19:10] <Rinchen> could we make that generic enough to handle blueprint histories when we get them?
[19:11] <Rinchen> perhaps just "activity"
[19:11] <kiko> Rinchen, no.
[19:11] <Rinchen> or "activityhistory'
[19:11] <kiko> no
[19:11] <matsubara> Rinchen: I'd rather keep it bughistory
[19:11] <kiko> they are completely unrelated -- there is no shared code or anything
[19:11] <flacoste> well
[19:11] <mpt> Eventually they might be shared code
[19:11] <mpt> but not in the short term
[19:11] <flacoste> one doesn't exists
[19:11] <matsubara> and then change the meaning to history-logging or whatever when we get there
[19:11] <flacoste> so i think it's premature
[19:12] <Rinchen> Sure, I'm ok with all of that.
[19:12] <Rinchen> Wanted to make sure we thought about it.
[19:12] <mars> are the issues we will be tagging data integrity bugs, UI bugs???
[19:12] <Rinchen> BjornT, your comments?
[19:12] <SteveA> how about "activitypage" ?
[19:12] <mpt> I disagree with having "page" in the tag name
[19:12] <mpt> because one of the bug reports is about not showing activity on a separate page at all :-)
[19:12] <kiko> bughistory
[19:12] <kiko> this is not about generic activity pages
[19:13] <BjornT> Rinchen: +1
[19:13] <kiko> it's about not or incorrectly recording bug history
[19:13] <matsubara> yeah, i agree with mpt
[19:13] <Rinchen> ok, we have 2  plus 1s for bughistory
[19:13] <Rinchen> any against?
[19:13] <mpt> I'm fine with bugactivity or bughistory
[19:13] <Rinchen> 3 vs 0
[19:13] <Rinchen> ok, approved.
[19:13] <Rinchen> matsubara, please update that page
[19:13] <Rinchen> kiko, announcements
[19:14] <kiko> project-announcements maybe?
[19:14] <kiko> I dunno
[19:14] <matsubara> will do as soon as we reach an agreement for the second tag
[19:14] <matsubara> Rinchen: ^
[19:14] <kiko> I know there are a few bugs related to that and we can't group them easily
[19:14] <mpt> Is there likely to be any other kind of announcement?
[19:14] <Rinchen> bac, your comments?
[19:14] <kiko> mpt, well, hmmm
[19:14] <kiko> not sure
[19:15] <Rinchen> In this case, I'm +1 for this tag which I won't go into here
[19:15] <mpt> I guess the bet is, will any other kind of announcements be introduced *and* need its own tag, before mass tag-renaming is implemented :-)
[19:15] <kiko> I'm +1 too
[19:15] <kiko> just not sure about the name
[19:16] <mpt> If not, it can just be "announcements"
[19:16] <kiko> but this is a specific feature, project and distro announcements
[19:16] <kiko> I feel announcements is a bit too generic a term
[19:16] <Rinchen> kiko, project-announcements ?
[19:16] <kiko> but that's a mild feeling not a strong thing
[19:16] <kiko> that's what I suggested
 project-announcements maybe?
[19:16] <Rinchen> ok, 2 for that. Any objections?
[19:16] <matsubara> if we're sticking a project- on it how about project-news ?
[19:17] <kiko> sure
[19:17] <Rinchen> yeah, I'm ok with that as well
[19:17] <bac_> i'd stick with announcements since that's what they are called in the UI
[19:17] <kiko> -news is so much shorter.. okay, whatever, official-bug-tags will solve that eh BjornT :)
[19:17] <kiko> project-announcements it is
[19:17] <kiko> matsubara, ko do it!
[19:17]  * Rinchen doesn't tend to get obsessive with the names so long as they don't exclude anything we want to include or are insanely long.
[19:18] <matsubara> ok. thanks everyone
[19:18] <Rinchen> ok, approved.
[19:18] <Rinchen> kiko, please ensure that page is updated.
[19:18] <Rinchen>  
[19:18] <Rinchen> Operations report (mthaddon/herb)
[19:18] <Rinchen>  
[19:18] <herb> It's been a pretty quiet week. We needed to restart codebrowse/loggerhead a couple of times due to memory utilization. We discussed this last week and I believe mwhudson is aware of the issue.
[19:18] <herb> Rolled out 1.2.5 yesterday. Went smoothly with 25 minutes of downtime. To the best of my knowledge we haven't heard anything about a re-roll. Will there be a re-roll with this release and, if so, when?
[19:19] <flacoste> herb: how is the memory usage of the app servers been going since the max batch size fix?
[19:19]  * Rinchen notes we should call the 2nd roll-out something other than re-roll :-)
[19:19] <herb> flacoste: we haven't had to restart them.  they still grow, but the systems haven't been swapping.
[19:20] <kiko> herb, there will be a re-roll, I was hoping for first thing tomorrow if that's ok with you?
[19:20] <barry> Rinchen: twotsee-roll
[19:20] <herb> kiko: no problem.  sounds good.
[19:20] <mpt> rick-roll
[19:20] <Rinchen> I was thinking more like a polish-roll   (and in Shiny not the country)  :-)
[19:20] <kiko> I was thinking polish corridor
[19:20] <Rinchen> right, anything else for herb?
[19:20]  * barry likes polish-roll-the-country :)
[19:21] <herb> Tha's it from Tom and me.  Thanks.
[19:21] <Rinchen> thanks herb and mthaddon
[19:21] <Rinchen>  
[19:21] <Rinchen> DBA report (stub)
[19:21] <Rinchen>  
[19:21] <statik> not for herb specifically but I'm curious whether the bzr smartserver we are running now supports protocol3
[19:21] <Rinchen> stub's not here
[19:21] <Rinchen> so I'll ask for the DBA report via email
[19:21] <kiko> statik, we are still on 1.3 on the codehost
[19:21] <statik> kiko: thanks
[19:21] <Rinchen>  
[19:21] <Rinchen> Sysadmin requests (Rinchen)
[19:21] <Rinchen>  
[19:21] <Rinchen> Is anyone blocked on an RT or have any that are becoming urgent?
[19:21] <kiko> jml wants to upgrade the codehost code but not bzr -- bzr will upgrade on monday in RF
[19:22] <statik> kiko: that will give us stacked branches and the new network protocol, eh? very exciting
[19:22] <Rinchen> ok, nothing heard...moving on
[19:22] <Rinchen>  
[19:22] <Rinchen> New packages required (salgado)
[19:22] <Rinchen>  * A top user-affecting issue (mrevell)
[19:22] <Rinchen> er
[19:22] <kiko> statik, yes, very
[19:22] <Rinchen> salgado is not here
[19:22] <Rinchen> please talk to him if you have any packages that you need added
[19:23] <Rinchen>  
[19:23] <flacoste> or me
[19:23] <Rinchen>  top user-affecting issue (mrevell)
[19:23] <Rinchen>  
[19:23] <mrevell> :)
[19:23] <mrevell> This week, the outstanding issue has been the on-going discussion on launchpad-users of how we work to prevent the use of Launchpad accounts for spamming purposes.
[19:23] <mrevell> However, as we're looking into solutions I'm not sure there's much to discuss here. Otherwise, it seems we've had a relatively quiet week, user-issues-wise
[19:23] <kiko> mrevell, Rinchen, SteveA and I had an interesting call about this
[19:24] <kiko> Rinchen, can you remind us of the interesting ideas SteveA had
[19:24] <Rinchen> there were to proposals
[19:24] <SteveA> we may end up doing what facebook does
[19:24] <kiko> there were from proposals too
[19:24] <kiko> right
[19:24] <SteveA> and using capchas for each and every interaction that causes information to be seen by other users
[19:24] <kiko> if you haven't validated you get captcha-annoyance at every step
[19:24] <SteveA> until someone validates their account
[19:25] <SteveA> and there may be many ways of validating an account
[19:25] <kiko> flacoste, you got that? it might be foundations 2.0+
[19:25] <kiko> one way of validating an account is to sign the coc!!
[19:25] <SteveA> including associating it with a mobile phone sms number
[19:25]  * kiko snickers
[19:25]  * Rinchen can't receive sms
[19:25] <SteveA> or being part of the strongly connected GPG group
[19:25] <SteveA> or whatever
[19:25] <sinzui> Rinchen: That is sooooo 1990s
[19:26]  * Rinchen is part of a strongly connected GPG group. :-)
[19:26] <mrevell> Would it be churlish to mention the stories of teams of people paid to fill-out captcha forms?
[19:26] <SteveA> Rinchen: then... YOU LOSE ;-)
[19:26] <Rinchen> sinzui, blame it on T-Mobile
[19:26] <kiko> I can receive sms but not from the USAAAA
[19:26] <kiko> mrevell, not for every single step, I doubt they do that
[19:26] <flacoste> my mobile is turned-off in a drawer unless i travel
[19:26] <Rinchen> anyway.....
[19:26] <kiko> the captcha farm myth probably only applies to account registration captchas
[19:26] <mrevell> Right
[19:26] <kiko> not for every step I take captchas
[19:27] <kiko> the police captchas
[19:27] <SteveA> every move I make capchas
[19:27] <Rinchen> So to recap, we have a few proposals that we are interested in evaluating further.
[19:27] <SteveA> we'll be watching you
[19:27] <bigjools> captcha in a bottle
[19:27] <kiko> that's so 1984
[19:27] <mars> SteveA, the GPG web of trust tie-in is interesting
[19:27] <Rinchen> mrevell, anything else? SteveA, anything else?
[19:27] <flacoste> since most data is seen by other users, it's basically a captcha on every form...
[19:27] <kiko> mars, tie-in being a pun there?
[19:27] <mrevell> Rinchen: that's all from me, thanks
[19:27] <SteveA> nothing else from me
[19:28] <Rinchen> thanks
[19:28] <kiko> flacoste, yes, simpler that way too
[19:28] <Rinchen> Doc Team report (mrevell)
[19:28] <flacoste> LaunchpadEditForm-voodoo
[19:28] <kiko> doc team!!!
[19:28] <mrevell> Hello!
[19:28] <mrevell> Although the doc team meeting last week was a wash-out, we've had another member sign up and offer to do German translations!
[19:29] <mrevell> I'm particularly excited about that, but the chap does warn that he's a touch rusty.
[19:29] <mrevell> In other doc news: Had a useful meeting with Mark S and the SEM designer, Gavin, on Tuesday. Tour is progressing well. Thanks to those who've sent comments on the inner page graphics.
[19:29] <mrevell> Thanks also to those who've given comments on the release announcement. I'll deal with those after the meeting.
[19:29] <mrevell> Later today, Elliot and I will be recording episode 3 of the podcast.
[19:29] <mrevell> Thanks Rinchen
[19:29] <Rinchen> thanks mrevell
[19:30] <Rinchen>  
[19:30] <Rinchen> Numbered experiments and [WWW] https://launchpad.canonical.com/Experiments (kiko)
[19:30] <Rinchen>  
[19:30] <kiko> hello hello
[19:30] <SteveA> I like this
[19:30] <kiko> I put that wikipage up
[19:30] <kiko> because I'd like us to record the experiments we run
[19:30] <SteveA> thanks kiko!
[19:30] <kiko> and at least detail what the experiment is and what the outcome was
[19:30] <kiko> the experiments are sequentially numbered and it's FCFS based on wiki edit
[19:30] <statik> very nice
[19:31] <kiko> so if you want to, say, experiment by right-aligning all form elements in a specific launchpad form
[19:31] <kiko> (which is a pretty bad idea)
[19:31] <kiko> you add an entry to that page and call it experiment n+1
[19:31] <kiko> where n is the last experiment recorded there
[19:31] <mpt> Result: mpt chased you with a cheese grater
[19:31] <Rinchen> I like this too. I'd like to request that the outcome be documented somewhere of course (on the wiki page associated with the experiment for example)
[19:31] <kiko> there you go
[19:31] <kiko> now I need a candidate to fill out LP001
[19:32] <kiko> who's that gonna be
[19:32]  * Rinchen raises flacoste's hand.
[19:32] <mars> kiko, I gather that's process experiments as well, like Foundations cycle planning?
[19:32] <kiko> mars, yes.
[19:32] <kiko> it's basically any experiment
[19:32] <Rinchen> I think flacoste could doc up planning poker :-)
[19:32] <flacoste> Rinchen: yeah, Foundations will come up with one, don't know it will be the first one though
[19:32] <flacoste> Rinchen: well, that experiment is over
[19:32] <kiko> you can do retroactive entries there too
[19:32] <Rinchen> :-)
[19:33] <flacoste> ah, then that could be it
[19:33] <Rinchen> I was going for something easy
[19:33] <kiko> there you go
[19:33] <kiko> please run experiments
[19:33] <kiko> and please record them there
[19:33] <kiko> experiments are fun and cheap
[19:33] <Rinchen> experimentation is good
[19:33] <Rinchen> so long as nobody gets hurt
[19:33] <Rinchen> kiko, anything else?
[19:34] <Rinchen> on this topic
[19:34] <kiko> no
[19:34] <Rinchen> k
[19:34] <Rinchen> I have a last minute addition
[19:34] <kiko> secret topic?
[19:34] <Rinchen>  
[19:34] <Rinchen>  
[19:34] <Rinchen> Storm n you (kiko)
[19:34] <Rinchen>  
[19:34] <kiko> aha
[19:34] <kiko> I knew it!
[19:34] <kiko> so
[19:34] <barry> bigjools: did you want to bring up the big branch topic?
[19:34] <kiko> jamesh is struggling with quite a few of our tests
[19:35] <kiko> and has been so for the past week or two
[19:35] <kiko> I've asked him to do a full run of all tests and figure out how much is failing
[19:35] <kiko> but it is getting close to the point where I am going to move devel focus over to storm
[19:35] <kiko> this will make edge much less useful
[19:35] <SteveA> a bold move, kiko
[19:36] <SteveA> I support it
[19:36] <kiko> and also commits us to doing the work to make storm work in a very short period of time
[19:36] <kiko> so if you are a launchpad engineer
[19:36] <flacoste> why edge will be less useful?
[19:36] <kiko> and if you are a team lead
[19:36] <kiko> then you may need to prepare for a few days interruption to fix any remaining tests
[19:36] <barry> kiko: anything we can do to help?
[19:36] <kiko> barry, yes, very soon, fix the tests which fail with storm
[19:37] <barry> kiko: cool.  that'll be fun
[19:37] <kiko> flacoste, because we'd not update edge until all the tests actually passed in-tree
[19:37]  * Rinchen questions barry's idea of fun.
[19:37] <BjornT> kiko: do we have a list of tests that fail?
[19:37] <flacoste> i don't understand how this will work
[19:37] <kiko> this can be very disruptive; we're not sure how much, but if it's a mess we'll need to figure out what to do with 1.2.6
[19:37] <flacoste> we'll close PQM?
[19:37] <mars> or we will focus PQM on Storm integration?
[19:38] <flacoste> i mean, the test suite pass or doesn't pass
[19:38] <flacoste> there is no way to land if the test suite doesn't pass
[19:38] <kiko> flacoste, no, but we'll either disable all failing tests and merge
[19:38] <mthaddon> I'm assuming we'd keep PQM open, but would be working on the storm integration branch instead of devel
[19:38] <kiko> or work on the storm integration branch
[19:38] <kiko> mthaddon, doesn't that require all tests pass?
[19:38] <mthaddon> kiko, it does, but it's up to you however many of the tests you want to enable - can do it progressively, or all at once
[19:39] <kiko> BjornT, not yet, but james will produce one. I'm hoping it's 30 not 150
[19:39] <flacoste> kiko: if problematic tests are disabled to allow some merge to go, that doesn't help keep the focus on storm
[19:39] <kiko> if it's 150 then it's a no-go
[19:39] <kiko> so we'll see
[19:39] <kiko> mthaddon, gotcha
[19:39] <Rinchen> what I'm hearing is merging storm integration with devel and fixing it so everything passes. Until then, edge won't update.
[19:39] <kiko> flacoste, it's not "some merge" it's the storm merge onto RF
[19:39] <kiko> Rinchen, yes
[19:39] <Rinchen> a bold move indeed
[19:39] <BjornT> kiko: ok should we make an effort into finding performance regressions as well?
[19:40] <kiko> BjornT, yes, though to me that's second priority
[19:40] <flacoste> mars produced a script for that
[19:40] <BjornT> kiko: or rather, how much of an effort should we make
[19:40] <flacoste> but jamesh never give feedback on it
[19:40] <Rinchen> mars, I saw that spec and script. I meant to ask about that.
[19:40] <kiko> BjornT, it's serialized -- once your tests pass, you can look at that
[19:40] <mars> flacoste, yes, but it needs a kind soul to try it out
[19:40] <kiko> flacoste, I think jamesh is stuck before that point
[19:40] <flacoste> i don't think so, all page tests run
[19:41] <flacoste> and this analyze the log file of the page tests
[19:41] <kiko> doctests don't
[19:41] <BjornT> flacoste, mars: does the script use existing sample data?
[19:41] <kiko> flacoste, sure, but jamesh is only one bold soul
[19:41] <mpt> Would it make sense to have a ratchet, so that storm can land while tests are still failing, but you can't make any further landing that increases the number of failures?
[19:41] <mpt> that would help keep the focus
[19:41] <kiko> mpt, too complex to add at this point, though interesting
[19:41] <kiko> flacoste, he won't look at perf regress until he's got all the tests running
[19:41] <mars> BjornT, it compares the access logs for two runs, so you can benchmark storm-storm, or storm-trunk
[19:41] <kiko> anyway
[19:42] <kiko> I don't want to run overtime, but I also think we need to be serious about the move and help us acheive what we set out to do
[19:42] <kiko> storm is the future
[19:42] <flacoste> anyway, this introduce more uncertainty in the 1.2.6 planning
[19:42] <kiko> flacoste, yes, I noted that up-front. we have some buffer time.
[19:42] <flacoste> no we don't :-)
[19:42] <kiko> be brave!
[19:43] <kiko> we do at my discretion only ;-)
[19:43] <BjornT> mars: so i can create a bunch of data, access a few pages, and compare the result?
[19:43] <kiko> Rinchen, feel free to wrap up, people are going to start asking me complicated questions now
[19:43] <Rinchen> ok, time to wrap up now that the storm is over :-)
[19:43] <flacoste> BjornT: yes
[19:43] <mars> BjornT, yep
[19:43] <BjornT> cool
[19:43] <Rinchen> ok then... what an eventful chat
[19:44] <kiko> AH!
[19:44] <cprov> very cool !
[19:44] <Rinchen> please ensure any of your absent team members read the log
[19:44] <kiko> one thing I can provide for you to look into
[19:44] <kiko> oh damn, it's in my xchat log
[19:44] <kiko> one sec
[19:44] <kiko> on devpad: ~jamesh/errors-systemdocs.txt
[19:44] <kiko> that's the failures accumulated in doc/*
[19:44] <mars> Rinchen, should we stick around after the meeting end to pepper kiko with questions? :)
[19:45] <Rinchen> mars, you can!
[19:45] <Rinchen> Thank you all for attending this week's Launchpad Developer Meeting.
[19:45] <Rinchen> == the end ==
[19:45] <kiko> == snif ==
[19:45] <Rinchen> on time photo finish
[19:45] <sinzui> _consider me gone_
[19:45] <SteveA> thanks!
[19:45] <Rinchen> Ok __sinzui__
[19:45] <mrevell> thanks