/srv/irclogs.ubuntu.com/2008/05/29/#launchpad-meeting.txt

=== bigjools_ is now known as bigjools
=== mrevell__ is now known as mrevell
=== danilo__ is now known as danilos
=== EdwinGrub is now known as EdwinGrubbs
=== cprov is now known as cprov-out
kikoharken all18:59
Rinchenwell, let's see if mootbot has recovered19:00
RinchenI think it hasn't19:00
gmb10:1 against.19:00
Rinchen#startmeeting19:00
Rinchenright then, I know seeker's been working on it19:00
* gmb wins19:00
matsubarame19:00
RinchenWelcome to this week's Launchpad development meeting. For the next 45 minutes or so, we'll be coordinating Launchpad development.19:00
abentleyme19:00
mrevellme19:00
RinchenRoll Call19:00
mrevellme19:00
gmbme19:00
sinzuime19:00
Rinchenme19:00
barryme19:00
bac_me19:00
bigjoolsme19:01
allenapme19:01
statikme19:01
adeuringme19:01
jt1me19:01
=== jt1 is now known as jtv
jtvme19:01
mthaddonme19:01
flacosteme19:01
matsubarame19:01
thumperme19:01
herbme19:01
kikoeu19:01
RinchenSteveA, danilos ?19:01
leonardrme19:01
mptmeme19:01
Rinchenschwuk, ?19:01
jtvRinchen: just pinged danilos19:01
mptme19:01
schwukme19:01
marsme19:01
Rinchenah mpt, are you here for the full meeting?19:02
SteveAme19:02
BjornTme19:02
flacostesalgado is on leave, Foundations is complete19:02
mptRinchen, I think so19:02
Rinchenk19:02
Rinchenthanks flacoste19:02
Rinchenreleases is here19:02
mptI just love you guys too much19:02
Rinchenrockstar, ?19:02
rockstarme19:02
BjornTBugs is here as well. intellectronica is on leave19:02
Rinchencprov-out, ?19:02
Rinchenmuharem is not here today with a hall pass19:03
cprov-outme19:03
Rinchenok, let's get going19:03
=== cprov-out is now known as cprov
RinchenAgenda19:03
Rinchen * Next meeting19:03
Rinchen * Actions from last meeting19:03
Rinchen * Oops report (Matsubara)19:03
Rinchen * Critical Bugs (Rinchen)19:03
EdwinGrubbsme19:03
Rinchen * Bug tags19: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:03
Rinchen * Doc Team report (mrevell19:03
Rinchen* Numbered experiments and [WWW] https://launchpad.canonical.com/Experiments (kiko)19:03
Rinchen 19:03
RinchenNext meeting19:03
Rinchensame time, same place, June 5th?19:04
kiko+119:04
RinchenAnyone know they will be absent?19:04
Rinchenok.  If you find out later, please update the agenda19:04
Rinchen 19:05
RinchenActions from last meeting19:05
Rinchen 19:05
RinchenNone remaining open19:05
Rinchen 19:05
RinchenOops report (Matsubara)19:05
matsubaraToday's oops report is about bugs 235818, 20057219:05
SteveAI'll be absent19:05
matsubaradanilo, #235818 is for you. Are you going to re-enable relicense translations19:05
ubottuLaunchpad bug 235818 in rosetta "Relicense translations link broken" [Undecided,New] https://launchpad.net/bugs/23581819:05
matsubarain an RC? If not, can you disable the link for the second rollout?19:05
ubottumatsubara: Bug 200572 on http://launchpad.net/bugs/200572 is private19:05
matsubaraflacoste, any news about 200572?19:05
=== Rinchen changed the topic of #launchpad-meeting to: Launchpad Meeting Grounds | Channel logs: http://irclogs.ubuntu.com/
SteveAactually, I'll be absent for 2 meetings in a row19:05
matsubaradanilos: ^19:05
flacostematsubara: no19:06
matsubaraflacoste: should I add that exception to the "User generated errors" section?19:06
jtvmatsubara: danilos may be having system problems again.19:06
matsubarajtv: ok. I'll chase him after the meeting then. thanks19:07
flacostematsubara: if you can identify them reliably, i guess so, i don't think we have time for this before 2.019:07
kikomatsubara, the first one, for danilo, is already fixed in RF, just landed.19:07
matsubarathanks kiko19:07
matsubaraflacoste: ok. I'll give it try. thanks19:08
matsubaraanything else shows up in the oops report today, and I'll follow up directly with people19:08
matsubaraI'm done Rinchen19:08
RinchenThanks matsubara19:08
Rinchen 19:08
RinchenCritical Bugs (Rinchen)19:08
Rinchen 19:08
matsubarathanks everyone19:08
kikomatsubara, I don't see any issue with moving that into UGE19:08
RinchenIt seems that we've talked about everything on my list or it has been fixed (thanks flacoste) so I have nothing for this week.19:09
matsubarakiko: ok. I'll do that19:09
Rinchen 19:09
RinchenBug tags19:09
Rinchen 19:09
RinchenWe have 219:09
Rinchenhttps://help.launchpad.net/TaggingLaunchpadBugs19:09
Rinchenmatsubara, bughistory19:09
Rinchenwe'll start with yours first19:09
matsubarahmm ok19:10
matsubarait's a tag to handle all bugs related to our +bug-activity page19:10
kiko+119:10
matsubaraactually it's +activity page19:10
matsubaraand given the number of examples, I think it's worth to have it.19:10
Rinchencould we make that generic enough to handle blueprint histories when we get them?19:10
Rinchenperhaps just "activity"19:11
kikoRinchen, no.19:11
Rinchenor "activityhistory'19:11
kikono19:11
matsubaraRinchen: I'd rather keep it bughistory19:11
kikothey are completely unrelated -- there is no shared code or anything19:11
flacostewell19:11
mptEventually they might be shared code19:11
mptbut not in the short term19:11
flacosteone doesn't exists19:11
matsubaraand then change the meaning to history-logging or whatever when we get there19:11
flacosteso i think it's premature19:11
RinchenSure, I'm ok with all of that.19:12
RinchenWanted to make sure we thought about it.19:12
marsare the issues we will be tagging data integrity bugs, UI bugs???19:12
RinchenBjornT, your comments?19:12
SteveAhow about "activitypage" ?19:12
mptI disagree with having "page" in the tag name19:12
mptbecause one of the bug reports is about not showing activity on a separate page at all :-)19:12
kikobughistory19:12
kikothis is not about generic activity pages19:12
BjornTRinchen: +119:13
kikoit's about not or incorrectly recording bug history19:13
matsubarayeah, i agree with mpt19:13
Rinchenok, we have 2  plus 1s for bughistory19:13
Rinchenany against?19:13
mptI'm fine with bugactivity or bughistory19:13
Rinchen3 vs 019:13
Rinchenok, approved.19:13
Rinchenmatsubara, please update that page19:13
Rinchenkiko, announcements19:13
kikoproject-announcements maybe?19:14
kikoI dunno19:14
matsubarawill do as soon as we reach an agreement for the second tag19:14
matsubaraRinchen: ^19:14
kikoI know there are a few bugs related to that and we can't group them easily19:14
mptIs there likely to be any other kind of announcement?19:14
Rinchenbac, your comments?19:14
kikompt, well, hmmm19:14
kikonot sure19:14
RinchenIn this case, I'm +1 for this tag which I won't go into here19:15
mptI guess the bet is, will any other kind of announcements be introduced *and* need its own tag, before mass tag-renaming is implemented :-)19:15
kikoI'm +1 too19:15
kikojust not sure about the name19:15
mptIf not, it can just be "announcements"19:16
kikobut this is a specific feature, project and distro announcements19:16
kikoI feel announcements is a bit too generic a term19:16
Rinchenkiko, project-announcements ?19:16
kikobut that's a mild feeling not a strong thing19:16
kikothat's what I suggested19:16
kiko<kiko> project-announcements maybe?19:16
Rinchenok, 2 for that. Any objections?19:16
matsubaraif we're sticking a project- on it how about project-news ?19:16
kikosure19:17
Rinchenyeah, I'm ok with that as well19:17
bac_i'd stick with announcements since that's what they are called in the UI19:17
kiko-news is so much shorter.. okay, whatever, official-bug-tags will solve that eh BjornT :)19:17
kikoproject-announcements it is19:17
kikomatsubara, ko do it!19:17
* Rinchen doesn't tend to get obsessive with the names so long as they don't exclude anything we want to include or are insanely long.19:17
matsubaraok. thanks everyone19:18
Rinchenok, approved.19:18
Rinchenkiko, please ensure that page is updated.19:18
Rinchen 19:18
RinchenOperations report (mthaddon/herb)19:18
Rinchen 19:18
herbIt's been a pretty quiet week. We needed to restart codebrowse/loggerhead a couple of times due to memory utilization. We discussed this last week and I believe mwhudson is aware of the issue.19:18
herbRolled out 1.2.5 yesterday. Went smoothly with 25 minutes of downtime. To the best of my knowledge we haven't heard anything about a re-roll. Will there be a re-roll with this release and, if so, when?19:18
flacosteherb: how is the memory usage of the app servers been going since the max batch size fix?19:19
* Rinchen notes we should call the 2nd roll-out something other than re-roll :-)19:19
herbflacoste: we haven't had to restart them.  they still grow, but the systems haven't been swapping.19:19
kikoherb, there will be a re-roll, I was hoping for first thing tomorrow if that's ok with you?19:20
barryRinchen: twotsee-roll19:20
herbkiko: no problem.  sounds good.19:20
mptrick-roll19:20
RinchenI was thinking more like a polish-roll   (and in Shiny not the country)  :-)19:20
kikoI was thinking polish corridor19:20
Rinchenright, anything else for herb?19:20
* barry likes polish-roll-the-country :)19:20
herbTha's it from Tom and me.  Thanks.19:21
Rinchenthanks herb and mthaddon19:21
Rinchen 19:21
RinchenDBA report (stub)19:21
Rinchen 19:21
statiknot for herb specifically but I'm curious whether the bzr smartserver we are running now supports protocol319:21
Rinchenstub's not here19:21
Rinchenso I'll ask for the DBA report via email19:21
kikostatik, we are still on 1.3 on the codehost19:21
statikkiko: thanks19:21
Rinchen 19:21
RinchenSysadmin requests (Rinchen)19:21
Rinchen 19:21
RinchenIs anyone blocked on an RT or have any that are becoming urgent?19:21
kikojml wants to upgrade the codehost code but not bzr -- bzr will upgrade on monday in RF19:21
statikkiko: that will give us stacked branches and the new network protocol, eh? very exciting19:22
Rinchenok, nothing heard...moving on19:22
Rinchen 19:22
RinchenNew packages required (salgado)19:22
Rinchen * A top user-affecting issue (mrevell)19:22
Rinchener19:22
kikostatik, yes, very19:22
Rinchensalgado is not here19:22
Rinchenplease talk to him if you have any packages that you need added19:22
Rinchen 19:23
flacosteor me19:23
Rinchen top user-affecting issue (mrevell)19:23
Rinchen 19:23
mrevell:)19:23
mrevellThis week, the outstanding issue has been the on-going discussion on launchpad-users of how we work to prevent the use of Launchpad accounts for spamming purposes.19:23
mrevellHowever, as we're looking into solutions I'm not sure there's much to discuss here. Otherwise, it seems we've had a relatively quiet week, user-issues-wise19:23
kikomrevell, Rinchen, SteveA and I had an interesting call about this19:23
kikoRinchen, can you remind us of the interesting ideas SteveA had19:24
Rinchenthere were to proposals19:24
SteveAwe may end up doing what facebook does19:24
kikothere were from proposals too19:24
kikoright19:24
SteveAand using capchas for each and every interaction that causes information to be seen by other users19:24
kikoif you haven't validated you get captcha-annoyance at every step19:24
SteveAuntil someone validates their account19:24
SteveAand there may be many ways of validating an account19:25
kikoflacoste, you got that? it might be foundations 2.0+19:25
kikoone way of validating an account is to sign the coc!!19:25
SteveAincluding associating it with a mobile phone sms number19:25
* kiko snickers19:25
* Rinchen can't receive sms19:25
SteveAor being part of the strongly connected GPG group19:25
SteveAor whatever19:25
sinzuiRinchen: That is sooooo 1990s19:25
* Rinchen is part of a strongly connected GPG group. :-)19:26
mrevellWould it be churlish to mention the stories of teams of people paid to fill-out captcha forms?19:26
SteveARinchen: then... YOU LOSE ;-)19:26
Rinchensinzui, blame it on T-Mobile19:26
kikoI can receive sms but not from the USAAAA19:26
kikomrevell, not for every single step, I doubt they do that19:26
flacostemy mobile is turned-off in a drawer unless i travel19:26
Rinchenanyway.....19:26
kikothe captcha farm myth probably only applies to account registration captchas19:26
mrevellRight19:26
kikonot for every step I take captchas19:26
kikothe police captchas19:27
SteveAevery move I make capchas19:27
RinchenSo to recap, we have a few proposals that we are interested in evaluating further.19:27
SteveAwe'll be watching you19:27
bigjoolscaptcha in a bottle19:27
kikothat's so 198419:27
marsSteveA, the GPG web of trust tie-in is interesting19:27
Rinchenmrevell, anything else? SteveA, anything else?19:27
flacostesince most data is seen by other users, it's basically a captcha on every form...19:27
kikomars, tie-in being a pun there?19:27
mrevellRinchen: that's all from me, thanks19:27
SteveAnothing else from me19:27
Rinchenthanks19:28
kikoflacoste, yes, simpler that way too19:28
RinchenDoc Team report (mrevell)19:28
flacosteLaunchpadEditForm-voodoo19:28
kikodoc team!!!19:28
mrevellHello!19:28
mrevellAlthough the doc team meeting last week was a wash-out, we've had another member sign up and offer to do German translations!19:28
mrevellI'm particularly excited about that, but the chap does warn that he's a touch rusty.19:29
mrevellIn other doc news: Had a useful meeting with Mark S and the SEM designer, Gavin, on Tuesday. Tour is progressing well. Thanks to those who've sent comments on the inner page graphics.19:29
mrevellThanks also to those who've given comments on the release announcement. I'll deal with those after the meeting.19:29
mrevellLater today, Elliot and I will be recording episode 3 of the podcast.19:29
mrevellThanks Rinchen19:29
Rinchenthanks mrevell19:29
Rinchen 19:30
RinchenNumbered experiments and [WWW] https://launchpad.canonical.com/Experiments (kiko)19:30
Rinchen 19:30
kikohello hello19:30
SteveAI like this19:30
kikoI put that wikipage up19:30
kikobecause I'd like us to record the experiments we run19:30
SteveAthanks kiko!19:30
kikoand at least detail what the experiment is and what the outcome was19:30
kikothe experiments are sequentially numbered and it's FCFS based on wiki edit19:30
statikvery nice19:30
kikoso if you want to, say, experiment by right-aligning all form elements in a specific launchpad form19:31
kiko(which is a pretty bad idea)19:31
kikoyou add an entry to that page and call it experiment n+119:31
kikowhere n is the last experiment recorded there19:31
mptResult: mpt chased you with a cheese grater19:31
RinchenI like this too. I'd like to request that the outcome be documented somewhere of course (on the wiki page associated with the experiment for example)19:31
kikothere you go19:31
kikonow I need a candidate to fill out LP00119:31
kikowho's that gonna be19:32
* Rinchen raises flacoste's hand.19:32
marskiko, I gather that's process experiments as well, like Foundations cycle planning?19:32
kikomars, yes.19:32
kikoit's basically any experiment19:32
RinchenI think flacoste could doc up planning poker :-)19:32
flacosteRinchen: yeah, Foundations will come up with one, don't know it will be the first one though19:32
flacosteRinchen: well, that experiment is over19:32
kikoyou can do retroactive entries there too19:32
Rinchen:-)19:32
flacosteah, then that could be it19:33
RinchenI was going for something easy19:33
kikothere you go19:33
kikoplease run experiments19:33
kikoand please record them there19:33
kikoexperiments are fun and cheap19:33
Rinchenexperimentation is good19:33
Rinchenso long as nobody gets hurt19:33
Rinchenkiko, anything else?19:33
Rinchenon this topic19:34
kikono19:34
Rinchenk19:34
RinchenI have a last minute addition19:34
kikosecret topic?19:34
Rinchen 19:34
Rinchen 19:34
RinchenStorm n you (kiko)19:34
Rinchen 19:34
kikoaha19:34
kikoI knew it!19:34
kikoso19:34
barrybigjools: did you want to bring up the big branch topic?19:34
kikojamesh is struggling with quite a few of our tests19:34
kikoand has been so for the past week or two19:35
kikoI've asked him to do a full run of all tests and figure out how much is failing19:35
kikobut it is getting close to the point where I am going to move devel focus over to storm19:35
kikothis will make edge much less useful19:35
SteveAa bold move, kiko19:35
SteveAI support it19:36
kikoand also commits us to doing the work to make storm work in a very short period of time19:36
kikoso if you are a launchpad engineer19:36
flacostewhy edge will be less useful?19:36
kikoand if you are a team lead19:36
kikothen you may need to prepare for a few days interruption to fix any remaining tests19:36
barrykiko: anything we can do to help?19:36
kikobarry, yes, very soon, fix the tests which fail with storm19:36
barrykiko: cool.  that'll be fun19:37
kikoflacoste, because we'd not update edge until all the tests actually passed in-tree19:37
* Rinchen questions barry's idea of fun.19:37
BjornTkiko: do we have a list of tests that fail?19:37
flacostei don't understand how this will work19:37
kikothis can be very disruptive; we're not sure how much, but if it's a mess we'll need to figure out what to do with 1.2.619:37
flacostewe'll close PQM?19:37
marsor we will focus PQM on Storm integration?19:37
flacostei mean, the test suite pass or doesn't pass19:38
flacostethere is no way to land if the test suite doesn't pass19:38
kikoflacoste, no, but we'll either disable all failing tests and merge19:38
mthaddonI'm assuming we'd keep PQM open, but would be working on the storm integration branch instead of devel19:38
kikoor work on the storm integration branch19:38
kikomthaddon, doesn't that require all tests pass?19:38
mthaddonkiko, it does, but it's up to you however many of the tests you want to enable - can do it progressively, or all at once19:38
kikoBjornT, not yet, but james will produce one. I'm hoping it's 30 not 15019:39
flacostekiko: if problematic tests are disabled to allow some merge to go, that doesn't help keep the focus on storm19:39
kikoif it's 150 then it's a no-go19:39
kikoso we'll see19:39
kikomthaddon, gotcha19:39
Rinchenwhat I'm hearing is merging storm integration with devel and fixing it so everything passes. Until then, edge won't update.19:39
kikoflacoste, it's not "some merge" it's the storm merge onto RF19:39
kikoRinchen, yes19:39
Rinchena bold move indeed19:39
BjornTkiko: ok should we make an effort into finding performance regressions as well?19:39
kikoBjornT, yes, though to me that's second priority19:40
flacostemars produced a script for that19:40
BjornTkiko: or rather, how much of an effort should we make19:40
flacostebut jamesh never give feedback on it19:40
Rinchenmars, I saw that spec and script. I meant to ask about that.19:40
kikoBjornT, it's serialized -- once your tests pass, you can look at that19:40
marsflacoste, yes, but it needs a kind soul to try it out19:40
kikoflacoste, I think jamesh is stuck before that point19:40
flacostei don't think so, all page tests run19:40
flacosteand this analyze the log file of the page tests19:41
kikodoctests don't19:41
BjornTflacoste, mars: does the script use existing sample data?19:41
kikoflacoste, sure, but jamesh is only one bold soul19:41
mptWould it make sense to have a ratchet, so that storm can land while tests are still failing, but you can't make any further landing that increases the number of failures?19:41
mptthat would help keep the focus19:41
kikompt, too complex to add at this point, though interesting19:41
kikoflacoste, he won't look at perf regress until he's got all the tests running19:41
marsBjornT, it compares the access logs for two runs, so you can benchmark storm-storm, or storm-trunk19:41
kikoanyway19:41
kikoI don't want to run overtime, but I also think we need to be serious about the move and help us acheive what we set out to do19:42
kikostorm is the future19:42
flacosteanyway, this introduce more uncertainty in the 1.2.6 planning19:42
kikoflacoste, yes, I noted that up-front. we have some buffer time.19:42
flacosteno we don't :-)19:42
kikobe brave!19:42
kikowe do at my discretion only ;-)19:43
BjornTmars: so i can create a bunch of data, access a few pages, and compare the result?19:43
kikoRinchen, feel free to wrap up, people are going to start asking me complicated questions now19:43
Rinchenok, time to wrap up now that the storm is over :-)19:43
flacosteBjornT: yes19:43
marsBjornT, yep19:43
BjornTcool19:43
Rinchenok then... what an eventful chat19:43
kikoAH!19:44
cprovvery cool !19:44
Rinchenplease ensure any of your absent team members read the log19:44
kikoone thing I can provide for you to look into19:44
kikooh damn, it's in my xchat log19:44
kikoone sec19:44
kikoon devpad: ~jamesh/errors-systemdocs.txt19:44
kikothat's the failures accumulated in doc/*19:44
marsRinchen, should we stick around after the meeting end to pepper kiko with questions? :)19:44
Rinchenmars, you can!19:45
RinchenThank you all for attending this week's Launchpad Developer Meeting.19:45
Rinchen== the end ==19:45
kiko== snif ==19:45
Rinchenon time photo finish19:45
sinzui_consider me gone_19:45
SteveAthanks!19:45
RinchenOk __sinzui__19:45
mrevellthanks19:45
=== mwhudson__ is now known as mwhudson
=== nand is now known as nand_
=== nand_ is now known as _nand_
=== _nand_ is now known as nand__
=== nand__ is now known as nand

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