[13:23] <warp10> Hi *
[15:44]  * beuno pokes mrevell 
[15:44] <mrevell> Hey beuno
[15:45] <beuno> hey  :)
[15:45] <beuno> will you be around in ~30 minutes?
[15:45] <beuno> I want to grab Rinchen and mpt, and try to do something sensible with help
[15:45] <mrevell> beuno: Sure, I'll be around for just about all of th rest of today.
[15:45] <mrevell> something sensible?
[15:45] <Rinchen> like make it work? :-)
[15:46] <beuno> Rinchen, it already works, so it has that much sense now
[15:46] <beuno> I just want it to be... well... better than average  :)
[15:46] <beuno> but I have to wrap something up, and then, I'll start the flamewar
[15:47] <mrevell> heh
[16:28]  * beuno poked mrevell, Rinchen and mpt 
[16:28] <beuno> *pokes
[16:28] <beuno> so...  help
[16:28] <mpt> hi
[16:28] <beuno> this is what happens today:
[16:29] <beuno> you click on something (ideally, an icon), and a div appears in the center of your screen
[16:29] <beuno> 600*400px aprox
[16:29] <beuno> and that embeds a URL in the iframe
[16:30] <beuno> which, AFAIK, will be help.lp.net
[16:30] <mpt> https://help.launchpad.net/SomeThing?action=print
[16:30] <beuno> yes
[16:30] <beuno> well
[16:30] <beuno> embeding that has a few problems
[16:30] <beuno> 1) if people click on a link, they'll navigate withing the iframe, which sucks terribly
[16:31] <beuno> 2) we can't control very much how it's presented
[16:31] <beuno> 3) we depend on an external site to load help
[16:31] <beuno> 4) I hate iframes
[16:31] <beuno> so, that's the first issue
[16:31] <beuno> thoughts?
[16:32] <mpt> (1a) We can't reach into the page with JS to make navigating do the right thing, because help.launchpad.net is a different domain so browsers won't give us permission to do that
[16:34] <mpt> (There's also the reasons previously discussed when LaunchpadHelp was being written: (5) the help is routinely a week or six behind the actual interface, (6) the help doesn't update at the same time as a rollout. Neither of which are mrevell's fault at all, it's just emergent from the process.)
[16:35] <mpt> mrevell?
[16:35] <mpt> Rinchen?
[16:41] <mrevell> mpt: I'm hoping that we can improve the process so that I'm involved much earlier in a feature's development, in order to provide UI and help text.
[16:42] <mrevell> Also, my intention is to use specially written pages for the in-line help - so, perhaps /QuickHelp/BugSupervisor or something similar. I think we'd discussed that previously
[16:42] <mpt> mrevell, right, the latter is what I was asking for an example of this morning
[16:43] <mrevell> mpt: Yeah, although obviously we have none of that right now so I pulled out a page of what I imagine will be the upper range of the length we can expect.
[16:43] <beuno> well, that mitigates the problem, but doesn't solve it
[16:44] <beuno> we still have an external page
[16:44] <beuno> no control over it
[16:44] <beuno> we have to pull a lot of useless HTML to show a few characters
[16:44] <beuno> external site, etc
[16:44] <beuno> so, the solution to that would be to have the inline help in the code base
[16:45] <beuno> make it simple for mrevell to update it
[16:45] <beuno> but that would involve bzr to some extent
[16:45] <beuno> that would solve all the problems above  :)
[16:45] <mrevell> I'm happy to use bzr
[16:46] <beuno> \o/
[16:46] <mrevell> I've forwarded you both an email that Andrea Corbellini, a Launchpad doc team member, sent me, with some ideas on how to manage inline help.
[16:46] <Rinchen> howdy, someone call?
[16:46] <mpt> Rinchen, yes, please read the last 20 mins
[16:48] <beuno> damn, Andrea really went great lengths to do the script...
[16:48] <mpt> hmm
[16:49] <mpt> Is that converting wikitext into HTML?
[16:49] <beuno> it's...
[16:49] <beuno> well, doing a lot of regex
[16:49] <beuno> it guesses the HTML
[16:50] <Rinchen> well, we could right a quick macro which looks for control sections  like  inlinehelp{{{  some help }}} and then call that
[16:50] <beuno> not sure this is the right fit, and we definetly don't want to hit help.lp.net every time you need inline help
[16:50] <Rinchen> so  ?=print-inlinehelp or something
[16:50] <Rinchen> another option is just to put the help in a branch
[16:50] <mrevell> Rinchen: I've sent you Andrea's email, as an FYI
[16:51] <Rinchen> and I give mrevell access to the source code
[16:51] <beuno> Rinchen, again, that will be a bit better, but won't solve the problem at large
[16:51] <beuno> help branch would be great
[16:51] <mrevell> Rinchen: Would we be limited to making changes at a roll-out?
[16:51] <Rinchen> mrevell, yes
[16:51] <Rinchen> mrevell, although edge would update when the db is not oepn
[16:51] <Rinchen> open
[16:51] <mrevell> right
[16:52] <mpt> We allow cherrypicks for urgent bug fixes
[16:52] <Rinchen> beuno, what would not be solved by bzr?
 but that would involve bzr to some extent
 that would solve all the problems above  :)
[16:52] <Rinchen> I am con fuse ed
[16:52] <mpt> Could we allow piggybacking cherrypicks for help text, on the grounds that changing help text is unlikely to cause bugs by itself?
[16:53] <beuno> Rinchen, that would be the second issue, which doesn't change anybody's workflow, it's just a different wat of showing the help
[16:53] <beuno> (I haven't presented that yet)
[16:54] <Rinchen> in an ideal world, the help wiki does not exist.  LP is intuitive and where someone needs some extra hand-holding, we have that inside LP right where the user might need it
[16:54] <mrevell> Is it technically difficult/undesirable to have a second bzr branch that's only for inline help and that I could push to outside of the normal roll-out process? If it's only text, like you say mpt, it's unlikely to introduce bugs.
[16:54] <Rinchen> we could have the help text as sourcecode mpt
[16:54] <Rinchen> still uses PQM but would allow it to be a separately managed branch
[16:56] <mpt> If putting the help text under Bazaar's control is to solve (or reduce) the problem of help text being out of sync with the code, then it needs to be possible for a single commit to change both Launchpad code and help text.
[16:56] <mpt> Is it possible to do that with sourcecode/?
[16:57] <Rinchen> hmmm just wondering about that. Let's ask Francis
[16:58] <Rinchen> asked on -code.  I think the answer is no
[16:58] <Rinchen> I think it's either trunk or sourcecode but not both
[16:58] <Rinchen> since the merge locations are different
[16:59] <Rinchen> alternatively we can make a  lib/canonical/launchpad/help directory and just reference the help text out of there
[17:00] <Rinchen> I'd very much like to have the help text as a separate file rather than having to edit code to change the help text
[17:00] <Rinchen> will also make it easier to translate into another language when we decide to do that
[17:00] <Rinchen>  (when/if ... that is)
[17:00] <mrevell> And it'll reduce the possibility of me introducing errors into the code...
[17:01] <beuno> yes, it should be in a seperate file, I don't see any reason for it not to
[17:01] <mrevell> y'know obviously I'd be super careful etc
[17:01] <beuno> a .py that can server specifically inline help
[17:02] <beuno> or separate that into content + python that does serving magic
[17:02] <beuno> so then we'd just request lp.net/inlinehelp?new_bug
[17:02] <beuno> or something like that
[17:02] <beuno> almost wouldn't have to change the current frontend at all for that  :)
[17:04] <beuno> ok, so, if that can be done, leaving aside implementation details
[17:04] <beuno> here's the second bit
[17:04] <beuno> I think inline help should be placed next to what you're helping about
[17:05] <Rinchen> ideally.
[17:05] <Rinchen> that's the biggest problem with the help wiki at this point
[17:05] <Rinchen> you have to go off and search for it
[17:05] <beuno> a sort of bubble that clearly starts at the item you're refering to
[17:05] <beuno> right now we just show it in the center
[17:05] <beuno> which is less than ideal IMHO
[17:05] <Rinchen> there's another issue where today we design help around an entire page or workflow
[17:06] <Rinchen> rather than on a particular field or set of buttons on a particular page
[17:06] <beuno> right, that should change
[17:06] <Rinchen> I'm only in partial agreement there
[17:06] <Rinchen> we still need to educate users on the overall flow
[17:06] <beuno> also, there a few things that we discussed on the 3.0 UI sprint which makes this much more interesting
[17:06] <Rinchen> How to get from A to D for example
[17:06] <beuno> Rinchen, well, there is a few ideas on that
[17:06] <mrevell> Yeah, I don't see the need for the user guide going away.
[17:06] <beuno> the one I like the most
[17:07] <beuno> is, the first time a user lands on a report a bug page
[17:07] <mrevell> LP is far more complex than the average web app, so inline help has a really useful place but so does the user guide
[17:07] <beuno> you popup inline help on each item that's relevent through the process
[17:07] <beuno> so you hand-hold them to the end
[17:07] <beuno> that can be repeated until the user thinks he's ready
[17:08] <beuno> also, the same thing can be applied for frequent users which face new features
[17:08] <beuno> so the actual global help is lp itself
[17:08] <beuno> and not a page with screenshots
[17:08] <beuno> of course, it's a long way to get there
[17:09] <beuno> but having inline help short and to the point, clearly pointing at what the help is for, is a good start
[17:09] <mpt> http://www.uxmatters.com/MT/archives/images/lw5-07_figure5.gif
[17:10]  * Rinchen can just see the requests on -users and #launchpad now.  "How do I turn off these damn help bubbles?!?!
[17:10] <mpt> http://www.uxmatters.com/MT/archives/images/lw5-07_figure8.gif
[17:10] <Rinchen> yeah, I like the ballon help best
[17:10] <beuno> Rinchen, well, just show them the first time a user goes through a process
[17:10] <Rinchen> it takes less space than a collapsible area
[17:11] <beuno> and then make it easy for them to see them again
[17:11] <Rinchen> beuno, that doesn't work around here unfortunately
[17:11] <mrevell> beuno: I like the idea but I'm concerned that our processes don't take in just one page
[17:11] <Rinchen> beuno, we have LOTS of people who can't even unsubscribe from a mailing list which, in the footer, is a link to unsubscribe
[17:11] <mrevell> I love the idea of having a prominent link to find out more about something that's new to the user but I'm not sure an automated run-through would be anything less than frustrating.
[17:11] <mpt> I think the overall problem here is that in most parts of Launchpad, we're so far from the point where adding help is the best way to address any particular usability problem, that we don't have good examples of help text to work with
[17:12] <mpt> so we're trying to imagine various presentations of text that doesn't exist yet :-)
[17:12] <Rinchen> there is that too (both mpt and mrevell)
[17:12] <Rinchen> The idea that I favour most is to have bubble help on anything that a user can change
[17:12] <Rinchen> and then a distinct link to "find out more" which takes them to a users guide
[17:13] <mrevell> When we've discussed the help spec in the past, the idea was always - AFAIK - to do our best to make 1. the UI intuitive, 2. the UI text sufficiently clear and 3. use help text on those parts of the page where you just can't get all the explanation into the UI text.
[17:13] <beuno> right, that's all I think we can do today
[17:13] <Rinchen> and that find out more could actually be in the bubble help for that mater
[17:13] <mpt> So, one good example that could be written right now is what "Convert to question" means in a bug report
[17:13]  * beuno has plans for the future
[17:13] <mrevell> mpt: Yeah, a good example.
[17:13] <mpt> because we can say quite confidently that adding explanatory text inline would be giving that link undue prominence
[17:14] <mpt> so adding popup help of some form *is* the best way to make it more understandable
[17:14] <mpt> So, maybe mrevell could write up a paragraph or two for that specific topic
[17:14] <mpt> then we can use that as an example for the popup help?
[17:14] <mrevell> Sure.
[17:15] <mpt> then explore alternative ways of presenting it
[17:15]  * Rinchen wonders if putting the popup help text would best be done in the interface definition.
[17:15] <Rinchen> would existing in 1 place but could be served on multiple pages without duplication
[17:16] <mpt> Rinchen, that might make it more difficult to make it context-sensitive (e.g. including the project name, or your Launchpad ID in bzr commands, etc)
[17:17] <Rinchen> dunno mpt. we'd have that in the browser files when calling the page
[17:17] <Rinchen> but it would certainly limit how much you could customize the text for a particular page
[17:17] <Rinchen> I'm counting on the fact that it's a standard across the system so the definition and use doesn't change
[17:18] <Rinchen> there's no reason we couldn't take the Interface help text and modify it on that particular page
[17:18] <Rinchen> s/on/for
[17:18] <Rinchen> but that does sound like too much work
[17:19] <beuno> right.  You're subscribing to ${project} and will recieve notifications for ${bug title}
[17:19] <beuno> doesn't seem *that* complicated
[17:20] <beuno> some thought will have to go into each piece of help
[17:22] <Rinchen> yeah, I was thinking about that beuno ... just encode substitution variables in the help text itself but there are issues then for anonymous users also because we might find that not all contexts have the variables defined
[17:22] <Rinchen> that doesn't mean it won't work
[17:22] <beuno> Rinchen, right. Start with public variables
[17:22] <Rinchen> it just means we'd have to do some testing and ensure if there are cases we'd find them and make corrections
[17:22] <beuno> and make the system more complex as you go
[17:24] <Rinchen> if we want to tinker with the interfaces in any fashion whatsoever, we need to get a proposal written and get that out to the LP dev team for technical review
[17:26] <beuno> cool, although I won't get to that this week, so that'll probably end up on mpt's side
[17:26]  * beuno ducks
[17:28] <mpt> -quack-
[17:40] <Rinchen> so, do we have a plan then?
[17:40] <Rinchen> beuno, you'll write up the concept?
[17:41] <Rinchen> and perhaps pass it on to mpt and mrevell ?
[17:41] <Rinchen> and for the new-comers.. context sensitive help in launchpad as bubbles :-)
[17:42] <beuno> Rinchen, sure, I'll give it a go and pass it down
[17:42] <beuno> I'll split it up into "what can be done now" and "what we can do the in the future"
[17:42] <Rinchen> nifty.  I think the existing spec we have lacks implementation details..but admittedly I haven't read it since March
[17:43] <beuno> the latter is something I'm suppose to work on anyways, if sabdfl answers my email soon  :)
[17:49] <Rinchen> nifty thanks beuno
[18:57] <statik> hewwo
[18:57] <Rinchen> how D
[18:58] <Rinchen> statik, did you let knmurphy in here? :-)
[18:59] <Rinchen> someone go poke Francis please
[18:59] <Rinchen> we're going to have a short meeting I think today
[18:59] <Rinchen> a bunch of folks are attending conferences and such
[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:01. 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] <Rinchen> moo
[19:00] <mpt> me
[19:00] <adeuring> me
[19:00] <mthaddon> me
[19:00] <gmb> meow
[19:00] <spm> me
[19:00] <mars> me
[19:00] <barry> me
[19:00] <herb> woof
[19:00] <bac> me
[19:00] <salgado> me
[19:00] <intellectronica> moi
[19:00] <BjornT> me
[19:00] <flacoste> me
[19:00] <mrevell> me
[19:00] <sinzui> me
[19:00] <cprov-lunch> me
[19:00] <leonardr> me
[19:01] <statik> me
[19:01] <Rinchen> I have apologies from kiko Steve  Diogo Schwuk Thumper Danilos Muharem
[19:01] <jtv> me
[19:01] <jtv> danilo's off this week
[19:01] <Rinchen> ok, Releases Team is here
[19:01] <EdwinGrubbs> me
[19:01] <statik> lpcomm is here
[19:02] <BjornT> allenap: ping
[19:02] <bigjools> me
[19:02] <flacoste> barry, mars: ping?
[19:02] <barry> flacoste: i me'd before you got here :)
[19:02] <mars> re-moo
[19:02] <stub> me
[19:02] <barry> mii
[19:02] <jtv> มี
[19:02] <flacoste> barry, mars: yeah, sorry :-)
[19:02] <flacoste> Foundations is here
[19:03] <Rinchen> looks like abently is also not here
[19:03] <Rinchen> and soyuz is here
[19:03] <Rinchen> great.. of we go
[19:03] <Rinchen> [TOPIC] Agenda
[19:03] <MootBot> New Topic:  Agenda
[19:03] <allenap> me
[19:03] <Rinchen>  * Next meeting
[19:03] <Rinchen>  * Actions from last meeting
[19:03] <Rinchen>  * Oops report (sinzui)
[19:03] <Rinchen>  * Critical Bugs (Rinchen)
[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:04] <Rinchen>  * Doc Team report (mrevell)
[19:04] <mthaddon> Rinchen, (mthaddon/herb/spm)
[19:04] <Rinchen> [TOPIC] Next meeting
[19:04] <MootBot> New Topic:  Next meeting
[19:04] <mrevell> I won't be here next week. I shall appoint someone to take my place for the user-affecting issue.
[19:04] <Rinchen> thanks mrevell
[19:04] <Rinchen> next mtg is the 17th same time location
[19:04] <Rinchen> anyone else know ahead of time they will be otherwise engaged?
[19:05] <Rinchen> ok.
[19:05] <Rinchen> [AGREED] Next meeting the 17th.  Apologies from mrevell
[19:05] <MootBot> AGREED received:  Next meeting the 17th.  Apologies from mrevell
[19:05] <Rinchen> [TOPIC] Actions from last meeting
[19:05] <MootBot> New Topic:  Actions from last meeting
[19:05] <Rinchen> none!
[19:05] <Rinchen> [TOPIC] Oops report
[19:05] <MootBot> New Topic:  Oops report
[19:05] <Rinchen> we don't have a full report today
[19:05] <Rinchen> sinzui, do you have anything in particular to discuss?
[19:05] <Rinchen> thanks to sinzui for covering for matsubara this week
[19:05] <sinzui> I'm standing in for matsubara. I'd like to bring 4 classes of opps to you attention. I don't think any are high priority, but they are dominating the reports I have seen this week:
[19:05] <sinzui> https://bugs.edge.launchpad.net/launchpad/+bug/52574
[19:05] <sinzui> https://bugs.edge.launchpad.net/launchpad/+bug/246591
[19:05] <sinzui> https://bugs.edge.launchpad.net/launchpad/+bug/48464
[19:05] <sinzui> https://bugs.edge.launchpad.net/launchpad/+bug/246932
[19:07] <Rinchen> any takers on those?
[19:07] <Rinchen> mars, perhaps on the last one: search ?
[19:08] <Rinchen> flacoste, any idea on the zope item?
[19:08] <gmb> I could take 48464, though I doubt I'd be able to get to it before the rollout.
[19:08] <flacoste> Rinchen: not on the radar until we upgrade
[19:08] <mars> Rinchen, sorry, my plate is full of 2.0
[19:09] <Rinchen> gmb, that's ok.  I just like finding someone to investigate these further.
[19:09] <sinzui> I'm not convinced that any of these oops are more important than our current work
[19:09] <gmb> Rinchen: In that case, I'll look into it, but I don't think it's urgent.
[19:09] <Rinchen> I agree
[19:09] <Rinchen> thanks gmb
[19:10] <Rinchen> sinzui, would you be so kind as to send the list above to matsubara via email please?
[19:10] <sinzui> I will
[19:10] <Rinchen> great thanks.
[19:10] <Rinchen> Anything for sinzui or any other comments on the oopses above?
[19:10] <Rinchen> ok then
[19:11] <Rinchen> [TOPIC] Critical Bugs (Rinchen)
[19:11] <MootBot> New Topic:  Critical Bugs (Rinchen)
[19:11] <Rinchen> [LINK] https://bugs.edge.launchpad.net/launchpad/+bug/246524
[19:11] <Rinchen> sinzui, thanks for working on this.  What's left to do on this one?
[19:11] <MootBot> LINK received:  https://bugs.edge.launchpad.net/launchpad/+bug/246524
[19:11] <gmb> Hah.
[19:12] <sinzui> I have a partial fix for this in review
[19:12] <Rinchen> sinzui, k. I see there are some newer comments in the bug so thanks for that
[19:12] <Rinchen> sinzui, need any assistance from anyone on this?
[19:12] <sinzui> the user who was locked out this morning was from a differnent scenario, So I believe work needs to be done
[19:13] <sinzui> I think the next branch will be easier/faster since I added test infrastructure
[19:14] <Rinchen> ok, I'll leave this one in your capable hands then.  Thanks.
[19:14] <Rinchen> [TOPIC] Bug tags
[19:14] <MootBot> New Topic:  Bug tags
[19:14] <Rinchen> we have one
[19:14] <Rinchen> https://help.launchpad.net/TaggingLaunchpadBugs
[19:14] <Rinchen> regression proposed by mpt
[19:14] <Rinchen> mpt, I see what you are going for here but I'm not convinced by the evidence that it's sufficient to warrant a bug tag.
[19:15] <Rinchen> Does anyone have any questions or comments on this proposed tag?
[19:15] <Rinchen> Team leads?
[19:15] <intellectronica> what use do you imagine for it?
[19:15] <cprov-lunch> Rinchen: how do we track regressions currently ?
[19:16] <intellectronica> it may be interesting for tracking, but otherwise i don't see how useful it is to tag regressions
[19:16] <mpt> I explained the use on the wiki page
[19:16] <cprov-lunch> Rinchen: well, I know we don't, but would it be good for us if we start doing it ?
[19:16] <BjornT> i don't see much use of such a tag
[19:16] <Rinchen> cprov-lunch, we don't currently other than in the description text or follow-on comments
[19:16] <mpt> If Importance was reliably set for bugs, knowing that something was a regression would tend to increase its importance
[19:17] <mpt> because all other things being equal, users are angrier about regressions than they are about other bugs that would otherwise be the same importance.
[19:17] <mars> intellectronica, I thought it useful for tracking bad 2.0 UI changes
[19:17] <barry> tags help find bugs, i'm not sure this tag helps in that case
[19:17] <cprov> Rinchen: I would like to see some numbers, but I don't know if it's a valid use-case for a tag.
[19:17] <mpt> The flaw in that argument is, that we don't currently reliably set Importance for bugs.
[19:17] <BjornT> mpt: shouldn't the description make clear that it's a regression?
[19:17] <Rinchen> We also at times create "regressions" when we change how things work... such as the UI
[19:17] <mars> Rinchen, right
[19:18] <mpt> BjornT, sure, but you could say that about almost all the tags we already have too.
[19:18] <BjornT> mpt: except that, as barry said, tags are used to find bugs
[19:18] <mpt> Ah, but the other tags we have are used for searching
[19:18] <mpt> right, right
[19:18] <mpt> good point
[19:18] <jtv> In theory, a regression should be a test failure, not a bug.
[19:18] <statik> i'm -1 on regressions, as it doesn't mean much without a lot of subjective interpretation
[19:18] <Rinchen> I say regressions in quotes because to us it is a change that has been thought-out but users may not approve and call it a bug
[19:19] <statik> where the other tags, like feeds or ui cannot really be debated when they apply :)
[19:19] <mars> statik, good point
[19:19] <BjornT> statik: well, ui can be debated :)
[19:19] <mpt> jtv, in practice, there is much our tests don't test, including but not limited to CSS and JavaScript
[19:20] <stub> So this is to work around us not setting Importance correctly. How come setting a tag is easier?
[19:21] <Rinchen> Ok,  Based on the discussion, I'm going to declare this one, at this point in time, not approved.  Sorry mpt.  Please keep up the proposals though.  If you have more justification to this you can add it to the wiki page and propose it again
[19:21] <mpt> ok
[19:21] <Rinchen> [AGREED] regressions tag decline for now.
[19:21] <MootBot> AGREED received:  regressions tag decline for now.
[19:21] <Rinchen> mpt, please update the wiki.  thanks
[19:21] <Rinchen> [TOPIC] Operations report (mthaddon/herb)
[19:21] <MootBot> New Topic:  Operations report (mthaddon/herb)
[19:22] <spm> Various application servers are dying and leaving a stale PID file: https://bugs.edge.launchpad.net/launchpad/+bug/247227
[19:22] <spm> Had three Cherry Picks to lpnet*, scripts and codehosting: https://bugs.edge.launchpad.net/launchpad/+bug/224623
[19:22] <spm> codebrowse has been migrated to a separate server
[19:22] <spm> Been running a LOSA sprint in London this week
[19:22] <spm> Librarian caching is live in production
[19:22] <spm> Personal Note: I did greatly appreciate all the 4am well-wishes last week :-)
[19:22] <spm> That's it from LOSA Land. Any questions from the channel?
[19:23] <Rinchen> flacoste, can you spare someone to look at the pid file bug above?
[19:23] <flacoste> Rinchen: i'll look at the logs
[19:23] <Rinchen> thanks flacoste
[19:23] <flacoste> and see if there is something
[19:23] <Rinchen> [AGREED] flacoste to look at bug 247227 to see if there is any obvious reason for stale pid files
[19:23] <MootBot> AGREED received:  flacoste to look at bug 247227 to see if there is any obvious reason for stale pid files
[19:23] <intellectronica> bad pidgin, bad
[19:23] <Rinchen> anything else for spm...
[19:23] <Rinchen> oh...
[19:24] <Rinchen> and I'll update the agenda to include you spm :-)
[19:24] <spm> Thanks Rinchen :-)
[19:24] <Rinchen> [TOPIC] DBA report (stub)
[19:24] <MootBot> New Topic:  DBA report (stub)
[19:24] <stub> Load spikes on the database correspond to load spikes on the appservers where spiders hammer us, causing timeouts.
[19:24] <stub> We currently have 8 cores on the db server. Assuming 50% of appserver time spent in Python and 50% waiting on DB queries and no batch processes, those 8 cores could service 16 simultaneous requests (this is an overestimate).
[19:24] <stub> We currently have 8 lpnet appservers, for a total of 32 handler threads. We also have 4 edge servers another 16 handler threads. So even when the replica database goes online we still have way more appservers than we need that can drive way too many queries to the db causing timeouts.
[19:24] <stub> I forgot to say thankyou to whoever thought of putting the max query counts for a page in the daily OOPS reports. These are pretty obviously prime targets to optimize and I believe the pages being shown up are being aggressively worked on.
[19:24] <stub> Is demo free at the moment? I need to do some testing with real appservers and a real database but don't want to use staging to avoid screwing up QA.
[19:24] <stub> oot.
[19:25] <mthaddon> stub, https://launchpad.canonical.com/DemoUsers
[19:25] <Rinchen> I believe demo is free stub.
[19:25] <stub> I think so too - just double checking :)
[19:26] <mthaddon> stub, demo is fairly out of date - pre-storm, for instance
[19:26] <Rinchen> I don't know of any of the conferences this week which are using it
[19:26] <bigjools> The Soyuz team is definitely aggressively working on those high query count pages
[19:26] <mthaddon> stub, so let us know if you want it updated
[19:26] <stub> I'll handle demo - I'll need to run my own branch
[19:26] <mthaddon> okey doke
[19:27] <Rinchen> mthaddon, can you please update the demousers page and add stub to it :-)
[19:27] <Rinchen> any further questions for Stu?
[19:27] <mthaddon> stub, how long should I put you down for? maybe you could add yerself? :)
[19:27] <stub> I'll add myself
[19:27] <mthaddon> merci
[19:27] <Rinchen> thanks stub
[19:27] <Rinchen> [TOPIC] Sysadmin requests (Rinchen)
[19:27] <Rinchen> Is anyone blocked on an RT or have any that are becoming urgent?
[19:27] <MootBot> New Topic:  Sysadmin requests (Rinchen)
[19:28] <Rinchen> I'll take that as a no.
[19:29] <Rinchen> [TOPCI] New packages required (salgado)
[19:29] <Rinchen> heh
[19:29] <salgado> anything for me this week?
[19:29] <Rinchen> [TOPIC] New packages required (salgado)
[19:29] <MootBot> New Topic:  New packages required (salgado)
[19:29] <salgado> guess no
[19:29] <stub> Should the dependencies contain version number requirements when packages come from sources other than hardy?
[19:30] <stub> I suspect I wasn't the only one without the pqm repo listed
[19:30] <Rinchen> and should we add the bzr ppa dependencies to it?
[19:30] <Rinchen> dunno stub, we had a few email threads about this back when I added that :-)
[19:30] <salgado> I've made it require specific versions when I was told a specific version was needed
[19:31] <salgado> stub, what's this pqm repo?
[19:31] <stub> :-)
[19:31] <mthaddon> just what we were wondering :)
[19:31] <stub> # The latest custom bzr-pqm package deb http://ppa.launchpad.net/jamesh/ubuntu hardy main
[19:31] <salgado> well
[19:31] <salgado> you need that for psycopg2
[19:32] <Rinchen> See https://launchpad.canonical.com/NewLaunchpadder  for the full list currently recommended
[19:32] <statik> salgado: btw i rewrote launchpad-dependencies a bit for my new project, and put it in a bzr branch using bzr-builddeb to build it, happy to share the branch with you if you are interested
[19:32] <salgado> statik, will you maintain separate branches for each distro series?
[19:33] <statik> salgado: nope, just using ppa copy functionality
[19:33] <stub> Anyway - just wondering if it is worth putting > 0.92 for bzr-pqm, >= 2.0.8 (or whatever) for psycopg2 etc.
[19:33] <salgado> stub, we do have that for psycopg
[19:33] <salgado> 2
[19:34] <salgado> statik, but that only works if you don't need to do any changes to the packages, I guess?
[19:34] <cprov> salgado: to cope with changes across series you can use auto-ppa package from landscape.
[19:35] <Rinchen> stub, I would support your proposal to add those since we need psycopg2
[19:35] <Rinchen> salgado, your take on stub's proposal?
[19:35] <salgado> Rinchen, we already do that: python-psycopg2 (>= 2.0.6+svn945~8.04)
[19:35] <salgado> that's what launchpad-dependencies require
[19:36] <statik> salgado: true, if i need different packages at some point i'll branch and have two series
[19:36] <salgado> and to have that installed one needs jamesh's ppa in sources.list
[19:36] <Rinchen> sure enough, ok then.
[19:36] <Rinchen> anything else for salgado?
[19:36] <Rinchen> thanks salgado
[19:36] <salgado> thank you
[19:36] <Rinchen> well, it's that time of the meeting.
[19:37] <Rinchen> it's the mrevell show!
[19:37]  * mrevell bows
[19:37] <Rinchen> [TOPIC] A top user-affecting issue (mrevell)
[19:37] <MootBot> New Topic:  A top user-affecting issue (mrevell)
[19:37] <mrevell> Yo. Today I have a couple of issues. First off, I'd like to note that today we had another person asking for help as they couldn't log into their account. Are we waiting on the next roll-out for that to be solved fully?
[19:37] <mrevell> I suppose that's a question for sinzui.
[19:37]  * stub wonders where his psycopg2 came from
 I have a partial fix for this in review
[19:37] <mrevell> thanks Rinchen
[19:38] <salgado> mrevell, todays issue was something else
[19:38] <intellectronica> fwiw, i think that this is something we should cp as soon as we've got a fix
[19:38] <mrevell> salgado: Oh was it?
[19:38] <salgado> intellectronica, +1
[19:38] <Rinchen> Yep, I'm also +1 on a CP for this
[19:38] <intellectronica> and/or proactively search for users that may be affected by these issues
[19:38] <sinzui> mrevell: I suspect that the code that claims an account is not updating the account correctly.
[19:39] <salgado> mrevell, it was.  currently we have 3 bugs, I think.  one for each view which doesn't update the account's status when they should
[19:39] <mrevell> sinzui: Ah, I see. So, is the action still to ping you when someone has this problem? Or is that pointless if the script isn't working properly?
[19:39] <sinzui> mrevell: I think so, if only to determine how the user discovered the problem
[19:40] <sinzui> The fix always seems to be the same, but where the code should have set the account status is different.
[19:40] <mrevell> Okay, thanks. I'll continue to make a noise about login problems, in that case, when they come up.
[19:40] <salgado> sinzui, shall I file bugs for the two other views which are not setting the status?
[19:40] <Rinchen> thanks mrevell. Any other questions for mrevell ?
[19:40] <mrevell> Second issue comes from andrea-bs. He has asked if there's any chance of bug 3522 being solved - i.e. are we going to implement email notifications when someone requests blueprint feedback?
[19:40] <sinzui> salgado: please do
[19:40] <salgado> will do
[19:41] <flacoste> mrevell: eventually :-/
[19:41] <mpt> Perhaps the feature should be hidden until it's implemented?
[19:41] <flacoste> mrevell: but that may take a while, depending on whether blueprints are a 3.0 priority
[19:41] <mrevell> mpt: That's quite tempting.
[19:41] <mrevell> flacoste: Right, thanks. It's certainly something I'd value.
[19:41] <mrevell> Thanks guys.
[19:41] <mrevell> back to you Rinchen
[19:41] <Rinchen> thanks mrevell. Any other questions for mrevell ?
[19:42] <Rinchen> [TOPIC] Doc Team report (mrevell)
[19:42] <MootBot> New Topic:  Doc Team report (mrevell)
[19:42] <mrevell> Nothing to report from the doc team, other than my appreciation for andrea-bs' continuing enthusiasm and involvement!
[19:42] <mrevell> I'm working to get the user guide and tour content ready for deployment this week.
[19:42] <mrevell> That's all from me, thanks Rinchen.
[19:42] <mrevell> Kinda the andrea-bs show, actually.
[19:42] <Rinchen> and thanks to flacoste for putting in the new tour :-)
[19:42] <andrea-bs> mrevell: thanks! :)
[19:42] <mrevell> yes, thanks flacoste :)
[19:43] <Rinchen> thanks mrevell
[19:43] <Rinchen> well, look at this. The meeting ran the full length.
[19:43] <Rinchen> Thank you all for attending this week's Launchpad Developer Meeting. See the channel topic for the location of the logs.
[19:43] <Rinchen> #endmeeting
[19:43] <MootBot> Meeting finished at 13:45.
[19:43] <Rinchen> Thanks again
[19:43] <jtv> Thanks Rinchen, and good night!
[19:44] <mrevell> thanks rinchen.
[19:44] <mrevell> gmb, rinchen, barry - see you later for the podcast recording
[19:44] <intellectronica> thanks Rinchen