[17:50] <kiko> a hoy
[19:00] <Rinchen> #startmeeting
[19:00] <MootBot> Meeting started at 13:02. The chair is Rinchen.
[19:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[19:00] <Rinchen> wootbot
[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] <Rinchen> [TOPIC] Roll Call
[19:00] <MootBot> New Topic:  Roll Call
[19:00] <Rinchen> me
[19:00] <mrevell> me
[19:00] <bigjools> me
[19:00] <jtv> me
[19:00] <abentley> me
[19:00] <leonardr> me
[19:00] <bac> me
[19:01] <intellectronica> me
[19:01] <EdwinGrubbs> me
[19:01] <sinzui> me
[19:01] <barry> me
[19:01] <al-maisan> me
[19:01] <schwuk> me
[19:01] <gmb> me
[19:01] <thumper> me
[19:01] <adeuring> me
[19:01] <kiko> me
[19:01] <mpt> me
[19:01] <salgado> me
[19:01] <kiko> cprov sends apologies but had to dash!
[19:01] <flacoste> me
[19:01] <Rinchen> matsubara?
[19:01] <BjornT> me
[19:01] <matsubara> me
[19:01] <kiko> thanks jtv for being with us
[19:01] <thumper> rockstar?
[19:01] <rockstar> ,e
[19:01] <Rinchen> releases team is here
[19:01] <rockstar> er, me
[19:02] <bigjools> cprov sends his apologies, I am covering for him
[19:02] <stub> me
[19:03] <kiko> stub!
[19:03] <Rinchen> herb, mthaddon ?
[19:03] <kiko> good to have you here
[19:03] <herb> me
[19:03] <mthaddon> here
[19:03] <Rinchen> statik, ?
[19:03] <Rinchen> hmm
[19:03] <Rinchen> well, we're missing a few people
[19:03] <Rinchen> but i'll move fwd
[19:04] <mrevell> Rinchen: I believe statik is travelling today
[19:04] <Rinchen> thanks
[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> plsu
[19:04] <Rinchen> er
[19:04] <Rinchen> plus
[19:04] <Rinchen>     *
[19:04] <Rinchen>       Policies for launchpad dependency packages (kiko)
[19:04] <Rinchen>     *
[19:04] <Rinchen>       Storm and Hardy Updates (kiko)
[19:04] <Rinchen>     *
[19:04] <Rinchen>       iframe on every LP page (kiko)
[19:04] <Rinchen> hmpf
[19:04] <Rinchen> [TOPIC] Next meeting
[19:04] <MootBot> New Topic:  Next meeting
[19:05] <Rinchen> I won't be here next week
[19:05] <BjornT> i won't be here next week
[19:05] <Rinchen> kiko, can you run the the meeting?
[19:05] <kiko> yes
[19:05] <kiko> I can
[19:05] <kiko> I am good at such things
[19:05] <Rinchen> very well
[19:05] <kiko> (making messes out of meetings)
[19:05] <Rinchen> ok, same time same place?
[19:05] <abentley> kiko: he said "run", not "ruin" :-)
[19:06] <Rinchen> [AGREED] meeting next week, same place, same time, Kiko to rui...er...run the meeting. :-)
[19:06] <MootBot> AGREED received:  meeting next week, same place, same time, Kiko to rui...er...run the meeting. :-)
[19:06]  * kiko scratches eyes
[19:06] <Rinchen> [TOPIC] Actions from last meeting
[19:06] <MootBot> New Topic:  Actions from last meeting
[19:06] <kiko> so he did, maybe that wasn't such a great id..
[19:06] <Rinchen> we had none
[19:06] <Rinchen> [TOPIC] Oops report (Matsubara)
[19:06] <MootBot> New Topic:  Oops report (Matsubara)
[19:07] <matsubara> today's oops report is about bug 239519
[19:07] <matsubara> thumper: can you take that one?
[19:08] <thumper> I'll allocate it, yes
[19:08] <matsubara> there's another OOPS which I'm checking but haven't filed a bug yet. https://devpad.canonical.com/~matsubara/oops.cgi/2008-06-11/EC36
[19:08] <matsubara> salgado: I think that oops is for you :-)
[19:08] <matsubara> it's an AssertionError in peoplemerge
[19:08] <Rinchen> [AGREED] Thumper to allocate someone to look at bug 239519
[19:08] <MootBot> AGREED received:  Thumper to allocate someone to look at bug 239519
[19:08] <salgado> matsubara, I'll have a look
[19:09] <matsubara> thanks, we can coordinate about it after the meeting.
[19:09] <matsubara> Rinchen: that's it from me. thanks
[19:09] <Rinchen> [AGREED] salgado to look at a particular oops :-)
[19:09] <MootBot> AGREED received:  salgado to look at a particular oops :-)
[19:09] <kiko> matsubara, I think it only occurs when I fuck it up, but it should be very easy to fix
[19:09] <Rinchen> thanks matsubara
[19:09] <matsubara> thanks everyone
[19:09] <kiko> oh, no
[19:09] <kiko> it's not
[19:09] <Rinchen> [TOPIC] Critical Bugs (Rinchen)
[19:09] <MootBot> New Topic:  Critical Bugs (Rinchen)
[19:09] <Rinchen> [LINK] https://bugs.edge.launchpad.net/soyuz/+bug/234254
[19:09] <Rinchen> cprov, what's the status with this one? This appears to me to either be fixed committed or high, but no longer critical.
[19:09] <MootBot> LINK received:  https://bugs.edge.launchpad.net/soyuz/+bug/234254
[19:10] <bigjools> Rinchen: it's a config change
[19:10] <bigjools> I think cprov did a branch for it, I don't know if it's in PQM or landed yet
[19:10] <Rinchen> there is one branch from a while ago documented but history shows that you've raised it in priority since then
[19:11] <Rinchen> I haven't seen any recent activity, hence my questioning.
[19:11] <bigjools> it's config for the restricted librarian
[19:11] <kiko> bigjools, can you check and update the bug accordingly, please?
[19:11] <bigjools> yup
[19:11] <kiko> bigjools, no bugs should be left critical
[19:11] <kiko> NONE
[19:11]  * kiko blows the cavalier trumpet
[19:11] <bigjools> AFAIK cprov is actively working on it
[19:11] <bigjools> so don't panic!
[19:11] <Rinchen> [ACTION] Julian to review and update bug 234254
[19:11] <MootBot> ACTION received:  Julian to review and update bug 234254
[19:11] <Rinchen> thanks jules
[19:12] <kiko> bigjools, it's not cprov's responsibility. it's the team's. it's a critical bug.
[19:12] <Rinchen> [TOPIC] Bug tags
[19:12] <MootBot> New Topic:  Bug tags
[19:12] <Rinchen> we have one
[19:12] <kiko> i.e. if you don't know about it, something's wrong
[19:12] <Rinchen> https://help.launchpad.net/TaggingLaunchpadBugs
[19:12] <kiko> a bug tag, my favorite
[19:12] <bigjools> I do know about it
[19:12] <Rinchen> package-diff  - cprov
[19:13] <Rinchen> bigjools, do you have anything to say on the bug tag on behalf of cprov-out?
[19:13] <adeuring> f
[19:14] <Rinchen> I'm ok with it if it helps your team out.
[19:14] <bigjools> Well he mentioned it to me before dashing off earlier, I know as much as you just pasted - I guess it's for bugs relating to the new package diff calculations, since there seem to be a few
[19:14] <bigjools> (BTW the fix for 234254 is #2 in PQM's queue)
[19:14] <Rinchen> we can approve it, reject it, or postpone it.   kiko, you have any thoughts?
[19:15] <Rinchen> al-maisan, any thoughts from you?
[19:15] <kiko> let me check.
[19:15] <bigjools> I would be happy with it
[19:15] <kiko> sure, I think that's fine
[19:15] <al-maisa1> Rinchen: sorry my connection dropped
[19:15] <al-maisa1> missed the question
[19:15] <Rinchen> al-maisa1, package-diff bug tag proposed by cprov
[19:16] <al-maisa1> fine with me
[19:16] <kiko> yeah, it makes sense to me
[19:16] <Rinchen> ok, so carried.
[19:16] <Rinchen> [AGREED] Package-diff tag approved.
[19:16] <MootBot> AGREED received:  Package-diff tag approved.
[19:16] <Rinchen> bigjools, can you get cprov-out to update that page again please and move the tag to approved?
[19:16] <bigjools> wilco
[19:16] <Rinchen> thank you sir
[19:16] <Rinchen> [TOPIC] Operations report (mthaddon/herb)
[19:16] <MootBot> New Topic:  Operations report (mthaddon/herb)
[19:17] <herb> Monday (2008-06-09) lpnet1 & lpnet2 had died around midnight.  Was caught by the SAs and they restarted.
[19:17] <herb> Monday (2008-06-09) lpnet4 died with logrotate. It was manually restarted.
[19:17] <herb> There are currently 2 CP requests awaiting approval. (r6410 & r6451)
[19:17] <herb> We're about mid-way through the hardy upgrades. The app servers are going today
[19:17] <herb> as we speak.
[19:17] <herb> Thanks to an update today edge is now using storm.
[19:17] <herb> The new codeimport system seems to be working well, but it hits the DB pretty ha
[19:17] <herb> rd. It doesn't seem there is any connection pooling of any kind which can result in 50+ open db connections.
[19:17] <herb> I failed to update Bug 224623 last week with the debug logs as promised.  Look f
[19:17] <herb> or them before the end of my day today.
[19:18] <Rinchen> thumper, any activities on the radar to address the db connections?
[19:18] <kiko> okay.
[19:18] <kiko> thumper, yeah, was going to ask that
[19:18] <thumper> hmm
[19:18] <herb> we haven't opened a bug on it yet.  just started noticing it recently.
[19:19] <herb> we can get a bug opened on it today if you'd like.
[19:19] <flacoste> herb: any idea why the app server died?
[19:19] <thumper> I'll talk with mwhudson_ about it this morning
[19:19] <stub> Is this one connection per process or thread, or just the usual open-and-close connections really fast? If the latter, Storm could fix that.
[19:19] <herb> flacoste: sadly no.
[19:19] <Rinchen> herb, if you could please, open a bug and let thumper and mwh know the number. Please include any data/output you have in the report.
[19:19] <herb> Rinchen: will do.
[19:20] <matsubara> ls
[19:20] <kiko> stub, hmm, I think it's the latter, tbh
[19:20] <kiko> thumper, do you know?
[19:20] <thumper> there are up to 10 processes running at once on each import machine
[19:20] <thumper> we only have two slaves
[19:21] <thumper> so I'd expect to see around 20 not 50
[19:21] <kiko> right
[19:21] <kiko> okay -- we'll figure it out with mwh the import code master
[19:21] <Rinchen> perhaps it is just an optimization issue....unused connections being closed later than expected.
[19:21] <herb> thumper: keep on eye out for the bug a bit later today.
[19:21] <Rinchen> any other questions for herb and mthaddon ?
[19:22] <stub> Previously, the zopeless commit would close and reopen a new connection. This behavior has (hopefully) been sorted as a side effect of the storm branch landing.
[19:22] <Rinchen> should be interesting to see what effect that has
[19:22] <Rinchen> thanks herb
[19:22] <herb> thanks
[19:23] <Rinchen> [TOPIC] DBA report (stub)
[19:23] <MootBot> New Topic:  DBA report (stub)
[19:23] <stub> This close and reopening is often done so fast you have 2 or 3 times as many clients on the db as necessary as they are being opened faster than PG can clean them up.
[19:23] <stub> Production DB will be upgraded to PostgreSQL 8.3 on Tuesday during the Hardy upgrade window.
[19:23] <stub> The rest of the DB reviews for this cycle will be done tomorrow and the db freeze lifted if edge is in good shape with todays branch. I might delay opening until Monday or Tuesday if there are urgent fixes that need landing on edge and kiko agrees. With luck, the freeze will be lifted by landing the auth-person-split branch.
[19:23] <stub> PQM has been running PG 8.3 for two days apparantly. I haven't confirmed this with my own eyes yet though as I just noticed the RT request followup :-) Thanks to Lamont and Tom.
[19:23] <stub> The databases on carbon (staging, demo) should be switched to 8.3 ASAP - I'll look at this if the losas don't beat me to it. The upgrade will also switch the DB to the correct locale (currently running default, should be C locale to match production).
[19:23] <stub> Nothing else to report.
[19:24] <kiko> stub, I had expected staging and demo to be running 8.3 already tbh
[19:24] <Rinchen> yay for auth-person-split
[19:24] <kiko> stub, will you do this before the weekend?
[19:24] <mars> me! phooey.
[19:25] <stub> Yes. staging and demo where to be done after PQM. The downtime window approached more rapidly than expected.
[19:25] <kiko> stub, I am kinda hoping everything will fall into place tomorrow -- the only thing I can imagine will help us on edge is fixing mars' favorite iframe and possibly a storm optimo, but it's OOPSes that might tell me otherwise
[19:25] <kiko> stub, yeah, we got things in gear now :)
[19:25] <stub> Yup
[19:25] <flacoste> mars' favorite iframe?
[19:25] <Rinchen> agenda item
[19:25] <Rinchen> anything else for Stu?
[19:26] <stub> beer!
[19:26] <Rinchen> and thai food, yes I read the lodging request :-)
[19:26] <Rinchen> thanks stub
[19:26] <Rinchen> [TOPIC] Sysadmin requests (Rinchen)
[19:26] <MootBot> New Topic:  Sysadmin requests (Rinchen)
[19:26] <kiko> fun
[19:26] <Rinchen> Is anyone blocked on an RT or have any that are becoming urgent?
[19:26] <stub> RT #30960 needs action Monday at the latest so I can confirm the PG upgrade will go smoothly.
[19:26]  * flacoste pokes barry
[19:26] <kiko> none from me, IS have nuked all of mine so quickly
[19:26] <bigjools> cprov asked me to mention 30778
[19:26] <barry> flacoste, Rinchen we are no longer blocked
[19:27] <flacoste> cool!
[19:27] <bigjools> which is the Gina machine
[19:27] <barry> well, my branch won't land for another 11 hours, but the rt was marked resolved :)
[19:27] <Rinchen> ok thanks. I'll have a look at them after the meeting, set dates and priorities, and ping the cuddly red fellow
[19:28] <Rinchen> a little deviation here for a moment
[19:28] <Rinchen> [TOPIC] Policies for launchpad dependency packages (kiko)
[19:28] <MootBot> New Topic:  Policies for launchpad dependency packages (kiko)
[19:28] <kiko> aha!
[19:28] <kiko> so today we had a bit of a revelation when we figured out that our dependencies packages aren't being directly used on the appservers
[19:28] <kiko> they are being used as references, but not literally
[19:29] <kiko> I had a call with james today to attempt to sort that out
[19:29] <kiko> turns out that there are some bad things we're doing, so I want salgado to document and follow a policy for package updates
[19:29] <salgado> on the app servers they are used, no?  just chokecherry that was missing them?
[19:29] <kiko> salgado, well, it varies. the PQM chroot, for instance, doesn't use l-d-d
[19:29] <kiko> anyway
[19:30] <kiko> let me cover the specifics, and then the policy
[19:30] <kiko> 1. httplib. I understand we're using a version that isn't in intrepid yet. is there a bug open for this being packaged in Ubuntu intrepid and backported to hardy?
[19:30] <kiko> (that's for barry and flacoste)
[19:30] <barry> kiko: not that i know of
[19:31] <kiko> barry, okay. there should be. see policy coming up in a sec.
[19:31] <kiko> 2. apache and ssh. both packages are required for l-d-d. they are both daemons and can't really be run inside the PQM chroot.
[19:31] <kiko> so following comes a policy definition
[19:31] <kiko> for our dependencies packages
[19:32] <kiko> 1. it's not okay to depend on daemons. you can recommend a daemon, but not depend on it.
[19:32] <kiko> 2. if you require a version which isn't available in the current ubuntu release we're running, then it's okay to use a custom package /as long as/ there is a request to package that version in Ubuntu, and that bug is escalated to the distro team
[19:33] <kiko> that's all. I guess this needs to go into a document, but I'll let Rinchen sort that out with salgado!
[19:33]  * barry will open a bug for httplib2
[19:33] <salgado> AFAIK, we need apache to run launchpad
[19:34] <salgado> not to run, but to access it
[19:34] <kiko> salgado, PQM doesn't have it, so no, we don't really.
[19:34] <salgado> most package managers don't do anything with recommends, so that may cause developers to have to manually install it
[19:34] <kiko> salgado, it's okay to have l-d-d recommend apachd
[19:35] <salgado> kiko, I meant for a user to access.  tests are something else
[19:35] <kiko> salgado, I actually think apt follows recommends.
[19:36] <Rinchen> in any event, I could modify the newlaunchpadder docs to ensure folks install recommends
[19:36] <flacoste> it's usually a config policy
[19:36] <stub> It doesn't really matter if RocketFuel setup documents an extra command - it isn't like anyone follows that process every day.
[19:36] <thumper> aptitude does
[19:36] <salgado> and I don't know what update-manager does with Recommends
[19:36] <abentley> Wouldn't it be okay to require apache for launchpad-developer-dependencies, but not launchpad-dependencies?
[19:36] <Rinchen> good point
[19:36] <salgado> that's what we do currently
[19:37] <salgado> maybe we should have launchpad-tests-dependencies
[19:37] <kiko> abentley, no.
[19:37] <salgado> and launchpad-developer-dependencies
[19:37] <abentley> shouldn't PQM et al be using plain launchpad-dependencies?
[19:37] <kiko> salgado, it's unnecessary. recommends works.
[19:37] <salgado> then PQM would only have lp-tests-deps installed
[19:38] <Rinchen> launchpad-dependences today recommends launchpad-developer-dependencies
[19:38] <kiko> and that's fine
[19:38] <kiko> as I said, recommends works
[19:38] <kiko> can we move on, Rinchen?
[19:38] <salgado> abentley, PQM needs the dev deps in order to run the testsuite
[19:39] <Rinchen> kiko, yes if you are done.  Salgado, can you get with kiko if you have further questions?
[19:39] <abentley> salgado: Okay.  I can see the argument that we don't want too many metapackages.
[19:39] <Rinchen> [TOPIC] New packages required (salgado)
[19:39] <MootBot> New Topic:  New packages required (salgado)
[19:39] <salgado> any new dependencies for this week?
[19:40] <Rinchen> [ACTION] Joey to ping Salgado about documenting package dependency policy
[19:40] <MootBot> ACTION received:  Joey to ping Salgado about documenting package dependency policy
[19:40] <kiko> sounds like no :)
[19:40] <Rinchen> [TOPIC] A top user-affecting issue (mrevell)
[19:40] <MootBot> New Topic:  A top user-affecting issue (mrevell)
[19:41] <mrevell> Hello. Three things today.
[19:41] <mrevell> First up: quick reminder that we'll have service interruptions on 17th, 18th and 19th June. You can find out more in our blog post at: http://news.launchpad.net/notifications/launchpad-service-interruptions-17th-18th-and-19th-june
[19:41] <mrevell> Second: Kiko's going to talk about this later, but here's a quick note to any non-team members present: you may spot an empty box at the bottom of pages on edge. We're aware of this, so please don't worry about filing a bug.
[19:41] <mrevell> And the main issue this week: matsubara mentioned that intellectronica is currently helping one of our users who is experiencing problems with the email interface.
[19:41] <mrevell> This person, Iain, is sending GPG-signed messages for both the bug tracker and Answers, but getting no response. So far, one other person has reported the same problem.
[19:41] <mrevell> You can see the question at: https://answers.edge.launchpad.net/launchpad/+question/35165
[19:41] <mrevell> I think intellectronica would welcome a discussion of what could be causing this.
[19:41] <mrevell> Thanks Rinchen.
[19:42] <Rinchen> Anything for mrevell or intellectronica?
[19:42] <intellectronica> to add more information to that - the user doesn't seem to be able to get even as far as requesting help via the email interface
[19:42] <barry> intellectronica: let me know if there's anything i can help with
[19:42] <Rinchen> [TOPIC] Doc Team report (mrevell)
[19:42] <MootBot> New Topic:  Doc Team report (mrevell)
[19:42] <kiko> mrevell, matsubara, intellectronica: I have confirmation from IS that the message hits us
[19:43] <kiko> who should I forward that information to?
[19:43] <intellectronica> kiko: me
[19:43] <mrevell> Cool, thanks guys.
[19:43] <mrevell> A busy week for me working on user guide material, and primarily further tweaks to the tour, following Mark's feedback. I'd like to arrange a call with each team lead to go through the relevant section of the tour content with you. Please ping me with suitable times.
[19:43] <mrevell> No news from the doc team this week.
[19:43] <mrevell> Thanks Rinchen.
[19:43] <intellectronica> there's a question. maybe this is the time to convert it to a bug
[19:44] <Rinchen> sounds good to me :-)
[19:44] <flacoste> intellectronica: i would look into signed_message_from_string failing
[19:44] <flacoste> intellectronica: look at the log, you should be able to find the email failing
[19:44] <kiko> intellectronica, will do. thanks!
[19:44] <Rinchen> [TOPIC] Storm and Hardy Updates (kiko)
[19:44] <MootBot> New Topic:  Storm and Hardy Updates (kiko)
[19:44] <kiko> aha
[19:45] <kiko> I am the bearer of great tidings
[19:45] <kiko> staging and our edge server are nor updated to latest Storm
[19:45] <kiko> err
[19:45] <kiko> now updated
[19:45] <kiko> we are aware of some performance regressions that this will impact
[19:46] <kiko> for instance, BjornT has seen the number of queries on certain bug pages going up surprisingly
[19:46] <kiko> we also know that PQM took a 15 minute hit
[19:46] <kiko> this is somewhat expected and we'll be working on fixing it as we progress
[19:46] <kiko> there's also an OOPS on the wild that mthaddon has triggered, which is something we're going to investigate further
[19:47] <kiko> ZStormError: Store named 'main' already exists
[19:47] <kiko> is what the OOPS says
[19:47] <kiko> aaaanyway. help us through the rough waters by offering help and objective issue reports. general whining is not ok.
[19:48] <kiko> last item of news is hardy upgrades -- you guys know this is happening next week, along with pg8.3 coming on tuesday thanks to stub and the losas
[19:48] <kiko> so keep your eyes peeled for any issues that come during this period, and let us know
[19:48] <kiko> thanks and sorry for running overtime -- it's always like that when you let me do the talking...
[19:48] <Rinchen> and for the final topic...
[19:48] <Rinchen> iframe on every LP page (kiko)
[19:48] <Rinchen> [TOPIC] iframe on every LP page (kiko)
[19:48] <MootBot> New Topic:  iframe on every LP page (kiko)
[19:48] <kiko> why is this me?
[19:48] <kiko> anyway.
[19:49] <kiko> edge has an iframe being rendered on every single page.
[19:49] <kiko> it's a CSS mistake, I believe -- invisible isn't actually causing invisibility.
[19:49] <flacoste> should be display: none
[19:49] <intellectronica> fyi, it also has a javascript error on all pages. it's part of the same bug
[19:49] <mars> kiko, working on it now
[19:49] <kiko> it's a critical problem, and as soon as we have a branch (tests for it will be.. interesting) we should push this right up to the front of the PQM queue.
[19:49] <sinzui> Invisible != none
[19:50] <kiko> mthaddon, herb: can you work with mars and intellectronica to ensure that happens? will owe you a tall glass 'a beer
[19:50] <sinzui> I thought the intent *was* to have it load everytime, so invisible was used.
[19:50] <herb> kiko: not a problem
[19:50] <kiko> I know the beer's not a problem. I meant the PQM reorder. :)
[19:50] <mpt> It shouldn't be invisible, it should be non-existent until summoned
[19:50] <mthaddon> kiko, sure
[19:50] <Rinchen> like a good familiar
[19:50] <Rinchen> err
[19:51] <Rinchen> Thank you all for attending this week's Launchpad Developer Meeting.
[19:51] <Rinchen> #endmeeting
[19:51] <MootBot> Meeting finished at 13:53.
[19:51] <thumper> mpt: not existant implies created with JS
[19:51] <abentley> Thanks Rinchen
[19:51] <mpt> thumper, exactly
[19:51] <thumper> Rinchen: thanks
[19:51] <barry> Rinchen: thanks
[19:51] <mrevell> thanks rinchen
[19:51]  * Rinchen attempts to summon the mootbot logs