#launchpad-meeting 2008-03-04 <barry> hello and welcome to this week's asiapac launchpad reviewer's meeting <barry> is anybody here today? :) <barry> jamesh, mwhudson ? <jamesh> hi <barry> jamesh: hi. is it even worth having this meeting today? <mwhudson> hello <jamesh> barry: a short meeting wouldn't hurt <barry> great. i'm just glad i remembered this week :) <barry> [TOPIC] agenda <barry> == Agenda == <barry> * Roll call <barry> * Next meeting <barry> * Action items <barry> * Queue status <barry> * Mentoring update <barry> * Review process <barry> * sabdfl request: make sure enums to be in the same interface files as the schemas where they are expressed. <barry> * thumper - unwrapping import statements (line wrapping that is) <barry> * drive-by copyright year updates <barry> (we can blow through this pretty quickly) <barry> [TOPIC] next meeting <barry> same time next week? i guess most people will be back from sprinting and meetings by then? <jamesh> sure. <mwhudson> makes sense to me <barry> great <barry> [TOPIC] action items <barry> thumper's not here and his was the only continued item <barry> [TOPIC] queue status <barry> #startmeeting <MootBot> Meeting started at 03:04. The chair is barry. <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] <barry> crap, helps if i turn on mootbot <mwhudson> :) <barry> [TOPIC] queue status <MootBot> New Topic: queue status <jamesh> I'm currently working on stub's one, and am also on call <mwhudson> jml's is merge-approved, really <barry> jamesh: great thanks. i couldn't quite finish sinzui's before i had to leave for the evening, but i'm going to try to finish it tonight <jamesh> jml is assigned one of cprov's branches which could be a problem <barry> it's a big branch iirc <jamesh> the other branches owned by jml and thumper are for other people who are sprinting <barry> are they generating the branches during the sprint? <jamesh> I have no idea <mwhudson> i don't think so <jamesh> the team leads probably won't, and the bzr sprinters would be working on bzr stuff <barry> so they're probably not itching for their lp branches <barry> anything else going on about the queue? <barry> [TOPIC] mentoring update <MootBot> New Topic: mentoring update * mwhudson is slightly surprised to see a branch he thought he'd landed still on there <mwhudson> (but not on-topic for this meeting) <mwhudson> barry: a bit fat "n/a" to this one? <barry> i think so! <barry> [TOPIC] review process <MootBot> New Topic: review process <barry> * sabdfl request: make sure enums to be in the same interface files as the schemas where they are expressed. <barry> this was from a couple of weeks ago, but because i missed last week's meeting here, i wanted to keep it on the list <mwhudson> noted <jamesh> noted. <barry> great, thanks <barry> * thumper - unwrapping import statements (line wrapping that is) <barry> there was a vote on this at the last ameu meeting. it was rejected ;) <barry> i'm thinking of keeping it on the list so thumper has a chance to defend his position <jamesh> I had no real opinion on this one way or the other when it came up in the branch I was reviewing <jamesh> barry: did you see thumper's reasoning in the review where it came up? <barry> jamesh: i didn't * jamesh looks <jamesh> """I have personally found that the import areas are a high source of merge conflicts. <jamesh> Something that the bzr hackers do is to split them like this once there is more than <jamesh> one line of imports. This is especially useful in places where there is a high likelyhood <jamesh> of different people editing the file at the same time. This way the bzr merge code <jamesh> and just insert the new imports instead of conflicting.""" <barry> ah. that did come up when we discussed it. the general consensus was that it wasn't hard to resolve the conflicts and people didn't want to read through a page of imports <jamesh> so his reasoning is for usability reasons rather than style <jamesh> okay. <jamesh> It hasn't often been a problem for me -- if the list of imports is so large that it is a problem, then the file probably has too much code in it :) <mwhudson> we need an import-aware merge algorithm! <barry> jamesh: agreed! :) <mwhudson> but i don't really see this as a big problem <barry> mwhudson: +1 <mwhudson> mash the import statements together, M-x sort-imports, run pyflakes <barry> i'll relay the decision to thumper and we can put it back on the agenda if he wants <barry> mwhudson: yep, that was basically the consensus! <barry> moving on... <barry> * drive-by copyright year updates <barry> i've started to see some branches trickle in with updates to the copyright line. i guess we don't have a script that fixes these, but do we have a policy about them? <barry> or is it cool to just fix 'em as you see em? <jamesh> Is there a particular problem we're trying to solve here? <mwhudson> i'm never really sure what these copyright lines are for, truth be told <barry> not a particularly serious one imo since we don't release the code <jamesh> I mean, there is no problem with people updating the copyright lines, but it probably doesn't make a difference <barry> but ianal <barry> jamesh: that's the way i feel about <barry> it <jamesh> any code that does get released will need the copyright headers changed to something other than "All rights reserved" anyway <barry> it's kind of silly that those lines are there at all i guess :) <mwhudson> right <jamesh> barry: it is worth having there in case a file gets separated from the tree <jamesh> for the same reason people license headers in the source code that they release <barry> right, but anything that gets released will need to be vetted anyway <barry> but i guess we're getting off track. <jamesh> yes <barry> it's okay if people update them in their branch, but we don't care too much <barry> anyway, that's it for me. anything you guys want to relay to the ameu crowd? <jamesh> yep (although reviewers should still be making sure that a license header appears in new files) <barry> yep, definitely <jamesh> nothing from me. <mwhudson> me neither <barry> cool <barry> well, thanks guys and talk to you soon! <barry> #endmeeting <MootBot> Meeting finished at 03:23. #launchpad-meeting 2008-03-05 <barry> #startmeeting <MootBot> Meeting started at 15:00. The chair is barry. <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] <barry> hello everybody and welcome to this week's ameu reviewer's meeting. who's here today? <gmb> me <salgado> me <danilos> me <sinzui> me * gmb listens to the wind blowing around the mostly empty meeting <barry> yeah, the asiapac meeting was pretty sparse too. sprints and team-leads meeting <barry> hopefully then we can make this quick. <barry> [TOPIC] agenda <MootBot> New Topic: agenda <barry> * Roll call <barry> * Next meeting <barry> * Action items <barry> * Queue status <barry> * Mentoring update <barry> * Review process <barry> * sabdfl request: make sure enums to be in the same interface files as the schemas where they are expressed. <barry> * thumper - unwrapping import statements (line wrapping that is) <barry> * drive-by copyright year updates <barry> [TOPIC] next meeting <MootBot> New Topic: next meeting <barry> i will be traveling to pycon next week. can someone else chair this meeting? <danilos> barry: can we have MootBot do it? :) <barry> :) <barry> other than that, does anybody else know they will not be here for the next meeting, same time and place? <barry> also note that i will miss the 3/19 meeting too <gmb> barry: I think you're better mailing the list about next week's chair. <barry> gmb: +1 <barry> [ACTION] barry email list about needing a chair for the next two weeks <MootBot> ACTION received: barry email list about needing a chair for the next two weeks <barry> [TOPIC] action items <MootBot> New Topic: action items <barry> * intellectronica to solicit feedback on ReviewRequestTemplate from launchpad <barry> mailing list. <barry> i think this was done <gmb> Yes, it was. <barry> cool <barry> * barry to communicate to l-r list that when allocating general queue <barry> reviews, please favor (but don't overwhelm) new recruits <barry> done <barry> * barry to communicate to l-r list that >800 line branches need to be <barry> arranged with a reviewer '''before''' they are submitted <barry> done <barry> * gmb to hack review-submit to enforce 800 line limit. <gmb> Done, but I need to run it past mwhudson. <gmb> So leave it as an action for next week, I think. <barry> gmb: cool, np <barry> gmb: thanks <gmb> np <barry> [TOPIC] queue status <MootBot> New Topic: queue status <statik> me! sorry i'm late <barry> i think intellectronica and danilo kicked ass today <sinzui> We have a volunteer for a chair <barry> last night the general queue was huge. today, it's small <danilos> yeah, we are both on last branches in general queue <danilos> (both by barry) <barry> statik: wow, thanks for chairing this meeting for the next two weeks! :) <barry> danilos: you rock * gmb chuckles at intellectronica's email. <barry> we have 6 pink branches, with 3 of those in conflict <statik> barry: I deserve that. sure , I can do that <barry> statik: it's okay if you can't or don't want to :) <gmb> intellectronica would be here but millbank caught fire so he's gone home :) <barry> jeebus <statik> i vill do it <gmb> I think "caught fire" might be an exaggeration <barry> statik: awesome thanks. <barry> salgado: what's up with julian's embargoed-archive branch? <salgado> barry, I think it's been approved already <barry> salgado: oh cool, PR probably wasn't update. no wories <salgado> and I forgot to update its status <barry> [TOPIC] mentoring update <MootBot> New Topic: mentoring update <barry> any mentors or mentoree comments today? <sinzui> I should give more branches to schwuk <barry> sinzui: give them /all/ to schwuk and take the weekend off :) <sinzui> barry: to hack of formatdoctest,py? <barry> sinzui: :) <barry> [TOPIC] review process <MootBot> New Topic: review process <barry> * sabdfl request: make sure enums to be in the same interface files as the schemas where they are expressed. <barry> have i mentioned that one here before? <gmb> Yes, last week, I believe :) <sinzui> yes * barry needs some ginko <sinzui> There is always an issue of circular imports that must be reconciled. <barry> sinzui: yep <barry> though for the one specific instance i changed, it wasn't a problem <barry> e.g. from canonical.launchpad.interfaces.teammembership import TeamMembership <barry> (or whatever) * barry skips thumper's proposal which we rejected last week <barry> * drive-by copyright year updates <sinzui> I can fix that with sed in a few minutes. <barry> sinzui: do you want to take that as an action item? <barry> sinzui: you'll need something to do this weekend :) <sinzui> barry: we /seriously/ want all the 2007 => 2008? <barry> well, i don't think it's a big deal personally <sinzui> I can do it. It wont take long. <barry> i think it's fine to do it as a drive-by but if you're motivated, rs=barry :) * sinzui still has a trailing whitespace script sitting in Tomboy <barry> [ACTION] sinzui to sed-ify update to copyright years <MootBot> ACTION received: sinzui to sed-ify update to copyright years <danilos> I'm pretty sure we've got files which have 2006 as the last year <danilos> or even 2005 or 2004 <barry> danilos: we're all over the map <barry> i'm sure we have files that have only one year in them <sinzui> danilos: right <barry> sinzui: oh, btw, i have a python script that does this for mailman. might be easily adapted, if sed isn't your bag <barry> sinzui: it handles copyrights with only one year in them <danilos> I don't think it's a big deal either (once we start opening up parts of LP, we might want to take a look over that, but no big deal atm) <sinzui> barry: I also have a my own find script written in Python that should be upgraded to do replace. <schwuk> barry: sorry - got delayed <barry> sinzui: cool. i'll leave it to you then <barry> schwuk: np <barry> danilos: agreed <barry> well, anyway that's it for me today. i'll open up the floor in case y'all have anything not on the agenda <gmb> I have one thought. <gmb> Which is this: <gmb> Can people, devs and reviewers alike, *please* make sure to Reply All to review emails rather than just replying to the list. <gmb> The conversation should be between reviewer and developer with a copy going to the list. <salgado> +1 <barry> gmb: +1 <sinzui> +1 <gmb> Emailing the list directly and not at least CCing the reviewer means that it can get filtered away. <barry> gmb: do you want me to send an email on that? <gmb> barry: If you would, yes. * gmb gets off his soapbox <gmb> Thanks. <barry> [ACTION] barry will email about cc policy on reviews <MootBot> ACTION received: barry will email about cc policy on reviews <danilos> well, I'd say people should generally use "Reply-All" ("follow up") anyway, except when they specifically target a person (to exclude everybody else) <gmb> danilos: Yes. It seems, though, that quite a few people do "reply to list" instead of "reply all" <statik> email is for old people <gmb> I think it's habit for mutt users to hit "L" when replying to mailing list messages ;) <danilos> gmb: I found that the headers sometimes seem a bit different when an email finally hits launchpad-reviews list <gmb> danilos: Is there some munching going on? <gmb> Munching? <gmb> Munging. <barry> i don't think so. should definitely not be munging reply-to <danilos> for example, I've seen my emails get there without CCs to my mentor or a developer, even if they got their messages <gmb> Hmm. <gmb> danilos: Now that you mention it, I saw that whilst salgado was metoring me. His replies would go to the developer and the list, but not to me directly. <danilos> for example, look at my emails from today: I've sent them all to tom.berger@ as well, and that's not showing up in the list <gmb> barry: This might be worth looking into, though I haven't got the first clue about why it'd be happening. <danilos> gmb: what would barry know about mailing lists anyway? ;) <barry> actually, nothing :) <gmb> Harsh. * barry has no clothes <gmb> I hope that's an emperor metaphor... * sinzui hands barry a banana leaf <barry> gmb: i haven't noticed a problem with ml traffic. can you or danilos email specifics and/or an example? <gmb> barry: I'll see if I can find one in my archives. <barry> gmb: take it anyway you want. i'm not saying :) <danilos> barry: sure, I can send you both what my client sent, and you can have a look at the same message in launchpad-reviews <barry> gmb, danilos cool <barry> anything else today? <barry> 4 <barry> 5 <barry> er <barry> 5 <barry> 4 <barry> 3 <barry> 2 <barry> 1 <barry> #endmeeting <MootBot> Meeting finished at 15:31. <barry> thanks everyone! <gmb> Cool, thanks barry. #launchpad-meeting 2008-03-06 <intellectronica> Rinchen: bing * mpt waves blearily to mwhudson <mwhudson> hi mpt <mwhudson> i didn't even get up in time to make coffee :/ <mpt> I'd actually prefer this meeting at 1200 UTC, because that's when my other meeting is :-P <thumper> mpt: ah, no <gmb> mwhudson: What you get for moving to the other side of the world, mate. <mwhudson> oof <intellectronica> mwhudson: it's not even clear that there is a meeting <barry> me? <intellectronica> but don't be sorry - waking up early builds character :P <sinzui> It's all about you <thumper> we're waiting for kiko to say yay or nay <mwhudson> wunderbar <mpt> #launchpad says "Next meeting (all welcome): Thu 6 March 2008, 1800UTC #launchpad-meeting" <thumper> but he isn't around right now <intellectronica> yeah, barry is our new Cod <salgado> I think barry was volunteering to chair the meeting? ;) * barry searches for his cape <sinzui> waking up early is an opportunity to have an accident while in a somnambulistic state * barry only finds his piece <statik_> thae cable company would choose *right now* to disconnect me <sinzui> No capes! Edna Mode was very clear on this point <intellectronica> sinzui: that's a /great/ word <barry> even cod capes? <mthaddon> or es capes <mpt> This conversation is in a soporific state <kiko> hello hello <statik_> shalom <barry> mpt: better than sophomoric <mpt> but kiko will soon fix that <sinzui> barry: Can you imagine the stench of a cod cape? You will certainly make friends with all the neighborhood cats. <statik_> al-maisan! welcome <mpt> Welcome al-maisan <cprov> me, me <kiko> where's that good ole Rinchen character <barry> sinzui: you're right. and ms mode says nothing about cod pieces, so... <al-maisan> statik_: thanks :-) <gmb> Riiiiiiiiiincheeeeeeen! <kiko> ORRIGHT <thumper> Rinchen says he's busy <bigjools> slacker <kiko> ok <sinzui> barry: Are you hinting that you are wearing a cod piece? <kiko> * Next meeting <kiko> * Actions from last meeting <kiko> * Oops report (Matsubara) <kiko> * Critical Bugs (Rinchen) <kiko> * Bug tags <kiko> * Operations report (mthaddon/herb) <kiko> * DBA report (stub) <kiko> * Sysadmin requests (Rinchen) <kiko> * New packages required (salgado) <kiko> * A top user-affecting issue (mrevell) <kiko> * Doc Team report (mrevell) <kiko> me <kiko> #startmeeting <MootBot> Meeting started at 18:07. The chair is kiko. <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] <barry> sinzui: hints and allegations <mthaddon> me <flacoste> me <leonardr> me <sinzui> me <mars> me <kiko> me <thumper> me <matsubara> me <adeuring> me <barry> me <mpt> me <FreeNode> me <bac> me <bigjools> me (until 1830UTC) <al-maisan> me <carlos> me <salgado> me <cprov> me <schwuk> me <stub> me <intellectronica> me (but leaving early, ~18:35) <gmb> me <statik_> me <kiko> well, we seem to have an official FreeNode representatirrrve <kiko> very good <mwhudson> me <carlos> jtv is travelling <BjornT> me (might leave a bit early as well) <kiko> mrevell is on the train <kiko> rinchen's blown us off <thumper> yup <kiko> steve's chatting up girls <kiko> what else <BjornT> allenap's internet connection is flakey, so he might not make it <kiko> ok <kiko> let's make this quick then <thumper> kiko: code's not blocked, can I go now <thumper> ? <kiko> thumper, no. <gmb> kiko: allenap just phoned to say he /won't/ make it <SteveA> me <kiko> [TOPIC] * Next meeting <MootBot> New Topic: * Next meeting <EdwinGrubbs> me <kiko> SteveA!! <SteveA> kiko: ! <kiko> so next meeting, who can't be here? <SteveA> me <barry> kiko: me <EdwinGrubbs> kiko: me <SteveA> I'll be en route to PyCon <mars> me <mthaddon> I will be off next week (vacation) * kiko can't live without mthaddon! <kiko> I'll be here <kiko> so [AGREED] meeting next week, same time, same location. * kiko looks at MootBot <kiko> [AGREED] meeting next week, same time, same location god dam mit <MootBot> AGREED received: meeting next week, same time, same location god dam mit <schwuk> maybe it didn't like the "so " <kiko> [TOPIC] Actions from last meeting <MootBot> New Topic: Actions from last meeting <kiko> * repost: salgado to investigate adding turbogears for codebrowse and germinate <kiko> * repost: danilos to investigate profiling and Rosetta team to prepare proposal for next week to fix remaining timeouts <kiko> * repost: mthaddon - discuss updating devpad rocketfuel archives to packs and do so if lifeless approved. <kiko> * repost: kiko and cprov - discuss bug 193656 <ubotu> Launchpad bug 193656 in soyuz "Process-death-row procedure became very slow" [Critical,Triaged] https://launchpad.net/bugs/193656 <kiko> * matsubara to file a place holder bug for OOPS-788EB21 and assign it to carlos who is already investigating it. Done: bug 196679 <ubotu> Launchpad bug 196679 in rosetta "ValueError on +language-packs" [Undecided,New] https://launchpad.net/bugs/196679 <kiko> * matsubara to investigate OOPS-788EC5 and confirm if it's related to 195809, if not file a new bug. <danilos> me <kiko> * matsubara to email flacoste about oops in 196661 and check if it was fixed by 191074. Done: 196661 is a new issue. Francis on it. <kiko> * cprov and salgado to discus python-apt packaging in lpdebs <mthaddon> kiko, devpad has been upgraded to packs format <kiko> mthaddon, good job. <matsubara> it's not related and I just filed bug 199203 for OOPS-788EC5 <kiko> salgado? <ubotu> Bug 199203 on http://launchpad.net/bugs/199203 is private <danilos> kiko: we have some reports, haven't agreed on the action yet (a lot of stuff has changed with the new DB hardware) <kiko> danilos, yeah, the performance is amazing this week! let's keep our eyes peeled, but it looks much better. <kiko> flacoste, do you know the answer to the actions for salgado? <salgado> kiko, haven't investigated yet <salgado> kiko, I think we're going to put turbogears inside sourcecode/ <danilos> kiko: some of my suspicions have been confirmed (i.e. lots of translations mean slower fetching of external suggestions), but some might need more investigation <kiko> salgado, do you need some input from anywhere? <salgado> kiko, and germinate should be easy to add <salgado> kiko, nope, don't think so <kiko> salgado, what do we need to do to make these happen? don't say give me 28h days <salgado> kiko, I'll do it tomorrow, promise! <kiko> salgado, :) thanks <kiko> so cprov and I have worked on the bug we had assigned to ourselves to fix death row slowness <salgado> they don't seem to be urgent, so they kept slipping <mwhudson> salgado: be warned, turbogears doesn't work with the version of sqlobject that's in sourcecode... <kiko> elmo gave me a hint, and cprov worked out a patch that makes it, oh, 30x faster :) <cprov> kiko: yes, and julian will be reviewing it in a bit <salgado> mwhudson, that's good to know. thanks! <kiko> [ACTION] salgado to investigate codebrowse and germinate inclusion in sourcecode, TOMORROW :) <MootBot> ACTION received: salgado to investigate codebrowse and germinate inclusion in sourcecode, TOMORROW :) <cprov> salgado: I'm just waiting to the new python-apt package to be published in gutsy-backports. <kiko> cprov, any ETA for that from mvo? <kiko> matsubara, what about your action items? <cprov> kiko: no :( <matsubara> kiko: already answered. <matsubara> kiko: <matsubara> it's not related and I just filed bug 199203 for OOPS-788EC5 <ubotu> Bug 199203 on http://launchpad.net/bugs/199203 is private <matsubara> kiko: and the other two are already done, and updated in the MeetingAgenda items themselves <kiko> matsubara, ah, I see that we've got some resolved ones there. thanks! <kiko> cool <kiko> matsubara, are any of them high or critical? <jml> hello! <kiko> hey jml <kiko> thumper, just saw your OOPS landing fix, thanks a lot -- we might need to get that cherrypicked if it's happenning on lpnet? <kiko> [TOPIC] * Oops report (Matsubara) <MootBot> New Topic: * Oops report (Matsubara) <matsubara> kiko: only flacoste's one <kiko> thanks. * flacoste is a slacker <matsubara> Today's oops report is about bugs 192242, 198828 <ubotu> Launchpad bug 192242 in launchpad-bazaar "OOPS linking an existing branch to a series" [High,Confirmed] https://launchpad.net/bugs/192242 <ubotu> Launchpad bug 198828 in launchpad "Upload project file with non-ascii character in the filename breaks the page" [High,Confirmed] https://launchpad.net/bugs/198828 <matsubara> Bug 192242 has no assignee yet, mwhudson recently changed its importance to High. Any code-team takers? <flacoste> but it should be fixed for next week <matsubara> Yesterday I chatted with Edwin about bug 198828. He took it and will have a fix soon. <kiko> thanks flacoste <mwhudson> i can look at it <kiko> matsubara, this happens because we have non-ascii filenames in islocc, right? <matsubara> Also bug 199203, which I just reported, could use some help from the code team to figure out the cause behind the oops <ubotu> Bug 199203 on http://launchpad.net/bugs/199203 is private <matsubara> kiko: yes <mwhudson> though i worry that i'm going to get confused about the intended workflows around productseries <kiko> mwhudson, hmm, if you wanna chat with me or thumper while we are around here, I'd be happy <kiko> mwhudson, if you like, arrange a call with us for tomorrow <kiko> can be early if you like <kiko> matsubara, thanks! <mwhudson> kiko: ping me when you get up? <mwhudson> i'm likely to be working a bit later tonight anyway <thumper> kiko: the code oops is on lpnet, so yes a cherry pick would be a good idea <kiko> thumper, please arrange it with mthaddon or herb_, rc=kiko <kiko> [TOPIC] * Critical Bugs (Rinchen) <MootBot> New Topic: * Critical Bugs (Rinchen) <kiko> we're going to skip this this week, unless anyone has a critical bug to raise <sodarock_home> matsubara: where you going to talk about https://bugs.launchpad.net/launchpad/+bug/196253 <ubotu> Launchpad bug 196253 in launchpad "OOPS importing pgp key" [High,New] <kiko> aha! <matsubara> oh sorry, forgot about that one. <kiko> sodarock_home, we can do that as a top-user-affecting-issue-of-the-week <kiko> (if matsubara likes) <matsubara> yep, could be <kiko> ok cool <kiko> so any critical bugs apart from the ones above? <matsubara> I'll proxy mrevell stuff anyway <kiko> ok <kiko> SteveA, ping? <kiko> [TOPIC] * Bug tags <MootBot> New Topic: * Bug tags <SteveA> kiko: hi <kiko> I had one proposed tag <kiko> wanted input from BjornT, SteveA and others <kiko> dupefinder <kiko> <kiko> Bugs related to the duplicate matcher <kiko> <kiko> kiko <flacoste> dupefinder? <kiko> <kiko> [WWW] https://bugs.edge.launchpad.net/malone/+bug/174443 <ubotu> Launchpad bug 174443 in malone "Project groups need option to offer bug/question suggestions across projects" [Undecided,New] <kiko> yep <kiko> anyone +/- on that? <mpt> There are about 3~4 bug reports that tag could be used for, that I know of <statik_> i am in favor of all tags <kiko> it's a bit of rather unique functionality we have <kiko> and we have it in answers and in bugs <kiko> anyone strongly against it? <kiko> going <kiko> going <kiko> gone <kiko> okay, I'll self-approve that one. :) <SteveA> nice <kiko> [TOPIC] * Operations report (mthaddon/herb) <MootBot> New Topic: * Operations report (mthaddon/herb) <mthaddon> DB migration for staging and demo now complete <mthaddon> Feeds URLs should now be working correctly on demo <mthaddon> Working on missing bug report for intellectronica <mthaddon> Need to work on capturing coredumps for PQM <mthaddon> that's it from herb and myself unless there are any questions <danilos> how long will we be without production DB mirror? <danilos> SteveA: ^ <mthaddon> danilos, that's up to SteveA and elmo to discuss <SteveA> we discussed it <mthaddon> danilos, but there's always staging <SteveA> I want you to use staging for this. You'll need to arrange with kiko and joey when it's appropriate for you to do heavy lifting on staging. <kiko> danilos, does it need to be r/w? <kiko> mthaddon, are the last snags with updating staging finished? <danilos> kiko: yes, occasionally (when testing scripts like we want to do right now) <mthaddon> kiko, yes, all looking good now <kiko> mthaddon, quite a number of them -- whose fault is that? <mthaddon> kiko, mine :( <kiko> was our setup complicated? <kiko> or undocumented? <kiko> or something else? <mthaddon> kiko, just more complicated when the DB and app server are on different boxes <kiko> mthaddon, yeah, I can see how that is <kiko> [TOPIC] * DBA report (stub) <MootBot> New Topic: * DBA report (stub) <stub> AuthPersonSplit has been drafted and wants feedback. Nothing else to report this week. <mthaddon> kiko, since we want to restore the DB to a new DB, and then if that works, bring the app server down, rename the DB, rollout new code, bring the app server back up, etc. <carlos> danilos: you didn't wait for the RT section! :-P <danilos> carlos: you get to mention it there, and then in the 'Translations: blocked' :) <mthaddon> kiko, and we also have authserver and mailman to worry about - which we were before too, but the new script is a little more comprehensive <kiko> mthaddon, yeah, I can see how that is. congrats on getting it on! <kiko> stub, who do you want feedback from? <stub> barry, sabdfl, stevea, kiko, salgado (already done), francis <stub> And anyone else interested :) <kiko> stub, we could do a phone call tomorrow earlier, if you like? <kiko> [TOPIC] * Sysadmin requests (Rinchen) <MootBot> New Topic: * Sysadmin requests (Rinchen) * barry will try to provide said feedback soon <carlos> RT: #30167 <Rinchen> Hi! Is anyone blocked on an RT or have any that are becoming urgent? <SteveA> I'm hungry <SteveA> I'll file an RT request <kiko> hmmm <Rinchen> back to you kiko <gmb> SteveA: Elmo will feed you shortly <stub> kiko: Read the spec first and see if a phone call is warrented. Hopefully I won't have to have calls with everyone :) <carlos> Rinchen: getting back a mirror to test data migration script for a regression in Dapper langauge packs <kiko> salgado, cprov: do you guys need RTs? <kiko> stub, we could have a confcall is my idea <mthaddon> SteveA, is RT 30167 obsolete based on your discussions? <flacoste> since most of us are in london <Rinchen> carlos, ok...send me the rt number in an email. <kiko> (for any of that packaging stuff) <cprov> kiko: no, it's all good. <Rinchen> please! <flacoste> apart barry and salgado - who already gave you feedback <carlos> Rinchen: ok <stub> kiko: ok. tomorrow. <kiko> cool <SteveA> mthaddon: is that to do with translations using a server? <kiko> stub, okay, will arrange -- thanks <kiko> [TOPIC] * New packages required (salgado) <MootBot> New Topic: * New packages required (salgado) <mthaddon> SteveA, yeah, staging accounts for translations <salgado> if any of the branches you're working on right now depends on any library which is not part of the launchpad-dependencies package, come talk to me ASAP. <SteveA> mthaddon: I disucssed it with kiko and elmo <kiko> mthaddon, let's chat about this in 5 minutes <mthaddon> cool <cprov> I'd like to know if we have a due date to migrate lp-dev default env to hardy. <kiko> any changes requiring new packages or a sourcecode update? <kiko> cprov, hmm, we don't yet. what's broken? <SteveA> mthaddon: and they can have staging accounts, but we'll need a process for them to agree when they're going to be doing r/w or resource intensive stuff <cprov> it will affect the alternatives for lp-dep package <cprov> kiko: on hardy we won't need any change in lp-dep. <kiko> I see. <kiko> well, remind salgado if you remember you need a package! <kiko> [TOPIC] * A top user-affecting issue (mrevell) <MootBot> New Topic: * A top user-affecting issue (mrevell) <matsubara> proxying mrevell: <matsubara> User-affecting issue: <matsubara> Hello! Today's user affecting issue was raised during the Bazaar <matsubara> sprint here in London and is to do with splitting bug reports. <matsubara> If someone reports a bug and it turns out that the issue is actually <matsubara> caused by more than one bug, it would be useful to be able to split <matsubara> the bug report. This is essentially the same as creating a new bug <matsubara> report, except that this new process of splitting a bug would allow <matsubara> the splitter to choose which comments would move into the new bug. <kiko> matsubara, not a bad feature, though perhaps a client-side script that cloned a bug would be a mitigation step <kiko> it wouldn't remove comments <matsubara> And I'm looking for a volunteer or mentor for bug https://bugs.edge.launchpad.net/launchpad/+bug/196253. It's one line change fix but I have no idea how to test. <ubotu> Launchpad bug 196253 in launchpad "OOPS importing pgp key" [High,New] <kiko> matsubara, cprov might be a good mentor for that? <mpt> That feature would be partly JavaScript, yes <cprov> matsubara: I can help you with that. <kiko> cool <mpt> it's reported as bug 158718, which is currently marked Low <ubotu> Launchpad bug 158718 in malone "ability to split bugs" [Low,Confirmed] https://launchpad.net/bugs/158718 <kiko> matsubara, can you relay that back as mrevell? <matsubara> cprov: ok. thanks. I'll chat with after the meeting <matsubara> kiko: sure thing. <matsubara> thanks mpt <cprov> matsubara: cool <kiko> [TOPIC] * Doc Team report (mrevell) <MootBot> New Topic: * Doc Team report (mrevell) <matsubara> proxying again: <matsubara> Hi. This week I've been down in London to take part in some of the <matsubara> Bazaar sprint and also to meet with members of the Launchpad team who <matsubara> have been here this week. <matsubara> The most important thing to come out of this for Launchpad <matsubara> documentation is that I've spoken with the Launchpad team leads. I've <matsubara> taken notes regarding the next few months of work on each of their <matsubara> parts of LP and this will feed into my user guide and new LP tour <matsubara> work. <matsubara> A new way of implementing context help in the LP UI has been discussed <matsubara> as well in London. mpt is planning to create mock-ups and a user <matsubara> experience description and I'm working to review our current UI text <matsubara> and produce new context sensitive help. <matsubara> Thanks. <kiko> okay, this is cool <kiko> nothing else to cover? <matsubara> nope, back to you kiko <kiko> [TOPIC] * Blockers <MootBot> New Topic: * Blockers <Rinchen> Releases Team: mpt blocked on foundations. <kiko> you know what to doooooooooooo <SteveA> SC: not blocked <thumper> code: not blocked <flacoste> Foundations: not blocked <kiko> flacoste, what is this blocked on foundations madness??? <carlos> Translations: Blocked on RT #30167 <flacoste> Rinchen: i'll unblock you tomorrow <BjornT> Bugs: not blocked <flacoste> Rinchen: actually, you're not blocked, you have other things to do :-) <gmb> Bugs team: not blocked <carlos> flacoste: is that my fault? * gmb should read scrollback <flacoste> carlos: nope <adeuring> HWDB: not blocked <kiko> thanks adeuring <carlos> ok <kiko> carlos, that RT should me sorted out real quick. <flacoste> carlos: well, you're also a blocker eventually, but that's not the one he's referring to :-) <mpt> SteveA had this other word for "not blocked, but needing stuff from" <kiko> okay, thanks everyone <mpt> But I forget what that word was <kiko> see you again next week <kiko> #endmeeting <MootBot> Meeting finished at 18:40. <carlos> flacoste: that's what I suspected... :-P <stub> Bed time <carlos> flacoste, mpt: I will try to get that done tomorrow. At least started * stub waves goodnight <kiko> night stub <mwhudson> thanks kiko <kiko> thanks mwhudson <flacoste> carlos: what was your next step? <carlos> kiko: is there anything I should do to get unblocked? <kiko> mwhudson, if you wanna call us tomorrow, let me know <kiko> carlos, no, I'll see to it with elmo <mpt> thanks carlos <carlos> kiko: ok, thank you <flacoste> carlos: is it the Navigation menu links? <mwhudson> kiko: well, i'll have a look-see today, and if i'm confused will hassle you when you get up :) <kiko> mwhudson, sounds good. thanks! <carlos> flacoste: take a look to current code, prepare an action plan and ask for a preimplementation call <carlos> flacoste: yeah <flacoste> carlos: ok, i discussed this with SteveA, so have a good idea of the solution, which is very easy actually <flacoste> carlos: we can discuss it tomorrow <carlos> flacoste: ok <carlos> flacoste: should we agree the time now? <flacoste> carlos: 15:30UTC? <carlos> flacoste: I need to be out of the office around that time <carlos> it needs to be earlier or much later... <flacoste> carlos: ok, let's see how it goes here tomorrow, otherwise, it probably have to be next week <flacoste> carlos: i'll try to find some time during a break in the morning discussions <carlos> ok * statik_ curses the network <carlos> flacoste: thanks <statik_> lpcomm:à¤²à¤¦à¥ <statik_> lpcomm: not blocked * statik_ goes downstairs to talk with the cable installers #launchpad-meeting 2008-03-11 <Seeker`> Hi, just a quick message to let you know that Mootbot may be disappearing for a while in the near future due to hosting issues <intellectronica> me #launchpad-meeting 2008-03-12 <gmb> So, who's chairing the meeting today? <sinzui> gmb: statik <gmb> Cool. <salgado> I almost said me, thinking that the meeding had started already <gmb> Curse! My trap is foiled. <gmb> Does statik know he's chairing? ;) <sinzui> gmb: barry and he discussed it <gmb> Right. <gmb> I'll go round up some of the troops... <intellectronica> me <danilos> me <jtv> me <flacoste> me <gmb> Hold your horses boys <statik> sorry folks <statik> fsck runs at the *worst* possible time <statik> #startmeeting <MootBot> Meeting started at 15:06. The chair is statik. <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] <statik> so, whos here? <gmb> me <jtv> me <intellectronica> me <statik> me <sinzui> me <bac> me <bigjools> me <salgado> me <gmb> schwuk will be late as he's had to step out <statik> * Roll call <statik> * Next meeting <statik> * Change time to 1400 UTC due to US daylight savings time? <statik> * Action items <statik> * Queue status <statik> * Mentoring update <statik> * Review process <allenap> me <statik> [TOPIC] Next meeting time <MootBot> New Topic: Next meeting time <BjornT> meme <statik> should we change the meeting time? <BjornT> +1 <statik> [VOTE] change the meeting time to 1400 UTC <MootBot> Please vote on: change the meeting time to 1400 UTC. <MootBot> Public votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0 to MootBot <MootBot> E.g. /msg MootBot +1 #launchpad-meeting <statik> +0 <MootBot> Abstention received from statik. 0 for, 0 against. 1 have abstained. Count is now 0 <jtv> +1 <MootBot> +1 received from jtv. 1 for, 0 against. 1 have abstained. Count is now 1 <gmb> +0 <MootBot> Abstention received from gmb. 1 for, 0 against. 2 have abstained. Count is now 1 <bac> -1 <MootBot> -1 received from bac. 1 for, 1 against. 2 have abstained. Count is now 0 <BjornT> +1 <MootBot> +1 received from BjornT. 2 for, 1 against. 2 have abstained. Count is now 1 <allenap> +0 <MootBot> Abstention received from allenap. 2 for, 1 against. 3 have abstained. Count is now 1 <bigjools> -1 <sinzui> +1 <MootBot> +1 received from sinzui. 3 for, 1 against. 3 have abstained. Count is now 2 <MootBot> -1 received from bigjools. 3 for, 2 against. 3 have abstained. Count is now 1 <intellectronica> +1 <MootBot> +1 received from intellectronica. 4 for, 2 against. 3 have abstained. Count is now 2 <salgado> +0 <MootBot> Abstention received from salgado. 4 for, 2 against. 4 have abstained. Count is now 2 <flacoste> +1 <MootBot> +1 received from flacoste. 5 for, 2 against. 4 have abstained. Count is now 3 <statik> [AGREED] Change this meeting to 1400UTC going forward <MootBot> AGREED received: Change this meeting to 1400UTC going forward <bigjools> can I point out that this will be over UK people's lunch hour when the clocks go forwards here <gmb> bigjools: No it won't. <gmb> 14:00 UTC == 15:00 BST * bigjools is a loser <gmb> Granted. <statik> [TOPIC] Action items <MootBot> Vote is in progress. Finishing now. <MootBot> Final result is 5 for, 2 against. 4 abstained. Total: 3 <MootBot> New Topic: Action items <statik> anyone have action items? <statik> ubmit to enforce 800 line limit. <gmb> Ah. <statik> * gmb to hack review-submit to enforce 800 line limit. <gmb> Big fat fail, I'm afraid. Still need to forward my patch to mwh for approval. <gmb> Leave it on the agenda; I'll tackle it this week. * gmb is also a loser <statik> there, there, don't be too hard on yourself. it's a lot of work sending an email <statik> [TOPIC] Queue status <MootBot> New Topic: Queue status <statik> I see 9 branches that are colored pink <gmb> Yeah, there are quite a few > SLA. <statik> but the general queue is empty <flacoste> db branches? <statik> flacoste: 3 are db branches <gmb> Are the on-call reviewers letting people know when they've been assigned branches from the queue? <statik> schwuk: need any help with your review? <statik> allenap: same question <gmb> statik: schwuk's not here yet <statik> the others over SLA are in the other reviewer meeting <sinzui> I know schwuk started to review navlinks-by-content, but I don't see it in my mail <statik> sinzui: are you his mentor? <allenap> statik: No, I'm okay right now, but a bit behind. I have apologised to abel. <sinzui> statik: I am <statik> sinzui: can you follow up with schwuk to see if he needs anything? <sinzui> I will <statik> allenap: great <statik> sinzui: thank you <statik> [TOPIC] Mentoring update <MootBot> New Topic: Mentoring update <statik> does anyone have some fantastic and insightful comments about mentoring? <gmb> No, but I've agreed to mentor bigjools whilst his mentor is away. <statik> does anyone want to complain about their mentors? <statik> gmb: that is great, thanks for volunteering <statik> I noticed you helping him with the lunchtime thing earlier <gmb> I shall resist from sticking the boot in further :) <statik> [TOPIC] Review process <MootBot> New Topic: Review process <bigjools> wise <statik> I have a question about the review process <statik> there was talk about releasing the lpreview plugin as open source <statik> is anyone following up on that? <gmb> statik: It was mentioned, then kiko mentioned the process that such a release would have to go through, then... nothing after that, I think. <statik> is there any reason that we should NOT release it? <sinzui> I think our recent additions would make it less useful for release. <bigjools> someone would need to manage submissions <statik> sinzui: what additions are those? <sinzui> The PR block ouput, make lint, 800 line limit, <statik> my thinking is that this plugin might be an interesting base for companies who are considering bazaar. I am not thinking that we will get useful contributions back <gmb> statik: I think that we'd have to have a released branch and an used-by-lpdevs branch really. <gmb> For exactly the reasons that sinzui stated. <statik> gmb: that sounds like extra work, which is a good reason not to release <gmb> Right. <statik> ok. the floor is open for anyone who wants to talk about our review process <statik> 5 <statik> 4 <statik> 3 <sinzui> schwuk asked me how do we review sourcecode changes <statik> 2 <statik> aha <statik> fantastic question <statik> we submit sourcecode changes via PQM <statik> but typically there are certain people who are more familiar with the code in a particular sourcecode dir <statik> for example, I recently added feedvalidator to sourcecode <statik> Edwin fixed a bug, and I reviewed it and submitted it <statik> I think for sourcecode changes we have a good idea of what is affected, and will need to individually arrange for reviews based on how significant the change is <statik> I don't think sourcecode changes can be assigned to the general review team <statik> but that is just my opinion <statik> BjornT: what do you think about review of sourcecode changes? flacoste? <sinzui> bugger <flacoste> i agree with your explanation <sinzui> I missed the response to my question <flacoste> but it also depends of the actual code <statik> we submit sourcecode changes via PQM <statik> but typically there are certain people who are more familiar with the code in a particular sourcecode dir <statik> for example, I recently added feedvalidator to sourcecode <statik> Edwin fixed a bug, and I reviewed it and submitted it <statik> I think for sourcecode changes we have a good idea of what is affected, and will need to individually arrange for reviews based on how significant the change is <statik> I don't think sourcecode changes can be assigned to the general review team <statik> but that is just my opinion <flacoste> for example, we don't usually commit to zope directly <flacoste> but first land upstream and backport the fix <flacoste> the idea is to prevent diversion <flacoste> although we currently have one (stub's changes to the testrunner which aren't meaningful for upstream) <sinzui> schwuk was review mwhudson's navlinks. to see the changes, he has to run loggerhead <schwuk> sinzui: for which I got instructions off mwhudson <sinzui> schwuk: rock! <statik> that sounds fine, I don't think we have anyone else on the team that is particularly familiar with loggerhead <statik> and I will deny ever sending patches upstream for it <schwuk> but IMO those instructions should have been included with the review request,or put on the wiki and linked to <schwuk> for everyone's benefit <statik> schwuk: good point, could you and mwhudson collaborate on getting some instructions on the wiki about running loggerhead? <schwuk> statik: sure <statik> awesome <statik> [AGREED] schwuk to work with mwhudson on getting loggerhead instructions on the wiki <MootBot> AGREED received: schwuk to work with mwhudson on getting loggerhead instructions on the wiki <statik> any other topics to discuss? <statik> 5 <statik> 4 <statik> 3 <statik> 2 <statik> 1 <statik> #endmeeting <MootBot> Meeting finished at 15:29. <flacoste> thanks statik! <bac> thanks statik <statik> thanks everyone! <gmb> Cheers statik <intellectronica> thanks statik #launchpad-meeting 2008-03-13 <cprov> I can haz meeting ?! * mwhudson blinks <statik> oi <danilos> we <cprov> me <sinzui> em <bac> Rinchen: ? <Rinchen> close <Rinchen> try again <thumper> kiko <kiko> hello hello <danilos> kikoooo <Rinchen> thumper, correct! <abentley> do me re fa so la ti do * thumper wonders if he can summon kiko into other channels <kiko> #startmeeting <MootBot> Meeting started at 18:02. The chair is kiko. <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] <kiko> hosted by me, with spammy MootBot in my wake! <kiko> [TOPIC] Roll Call <MootBot> New Topic: Roll Call <sinzui> me <thumper> me <bac> me <carlos> me <statik> me <herb> me <abentley> me <jt1> me <salgado> me <mrevell> me <matsubara> me <intellectronica> me <kiko> hooo is heeereee <statik> Edwin is at pycon <kiko> me <BjornT> me <cprov> me <mpt> me <adeuring> me <Rinchen> me <danilos> me <schwuk> me <mwhudson> me <kiko> me <flacoste> me <allenap> me * kiko pokes gmb_ and BjornT <leonardr> me <kiko> one for being absent, one for being his manager! <kiko> stub!! <stub> kiko!! <kiko> zat iz me <kiko> okay then <flacoste> barry and maris are off to PyCon <kiko> BjornT, gmb_ absent? <kiko> yeah <kiko> poor pyconners <kiko> [TOPIC] Agenda <MootBot> New Topic: Agenda <kiko> * Next meeting <kiko> * Actions from last meeting <kiko> * Oops report (Matsubara) <kiko> * Critical Bugs (Rinchen) <kiko> * Bug tags <kiko> * Operations report (mthaddon/herb) <kiko> * DBA report (stub) <kiko> * Sysadmin requests (Rinchen) <kiko> * New packages required (salgado) <kiko> * A top user-affecting issue (mrevell) <kiko> * Doc Team report (mrevell) <kiko> * canonical_url(..., view_name) (aaron, me) <kiko> * Blockers <gmb_> me <gmb_> Sorry, I suck. <kiko> [TOPIC] Actionz from last meet1ng <MootBot> New Topic: Actionz from last meet1ng <kiko> * salgado to investigate codebrowse and germinate inclusion in sourcecode <kiko> salgado rocks and rolls <salgado> done! <kiko> Thank you all for attending this week's Launchpad Developer Meeting. See the channel topic for the location of the logs. <kiko> hah! false alarm <kiko> [TOPIC] Oops report (Matsubara) <MootBot> New Topic: Oops report (Matsubara) <matsubara> Today's oops report is about bugs 201856, 201853, 161743, 200572 <ubotu> Launchpad bug 201856 in launchpad-bazaar "OOPS recorded ssh'ing into bazaar.launchpad.net" [Undecided,New] https://launchpad.net/bugs/201856 <ubotu> Launchpad bug 201853 in launchpad-bazaar "OOPS recorded executing remote command" [Undecided,New] https://launchpad.net/bugs/201853 <ubotu> Launchpad bug 161743 in launchpad-bazaar "Traceback from Twisted while running codehosting acceptance tests" [High,New] https://launchpad.net/bugs/161743 <ubotu> Bug 200572 on http://launchpad.net/bugs/200572 is private <matsubara> thumper, can you find assignees for the lp-bzr ones? First two should not record oopses <matsubara> or if they do, those oopses should be like SoftTimeRequests in the sense that they're not fatal. #161743 is the top one for codehosting at the moment. <matsubara> Who should take care of 200572? Foundations maybe? <thumper> matsubara: yes <kiko> please let this not be an XSS nonsense <carlos> kiko: you jumped next week meeting... I will not be around (on public holidays) <kiko> ah, right <kiko> umm mmm <kiko> carlos, right, let's do that after this one. <kiko> matsubara, you sure you don't want to fix that one yourself? it's so easy <carlos> ok <flacoste> we should tansform that into UnexpectedFormData? <flacoste> this can happen in a lot of place actually <Rinchen> +1 for UFDs <Rinchen> the more we can capture, the better we can diagnose <kiko> well <kiko> sure, UFD is fine. <matsubara> I think it should be a 404 <flacoste> for example, i'm sure http://launchpad.dev/%ED45 would suffer the same fate <BjornT> i think it should be a 404 as well. it's not a form. <kiko> if you visit http://launchpad.net/ubuntu/hoary/bar <kiko> you get a 404 <kiko> so I correct myself <kiko> 404 -- this is just an artifact of improper utf8 handling in the query? <matsubara> flacoste: the traceback looks different. <kiko> matsubara, if you visit https://edge.launchpad.net/ubuntu/hoary/%ee you get no OOPS page, but a Please try again. :) <matsubara> flacoste: and the one described in the bug report goes directly into the db <flacoste> normal, it's not the same code path <flacoste> but the exception should be the same, no? <matsubara> I mean, the one described in the report triggers a DB ProgrammingError kind of error, while the other triggers the usual UnicodeDecodeError <flacoste> right, <stub> We don't have any guards in our FooSet.getByName methods for invalid UTF8, so PG will barf. <flacoste> i remember adding a ascii encoding to Pillar for tests purpose <kiko> flacoste, matsubara: can you guys meet up and make a decision later? <flacoste> actually, there are many places where invalid UTF8 can be introduced <kiko> this is an issue that really annoys
{'channel': 'launchpad-meeting', 'month': 3}