/srv/irclogs.ubuntu.com/2006/11/24/#launchpad-meeting.txt

=== danilos [n=danilo@adsl-221-97.eunet.yu] has joined #launchpad-meeting
=== carlos [n=carlos@54.Red-88-18-197.staticIP.rima-tde.net] has joined #launchpad-meeting
carloshi05:01
SteveAhi05:01
daniloshi all05:01
SteveAlet's start anyway05:01
danilossure05:01
SteveAfirst of all, what are you guys currently working on?05:02
danilossorry if I confused you today Steve, I guess my connection to #launchpad dropped, while I was stil in #canonical05:02
danilos(and I lost my phone in Sunnyvale, so  didn't have your number right away)05:02
SteveAdanilos: ok.  I was worried you were ill like many people seem to be right now05:02
danilosno, I am fine, or at least not counting mental illness :)05:02
carlosatm, I'm finishing bug-6801405:03
carlosabout the reverting translations05:03
SteveAwhat's left to do there, carlos?05:03
carlosand have pending TranslationReview's review answer05:03
danilosanyway, I am wrapping up firefox stuff... I managed to break PO import (i.e. some tests are failing for me), so I am fixing that now05:03
carlosSteveA: improve the 'locking' detection code05:04
carlosactually, make it work as it should05:04
danilosI also have a couple simple bugfixes on my plate05:04
carlosand fix all tests05:04
carlosI would like to leave it in the review queue today05:04
SteveAok05:05
SteveAwe should get it reviewed as a priority05:05
SteveAdanilos: tell me about how the FF stuff is going05:05
danilossure05:05
danilosI have import and export working, but still have to switch to store actual alternate_msgid inside potmsgset table (I started with storing an ID into pomsgid table, but Carlos and I discussed it on UDS, and agreed that there is no point in that)05:06
danilossince the code involves changes to PO import/export as well, I have that slightly broken right now05:07
danilosand I haven't yet ported all the other importing mechanisms to ITranslationImport (such as tarballs, KDE langpacks,...)05:08
danilosI also have OOo import but no export yet05:08
carlosdanilos: could you finish FF without changing tarballs and KDE langpacks?05:08
daniloscarlos: yes, that's the plan, actually05:09
carlosok, I would prefer to do that in different branches so we get smaller branches and merges more often...05:09
daniloscarlos: sure, makes sense05:09
carlosff is already quite big..05:09
SteveAthere seem to be a lot of unfinished branches on the PendingReviews page 05:09
SteveAand, having code that is not landed on mainline, well, it gets more difficult to maintain as time goes on05:10
carlosbug-44214 is already answered and should be ready to merge, unless I missed anything05:10
danilosI have a couple which are partial bug-fixes for some of my in-progress bugs05:10
SteveAwhat's a partial bug fix?05:10
carlosthe other branches I have there are not high priority and I had to leave them stopped because are not near finishing. Though, I want to resume them as soon as possible05:11
daniloswhich fixes some instances of the problem (eg. the one with legend being shown on pages when no language stats are shown)05:11
danilos(and there are several templates, and one of them will require some code refactoring to fix it cleanly)05:12
SteveAdanilos: I see.  thanks.  although it seems strange to me that it needs the same kind of fix in many places 05:12
danilosSteveA: well, we have page which list multiple POtemplates, and only a single "legend", and another page which has a single POtemplate and "legend"05:13
carlosdanilos: couldn't we share some code there?05:13
daniloscarlos: sure, but that exactly means some "code refactoring" I mentioned above :)05:13
carlosI see05:14
carlosok05:14
SteveAso, thinking concretely about the data-loss fix05:14
SteveAcarlos, you said you expect it to be up for review today?05:14
danilosbtw, we also have more of those +rosetta-index oopses for yesterday05:15
carlosI hope that, yes, unless the tests gave me more problems than they should...05:15
SteveAhow big is the diff?05:15
carlosit's not working so I don't know how will be the final diff, but it shouldn't be more than 100-200 line changes/additions05:16
carloswithout counting tests05:17
carloseven less...05:17
SteveAok, so a smallish review05:17
carlosI think so, yes05:17
SteveAso, we should get it reviewed by someone right away, when it is ready05:18
carlosI think test changes will be higher than code changes05:18
carlosok05:18
SteveAdanilos: about the FF work, how long do you think before you can get something for review?05:18
danilosSteveA: just a couple of days--tuesday/wednesday most likely05:18
SteveAand what parts of the spec does that cover?05:19
danilosSteveA: any chance of getting this cherrypicked before 1.0 if review goes favourably and without too many changes?05:19
danilosSteveA: well, complete spec: we get Firefox XPI export/import05:19
SteveAok, so the expectation we're talking about is the firefox support spec being up for review by wednesday?05:20
danilosexactly05:20
daniloswith full tests05:20
SteveAthat would be wonderful.  how confident do you feel about that?05:20
danilospretty confident05:21
SteveAok, thanks05:21
danilosif I run into problems, I'll ask carlos for some help05:22
SteveAalso, tell me and kikok05:22
carlosdanilos: please, do it05:22
SteveAwe want to hear about your problems05:22
SteveAand when things go well too05:22
danilosand he won't mind at all, since he'd like to get to know the code for kde plural forms bug05:22
SteveAjust ping us on irc and tell us things05:22
SteveAabout how it is going05:22
danilosSteveA: ok, I know I've been pretty bad about communicating with you05:22
danilosand kiko05:22
SteveAlooks like we're planning to have FF stuff rolled out around 12 December05:23
carlosSteveA: should we talk also about Rosetta DB optimizations?05:24
danilosSteveA: how does that fit into 1.0 and time-based releases after that?05:24
carlosbtw, I will be off the week before that (4th-10th)05:25
SteveAdanilos: we still need to work that out05:25
danilosSteveA: ok, I'll start some discussion on launchpad list05:25
SteveAabout what?05:25
SteveAkiko and I have been discussing what to do about 1.0->1.105:26
SteveAwe need to discuss the whole thing with mark today (in about 10 mins)05:26
SteveAand then write a plan for it05:26
daniloswell, about what is going to be the meaning of 1.1, 2.0 etc.05:26
SteveAI don't think there's much to discuss on the launchpad list yet, until we've got approval for the basic idea05:26
danilosiow, I am not entirely sure I understand what you mean by that05:27
danilosare we simply going to replace our "rollouts" with "releases"?05:27
SteveAno05:27
SteveAwe'll still do regular rollouts every 1-2 weeks05:27
SteveAor 2-3 weeks05:27
SteveAwe'll do planning of features on a 13 week cycle05:27
danilosok, we're probably getting into marketing area then, if I am not mistaken?05:28
SteveAI don't want a lot of discussion on the list.  I just want to receive comments and feedback at this point05:28
danilosSteveA: ok, sure, I'll think about it some more, and post you my comments05:29
SteveAonce we've got the general direction approved, then I'd like discussion with everyone05:29
danilosyeah, got it05:29
SteveAlet's talk about the db optimizations05:29
danilosok, let me check if stub updated the spec with latest "findings" from UDS05:29
carloskiko suggested to implement it before improve translation form performance05:29
carlosI really don't mind to do it before or after that05:30
danilosI don't think stub updated it; we basically agreed that we want all our 40+M row tables merged into one05:31
carlosbut I guess that will only delay the performance fix05:31
daniloswell, I think the kiko's suggestion is because we probably won't need much translation form optimization work afterwards05:31
daniloswe're currently doing joins across 3 40M row tables, and we'd be doing it over 1 50M row table afterwards instead05:32
carloswell, I don't think it's a bad thing to change the way suggestions work as we planned to do it05:33
carlosthat will allow us to scale better in the future05:33
=== kiko [n=kiko@200-171-140-32.dsl.telesp.net.br] has joined #launchpad-meeting
SteveAhey kiko05:34
kikoho SteveA 05:34
SteveAI'm waiting on hold, btw05:34
daniloshey kiko05:34
SteveAon the subject of the FF spec05:34
SteveAdanilo is pretty confident that it will be up for review, with tests etc. by wednesday05:35
SteveAif that's so, I expect it to be rolled out right before or after the xmas break05:35
SteveAcarlos expects the data-loss fixes to be up for review tonight05:36
danilosSteveA: hum, when's the christmas break? (you mentioned 12 December above, but that doesn't sound "christmassy" to me ;)05:36
SteveAit is a small patch05:37
SteveAdanilos: did I?  for some reason I wrote 24 dec in my notes05:37
SteveAmust have got confused with today's date05:37
carlosSteveA: yeah, you said 12 December05:37
danilos<SteveA> looks like we're planning to have FF stuff rolled out around 12 December05:37
SteveAok, that's more like it05:37
SteveAthere remains a question about when to do the DB optimisations discussed at UDS05:38
kikoI think that is really important05:39
kikoit will make performance much better05:40
SteveAit would have the most effect across most users05:40
danilosif we want to use that to fix timeouts as well, it should be of relatively high priotity05:40
daniloss/priotity/priority/05:40
kikoand it will allow improvements later to be made much more easily05:40
danilosand I'd also need somewhat for proper search support05:40
carloskiko: I'm fine, as long as we don't forget the suggestions improvements we had planned before that DB change05:40
SteveAwe didn't yet talk about: search, translation review, OO work05:41
kikocarlos, I think the suggestions improvements may be rendered unnecessary by the DB work.05:41
danilosok, we've had john berkus (I think) from postgres to join us on db optimisations session on UDS as well05:41
kikoSteveA, this new age is very soothing05:41
carloskiko: well, I think that we should do it, better code, more clean, and will allow us to scale much more in the future...05:41
SteveAI think I'll dial back in and cowboy the leader code in there05:41
kikocarlos, what are you referring to there?05:42
daniloshe mentioned a really cool thing about something called "partial indexes" (well, I thought it was cool anyway), where you can have indexes for only some values of certain column in a table05:42
kikoyeah05:42
kikonot in pg8.1 I think05:42
carloskiko: well, instead of doing 3-4 queries for each entry to get all suggestions, making just one query05:42
danilosi.e. we'd also need to add "language" column to our potranslations table, so we can have per-language indexes05:43
carloswith the change danilos just said, we could split our DB per language in different databases05:43
danilos(and just to explain the context, we were very much concerned about performance of substring searches in 12M row table)05:44
carlosreducing the amount of rows too05:44
daniloscarlos: I think there is actually no need to split database if we can have partial indexes05:44
carlosdanilos: I said that we could, not that we should do it right now05:44
danilosbut as kiko said, yes, this requires 8.2, and stub didn't seem too fond of the idea05:44
carlosit's just one idea from Mark05:44
carlosso I was pointing that we would be able to implement it05:45
kikodanilos, yeah. we can do that later, anyway. a partial index on approved strings would be cool, I can see.05:45
daniloswell, maybe "not too fond" is a bit too strong; he just mentioned something about it not being too simple to do (=time, care)05:46
danilosbut that it's planned anyway05:46
kikocarlos, so what about TR? I saw the UI at allhands and had some comments.. do you have time for it in the short term?05:46
carlostime to finish it?05:47
carlosor to implement your comments?05:47
carlosboth answers are 'yes'05:47
kikoboth yes05:48
carlosI got an initial review from Bjorn05:48
carlosI will address all his comments and once that's approved, I will implement the UI changes you suggested05:48
carlosso I don't complicate bjorn's life too much05:49
kikook.05:49
carloshmm, not sure whether that expression is valid too in English... ;-)05:49
kikoit is!05:50
carlosok ;-)05:51
carlosnext point?05:52
carlosor do you have a phone call now?05:52
kikowe're mid-phone call, yes05:52
danilosaccording to SteveA's summary of points above, OO work05:52
carlosok05:52
kikoyes, please dive in05:52
danilosok, I'll put out current state anyway, so you can comment when you get back05:53
kikoand tell us all about this OO work05:53
danilosit's the same as pre-UDS/AllHands: OOo import is working (importing single GSI file into multiple translation domains), export not started yet05:54
daniloson UDS/AllHands, had a couple discussions with doko (OOo package maintainer) about how to best provide GSI files for him, and what domains to use, so need to incorporate his feedback as well (i.e. some bits different for help translation--actually have to check with him for more details on that one)05:55
danilos(which reminds me: carlos and I also had a discussion with pitti on documentation language packs, and one of the suggestions was to actually support direct import/export of DocBook XML files in Rosetta, just like we're going to support other formats such as FF/OOo)05:56
carlosdanilos: anyway, that's another spec that we should write and plan to implement, if we have time06:18
daniloscarlos: right, but that's another thing distro team wants of launchpad, so I thought I should also bring it up ;)06:20

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