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

=== mwhudson__ is now known as mwhudson
barry#startmeeting03:00
barryhello everyone and welcome to this week's asiapac reviewer's meeting03:00
barrywho's here today?03:00
spivOh, hi.03:00
spivI'm here :)03:00
sinzuime?03:00
barryspiv: hi! :)03:01
spivjml is in Prague I guess?03:01
barrythumper: ?03:01
barrymwhudson: ?03:01
spiv(good thing I was idling in here!)03:01
* thumper smacks forehead03:01
barryspiv: that's okay.  i haven't eaten dinner yet :)03:01
thumpercompletely forgot, sorry03:01
thumperI'm hip deep in pqm03:01
thumper(the source that is)03:01
barryouch03:01
barrywe can make it a quick one then03:02
thumperwell, if we ignore for the moment that the patch will be approx 3k lines03:02
barry== Agenda ==03:02
barry * Roll call03:02
barry * Next meeting03:02
barry * Action items03:02
barry * Queue status03:02
barry * Mentoring update03:02
thumperit will make it better03:02
barry * Review process03:02
barry   * Help people learn how big branches can be split up (BjornT)03:02
barry   * Final vote multiline import03:02
barryit being a us holiday next week, i will not be here.  shall we just skip it and convene back in 2 weeks?03:02
thumperbarry: I'm guessing that mwhudson is afk too03:02
barrythumper: gotcha03:02
thumperbarry: sure, I don't mind skipping03:03
thumperbarry: expecially as it is a week 403:03
barrythumper: yep03:03
barry * Action items03:03
barry * barry drive to decision about multiline sequences03:03
barryi think we're close to a decision here, but i'l say more in a few minutes03:03
barry * barry to solicit ideas to better handle review scheduling and workload03:04
barrynot done03:04
barry * (continued) thumper to report on pending-reviews killer in LP03:04
thumpernot done either03:04
barrythumper: shall we keep this on the agenda or ditch it?03:04
thumperbarry: ditch for now I think03:04
thumperwe have things coming up03:05
barrythumper: sounds good03:05
thumperbut it doesn't really help saying skip it each week03:05
barrythumper: all post 2.0 right?03:05
thumperyeah03:05
barryworks for me03:05
spiv+103:05
barry * Queue status03:05
* thumper hasn't looked at the queue in ages03:06
barrynothing much from me here.  i got through a bunch of branches today, and assigned the 3 i couldn't get to03:06
barrydoesn't look too bad right now but i wouldn't want to be sinzui on friday :)03:06
sinzuiAnd Saturday03:06
barrysinzui: only because you like it :)03:07
sinzuiNo Soccer this weekend03:07
barrysinzui: promise me you will not work on the holiday! :)03:07
sinzuiWork on what?03:08
barryit's national bbq day03:08
* sinzui starts the heater on the pool03:08
* barry is going to skip the mentoring update03:08
barrysinzui: very nice!03:08
barry * Review process03:08
barry   * Help people learn how big branches can be split up (BjornT)03:09
thumperdon't talk to me about that right now03:09
barryat ameu , bjorn brought up a discussion on how to get people to learn how to split their big branches03:09
thumperI have a real killer03:09
barrythumper: your branch?03:09
thumperyeah, me for lifeless03:09
mwhudsonoh man, i _always_ forget this meeting03:09
spivbarry: a sharp whack across the knuckles with a big ruler every time a branch goes over the limit? ;)03:10
thumperspiv: it is a pqm refactoring branch03:10
barryspiv: that's one idea!03:10
thumperspiv: most of it is just moving stuff to modules03:10
barryi had a big branch, but mostly because i added some upstream files03:10
thumperwould you believe I got __init__.py down to just having __version__ in it?03:11
barrybut in general, all the branches i saw today were < 800 lines03:11
barryso i don't know how common this is03:11
mwhudsoni'm not really aware of it being a problem03:11
sinzuiI think we need a wiki page to collect ideas, then circulate a email of the top 5-10 tips after two weeks03:11
spivSo there's two possible issues I guess.03:11
thumperI don't think it is a big problem right now03:11
barrywhat i'd say is that if you notice the same offenders over and over again, we should work with those people to get them to learn how to organize their work better03:11
thumper+103:11
mwhudsoni think 800 lines is a low enough limit that it can be slightly exceeded without causing much pain03:11
barrymwhudson: agreed03:12
spivOne is that maybe people are doing to much work, rather than sending things incrementally (i.e. "send-as-you-go")03:12
spivThe other is that maybe when a big branch happens (which can be hard to avoid), people don't know how to split them up.03:12
barryspiv: it was brought up that looms can be a useful tool for organizing a complex branch into reviewable chunks03:12
spivI'm not sure which of these two Bjorn is referring to?03:12
mwhudsonit requires a certain discipline to go 'oh crap to do X i need Y and then i need Z' and then put each thing in it's own branch03:12
spiv(maybe both?)03:12
barryspiv: i get the sense that it's a lot of the latter.  how to help people learn how to split it up03:13
spivOk.03:13
barrybut otoh, most of the branches i've been reviewing have been fine03:13
sinzuispiv: I believe I'm now seeing a pattern of multiple branches being submitted on the same day. bug branches are being split instead of being driven to the right solution through review.03:13
spivThis is something that the broader bzr user community would benefit from education about.03:14
mwhudsonsinzui: i'm not sure i understand03:14
sinzuis/bug branches/but branches/03:14
barryi'm going to ask BjornT to start a discussion on the ml about this03:14
spivThere's a fairly straightforward process you can go through with looms + bzr shelve.03:15
mwhudsonsinzui: at least in an ideal world, the correct solution should be determined around the time of the pre-imp call03:15
mwhudsonnot the review03:15
spivWhich has occasionally been described on #bzr and maybe on the mailinig list.03:15
barryspiv: is there anything written up about this way of working?  it's definitely something i do03:15
spiv(the bazaar@ mailing list)03:15
spivBut I don't think it's been written up properly.03:15
barrymwhudson: yes, we want to push the organization earlier in the process03:15
spivSo perhaps the thing to do is write a good, clear tutorial on it, and put it in the loom plugin docs?03:15
sinzuimwhudson: I think 1800 line branches are being written, then split. The view is in a precarious position because there may be drastic changes to the model and utils below it. not to mention that mpt my have grievous things to say about the UI.03:16
spivAnd use the launchpad team as guinea pigs for that doc :)03:16
mwhudsonsinzui: ah, i see03:16
barryspiv: +1.  if you want to drive it/start it, i will certainly chip in03:16
spivI don't have time for that at the moment.03:17
mwhudsonwell, this is all about the 'ready to code' mantra i guess03:17
spivI'd be happy to proof read.03:17
barry[ACTION] barry to write something up about working effectively with looms+shelve03:17
spivmwhudson: agreed03:17
spivbarry: thanks!03:18
barryi gotta run, so i'm going to (try to) make this last item short:03:18
barry   * Final vote multiline import03:18
barrydid you all see mars's suggestion?03:18
mwhudsonremind me?03:18
barryinstead of: from canonical.launchpad.interfaces import ([800 lines later)03:19
barrydo: from canonical.launchpad.interfaces.bugs import (many fewer things)03:19
barryand eradicate (over time) all import-*'s in __init__.pys03:19
barryand do not do one-line-per-import03:19
barrythoughts?03:19
spivI'm +0 on that, I think.03:20
mwhudsoni don't think this will please the people who think one-line-per-import will take too much space, will it?03:20
mwhudsonbut yeah, import-* sucks, even when used carefully03:20
spivThere's a risk that module renaming/interface moving will then cause merge-time conflicts.03:20
barryyes, import-* sucks for many reasons03:20
barryspiv: we won't actually move anything, we'll just do a more-specific import03:21
spivEvil though import * is, it does make the actual layout of canonical.launchpad.interfaces.* etc a blackbox to other packages.03:21
thumperbarry: I think spiv means if we do move something03:21
barrywhich should reduce big parenthesed import statements, thus reducing conflicts03:21
spivbarry: right, but when something moves03:21
barryyeah, i see what you mean03:21
rockstarimport-* destroys the convenience of namespaces.03:21
mwhudsonthis seems to be a bit03:21
spivI'm not sure it's a significant problem.03:22
rockstarIf we always import *, we get php at some point03:22
spivBut it does make me hesitate a little.03:22
barryme neither.  i don't know how often interfaces move around03:22
mwhudson'import statements attract conflicts' -> 'but one-line imports are too verbose' -> 'lets do something else that doesn't really solve either problem'03:22
mwhudsonish03:22
barryunless it does :)03:22
spivYeah, my gut feeling is with mwhudson, that this is a largely orthogonal issue.03:22
mwhudsonbut then i don't really have a problem with conflicts in import statements _or_ large amounts of imports at the top of files03:23
barryi think it will reduce conflicts on import lines, which iiuc is the primary motivation for moving to one-line-per-import03:23
mwhudsonso maybe i should just shut up and hope people stop bothering me by talking about it :)03:23
barry:-D03:23
barryok, well i didn't hear howls of objections, so i'l take that as "let's try it and see"03:24
barryi just want to get this f'n item off my list ;)03:24
barrythat's all i have today.  anything else from y'all?03:24
thumpernop303:25
thumpere03:25
spivbarry: my vote on any specific proposal is +0, but my meta-vote is +1 for barry just declaring how it will be. :)03:25
thumperditto03:25
mwhudsonbarry for president!03:25
* mwhudson waits for the s/!=/<>/ branch of doom03:25
spivmwhudson: well, I might be -0 on *that* specific one ;)03:26
* barry is just waiting until the psf f's up the trademark and then it's off to the fork he goes!03:26
barryanyway. thanks everybody.  see you in 2 weeks!03:26
barry#endmeeting03:26
mwhudsonbye barry03:26
mwhudsonhm, python.org seems down03:26
spivmwhudson: there's always python.com03:27
mwhudsonoh no03:27
mwhudsonprobably my internet being crap again03:27
=== mpt_ is now known as mpt
=== salgado-afk is now known as salgado
=== mrevell is now known as mrevell-lunch
=== mrevell-lunch is now known as mrevell
mrevellHello! Is anyone here for the Launchpad documentation meeting?17:01
=== salgado is now known as salgado-lunch
=== salgado-lunch is now known as salgado
=== gumpa_hiding is now known as gumpa
=== salgado is now known as salgado-afk

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