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

=== mrevell is now known as mrevell-lunch
=== salgado-afk is now known as salgado
=== mrevell-lunch is now known as mrevell
* gmb goes to grab a drink14:54
barry#startmeeting15:00
* barry hopes somebody will kick mootbot15:00
barryanyway...15:00
barrywelcome to this week's launchpad ameu reviewers meeting.  who's here today?15:00
bigjoolsme-ow15:00
allenapme15:00
gmbme15:00
bacme15:00
* barry knows abentley sent his apologies15:01
cprovme15:01
BjornTme15:01
salgadome15:01
sinzu1me15:01
=== sinzu1 is now known as sinzui
sinzuime15:01
EdwinGrubbsme15:01
barryflacoste: ping15:01
intellectronicame15:01
barrydanilos: ping15:02
barry[TOPIC] agenda15:02
barry * Roll call15:03
barry * Next meeting15:03
barry * Action items15:03
barry * Queue status15:03
barry * Mentoring update15:03
barry * Review process15:03
barry   * watch for dead end links ([[https://bugs.edge.launchpad.net/launchpad/+bug/254436|bug 254436]] - flacoste)15:03
ubottuLaunchpad bug 254436 in launchpad "Launchpad contains lots of dead-end links" [Undecided,Incomplete]15:03
ubottuLaunchpad bug 254436 in launchpad "Launchpad contains lots of dead-end links" [Undecided,Incomplete] https://launchpad.net/bugs/25443615:03
barry[TOPIC] next meeting15:03
barryweek += 1?15:03
barryanybody know they won't be here?15:03
sinzuiI may not15:04
gmbI won't be.15:04
sinzuiThat depends upon my connectivity next week15:04
barrycool.  please update the apologies section on ReviewerMeetingAgenda15:04
barry[TOPIC]  * Action items15:04
barry * intellectronica to write up guidelines on check_permission in the wiki and email the ml for additional input15:05
intellectronicai haven't done that, but have done my other action items.15:05
barryintellectronica: rock on, thanks15:05
barry * intellectronica to start a list on the wiki of devs/available platforms15:05
barrydone15:05
barry * intellectronica to start the ball rolling on an email to the ml re: multiple browsers/platforms15:06
barrydone15:06
barry * Queue status15:06
barrynothing much from me here. does anybody have any comments?15:06
* sinzui reprimands himself for not updating pending review 15:07
* barry can't kill of PR fast enough15:07
barry[TOPIC]15:07
barry * Mentoring update15:07
barryi don't think we have any mentors currently?15:07
barryjust abentley i believe15:08
intellectronicado we have more people we want to invite, then?15:08
barryintellectronica: my question exactly :)15:08
flacosteme15:08
barrywe had talked about mars and leonardr15:09
barryany other suggestions?15:09
barryanyway, send them to me if you have them15:10
barry[TOPIC] review process15:10
barrynot much from me here, except that i did my first merge proposal this week15:10
barrytim and i talked about some improvements to that code and tim sent an email to the list about our discussions15:10
barryi think with those additions, this is going to be really nice15:11
barrydiffs on the web and all-email reviewers are still a little ways off, but iiuc are being actively worked on15:11
barrydoes anybody else have comments about merge proposals?15:11
barryanyway, i'd like to encourage people to try them out, submit bugs, send emails, etc.  tim and co are very interested in making it fit with our process15:13
barry   * watch for dead end links ([[https://bugs.edge.launchpad.net/launchpad/+bug/254436|bug 254436]] - flacoste)15:13
ubottuLaunchpad bug 254436 in launchpad "Launchpad contains lots of dead-end links" [Undecided,Incomplete] https://launchpad.net/bugs/25443615:13
BjornTone thing i noticed is that it's really hard to follow the reviews by e-mail15:13
ubottuLaunchpad bug 254436 in launchpad "Launchpad contains lots of dead-end links" [Undecided,Incomplete]15:13
sinzuiWe ultimately need something can can do branch analysis like out make lint.15:13
flacostesee bug report :-)15:13
barryBjornT: yep.  this is being actively worked on.  tim knows we want to do reviews by email15:14
* flacoste is n't really here sorry15:14
flacostewe might postpone15:14
barryflacoste: next week?15:14
barryflacoste: ok15:14
barrywow. shortest meeting evar.  does anybody have anything not on the agenda?15:15
barryone thing from me then: if you have any suggestions for improving this meeting, making it more relevant or, um, interesting please let me know.  i want to take joey and kiko's lead and make sure you're getting benefit out of these meetings15:16
kikoone trick15:17
kikois to get the people coming to the meeting15:17
kikoto raise most of the agenda, preferrably in advance15:17
kikois there an easy place to coordinate this -- i.e. add agenda topics, etc?15:17
intellectronicakiko: https://launchpad.canonical.com/ReviewerMeetingAgenda15:18
barrykiko: yes15:18
kikoand traditionally, how much of it is boilerplate and how much is dynamic?15:18
barrykiko: a lot of it is boilerplate15:18
barrywhich i'm not sure is very helpful to folks.  e.g. the mentor update is useless to asiapac15:19
barryqueue status is occasionally useful15:19
kikoright15:19
kikoyeah, I hear lots of debate about that15:19
kikoso to add some spice to this conversation15:19
kikohow about I throw up a topic of controversy?15:20
barrykiko: puke away15:20
kikoblech15:20
barry"throw up"15:20
kikocould we avoid the need to do pre-merge reviews for certain types of change that we want to encourage?15:20
kikopre-merge reviews are something that does add a set of handoffs to our process15:21
kikoin many cases I think the benefits outweigh the cost15:21
kikobut are there cases where a post-merge review would be smarter?15:21
intellectronicai can't imagine such a case. do you have an example?15:22
kikoreally?15:23
kikowow15:23
kikoI must have done my job well of convincing us of pre-merge reviews! :)15:23
bigjoolsrefactoring?15:23
BjornTfor simple straightforward changes it would make sense, but it's hard to identify them15:23
kikoI thought refactorings too, if there was a good pre-imp call15:23
bigjoolsare we heading back to r=trivial ? :)15:24
gmbIf we're talking about a textual change, fixing a typo or some such, maybe, but it'd have to be very, very, very trivial.15:24
kikothis is a bit different15:24
kikoas a reviewee15:24
kikodo you think you always get value out of a review?15:24
kikoand do you think the value outweighs the cost?15:24
kikoI'd like you all to think back to single-person projects you might have worked on15:24
intellectronicait's so cheap to get something reviewed these days, that the overhead is very low (unless it's hours before the pqm deadline)15:24
kikowhere you could check in code very quickly without asking anybody15:25
kikois your productivity different there and here?15:25
bacyes i get value.  either improvements are suggested or i get the affirmation that the approach made sense and was sound.15:25
barrykiko: yes. productivity is different.  one thing that might be interesting is to relax the requirement /if/ we could do some kind of real-time pair programming15:25
intellectronicathat's, basically, what trivial used to be. i thought it was ok to have it and was a bit sorry that it was gone. but for almost everything else, yes, you do get something out of a review15:26
barrykiko: iow, if you and i pair on a particular task, chances are we're already reviewing each other's code so it'll (presumably) be higher quality15:26
barryotoh, doing that in our distributed environment is challenging15:26
allenapIf we relax the requirements, I'm worried that what seems like a good idea might get coded and merged before we appreciate why it's not a good idea.15:27
barryintellectronica, kiko also note that we're encouraging drive-bys, which takes care of many previously r=trivials15:27
EdwinGrubbsherb: I'm still getting the 404 error when accessing <https://api.staging.launchpad.net/projects>. Unfortunately, you have to authenticate using the REST API to even see the error. Can you check in the logs to see if IP 12.231.120.224 is still getting redirected to product.html?15:27
intellectronicabarry: i think an interesting formulation of that could be that the goal is two have at least two developers behind a branch, and let them agree how they manage that15:27
BjornTas i understand it, kiko wasn't suggesting dropping the reviews, but exchanging some pre-merge reveiws with post-merge reviews15:27
barryintellectronica: interesting15:27
EdwinGrubbsherb: fyi, my IP is 12.231.120.224 and not an IP related to the rewrite rule. I wasn't clear before.15:28
barryi personally don't find arch-commits the most conducive format for that though15:28
barrythough i realize others do15:28
allenapBecause merged code starts running on edge, and thus mangling production data, post-merge reviews might be too late.15:28
kikowhat BjornT said, exactly (sorry, phone call)15:28
EdwinGrubbsherb_: I'm still getting the 404 error when accessing https://api.staging.launchpad.net/projects;. Unfortunately, you have to authenticate using the REST API to even see the error. Can you check in the logs to see if my IP 12.231.120.224 is still getting redirected to product.html?15:28
barryEdwinGrubbs: -> #launchpad-code ?15:29
kikoEdwinGrubbs, why are you asking about this in -meeting?15:29
EdwinGrubbsbarry: oops soory15:29
kikooops15:29
BjornTallenap: this would only be for certain changes, though. for example, if you have a really detailed pre-implementation call, and the changes seem straightforward15:29
* barry laments that few people have pre-impl calls these days :/15:30
BjornTbarry: something like this might encourage people :)15:30
* gmb makes a point of having at least an pre-imp IRC chat now15:30
barrykiko: i think this is an interesting discussion.  can you take it to the ml to get non-reviewer input?15:31
intellectronicahow about that suggestion? instead of reviewer, rename that post to copilot. you can agree to just have a pre-imp, hack together, hack then get reviewed, or just rubber stamp (if it's a trivial)15:31
kikobarry, no, but you can :)15:31
allenapI think that's true - about promoting calls.15:31
kikoI don't want to own this discussion, just to stimulate it15:31
barrykiko: i might not be able to do justice to your enthusiasm :)15:31
kikobarry, try harder <wink>15:32
* barry tries to get stimulated15:32
barrykiko: okay :)15:32
barryintellectronica: yes, let's explore that too15:33
allenapOh, bad images.15:33
barryallenap: oh, you've seen them?! :)15:33
barry[ACTION] barry will, er, stimulate discussion on post-merge reviews and pair-programming15:33
barrykiko: thanks for bringing this up15:34
barryany other topics today?15:34
kikobarry, you're welcome15:34
* sinzui wonders who his stimulating partner will be in pair programming15:35
* gmb remembers this is a public channel; behaves15:35
barryi think that's a sign that we're done15:35
barry#endmeeting15:35
bigjools+115:35
barrythanks everyone! :)15:35
intellectronicacheers barry15:36
gmbThanks barry15:36
=== kiko is now known as kiko-phone
=== salgado is now known as salgado-lunch
=== salgado-lunch is now known as salgado
=== kiko-phone is now known as kiko
=== thumper_laptop is now known as thumper
=== salgado is now known as salgado-afk
=== salgado-afk is now known as salgado
=== salgado is now known as salgado-afk

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