/srv/irclogs.ubuntu.com/2008/08/07/#launchpad-meeting.txt

=== Rinchen` is now known as Rinchen
=== Ursinha is now known as Ursinha-zzz
=== salgado-afk is now known as salgado
=== Ursinha-zzz is now known as Ursinha
=== salgado is now known as salgado-lunch
=== salgado-lunch is now known as salgado
matsubaramoo18:58
al-maisan:-)18:59
Rinchenah what the hey18:59
Rinchen#startmeeting18:59
RinchenWelcome to this week's Launchpad development meeting. For the next 45 minutes or so, we'll be coordinating Launchpad development.18:59
MootBotMeeting started at 13:03. The chair is Rinchen.18:59
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]18:59
Rinchencluck18:59
sinzuithunk18:59
bigjoolsmoo18:59
Ursinhame19:00
barrysqueek19:00
Rinchenoh yeah19:00
Rinchen[TOPIC] Roll Call19:00
MootBotNew Topic:  Roll Call19:00
mrevellme19:00
Rinchencluck19:00
allenapme19:00
adeuringme19:00
bacoink19:00
matsubarame19:00
marsme19:00
barryme19:00
EdwinGrubbsme19:00
sinzuithunk19:00
Ursinhame19:00
matsubarathe launchpad farm19:00
bigjoolsbaa19:00
salgadome19:00
Rinchenreleases team is here19:00
Rincheneven though we're excused!19:00
RinchenTranslations won't be here19:00
al-maisanme19:01
Rinchenbjorn and francis are excused19:01
stubme19:01
Rinchenmthaddon is also excused19:01
thumperme19:01
Rinchenbarry, can you report on foundations for me19:01
stubjtv and danilo are on a sprint19:01
barryRinchen: sure19:01
intellectronicame19:01
Rinchenintellectronica, can you check on the bugs team please19:02
salgadofoundations is here too19:02
Rinchenrockstar ping?19:02
barryleonardr: ping19:02
rockstarme19:02
Rinchenok code is here19:02
marsleonardr, meeting?19:02
leonardrme19:02
abentleyme19:02
bigjoolscprov: ping19:02
salgadoapart from leonardr, that is. :)19:02
salgadono we're complete19:02
barryfoundations is here19:02
Rinchensoyuz?19:02
salgadonow19:02
RinchenI saw al-maisan.  cprov? bigjools ?19:02
bigjoolsone missing, Celsooooo?19:02
thumpercode is here19:03
Rinchenthanks19:03
Rinchen[TOPIC] Agenda19:03
MootBotNew Topic:  Agenda19:03
cprovme19:03
Rinchenyou'll notice that mrevell is no longer reporting on his sections by design19:03
Rinchenthese will now be brought up on demand19:03
Rinchen * Next meeting19:03
Rinchen * Actions from last meeting19:03
Rinchen * Oops report (matsubara/ursinha)19:03
Rinchen * Critical Bugs (Rinchen)19:03
Rinchen * Bug tags19:03
Rinchen * Operations report (mthaddon/herb/spm)19:03
Rinchen * DBA report (stub)19:03
Rinchen * Sysadmin requests (Rinchen)19:03
Rinchen * New packages required (salgado)19:04
Rinchen* user affecting issue (intellectronica)19:04
Rinchen[TOPIC] Next meeting19:04
MootBotNew Topic:  Next meeting19:04
Rinchennext week same time19:04
matsubaraI won't be here19:04
Rinchenk, thanks19:04
Rinchenanyone else19:04
RinchenFrancis will as well19:05
Rinchen[AGREED] same time same place on the 14th.  flacoste and matsubara are excused19:05
MootBotAGREED received:  same time same place on the 14th.  flacoste and matsubara are excused19:05
Rinchen[TOPIC] Actions from last meeting19:05
MootBotNew Topic:  Actions from last meeting19:05
Rinchenthere are none recorded19:05
Rinchen[TOPIC] Oops report (matsubara/ursinha)19:06
MootBotNew Topic:  Oops report (matsubara/ursinha)19:06
Ursinhahi all19:06
* Ursinha waves19:06
Ursinha5 bugs for today: 174480, 252695, 251569, 255816 and 24659119:06
Rinchen(rockstar, bring your boat - flash floods here today)19:06
UrsinhaSomeone of foundations is needed to take a look at bug 255816. Anyone?19:06
ubottuLaunchpad bug 255816 in launchpad "ComponentLookupError accessing /manage" [Undecided,New] https://launchpad.net/bugs/25581619:06
Ursinhatwo bugs for salgado: bug 252695 and bug 251569, how are these?19:07
ubottuLaunchpad bug 252695 in launchpad "+peoplelist taking too long to render and timing out" [Undecided,In progress] https://launchpad.net/bugs/25269519:07
ubottuLaunchpad bug 251569 in launchpad "UnicodeEncodeError when trying to search in launchpad/people/+index" [Undecided,Confirmed] https://launchpad.net/bugs/25156919:07
barryi can look at 25581619:07
Ursinhabarry, nice, thanks19:07
salgadoUrsinha, 252695 is on PQM19:07
salgadoUrsinha, didn't have a chance to look at the other19:07
Ursinhasalgado, when you have the time, please :)19:08
matsubarabarry, notice that the fix might be similar to whatever we did to fix bug 5494419:08
ubottuLaunchpad bug 54944 in launchpad "ComponentLookupError accessing ++skin++ page" [Low,Invalid] https://launchpad.net/bugs/5494419:08
barrymatsubara: thanks19:08
Ursinhaok19:08
Ursinhabug 246591, thumper, have you checked this out with mwhudson?19:08
ubottuUrsinha: Bug 246591 on http://launchpad.net/bugs/246591 is private19:08
Ursinhagrrr19:08
thumperUrsinha: he hasn't been online since we chatted last night19:09
Ursinhathumper, oh19:09
thumperUrsinha: I'll chase this morning19:09
Ursinhathumper, ok, thanks19:09
Ursinhathe last one19:09
Ursinhaintellectronica, have news on bug 174480?19:09
ubottuLaunchpad bug 174480 in blueprint "Person's +roadmap page contains blueprints they're not assigned to" [Undecided,New] https://launchpad.net/bugs/17448019:09
intellectronicaUrsinha: sorry, not yet19:10
Ursinhaintellectronica, would be appreciated too :)19:10
Rinchen[AGREED] barry to look at 255816, salgado has fix for 252695 in PQM, salgado to look at 251569, thumper to poke mwh about 246591, intellectronica to take on 174480.  Thanks guys!19:10
MootBotAGREED received:  barry to look at 255816, salgado has fix for 252695 in PQM, salgado to look at 251569, thumper to poke mwh about 246591, intellectronica to take on 174480.  Thanks guys!19:10
Ursinhathat's all folks19:10
Ursinhathanks!19:10
matsubarathanks all!19:10
Rinchen[TOPIC] Critical Bugs (Rinchen)19:11
MootBotNew Topic:  Critical Bugs (Rinchen)19:11
Rinchen[LINK]https://bugs.edge.launchpad.net/launchpad/+bug/25186919:11
Rinchenneeds an owner19:11
Rinchen[LINK]https://bugs.edge.launchpad.net/malone/+bug/25397019:11
RinchenEdwin, how is this progessing19:11
MootBotLINK received: https://bugs.edge.launchpad.net/launchpad/+bug/25186919:11
MootBotLINK received: https://bugs.edge.launchpad.net/malone/+bug/25397019:11
Rinchenand I've already spoken to jtv about19:11
Rinchen[LINK] https://bugs.edge.launchpad.net/rosetta/+bug/25575819:11
ubottuLaunchpad bug 251869 in launchpad ""not allowed here" while merging to accounts" [Critical,Confirmed]19:11
MootBotLINK received:  https://bugs.edge.launchpad.net/rosetta/+bug/25575819:11
ubottuRinchen: Error: This bug is private19:11
RinchenStarting next week, QA will be taking over this section! Yippee :-)19:11
ubottuMootBot: Error: This bug is private19:11
ubottuRinchen: Error: This bug is private19:11
ubottuMootBot: Error: This bug is private19:11
RinchenEdwinGrubbs, ^^19:11
Rinchensalgado, I know you have a lot on your plate. Is there someone who could look at 251869 though?19:12
Rinchenit's marked as CRITICAL19:12
RinchenI'm not so sure it is19:12
salgadothat's exactly what I was going to say19:12
salgadoI don't agree it's critical19:12
EdwinGrubbsRinchen: It has already been cherry picked. Sorry I forgot to mark the ticket Fix Released.19:13
salgadoit has prevented a couple users from merging their accounts, and in both cases a LP admin was able to do the merge for them19:13
RinchenEdwinGrubbs, excellent. Please include the RF number in there if it is not already.19:13
Rinchenok salgado I've lowered that one19:14
Rinchenok, that's it from me.19:14
RinchenAnything else before I move on?19:14
Rinchen[TOPIC] Bug Tags19:15
MootBotNew Topic:  Bug Tags19:15
Rinchenwe have one19:15
Rinchenhttps://help.launchpad.net/TaggingLaunchpadBugs19:15
Rinchentwo actually19:15
Rinchenfirst up, mrevell - tour tag19:15
mrevellHello. We have bugs filed against the launchpad-documentation project that cover several things - e.g. user guide, tour, and so on.19:15
mrevellIt would be handy to be able to group together anything relating to the tour as we then hand the changes off to a specific developer/outside designer.19:16
intellectronicai think the tour should be a product19:16
sinzui+119:16
Rinchensinzui, on the tag or the product suggestion?19:16
mrevellintellectronica: Why would a product be more suitable?19:16
mptIt doesn't have separate source code19:17
sinzuiWe don't need a tag, the tour is autonomous from launchpad apps19:17
intellectronicamrevell: because it's not a subclass of bugs of any one lp product. it's a pretty self contained piece of functionality19:17
RinchenI think mrevell's point is that it already has a product, called launchpad-documentation19:17
sinzuiit is /more/ separate than answers or bus19:18
Rinchenbut there are other items that use that product as well19:18
intellectronicathat's not the same thing19:18
Rinchenand he'd like to have a way of keeping them separate19:18
Rinchenis that right mrevell ?19:18
intellectronicathe tour isn't really documentation, it's more marketing19:18
sinzuiand we update and review the tour differently form code19:18
mrevellYes Rinchen. I'm thinking of also suggesting "inline-help" and "user-guide" tags in the future.19:18
Rinchenok, let's not get ahead of ourselves :-)19:18
mptIdeally, where a change to Launchpad code affects what the tour should say, the same branch should update that part of the tour at the same time.19:19
mrevellintellectronica: It's docu,mentation for prospective users :)19:19
intellectronicainline-help and user-guide are documentation bugs, i agree19:19
Rinchenthumper, do you have any comments?19:19
thumperabout a product for the tour?19:20
matsubaraI think we won't have that many bugs on the tour anyway, so that doesn't justify having its own product19:20
Rinchenthumper, yes...or the tag.19:20
thumperI don't think the current lp projects should be projects19:20
thumperso I'm -1 on a product, +1 on a tag19:20
matsubaraI'm +1 on the tag, -1 on the product as well (but I'm biased :-)19:21
thumpersorry for mixing products and projects there19:21
Rinchenmrevell, do we really have a lot of bugs that would require a tag (let alone a product)?19:21
intellectronicathumper: i don't look forward to a day when i'll have to dig out the relevant bugs from a long list of all lp bugs19:21
Rinchenyou didn't include any examples which is why I ask19:21
mptintellectronica, so fix the bugs that make tagging unnecessarily difficult :-)19:22
intellectronica:)19:22
matsubara+1 mpt19:22
mrevellRinchen: The tour bugs come when there's a major tour update. So, there were a few bugs after the most recent roll-out - but it is a *few*, ten maybe fifteen at most.19:22
mptThe longer those bugs go unfixed, the more people are tempted to do silly things like splitting the same bunch of source code into separate "projects"19:22
mrevellRinchen: But they come at one time.19:22
mrevellI suggest a tag so that it's easy for me to look at what needs fixing on the tour and then I can go to our external designer and get a quote.19:22
Rinchenok19:23
intellectronicawhile i'd prefer a tag, i think that mrevell should ultimately decide on this one, since he's managing this project, and he will benefit (or suffer) from the change the most19:24
Rinchengiven that the amount of bugs are not very high and it currently fits well within it's existing product, I don't think a new product is the right thing in this particular instance19:24
RinchenI also do not think a tag would be warranted but I have "been there, done that" when dealing with the tour and the provider so I'm +1 on a tag for it's existing product19:24
Rinchenintellectronica, well, he did. He wants a tag :-)19:25
thumperJFDI19:25
mrevellthumper: my thoughts exactly :)19:25
allenap+119:25
Rinchenok. so carried19:25
mrevellthanks all for your input19:25
Rinchen[AGREED] tour tag for the launchpad-documentation product approved. mrevell to update the tags page19:25
MootBotAGREED received:  tour tag for the launchpad-documentation product approved. mrevell to update the tags page19:25
Rinchenok, for tag #2...19:26
Rinchenmatsubara, rca19:26
matsubaraone of the things we decided to do during the sprint is to have a root cause analysis for critical bugs, and we would use a bug report to hold information about the RCA. so the tag is basically to help us group those together. I'm ok on re-proposing this tag once we have the process in place and a initial RCA bug as an example.19:26
barryit's an interesting idea, but can we pick something other than an abbreviation?19:27
thumperbarry: rooted?19:27
Rinchenso the team leads spoke about RCAs on last week's call19:27
Rinchenand the TL's agreed we should pilot this19:27
Rinchenand the QA group is going to do this for Critical bugs (only)19:27
barrythumper: sounds like pwnd :)19:27
barrythumper: maybe root-cause?19:27
Rinchenthe process needs to be updated a bit so...stay tuned and we'll have that out to everyone19:28
thumperRinchen: I like root-cause better than rca too19:28
matsubarabarry, fine by me.19:28
abentleythumper: Yeah, I guess Root Cause Analysis has a different flavour in some dialects.19:28
thumperabentley: :p19:28
RinchenAny objections?19:28
Rinchenok. thanks19:28
thumperRinchen: only to rca, not the concept19:28
Rinchen[AGREED] root-cause tag approved. matsubara to update the tags page.19:29
MootBotAGREED received:  root-cause tag approved. matsubara to update the tags page.19:29
Rinchen[TOPIC] Operations report (mthaddon/herb/spm)19:29
MootBotNew Topic:  Operations report (mthaddon/herb/spm)19:29
* Rinchen pokes herb 19:30
Rinchenok19:30
Rinchenwell19:30
Rinchenwe'll move along then19:30
Rinchen[TOPIC] DBA report (stub)19:31
MootBotNew Topic:  DBA report (stub)19:31
stubThe trunk will be open for database landings tomorrow, and the remaining db patch reviews done assuming this conjunctivitis doesn't get bad.19:31
stubOne landing will be the branch that gives us master and slave stores to play with.19:31
stubYou can explicitly use the slave store to speed things up when your code doesn't need to write to the db and doesn't mind if the data is slightly lagging. I'm sure we can all think of many examples that will benefit from using this.19:31
stubYou can explicitly use the master store when you need to make modifications or the data absolutely has to be up to date.19:31
stubExisting code all uses the default store, which is set by the publisher based on the type of request - read only requests will get the slave store as their default, which should offload at least 30% of our load to the replica databases (when they are live).19:31
stuboot.19:31
RinchenThis is great news stub19:32
Rinchenany questions for stub?19:32
barrystub: what's the name of the slave store?19:32
thumperstub: any idea what the delay will be like getting updates from the master to the slave(s)?19:32
stubgetUtility(IStoreSelector).get(LPMAIN_STORE, SLAVE_FLAVOR)19:32
barrystub: thx19:32
stubthumper: 2 seconds to minutes - we won't know until we see it under real load.19:33
* thumper nods19:33
stub(which we will do before switching the load balancing on)19:33
Rinchenstub, running this on demo or staging ahead of time and asking the lp community to test this would be a brilliant idea19:34
* thumper wonders about post redirects19:34
stubYes, but that still isn't real load. It is a hint, but not a true picture.19:34
thumperif we have a post that goes to writable store, which does a redirect post saving to a get, will that go to a copy that doesn't have the update?19:34
sinzuistub, does the master/slave negotiation for requests know about @safeget?19:34
stubthumper: The current load balancing implementation will keep connections using the master store for 5 minutes after a POST request19:34
thumpercool19:35
stubsinzui: No, because I don't know about it either.19:35
Rinchenany more questions for stub?19:35
stubsinzui: There is at least one hole in the algo at the moment, so it wouldn't work if we switched it on today (webservice requests all need the master at the moment). This branch is landing the infrastructure though, and enough for testing on demo and staging.19:36
stubsinzui: @safeget Sounds like something else the load balancing needs to be aware of as well.19:37
sinzuiI meant @safe_action that we use with get requests.19:37
sinzuiI was wondering if those submits will be using master when I think they should always use the slave19:38
stubsinzui: It depends if we can make an inteligent decision that early in the publication.19:38
Rinchenthanks stub.  I'm going to move on....19:39
Rinchenin the interest of time19:39
Rinchen[TOPIC] Sysadmin requests (Rinchen)19:39
RinchenIs anyone blocked on an RT or have any that are becoming urgent?19:39
MootBotNew Topic:  Sysadmin requests (Rinchen)19:39
thumperRinchen: there is one19:39
thumperRinchen: but I don't know the number19:39
bigjoolsRinchen: I can't remember the numbers right now but I have a couple for private PPAs19:39
Rinchenlast week it was  31340, 31296, and 3138919:39
thumperRinchen: it was about moving a staging code import box to production environment19:40
Rinchenok, if you guys could email those to me please I'll see what I can do19:40
* thumper nods19:40
Rinchensprinting this week so it's been rather hard for me to chase those19:40
Rinchenthanks19:40
Rinchen[TOPIC] New packages required (salgado)19:40
MootBotNew Topic:  New packages required (salgado)19:40
salgadoanything for me this week?19:41
Rinchenok, thanks salgado19:41
Rinchenso, let's slow things down a little  ;-)19:41
Rinchen[TOPIC] user affecting issue (intellectronica)19:41
MootBotNew Topic:  user affecting issue (intellectronica)19:41
* Rinchen pokes intellectronica 19:42
intellectronicain discussions with the ubuntu community, it has come to my attention that one issue that makes life very difficult for them, is launchpad being slower than they think is usable19:42
intellectronicaouch19:42
intellectronicait occured to me, that we often don't know that pages become unusably slow until they start timing out19:43
Rinchenwe here this from folks in China as well.  We have experimented with non-ssl connections but it has not improved anything greatly19:43
intellectronica(or until users report bugs)19:43
intellectronicai think it's db queries in most cases, not the transport19:43
stubWe are still chasing hard timeouts. Ideally these would be 0 and we are chasing soft timeouts instead. I think many of us tend to think of soft timeouts as normal or maybe early warnings rather than problems that need fixing.19:44
intellectronicaso i have no idea how to tackle this, but would like to invite you all to think about this and maybe start a discussion on what we can do to track the speed of requests and improve things before they become serious problems19:44
matsubarayeah, we bring those soft time outs up from time to time, but they are postponed as not yet critical19:45
thumperI know on the code side, a usability point is the number of clicks / edits needed19:45
thumperso it is more of a workflow thing19:45
thumperrather than a webapp speed thing19:45
intellectronicamatsubara: yeah, we can think of those as usability issues, rather than critical bugs19:45
intellectronicathumper: no, i think they are talking about page load times, not interaction19:45
thumperintellectronica: oh, ok19:46
abentleythumper: Rationally, yes.  Emotionally, high latency feels depressing.19:46
mptI have read that people who complain about slow page load times think that a site has become much faster when the design has improved but the speed has not19:46
* thumper is used to slowish pages from NZ19:46
sinzuitranslations were hoping for AJAX to make it's page feel faster.19:47
stubI suspect slow pages are those bugs that will never be looked at given our current priorities. Maybe now 2.0 is out we can look at polishing what we have over driving new features?19:47
marsintellectronica, there was a little discussion about pulling the page times from the Apache logs.  That could give you some hard data.19:47
intellectronicampt: well, they were talking about this yesterday quite a lot, so obviously this hasn't affected their perception :)19:47
mptobviously what hasn't?19:47
intellectronicamars: that, i think, is a really good thing to do. especially if it's done periodically and graphed19:47
intellectronicampt: obviously the new design hasn't changed the user's perception of speed19:48
Rinchenthe problem with load times it that it doesn't account for delay incurred over the wire.19:48
Rinchenpages load for me in the USA about 10 times slower than in London19:48
mptintellectronica, I wouldn't expect it to, the 2.0 changes are tiny usability-wise19:48
intellectronicaRinchen: sure, but given that there's little we can do about the transport, why worry about it?19:48
marsyep.  I don't remember if there is a way to pull the full page load time though - not just the HTML, but scripts, images, etc. in aggregate.19:48
Rinchenintellectronica, because I think a good portion of the issue is geographically induced19:49
intellectronicampt: indeed. and i agree that in-page interaction would improve things /a lot/19:49
Rinchenwe still serve the same amount, but depending on where you are, it may be fast (London) or slow (China)19:49
intellectronicaRinchen: so maybe we should aim at researching that too?19:49
marsintellectronica, btw, response times could also become a big issue when we add more AJAX.19:49
intellectronicamars: how so?19:50
RinchenI've had some initial conversations with upper management about that in fact.  But yes, we should definitely look into ways of improving that19:50
marssure, it's AJAX, it's snappy, but that doesn't help if the XHR takes 1000ms to run :(19:50
beunomars, ajax will reduce the amount of unnecessary queries you do. I do agree slow ajax is even worst19:50
beuno(and hi everyone)19:50
intellectronicamars: well, you won't be waiting on the entire page, as you do now19:50
marsintellectronica, yes, true19:51
RinchenMy advice at the moment is that everyone here consider this topic for a bit and bring up ideas to your team leads (and also intellectronica).19:51
bigjoolsSome of our pages carry a lot of data which can cause a lot of queries.  When optimising for fewer queries it's still easy to not improve the speed because the code becomes the slow part, so we need to be mindful of both code speed and number of queries.19:52
RinchenWe have a TL meeting coming up in a few weeks. It would be an interesting time to discuss it19:52
mrevellIt's worse when an AJAX request goes slowly because you can't easily reload the page to start again.19:52
abentleyintellectronica: Sometimes JavaScript itself can take a long time to load.19:52
intellectronicaabentley: you mean js runtime? that depends on the client, but we should never reach the point where this can be an issue19:53
Rinchenthank intellectronica for bringing this up.  I happen to think it's very important19:53
abentleyintellectronica: No, I mean the JavaScript code for a particular web site.19:53
RinchenI'd like to table the JS discussions until later.  Anything else for intellectronica before we close?19:54
Rinchenok then.19:54
RinchenThank you all for attending this week's Launchpad Developer Meeting. See the channel topic for the location of the logs.19:54
Rinchen#endmeeting19:54
MootBotMeeting finished at 13:58.19:54
intellectronicathanks Rinchen19:55
allenapCheerio everyone.19:55
mrevellthanks Rinchen19:55
thumperta19:55
al-maisanbye!19:55
=== cprov is now known as cprov-afk
=== salgado is now known as salgado-afk

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!