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

=== jml` is now known as jml
=== salgado-afk is now known as salgado
=== mrevell is now known as mrevell-lunch
barry#startmeeting15:00
barryheh15:00
barryhello everyone and welcome to this week's ameu reviewer's meeting15:00
barryi know a lot of people are away, but who's here today?15:00
sinzu1me15:00
=== sinzu1 is now known as sinzui
sinzuime15:00
allenapme15:00
intellectronicame15:00
schwukme15:00
bacme15:00
salgadome15:00
EdwinGrubbsme15:01
gmbme15:01
intellectronicasorry, everyone, for allenap and mine no-show today. we've been working very hard on that hacking thing15:01
intellectronicahttp://farm3.static.flickr.com/2395/2511062130_f148267b7f.jpg15:01
barryintellectronica: why is allenap smiling?  that doesn't look like work! :)15:02
intellectronicabarry: something to do with JSON marshaling, iirc15:02
barry * Roll call15:02
barry * Next meeting15:02
barry * Action items15:02
barry * Queue status15:02
barry * Mentoring update15:02
barry * Review process15:02
barry   * Help people learn how big branches can be split up (BjornT)15:02
barry   * Adopt mars suggestion for more-specific imports; don't do multiline imports; communicate decision.15:02
barry * Next meeting15:03
barryeveryone okay with week += 115:03
barryanybody know of sprints or holidays, or know you won't be here?15:03
intellectronicai won't be here, i'll be on vacation15:04
salgadoI won't be here. vacation as well15:04
danilosme15:04
barrycool15:04
barry * Action items15:04
danilosas in, me here today, though late15:04
barry * barry drive to decision about multiline sequences15:04
barryso we've made a decision: we're going to adopt mars's suggestion and not multiline imports.  hopefully that will cut down on conflicts, but even if it doesn't, it'll be a win15:05
barryas we're all agreed __init__.py's import-*'s suck :)15:06
barry[ACTION] barry to update style guides and email ml15:06
barry * barry to solicit ideas to better handle review scheduling and workload15:06
barrynot done15:06
barry * flacoste to add `safe_hasattr()` to `lazr.utils`15:07
flacostei suck15:07
flacostecarry on15:07
barry;)15:07
barry * bjorn to add recommendation to test style guide saying don't use asserts in doctests15:07
sinzuiThat will wait until a week 015:07
barryi don't think BjornT is here15:07
barryso we'll just carry on15:07
gmbbarry: He's in a UDS session, I think.15:08
barry * Queue status15:08
barrygmb: np15:08
barrysalgado: you're switching ocr today, is that right?15:08
salgadobarry, that's right15:08
salgadowill update the wiki15:09
barrysalgado: thanks for helping out w/coverage!15:09
barrylooks like we have a few pink branches15:09
barryEdwinGrubbs: what's happening w/ the cprov and julian branches?15:10
EdwinGrubbsbarry: I think they are done except for mentoring possibly.15:10
salgadothey have been mentored15:10
salgadoI think15:11
barrycool, so just waiting to land?15:11
salgadoI think it's just the status that hasn't been updated15:11
barrynp15:11
barryschwuk: any word on the adeuring #1 branch?15:11
schwukbarry: in progress15:12
cprovsalgado: you did, I will reply it this evening. Sorry for the delay.15:12
* schwuk forgot to check pending reviews and missed it15:12
barryschwuk: cool, thanks.  iirc, there was reluctance to start on the 2 and 3 branches until the first one got reviewed15:12
sinzuiI think splitting a large branch and submitting all the parts at once is unfair.15:12
barryschwuk: you should check out bac's script :)15:12
bacbarry,sinzui : we talked to abel about it yesterday.  he said they are pretty dependent.  2 & 3 should be withdrawn15:13
schwukbarry: I had it running, but I broked it :(15:13
barrysinzui: if they are highly intertwined15:13
bacbut due to abel being at UDS i didn't get to talk with him directly15:13
barrybac: ok, thanks for the feedback.  i'll remove those branches from PR15:13
barrybac: and email abel so he knows to resubmit them when he gets #1 through15:14
barryanything else on the queue?15:14
bacbarry: also make sure he knows about the depends option in review-submit15:14
barrybac: good point!15:14
barrymoving on...15:15
barry * Mentoring update15:15
barryany feedback, issues?15:15
barry * Review process15:16
barry   * Help people learn how big branches can be split up (BjornT)15:16
barrywell, we didn't really reach any conclusions on this one, but for the folks working on abel's branch, can you think about this some and make any (general) suggestions to the ml?15:17
barry   * Adopt mars suggestion for more-specific imports; don't do multiline imports; communicate decision.15:18
barryalready mentioned.15:18
barryanyway, that's all i have on the agenda.  does anybody have any other topics?15:18
sinzuiI think splitting a large branch and submitting all the parts at once is unfair.15:19
intellectronicasinzui: huh?15:19
intellectronicayou should submit as soon as the code is available15:19
sinzuiI think that stands as a topic. The last branch is in a precarious position.15:19
sinzuiA mistake in the bottom of the design may topple the top branch15:20
bacand even mundane changes can bubble through all parts causing the reviewers to do extra work15:20
sinzuiintellectronica: I agree that once a chunk of code is ready for review, it should be.15:21
intellectronicatrue, but i think if you already reached the point where you have all code ready at once there isn't much that can be done about this15:21
intellectronicawe should pay attention to 'Depends:' in the submission, and try to spot problematic cases15:21
intellectronicaalso, it should be the responsibility of the developer to sort out effective reviews15:22
barrywell, the pre-impl should have helped with any design issues, no?15:22
sinzuiYep15:22
sinzuiA pre-imp should estimate the number of lines required and plan the branches15:22
schwuksinzui: +115:23
barryintellectronica: true, but devs should be conscious of not wasting reviewers time, so they should be highly confident their branches are solid15:23
barryand if not, get more up-front help in planning the branches15:23
schwukIf a branch is a few lines over the limit, fair enough. If it's 100+ lines over then the work hasn't been chunked properly (see pre-imp calls)15:23
intellectronicaschwuk: b.t.w did you have a pre-imp with abel? you are the developer most likely to be able to have an effective one with him15:23
schwukintellectronica: no, and he's not listed a pre-imp call on the review request.15:24
barryi will mention this to him, when i email him about his branches15:26
schwukbarry: I've queried it in my review as well.15:26
barryschwuk: thanks15:27
barryanything else?15:28
barry#endmeeting15:29
barrythanks everyone!15:29
schwukthanks barry15:29
=== salgado is now known as salgado-lunch
=== salgado-lunch is now known as salgado
=== Rinchen` is now known as Rinchen
=== salgado is now known as salgado-afk

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