/srv/irclogs.ubuntu.com/2010/12/15/#launchpad-meeting.txt

=== Ursinha-afk is now known as Ursinha
=== mrevell is now known as mrevell-lunch
=== mrevell-lunch is now known as mrevell
=== Ursinha is now known as Ursinha-lunch
bac#startmeeting15:00
MootBotMeeting started at 09:00. The chair is bac.15:00
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]15:00
jelmerme15:00
bachello, who is here today?15:00
abentleyme15:00
bigjoolsme15:00
sinzuime15:00
jcsackettme15:00
benjime15:00
mrevellme15:00
deryckme15:00
EdwinGrubbsme15:00
henningeme15:00
flacosteme15:00
* benji things it should be "I" :P15:00
marsme15:00
marsbenji, "moo" is always fun15:01
benjiheh15:01
salgadome15:01
gary_posterme15:02
danilosme15:02
gmbMe15:02
=== allenap` is now known as allenap
allenapme15:02
danilosoh, capital "Me" is here as well15:02
bacgreat, let's start.  pretty light agenda today15:03
bac[topic] agenda15:03
MootBotNew Topic:  agenda15:03
bac* Roll call15:03
bac * Agenda15:03
bac * Outstanding actions15:03
bac * Mentat update.15:03
bac   * Salgado (ui)15:03
bac   * StevenK (code)15:03
bac   * MRevell (ui)15:03
bac * New items15:03
bac   * Should reviewers expect the review template to be used? - abentley15:03
bac   * Integrating test timing into reviews, recap.  -bac15:03
bac * Peanut gallery15:03
bac[topic] mentat update15:03
MootBotNew Topic:  mentat update15:03
bacsalgado, getting any more UI reviews?15:03
gary_posterbac, benji should be in mentat update15:03
salgadonope15:04
bacmrevell, getting any?15:04
bacthanks, gary_poster15:04
mrevellbac, No.15:04
salgadohaven't done any in a long while15:04
jelmerI will have one tomorrow15:04
jcsackettbac: i'm in the mentoring process as well.15:04
danilosI've also asked henninge to be my UI mentor as well, so I'll be starting as UI reviewer one of these days as well15:04
sinzuisalgado, me too15:04
bac sorry benji and jcsackett.  updated on the wiki now15:04
benjinp15:04
danilosperhaps there's no need for UI reviewers anymore15:04
flacostedanilos: why?15:05
sinzuisalgado, may be should agree that mentoring ui <= 3 month15:05
danilosflacoste, why would I want to be, or why there might not be a need?15:05
sinzuisalgado, maybe you should graduate next week because you have all the experience you are ever going to get15:05
danilosflacoste, it's just that people haven't been getting any UI branches for review15:05
abentleydanilos, there's certainly a need for UI review, but maybe not one so frequent as to demand specialized reviewers.15:05
bacsinzui: +115:05
EdwinGrubbsbenji has been doing a good job, but we haven't been getting very many requests for reviews on Wednesday15:06
salgadosinzui, well, I'm not sure a time limit is a good idea as in some periods (like now) we may stay a long time without doing any reviews15:06
danilosflacoste, i.e. mrevell and salgado hasn't gotten any in a week, so I am wondering if it's smart to try to achieve that specialization with unused workforce we've got15:06
jcsackettEdwinGrubbs: i've found the same thing on thursdays--i think maybe it's an end of year slow down?15:06
flacostejcsackett: probably is15:06
henningeI have not had that many, either.15:07
bacjcsackett, flacoste: but with the BugJam on perhaps it'll pick up?15:07
salgadodanilos, fwiw, I was doing 3 or so reviews a week when I started.  just lately there doesn't seem to have been many people working on UI15:07
abentleyfwiw, monday OCR is rarely busy.15:07
flacostebac: number of reviews should yes15:07
flacostesalgado, danilos: yeah, UI reviews usually come in burst15:07
flacostewhen a new feature is developped15:07
danilossalgado, right, thanks; I don't want to become a mentat as well and thus distribute the low UI activity over more people15:08
bacdanilos: perhaps you have a point that we don't need new UI reviewers in the pipeline if we can't get enough to get the current mentats trained.15:08
danilosbac, right, that was my point15:08
jcsackettbac: maybe get a queue of people willing to be UI and phase them in when the next feature rush begins?15:08
abentleydanilos, Sorry, I thought you meant the whole concept was outdated.15:08
bacabentley: yeah, me too15:09
danilosabentley, oh no, sorry for confusing you guys :)15:09
bac[topic] Should reviewers expect the review template to be used? - abentley15:09
MootBotNew Topic:  Should reviewers expect the review template to be used? - abentley15:09
abentleyBack when I  started, there was a template that was expected to be used for code review.15:10
abentleyIt's basically preserved in the lpreview_body plugin.15:10
abentleyIt expects a summary, pre-implementation notes, implementation details, lint, etc.15:10
abentleyI use it, but I find that basically no one else does.15:11
bacabentley: i always use it and really like it when others do.15:11
abentleyOkay, maybe that's too strong.15:11
jcsackettabentley: that template was provided to me when i started. i've seen it from a few others (though sometimes not with all sections).15:11
bigjoolsI use it sometimes.  It's massive overkill for simple branches.15:11
abentleyThere are a bunch of people not using it.15:11
bacpersonally i like it because i'm both lazy and forgetful.  it helps with both.15:11
deryckI don't use it.  there I owned up to it. ;)15:11
* deryck looks around at the rest of the room15:12
deryckI feel it's too prescriptive.15:12
bacbigjools: the sections that are overkill are easily deleted or marked 'n/a'15:12
abentleybac, +115:12
jcsackettderyck: could you unpack that a bit? not sure what you mean.15:12
bigjoolsthat's extra hassle, particularly if I use the web ui15:12
flacosteactually, web ui is the major problem there15:12
bacbigjools: oh.  i *never* use the web ui...15:12
flacostei most often use the web ui to submit branches15:12
flacoste(ok, i don't submit that many anymore...)15:13
jcsacketti use the web ui, and find that pasting in the template as a starting point isn't that big a deal.15:13
gary_postermore people may be using it soon, if the switch to using tarmac is successful15:13
flacostei'd use the template15:13
gary_posterit == the web15:13
flacosteif it was easy to get at15:13
abentleygary_poster, why?15:13
flacostegary_poster: why?15:13
bigjoolsif the branch is cleaning up, or a trivial bug, I find that template too prescriptive, annoying to edit and a waste of time.15:13
gary_posterbecause you'll be able to submit without using a commandline if you want15:13
bigjoolshowever, it's useful for a more complex change15:13
abentleygary_poster, I think you are talking about lp-land, not lp-propose.15:14
jelmerIt'd be nice if it the template was available in the web interface as well, not just in "bzr send".15:14
gary_posteroh, you are right, abentley.  thanks, sorry15:14
jelmerI'm also guilty of not using the template now that I've switched to using the web interface primarily for proposing merges.15:14
abentleyjelmer, it's not just in bzr send, it's also in lp-propose, and that's preferred.15:15
gary_posternot using template: me too.15:15
abentleyjelmer, I don't see how the web site is going to run lint on your local machine :-)15:15
bigjoolsI stopped using lint when it kept coming up with a million* false positives15:15
abentleyPersonally, I think it's a useful reminder of key things.15:15
abentleyLike who the pre-implementation call was with.15:16
abentleyI agree it's overkill for trivial bugs.15:16
bigjoolspre-imp details are the most useful thing on that template15:17
abentleybigjools, it's pretty good for me now.15:17
abentleybigjools, lint is pretty good for me, I mean.15:17
benjiabentley: indeed; I use it as a checklist; I make sure that I've considered every item on the template, even if I don't include it15:17
bigjoolsok I'll try it again, thanks15:17
baci guess the bigger issue is whether reviewers think the merge proposals are providing all of the expected information, whether people use the available tools, or not.15:17
flacosteabentley: does lp-propose submit the template on the web UI?15:18
abentleybac, also, if we're going to include test execution times, it would be sensible to add them to the template.15:18
* flacoste doesn't know about lp-propose15:18
bigjoolss/expected/useful and pertinent/15:18
bacthose that i see that use the template tend to cover all of the bases.  doesn't do a thing about the quality of the prose, though.15:18
abentleyflacoste, it opens up your editor to edit the description, then loads the proposal in the browser when it's done.15:19
flacostebac: dev writes in code :-p15:19
flacosteabentley: then I should be using that!15:19
jcsackettabentley: that sounds like the coolest thing ever.15:19
flacostei think it might just be that people don't know about lp-propose15:19
danilosI find it's hard to find out about it15:19
* jcsackett never heard about it.15:19
deryckbac: that's part of my issue with the template, sometime those who use it, just list a bunch of info, rather than writing a couple paragraphs explaining what is happening in the code, which is often more useful to me.15:19
danilosI used to have one of previous submit plugins with the template, but now I type most of the relevant sections out of my head15:19
bacabentley: i think part of the problem is new people don't know how to use your plug-in and some experienced folks forgot.  could you send out a reminder email or a pointer to the wiki?15:20
jelmerI was vaguely aware of it, but didn't know it was the proper way to propose merges instead of the web UI.15:20
danilosit's simply hard to find what the latest and best way to submit MPs is (i.e. appropriate plugin and such: I knew nothing about lp-propose either)15:20
flacostejelmer: it sounds like it's a wrapper around the uI, which is exactly what we need15:20
abentleyjelmer, I meant that it's preferred over "bzr send", not necessarily the web UI.15:20
marsdanilos, yes, that is odd - we used to do that just fine (years ago, when I joined)15:21
abentleydanilos, it ships as part of bzr :-P15:21
jelmerabentley: don't you still need lpreview_body to actually get the template though?15:21
abentleyjelmer, yes, you do.15:21
danilosabentley, heh, right, that's probably why it's harder for people to find out about it: if you are not actively looking for it and you've been using something like lpreview_body or whatever in the past, you wonder why it doesn't work as well anymore15:22
abentleyjelmer, since it's packaged, we could add it to lp-developer-dependencies, if it's not already.15:22
danilos(and I was actually stuck on whatever was before lpreview_body with my "lpsend" as the alias)15:22
jelmerabentley: I think that's a good idea15:23
bacabentley: can you send that reminder email and pursue getting it added to lp-d-d?15:23
abentleydanilos, I bear some blame, since I wrote it and didn't promote it.15:23
abentleybac, Sure.15:23
bacabentley: thanks for bringing up the topic...and for writing the tool.15:23
bacmoving on15:23
bac[topic]  Integrating test timing into reviews.  --bac15:23
MootBotNew Topic:   Integrating test timing into reviews.  --bac15:23
baclast week we started the discussion about paying attention to test timing.  we've had a lot of discussioin on the mailing list about what that means.15:24
bachas anyone tried and have successes or failures to report?15:24
marsAaron added two tests yesterday, timing was 2 seconds15:25
bigjoolstiming info on its own means nothing to me15:25
marsTBH, I didn't know how far to pursue it - how much was setup, how much existing tests, what it ok?15:25
mars'what is ok'15:25
flacostebac: given that we are planning on rewriting the persistence layer and that there is controversy on the metrics side15:26
flacostewhy don't we move on to another aspect?15:26
flacosteand revisit this later, once the story around persistence and tests is more clear15:26
bacfrancis, sure we can do that15:26
flacostewell, that's not an edict!15:26
flacostejust proposing15:26
baci unwisely thought this would be an easy one to start with15:26
bigjoolsI concur :)15:26
baci'll propose something next week15:27
bac[topic] peanuts15:27
MootBotNew Topic:  peanuts15:27
bigjoolso/15:27
bacyes bigjools?15:28
abentleyWho's seen A Charlie Brown Christmas this year? :-)15:28
bacare you really left handed?15:28
bigjools...15:28
danilosbac, that was him with his back turned on us15:28
gary_poster:-)15:28
* bigjools is speechless for the first time in ages15:28
bigjoolsanyway15:28
danilosbut he's also a slow typist (especially with only one hand)15:28
* gary_poster laughs15:29
* bigjools sees the gutter approaching15:29
marslol15:29
bigjoolsI want to talk about the mailing list thread that jelmer brought up15:29
bigjoolsregarding api only functions in model classes15:29
jelmerbigjools: thanks, I forgot about that15:29
bigjoolsI think it's a good idea to prepend api_ in front of any method that's only used in the api15:30
* danilos is still behind on his mail15:30
bigjoolsanyone got any comments?15:30
abentleybigjools, I think it's a good idea.15:30
bigjools(with liberal use of export_as of course)15:30
danilosother than that we should have made API a separate layer in the first place? no :)15:30
bigjoolsI assume that's coming15:31
danilosanyway, "api_" as the prefix for API-only methods is probably good15:31
bigjoolsthis is a stopgap15:31
abentleybigjools, it makes me sad that the API has the zope naming convetion, though.15:31
jelmerabentley: is that documented somewhere?15:31
bigjoolswe should change that *now* if we can15:31
bigjoolsbut it might be too late15:31
abentleyjelmer, Not as a special thing.  All our code has the zope naming convention.15:31
=== Ursinha-lunch is now known as Ursinha
marsdanilos, makes sense: model -> views (HTML), model -> api-layer (JSON)15:31
jelmerabentley: I found a couple of methods which explicitly used "export_method_as" and used names with underscores and lowercase characters.15:31
gary_posterI think it's too late myself15:31
leonardrbigjools: a while ago we decided it was too late15:31
gary_posterconsistency is more valuable IMO15:32
leonardrand now it's even later15:32
bigjools:(15:32
abentleygary_poster, definitely too late for 1.0 :-(15:32
gary_posteryup15:32
bigjoolsmaybe on the next version bump?15:32
bigjoolsthen we can make everything consistent15:32
bigjoolsit's a bit of a mess right now15:32
danilosE_TOOMUCHWORK15:33
danilosat least imo15:33
* gary_poster thinks that the webservice will get attention separately15:33
bigjoolsI think it's valuable work - we don't have anyone looking at our whole api, other than the people who use it15:33
danilosof course, we can choose when the next version bump will be15:33
gary_posteri.e., this is the worng forum15:33
danilosgary_poster, +115:33
jcsackettgary_poster + 115:33
gary_posterlooking at the whole api: that was to have been what leonardr did soon :-)15:33
bacgary_poster: yep15:33
bigjoolsanyway, votes for api_ ?15:33
abentleybigjools, +115:33
danilosbigjools, +115:34
gary_postersure, _115:34
bac+115:34
gary_posterheh15:34
deryck+115:34
gary_poster+15:34
jcsackett+115:34
danilos:)15:34
jelmer+115:34
deryckis underbar 1 even less than -1? ;)15:34
bigjoolsit's a wunderbar15:34
benji+115:34
gary_posterheh, yeah, maybe so :-)15:34
leonardr+015:34
bacbigjools: looks like you have a winner15:34
bigjoolsmotion carried15:34
bacbigjools: will you update the style guide?15:34
bigjoolsif I can remember where it is15:35
bigjools:)15:35
jelmerAlternatively, I'd be happy to update it15:35
danilosbigjools, I am guessing dev.launchpad.net/StyleGuide :)15:35
danilosnope, but it does give useful hints :)15:35
bigjoolswhat!  it's in an obvious place?  I'd never have thought to look there.15:35
bacany other topics?15:35
baci'll look at the list of people who will be around next wednesday and cancel this meeting if it looks too low.15:37
bacthanks for coming everyone15:37
flacostethanks bac15:37
bac#endmeeting15:37
MootBotMeeting finished at 09:37.15:37
daniloscheers bac15:37
marsthanks bac15:37
bigjoolscheers15:37
gary_posterthank you15:37
gmbTa15:37
abentleythanks, bac.15:37
jcsackettthanks, bac.15:38
benjileonardr: your "and now it's even later" comment made me think of TMBG's "Older" (http://www.youtube.com/watch?v=2ltJ8kK4G90&feature=related)15:39
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
=== leonardr is now known as leonardr-afk
=== benji is now known as benji-lunch
=== benji-lunch is now known as benji
=== Ursinha is now known as Ursinha-brb
=== leonardr-afk is now known as leonardr
=== Ursinha-brb is now known as Ursinha

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