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

=== Ursinha is now known as Ursinha-zzz
=== salgado-afk is now known as salgado
barry#startmeeting15:00
MootBotMeeting started at 09:04. The chair is barry.15:00
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]15:00
barryhello everybody and welcome to this week's ameu reviewer's meeting.  who's here today?15:01
sinzuime15:01
gmbme15:01
bacme15:01
allenapme15:01
salgadome15:01
intellectronicame15:01
barryEdwinGru EdwinGrub EdwinGrubb EdwinGrubbs is here 4 times i guess :)15:01
intellectronicabarry: BjornT is away on holiday15:01
EdwinGrume15:01
barryintellectronica: thanks15:02
barrybigjools: ping15:02
bigjoolshello!15:02
bigjoolssorry15:02
barryno worries!  hi15:02
barrydanilos: ping15:03
cprov-outme15:03
barryanybody else i'm missing?15:03
barrycprov-out: hi15:03
bacjtv?15:03
=== cprov-out is now known as cprov
barryhe only shows up sometimes because of his weird timezone15:03
barrysometimes he's in asiapac15:03
bacah, ok.15:04
cprovbarry: hi there15:04
barryi think we're just missing abentley but i pinged him in #lp-code (tho he's marked away)15:05
barryokay, let's get started!15:05
barry[TOPIC] agenda15:05
MootBotNew Topic:  agenda15:05
barry * Roll call15:05
barry * Next meeting15:05
barry * Action items15:05
barry * Queue status15:05
barry * Mentoring update15:05
barry * Review process15:05
barry   * dogfooding launchpad? (barry)15:05
barry   * too many branches? (barry)15:05
barry[TOPIC] next meeting15:05
MootBotNew Topic:  next meeting15:05
barryweek += 115:05
barryanybody know of sprints or other events that week?15:05
barrycool15:06
barry[TOPIC] action items15:06
MootBotNew Topic:  action items15:06
barry * intellectronica to write up guidelines on check_permission in the wiki and email the ml for additional input15:06
intellectronicasorry, one more week passed without me doing that15:07
intellectronicaplease let's carry this over to next week15:07
barryintellectronica: will do15:07
barry * barry to ping jamesh and stub on the testsuite2 branch15:07
barrydone, but i have not heard back yet15:07
barry * barry to update PreMergeReviews15:07
barrynot done, and now i have to go back and try to remember what this was about ;)15:08
barryvacations tend to blank my mind15:08
barry * intellectronica to start a list on the wiki of devs/available platforms15:08
intellectronicasee above :(15:08
barryk15:09
barry * intellectronica to start the ball rolling on an email to the ml re: multiple browsers/platforms15:09
barrysame? :)15:09
intellectronicayup15:09
barryk15:09
barry[TOPIC] queue status15:09
MootBotNew Topic:  queue status15:09
sinzuiI see I got a branch while I was away15:09
barryi'm a bit concern that we're having trouble keeping up with reviewer branches.  there's 9 in the GQ15:10
intellectronicawe had lots of sprints lately, as well as the release15:10
sinzuiI think sprinting really undermines our reviewing15:10
baci think i was only able to get two off the GQ yesterday.15:11
bigjoolsI get the feeling that OCR does the bulk of reviewing now, which is unfair on the OCRs15:11
barrysinzui, intellectronica agreed15:11
barrybac: i'm sorry that i didn't help matters :/15:11
gmbbigjools: You mean the GQ reviewing?15:11
gmbOr just in general?15:11
bigjoolsnon-GQ15:11
gmbBut that's what they're there for isn't it?15:11
bigjoolsI mean that for reviewers not on call, they don't get much to do15:12
gmbAh, right.15:12
bigjoolss/not/never/15:12
barrybigjools: my concern is that ocr reviews are consuming a full day so gc branches tend to get neglected.  is that a fair observation?15:12
bigjoolsjust an observation....15:12
bigjoolsI concur15:12
bacbarry: yes15:12
gmbbarry, bigjools: Why don't we do an allocation run of the GQ today to get it cleared and mail the list. Better that we get all hands on deck to avoid the building.15:13
gmbBuildup, even.15:13
bigjools+115:13
sinzuiI have had opposite days15:13
barrygmb: +1.  allenap and cprov, ping me when you're done for the day and i'll do an assignment cull15:14
allenapbarry: Okay.15:14
gmbsinzui: Yes, but you meke up for it by being the Friday Wk3 guy ;)15:14
cprovbarry: k15:14
sinzuiand saturday15:14
bigjoolshere's an idea, can we make the review-submit output put the number of lines of diff in the PR stanza?15:15
bigjoolsit would make it easier to distribute GQ items based on LOC workload15:15
barrybigjools: that's a good idea.  i'd think that should be fairly easy15:15
* gmb remembers when the server side tool was written to do exactly that... Oh well.15:16
barrybigjools: for this allocation run, i'll try to use pending-reviews to even things out15:16
bigjoolsgmb: server-side tool?15:16
barryi just want to get a feel for your thoughts: is the current backlog a symptom of process breakdown, or just a temporary situation caused by sprints, releases, and vacations?15:17
gmbbigjools: At AllHands mwh and I hacked a client-server setup for review management together. The server side bit never got used though because of the (then) upcoming features in LP.15:17
gmbbarry: I *think* it's a result of all the sprints.15:17
bigjoolsgmb: ah ok15:17
gmbFor example, the bugs sprint last week took 4 reviewers (well, 3 + a team lead) out of play.15:17
bigjoolsbarry: I think it's both - because OCRs are responsible for allocating the GQ at the end of the shift, when there's no OCR that process sufferes15:18
gmbAnd the foundations sprint was bigger in terms of effect.15:18
barrygmb: foundations was similarly occupied two weeks ago (and sinzui and i were on vacation last week)15:18
barrybigjools: yes.  i also think there's more tension lately between ocr and gc15:19
bacbigjools: i thought we agreed that the OCR would *not* allocate the GQ at the end of the shift anymore.15:19
barryi'm going to think about that some this week, but if you have any comments, email or irc them to me15:19
sinzuibac: We did agree15:19
* sinzui may have gotten his branch because it is JS.15:20
bigjoolsah, so who's doing it now?15:20
bigjoolsmy memory sucks15:20
barrybigjools: the plan was to consume gq branches during lulls in ocr, but there have been any such lulls15:20
barrybigjools: so the gq isn't getting consumed (or not enough to keep up with demand)15:21
barryat least lately15:21
bacbarry: do the asiapac guys stay pretty busy with on call reviews?  are they working on the GQ otherwise?  just wondering...15:21
barrybac: i'm not really sure, but that's a good question to ask them15:21
bigjoolsI feel that the GQ should be allocated daily to ensure that OCRs don't do everything15:22
sinzuiI don't care for allocation. User who put something in the GQ are still obligated to see that their branch is reviewed.15:23
bacwe need to encourage the reviewers who aren't OCR to periodically take a branch, too.  generally those people are the team leads, who are incredibly busy, but a branch or two a week would help15:23
* bac admits they may be doing so already and i just haven't paid attention15:23
bigjoolssinzui: how do you chase a review if it's in GQ?15:23
barryi don't much like allocation either, but i really don't want ocrs or really any reviewer to get burned out or feel compelled to review more than their fair share15:24
barryi remember kiko saying at all-hands, if we have too many branches than can reasonably be reviewed, then that's a different problem that has to be solved15:24
bigjoolsperhaps we need all reviewers to do OCR then?15:24
barry(or something like that)15:24
sinzuibigjools: I note that cpov is pretty good at finding a reviewer for his branch if it has not moved from the GQ in 24 hours. Maybe he know I can't say no.15:24
bigjools:)15:24
barry:)15:25
cprov:)15:25
bigjoolsif the dev has to always find a reviewer like that then the GQ is redundant15:25
barryi'll just note that it's probably difficult for jtv to request an ocr15:25
bacsome developers throw stuff on the GQ and then ignore it.  i did one yesterday that was 10 days old or so15:26
sinzuiit is, I often pull his branch out for review because I want to see that old translations code purged.15:26
barrybac: yes, you're right15:26
bacbarry: that's not really true.  jtv is in an odd time zone but he works really odd hours.  i do OCR for him all the time.15:26
barrybac: maybe it's just mondays then :)15:26
barry[ACTION] barry to do a gq allocation at the end of today15:27
MootBotACTION received:  barry to do a gq allocation at the end of today15:27
barrylet's move on...15:27
barry[TOPIC] mentoring update15:28
MootBotNew Topic:  mentoring update15:28
cprovwise decision.15:28
barryany comments from mentors or mentorees?15:28
barryi had a good conversation with abentley about his reviewing, though i guess i have to ping him about this meeting :)15:28
barryhe's just starting really15:29
bigjoolsI'd like to commend cprov for his quality reviews15:29
barrycprov: yay!15:30
cprovbigjools: oh, thank you so much.15:30
barryi think we currently have only 2 mentored reviewers.  do we have the bandwidth (and candidates) for maybe one more?15:31
barryanyway, if you have suggestions, send them my way15:32
barry[TOPIC] review process15:32
MootBotNew Topic:  review process15:32
barry   * dogfooding launchpad? (barry)15:32
barryso i talked to thumper before vacation about using merge proposals in lp for our reviews.  we all want to kill PR, so i'm wondering, even with the missing features (e.g. diff) is anybody up for an experiment to use lp to manage our reviews?15:33
* bigjools is up15:33
sinzuime is15:33
gmb+115:33
bac+115:33
cprov+115:33
barryi think the one thing you'll have to do is do the diff on the client side, but that shouldn't be too hard15:34
bigjoolsa lot of us do that anyway15:34
barrybigjools: good point15:34
* bac generates his own diff15:34
gmbThat's only a problem with dependant branches.15:34
bigjoolsanything to drive a stake into PR and pour garlic and holy water over it is fine with me15:35
barryi think we also need to ask a few devs to use lp instead of review-submit15:35
barrybut we don't want everyone to rush to lp yet :)15:35
barrygmb: right.  so let's cut child branches out of the experiment for now15:35
bigjoolshow easy is it?  are there any demos/instructions?15:36
barryperhaps what we can do is invite each dev to submit one non-dependent merge proposal, and then have a few of us use it when we're ocr15:36
barrybigjools: i've used it for public, hosted code, but not for private, remote branches15:37
barrybigjools: but that's part of the experiment i guess ;)15:37
bigjoolsbarry: are you volunteering to write a howto then? :)15:37
barrybigjools: yep, i'm willing to figure it out and write it up15:38
bigjoolsyou da man!15:38
barry[ACTION] barry to figure out dogfooding lp and writing it up15:38
MootBotACTION received:  barry to figure out dogfooding lp and writing it up15:38
barrythen i suggest we go with the 6 volunteer reviewers (including myself) for a few weeks and see how it goes15:38
barrysound good?15:39
bigjoolsI will help you15:39
barry(with the invite for devs to submit one standalone branch to lp)15:39
barrybigjools: awesome15:39
barrycool.  we have 5 minutes left.  i think we've basically talked about the other item i had on the list.  so i'll open the floor up to any other comments15:40
barryif not, then we're done!15:41
barry#endmeeting15:42
MootBotMeeting finished at 09:45.15:42
barrythanks everyone!15:42
bigjoolscheers!15:42
=== mrevell_ is now known as mrevell
=== salgado is now known as salgado-lunch
=== salgado-lunch is now known as salgado
=== e-jat is now known as e-jat_zZzZ
=== salgado is now known as salgado-afk
=== Moot2 is now known as MootBot

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