[01:37] <Tanya> halo
[18:58] <Rinchen> hello MootBot
[18:58] <Rinchen> nice of you to join us
[18:59] <thumper> Rinchen: now what would be good was if MootBot could reply nicely
[18:59] <Rinchen> mtg logs have changed
[18:59]  * Rinchen sighs.
[19:00] <Rinchen> #startmeeting
[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] <MootBot> Meeting started at 13:00. The chair is Rinchen.
[19:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[19:00] <Rinchen> [TOPIC] Roll Call
[19:00] <MootBot> New Topic:  Roll Call
[19:00] <mrevell> me
[19:00] <rockstar> me
[19:00] <Rinchen> me!
[19:00] <leonardr> me
[19:00] <al-maisan> me
[19:00] <mars> me
[19:00] <adeuring> me
[19:00] <schwuk> me
[19:00] <bac> me
[19:00] <sinzui> me
[19:00] <barry> me
[19:00] <cprov-afk> me
[19:00] <flacoste> me
[19:00] <BjornT> me
[19:00] <mpt> me
[19:00] <bigjools> me
[19:00] <statik> me
[19:00] <Rinchen> allenap and gmb send their apologies today
[19:00] <intellectronica> me
[19:00] <Rinchen> kiko-fud, SteveA_
[19:00] <kiko-fud> me
[19:01] <kiko> or course!
[19:01] <Rinchen> matsubara, ?
[19:01] <matsubara> me
[19:01] <abentley> me
[19:01] <salgado> me
[19:01] <Rinchen> releases team is here
[19:01] <flacoste> foundations is here
[19:01] <Rinchen> bugs appears to be here
[19:01] <Rinchen> thumper, ?
[19:02] <Rinchen> abentley, ?
[19:02] <kiko> tim's here, yeah
[19:02] <rockstar> abentley me'd
[19:02] <Rinchen> ah, good thanks
[19:02] <Rinchen> EdwinGrubbs, ?
[19:02] <abentley> Yeah, me
[19:02] <EdwinGrubbs> 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] <mthaddon> me
[19:02] <Rinchen>  * Doc Team report (mrevell)
[19:02] <herb> me
[19:02] <Rinchen> [TOPIC] Next meeting
[19:02] <MootBot> New Topic:  Next meeting
[19:03] <kiko> I won't be here!
[19:03] <Rinchen> same time same place kiko?
[19:03] <Rinchen> ok, so it's me and the rest of the team minus you and gmb
[19:04] <Rinchen> [AGREED] Next meeting same time, place on 3 July - kiko and gmb send apologies
[19:04] <MootBot> AGREED received:  Next meeting same time, place on 3 July - kiko and gmb send apologies
[19:04] <Rinchen> [TOPIC] Actions from last meeting
[19:04] <MootBot> New Topic:  Actions from last meeting
[19:04] <Rinchen> [AGREED] None
[19:04] <MootBot> AGREED received:  None
[19:04] <Rinchen> [TOPIC] Oops report (Matsubara)
[19:04] <MootBot> New Topic:  Oops report (Matsubara)
[19:05] <matsubara> Sorry, haven't prepared an oops report. I'll follow up with individuals.
[19:05] <Rinchen> boo hiss
[19:05] <kiko> !
[19:05] <kiko> well
[19:05] <kiko> I can make one up on the fly
[19:05] <kiko> I have one for bac and EdwinGrubbs: OOPS-907S114
[19:05] <kiko> I believe it's fixed, but is it really?
[19:06] <thumper> me
[19:06] <kiko> I have a fix for the RDF timeouts in my tree, will try and finish tonight
[19:06] <matsubara> kiko: I think that one is the one bac fixed as one of his BAD items on the test plan
[19:06] <kiko> very good
[19:06] <kiko> thumper,         6 /    0  BranchMergeProposal:+request-review
[19:06] <kiko> thumper, six timeouts on staging is really high
[19:06] <bac> kiko: actually that OOPS occurred during integration testing with the salesforce proxy -- an error on the far side.
[19:07] <kiko> bac, will it happen in production, though, and should it?
[19:07] <matsubara> bac, so that's not bug 242422?
[19:07] <kiko> thumper, can you look into that and see if it can be improved?
[19:07] <thumper> kiko: that was me seeing if the storm branch with __contains__ was there
[19:07] <bac> kiko:  it has been fixed in my integration work with surfous
[19:07] <kiko> thumper, oh, okay -- it works today?
[19:07] <kiko> bac, okay.
[19:07] <bac> matsubara: no, not part of bug 242422
[19:07] <thumper> kiko: I haven't tested today, only been awake for a few minutes
[19:07] <kiko> thumper, okay, if you could test I'm your fan
[19:08] <kiko> when you have a sec
[19:08] <kiko> BjornT, does your branch with +packages improvements live anywhere where somebody else could pick it up?
[19:08] <thumper> kiko: yes, works today
[19:08] <Rinchen> kiko just gave us a new t-shirt design "I'm your fan"
[19:08] <kiko> awesome
[19:08] <BjornT> kiko: well, it's landed
[19:08] <Rinchen> anything else kiko on oopses?
[19:08] <kiko> when appropriate!
[19:08] <kiko> BjornT, OOPS-907S177 :-/
[19:08] <kiko> BjornT, I thought there were additional fixes though
[19:09] <BjornT> kiko: someone could certainly pick it up. there is still a soyuz task open for the bug
[19:09] <kiko> BjornT, do you have any work done on it that you could share, or is that it?
[19:09] <danilos> (just in, jtv's network is down, but he smsed me to say that log(0) fix is awaiting review)
[19:09] <kiko> barry, will you have a fix for OOPS-907S44 by monday?
[19:09] <kiko> thanks danilos
[19:09] <kiko> danilos, log(0) fix? :)
[19:10] <barry> kiko: i'm working on it!
[19:10] <kiko> barry, that's not what I asked :)
[19:10] <barry> kiko: i know :)
[19:10] <kiko> heh
[19:10] <kiko> adeuring, do you have time to look at this many queries in OOPS-907EA192 -- though I believe I know what that one is, hard to fix
[19:10] <danilos> kiko: that's what jtv said "oopses about log(0)" :)
[19:10] <Rinchen> log(0) sounds like a productivity modifier :-)
[19:10] <BjornT> kiko: no, i didn't have time to get rid of the soyuz queries. the work in the view class is pretty much there. what is missing is methods for getting the information from the db.
[19:10] <kiko> wow
[19:10] <adeuring> kiko: yes
[19:11] <Rinchen> jtv just sms'd me with the same report
[19:11] <kiko> BjornT, thanks. bigjools, if you have a second left over tomorrow or monday, it's similar work to your +queue improvements and is a top-query page for us today.
[19:11] <SteveA_> hi
[19:11] <kiko> thumper, are there fixes already in place for OOPS-907EC70 and OOPS-907EB53 -- that's on edge which is kinda old.
[19:11] <kiko> that's it for me
[19:12] <thumper> lemmie check
[19:12] <Rinchen> [TOPIC] Critical Bugs (Rinchen)
[19:12] <MootBot> New Topic:  Critical Bugs (Rinchen)
[19:12] <Rinchen> Yay. We have none pending!
[19:12] <Rinchen> second week in a row iirc
[19:12] <kiko> well, wait till monday! :)
[19:12] <Rinchen> Good job folks
[19:12] <thumper> kiko: yes, both landed
[19:13] <kiko> thumper, you the man, **2. :)
[19:13] <Rinchen> [TOPIC] Bug tags
[19:13] <MootBot> New Topic:  Bug tags
[19:13] <Rinchen> we have one
[19:13] <kiko> let me guess
[19:13] <Rinchen> https://help.launchpad.net/TaggingLaunchpadBugs
[19:13] <kiko> package diffs! :)
[19:13] <Rinchen> codereview by matsubara
[19:13] <cprov-afk> kiko: again ?
[19:14] <kiko> heh
[19:14] <thumper> +1 to codereview
[19:14] <kiko> +1 to codereview
[19:14] <thumper> we are going to get a number of bugs :-)
[19:14] <kiko> though
[19:14] <mpt> a number? like 2?
[19:14] <kiko> is that confusable with stuff in picked up during our internal code review process?
[19:14] <thumper> mpt: have more than that already
[19:14] <mpt> ok :-)
[19:15] <Rinchen> As we expand the capabilities of LP Code Review, it might be worthwhile now to make this category slightly more generic.
[19:15] <Rinchen> and also to prevent any confusion with infrastructure code review
[19:15] <mpt> kiko, that problem applies to many things about Launchpad already (cf. the "Launchpad itself" hack)
[19:15] <intellectronica> why not merge-proposal. is that not the name we actually use in launchpad?
[19:15] <thumper> intellectronica: because we'd rather think of the thing as a code review of a proposed merge :)
[19:16] <matsubara> I think codereview is slightly more generic than merge-proposal
[19:16] <kiko> it's fine by me, either way -- didn't want to polemize!
[19:16] <Rinchen> to be consistent with the other tags, it should be "code-review"
[19:16] <statik> i always learn new words in this meeting
[19:16] <matsubara> I'm not fussed about the tag name too, I just want to group those bug reports and codereview was the first thing that came to my mind
[19:17] <Rinchen> I can't think of a more general term for branch actions of this sort so I'm +1 on "code-review"
[19:17] <Rinchen> matsubara, thumper can you live with the hyphen?
[19:18] <matsubara> danilos: you don't have any comment?
[19:18] <thumper> hyphen is good
[19:18] <matsubara> Rinchen: yes
[19:18] <Rinchen> any opposition?
[19:18] <kiko> go go go
[19:18] <Rinchen> [AGREED] "code-review" tag approved. matsubara to update page and tag
[19:18] <MootBot> AGREED received:  "code-review" tag approved. matsubara to update page and tag
[19:18] <Rinchen> [TOPIC] Operations report (mthaddon/herb)
[19:18] <MootBot> New Topic:  Operations report (mthaddon/herb)
[19:19] <herb> Thursday (2008-06-19): The last of the Launchpad machines were updated to hardy.
[19:19] <herb> Thursday (2008-06-19): Codebrowse was restarted a handful of times. It was suspected this was due to people browsing MySQL branches. Based on some of the emails we've seen today it seems that this is the case.
[19:19] <herb> Wednesday (2008-06-25): Codebrowse was moved to it's new server.
[19:19] <herb> Edge has been running with storm since Tuesday (2008-06-24) and seems to be doing well.
[19:19] <herb> We're release-critical as of the wee hours this morning, and we're scheduled for the new release late Monday / early Tuesday.
[19:19] <herb> There are 2 cherry picks waiting for approval (r6410 and r6451) and 1 that's been approved (r6530). We don't know yet when r6530 will be rolled.
[19:19] <herb> That's it from Tom and me unless there are questions.
[19:19] <mthaddon> er, unfortunately codebrowse had to be reverted from it's new server - mwhudson is working on it
[19:19] <kiko> herb, does it really need to be rolled out?
[19:20] <flacoste> herb: is one of those for the xmlrpc private server?
[19:20] <kiko> mthaddon, thumper: will the new codebrowse code rock the boat?
[19:20] <herb> kiko: we're trying to determine if it is necessary.
[19:20] <barry> flacoste: 6530
[19:20] <mthaddon> kiko, in what way?
[19:20] <thumper> kiko: what boat?
[19:20] <kiko> mthaddon, thumper: in a good way.
[19:21] <kiko> flacoste, statik: I'd like to know if that's really necessary or not, given the monday rollout
[19:21] <mthaddon> kiko, if it worked, yes - like I said, we had to revert, but mwhudson is working on it
[19:21] <kiko> mthaddon, oh, that was with the new code already?
[19:21] <mthaddon> kiko, yes
[19:21] <statik> kiko: i'm ok with waiting for monday
[19:21] <flacoste> statik, SteveA_: can the mailing list deployment wait until the roll-out?
[19:21] <beuno> FWIW, it seemed to be a problem with accesing branches over HTTP instead of locally, because it got moved to a seperate machine  :)
[19:22] <beuno> (Loggerhead that is)
[19:22] <beuno> and hi  :)
[19:22] <Rinchen> caching ftw ;-)
[19:22] <mthaddon> beuno, right, that was the problem (although that's what we were trying to do with it, so it's a problem that it's a problem)
[19:22] <Rinchen> Anything else for herb or mthaddon ?
[19:22] <mthaddon> Rinchen, er, no
[19:22] <SteveA_> flacoste: monday?
[19:23] <kiko> funtastic
[19:23] <kiko> mthaddon, flacoste: will you guys coordinate on the /@@ fix?
[19:23] <kiko> I am really excited about getting that rolled
[19:23] <flacoste> kiko, mthaddon: yes
[19:23] <kiko> I think it will make a huge difference
[19:23] <mthaddon> sounds good on /@@/
[19:23] <kiko> mthaddon, note that the /@@ stuff also needs the cache-control jimmied in
[19:23] <flacoste> SteveA_: yeah, kikos wants to hold off the cherry pick and wait for the regular roll-out
[19:24] <SteveA_> if it's just monday, then okay
[19:24] <mpt> kiko, if you start caching /@@/ at all, you could get six times as much benefit by fetching all those resources from launchpad.net rather than from the same hostname as the rest of the page (e.g. code.launchpad.net)
[19:24] <mthaddon> SteveA_, monday evening my time :)
[19:24] <SteveA_> fine
[19:25] <kiko> mpt, that requires changing paths everywhere in our templates though.
[19:25] <mpt> hmm
[19:25] <flacoste> kiko: we could do it at the apache level
[19:25] <mpt> maybe it could redirect?
[19:25] <flacoste> yep
[19:25] <flacoste> 301
[19:25] <kiko> mpt, flacoste: wouldn't that be slow as slow?
[19:26] <mpt> but then maybe a redirect is slower
[19:26] <mpt> yeah
[19:26]  * mpt shrugs
[19:26] <flacoste> not really
[19:26] <kiko> for me, a redirect is very slow
[19:26] <flacoste> only the first time
[19:26] <flacoste> well
[19:26] <statik> fetching static resources from a separate server is faster because it bypasses the browser throttling of how many simultaneous connections to a server are made
[19:26] <kiko> not for the first time -- every time code.l.n/@@/foo is hit, we'd be 301ing him back to l.n/@@/foo
[19:26] <statik> i think redirecting would kill any performance gains
[19:26] <flacoste> browser should cache the redirect
[19:27] <kiko> I dunno if any browser does that, and not persistently
[19:27] <flacoste> anyway, fixing the path in all of the templates is outside the current scope
[19:27] <flacoste> so, it's redirect-away or forget this
[19:27] <mthaddon> flacoste, how much work would that really be?
[19:27] <flacoste> mthaddon: fixing all the templates?
[19:27] <mthaddon> yeah
[19:28] <flacoste> well
[19:28] <flacoste> maybe not that much
[19:28] <statik> i'll volunteer to help mass-editing some templates to get a nice speedup for our users
[19:28] <kiko> it's annoying though, putting a tal: expression for each /@@ in there.
[19:28] <kiko> not sure.
[19:28] <mpt> yeah, that would annoy me
[19:28] <kiko> flacoste, statik: we could do that post-1.2.6 anyway.
[19:28] <statik> totally
[19:29] <kiko> the most important thing is serving that stuff statically
[19:29] <kiko> the rest is icing.
[19:29] <mpt> Perhaps make it part of the template interpretation layer
[19:29] <flacoste> ok
[19:29] <flacoste> mpt: dream on :-)
[19:29]  * mpt handwaves
[19:29] <flacoste> template interpretation layer = TAL engine = not-customizable
[19:30] <flacoste> or rather !extensible
[19:30] <Rinchen> I think we're ready to move on
[19:30] <mpt> not in the TAL engine
[19:30] <mpt> maybe just before that
[19:30] <mpt> anyway
[19:30] <mpt> sorry for the digression
[19:30] <Rinchen> I think that was...thank you herb and mthaddon
[19:30] <Rinchen> [TOPIC] DBA report (stub)
[19:30] <MootBot> New Topic:  DBA report (stub)
[19:30] <Rinchen> stub is not here
[19:30] <Rinchen> so
[19:30] <Rinchen> [AGREED] Rinchen to email stub for dba report
[19:30] <MootBot> AGREED received:  Rinchen to email stub for dba report
[19:30] <Rinchen> [TOPIC] Sysadmin requests (Rinchen)
[19:30] <MootBot> New Topic:  Sysadmin requests (Rinchen)
[19:31] <Rinchen> Is anyone blocked on an RT or have any that are becoming urgent? I know about Thumper's
[19:31] <intellectronica> yeah, we need api.staging.l.n set up
[19:31] <mthaddon> intellectronica, in process
[19:31] <Rinchen> matsubara, your shot factory request has been denied.  Speak to me after the meeting for alternatives.
[19:31] <bigjools> Rinchen: the one I talked about in the week with you
[19:31] <intellectronica> mthaddon: fantastic
[19:31] <matsubara> Rinchen: ok.
[19:31] <mthaddon> intellectronica, btw, it'd be nice to have a bit more lead time on RTs like that if possible
[19:32] <cprov-afk> bigjools: https://rt.admin.canonical.com/Ticket/Display.html?id=31016
[19:32] <SteveA_> we should have a checklist for this stuff
[19:32] <SteveA_>  - changes to DNS
[19:32] <intellectronica> mthaddon: i realise that
[19:32] <SteveA_>  - access to new machines
[19:32] <SteveA_>  - extra memory / disk resources
[19:32] <thumper>  - email processing changes
[19:32] <SteveA_> etc.
[19:33] <Rinchen> bigjools, cprov-afk - need a due date for that if you could please
[19:33] <SteveA_> and go through that when planning changes
[19:33] <SteveA_> to give IS advance notice
[19:33] <bigjools> Rinchen: it's for 1.2.6
[19:33] <SteveA_> and note that many DNS changes need to apply to both lpnet and edge and staging etc.
[19:33] <statik> i just want to say that our IS and OSA team rocks
[19:34] <statik> i don't care who knows it
[19:34] <intellectronica> they totally do!
[19:35] <mthaddon> too kind, too kind
[19:35] <Rinchen> bigjools, I've updated the ticket and pinged elmo
[19:35] <bigjools> thanks Rinchen
[19:36] <Rinchen> SteveA_, actually I think those sections are in the roll-out template
[19:36] <Rinchen> but not to that level of detail
[19:36] <Rinchen> [TOPIC] New packages required (salgado)
[19:36] <MootBot> New Topic:  New packages required (salgado)
[19:36] <kiko> Rinchen, would be useful to update that, though the problem I see is that the roll out of APIs spanned more than 4 months, so..
[19:36] <salgado> any new packages this week?
[19:36] <kiko> I have a request.
[19:36] <kiko> salgado, can we use P3As for lp-meta-deps?
[19:37] <kiko> pretty please
[19:37] <thumper> salgado: I think mwh said there are new deps for loggerhead
[19:37] <thumper> salgado: simpletal and paste
[19:37] <bigjools> Pimp Your P3A
[19:37] <salgado> kiko, can we sign packages there?
[19:37] <Rinchen> kiko, SteveA - I'll update the roll-out template with that info
[19:37] <salgado> oh, Private PPAs
[19:37] <kiko> salgado, not yet. but you can rsync and sign afterwards! :)
[19:37] <cprov> salgado: you can, we can't sign repositories.
[19:38] <cprov> salgado: mirror & signing is trivial, though
[19:38] <salgado> we haven't done so because people have complained about that
[19:38] <kiko> salgado, help dogfood p3a!
[19:38] <kiko> we'll let you use them free of charge, I checked with mark
[19:38] <kiko> special offer
[19:38] <salgado> thekorn, I need a bug report
[19:38] <bigjools> cheap at half the price
[19:38] <salgado> thumper, ^
[19:39] <thumper> salgado: I'll pass that on to mwh
[19:39] <thumper> salgado: filed against what?
[19:39] <salgado> thumper, meta-lp-deps
[19:39] <thumper> k
[19:39] <Rinchen> salgado, I wanted to thank you for updating these packages.
[19:39] <SteveA> thanks Rinchen
[19:39] <salgado> Rinchen, you're welcome
[19:39] <salgado> kiko, I can give it a try.  where should I look for docs about it?
[19:40] <statik> ooh, i want to mirror and sign my own PPA
[19:40] <kiko> salgado, have a quick call with julian, it's all pretty easy
[19:41] <kiko> thanks
[19:41] <cprov> statik: someone posted a nice script sometime ago in lp-user ML (debmirror-based)
[19:41] <statik> cprov: thanks, will look for it
[19:41] <Rinchen> anything further for salgado?
[19:42] <Rinchen> [TOPIC] A top user-affecting issue (mrevell)
[19:42] <MootBot> New Topic:  A top user-affecting issue (mrevell)
[19:42] <mrevell> Hi
[19:42] <mrevell> Again the theme this week has been people who have subscribed to all Ubuntu bugs, only to find they don't know how to unsubscribe. We also get quite a few requests for help with Ubuntu to feedback|help@launchpad.net
[19:42] <mrevell> I've been wondering if an auto-reply would enable people to help themselves, before I'm able to reply to them.
[19:42] <mrevell> I've popped a suggested auto-reply email on the team list and would appreciate your comments.
[19:42] <mrevell> Other than, nothing outstanding as a user-affecting issue this week. Thanks Rinchen.
[19:43] <Rinchen> thanks mrevell
[19:43] <Rinchen> anything for mrevell ?
[19:43] <intellectronica> mrevell: i think that these are two separate issues
[19:43] <intellectronica> if users subscribe to ubuntu by mistake, it may be that the ui is not clear enough
[19:43] <mrevell> intellectronica: Ubuntu help requests and bug unsubscrive requests are, yes.
[19:44] <mpt> There are (multiple?) bug reports about this
[19:44] <SteveA> I believe we have plans for a UI to show you all subscriptions to mail, in one straightfoward page
[19:44] <intellectronica> indeed, and i even think we have a pretty good idea of how it should be solved
[19:44] <SteveA> whether these are mailing lists or subscriptions that send mail
[19:44] <SteveA> and this page will be included in the footer of all emails
[19:44] <Rinchen> the issue is actually a bit compounded by gmail which treats the "you are receiving this bug report because" message as a quote and collapses it so you don't see it unless you know enough to expand the section
[19:44] <SteveA> well, a link to hte page
[19:44] <cprov> statik: I lied, the script is in our 'bug #1' -> https://bugs.edge.launchpad.net/soyuz/+bug/125103
[19:45] <intellectronica> Rinchen: maybe we should change the formatting?
[19:45] <Rinchen> intellectronica, it's crossed my mind before. I was waiting to see if there were other reports of this before I suggested it.
[19:45] <Rinchen> we know that many LP users have gmail accounts
[19:46] <Rinchen> don't we barry :-)
[19:46] <mrevell> Sure, we plan to show all subscriptions but right now we don't. In the the time between now and our providing that, lots of people will remain confused as to how to unsubscribe. As soon as we implement that, or de-confuse the UI, I think an autoreply may help people find the answer they need. Lots of support contact addresses do the same sort of thing.
[19:46] <intellectronica> Rinchen: let's file a bug, if there isn't one yet, so that we see if there's much activity
[19:46] <barry> Rinchen: indeed
[19:46] <intellectronica> i use gmail, but i always considered the folding of that footer a feature!
[19:46] <mpt> bug 110953, bug 89938, bug 217337
[19:47] <Rinchen> intellectronica, you are me to file the bug?
[19:47] <Rinchen> s/are/or
[19:47] <intellectronica> Rinchen: i'd love to be you. for now i'll setlle for filing bugs ;)
[19:47] <Rinchen> lol
[19:48] <Rinchen> [ACTION] Rinchen to file bug on gmail footer auto-collapse as possible reason for inability of users to know how to unsubscribe from bug reports
[19:48] <MootBot> ACTION received:  Rinchen to file bug on gmail footer auto-collapse as possible reason for inability of users to know how to unsubscribe from bug reports
[19:48] <Rinchen> [TOPIC] Doc Team report (mrevell)
[19:48] <MootBot> New Topic:  Doc Team report (mrevell)
[19:49]  * Rinchen nudges mrevell.
[19:49] <mrevell> This week I've continued work on the user guide. Many thanks to jtv for his feedback on the translations section. No news on the doc team, I'm afraid, although I expect they will offer great help in reviewing the user guide ove the coming weeks
[19:49] <mrevell> sorry Rinchen, was hunting for the tomboy note
[19:49] <Rinchen> We also have had a member of the doc team file a bunch of bugs on the updated help wiki
[19:49] <Rinchen> that was helpful
[19:50]  * sinzui -> afk to get automobile
[19:50] <mrevell> Yes. And it's worth noting, if you haven't seen already, that help wiki is now running MoinMoin 1.6
[19:50] <kiko> cool
[19:50] <Rinchen> Anything further for mrevell?
[19:50] <mrevell> so if you notice anything odd, please let me or Rinchen know.
[19:50] <Rinchen> ok, sorry for being a bit over today
[19:50] <Rinchen> blame kiko ;-)
[19:50] <Rinchen> Thank you all for attending this week's Launchpad Developer Meeting. See the channel topic for the location of the logs.
[19:50] <Rinchen> #endmeeting
[19:50] <MootBot> Meeting finished at 13:51.
[19:51] <mrevell> thanks rinch
[19:51] <SteveA> thanks!
[19:51] <mrevell> thanks Rinchen
[19:51] <intellectronica> thanks Rinchen
[19:51] <al-maisan> thank
[19:51] <rockstar> thanks
[19:51] <al-maisan> s
[19:51] <mpt> thanks Rinchen
[19:51] <kiko> woo, I take the blame
[19:57] <Rinchen> you're the default :-0