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

=== barry-away is now known as barry
thumperbarry: were we going to have that meeting?02:58
barrythumper: i think we should02:58
* thumper nods02:58
barrythumper: 2 minutes02:58
thumperok02:59
mwhudsonhello02:59
barry#startmeeting03:00
MootBotMeeting started at 21:03. The chair is barry.03:00
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]03:00
barryhello everybody and welcome to this week's asiapac reviewers meeting03:00
jmlhello03:00
barryi see my clock is off by 3 minutes?03:00
barrywho's here today03:00
mwhudsoni am here03:00
jmlI am03:01
barrythumper is too i know03:01
thumperme03:01
barryi can't update the meeting page because i guess the machine updates are still running03:02
barryapologies for last night btw03: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
barry * Review process03:02
barry  * Module alternatives - do we really want them?03:02
barryshall we go ahead and do our regular time next week?03:02
thumperyep03:02
jameshokay03:03
barrycool03:03
barry * Action items03:03
mwhudsonyes please03:03
barry[TOPIC]  * Action items03:03
MootBotNew Topic:   * Action items03:03
barrynothing outstanding03:03
barry * Queue status03:03
barry[TOPIC]  * Queue status03:03
MootBotNew Topic:   * Queue status03:03
barrydoes it seem like we have a bajillion branches that need reviewed this cycle?03:04
jmlyes.03:04
* jml hasn't checked his queue today.03:04
thumpergee, I wonder why?03:05
mwhudsoni don't know that it's going to be any more intense than usual for week 3 though03:05
spivIt seems like the bzr team have a bajillion reviews to atm too :)03:05
mwhudsoni thought that was just one humungous review :)03:05
barryi'm a little worried that ocrs are getting overloaded or burned out.  do any of y'all feel that way?03:06
thumperrocs?03:07
thumperorcs?03:07
mwhudsonit's much easier for us 'round here03:07
jmlbarry: I don't.03:07
barryon call reviewers :)03:07
thumperah03:07
jmlbarry: there's a minor problem where I get requests for reviews on Friday afternoons03:07
jmlbarry: that's resulted in a couple of Europeans having to wait 24hrs between review cycles.03:08
barryjml: you get them while on call or in your queue?03:08
thumperjml: is there someone to pass the reviews onto?03:08
jmlbarry: while on call.03:08
jmlthumper: there wasn't this time.03:08
thumperwho is the european on on Friday?03:09
jmlat other times in the cycle I probably would have just said no :)03:09
barrydavid murphy03:09
barrythen in the us it's superman, er, sinzui03:09
jmlbarry: where does the schedule live?03:09
barryhttps://launchpad.canonical.com/OnCallReviewers03:09
barryi still would love to fill wednesday more03:10
barrybut we lost statik as a reviewer, which is too bad, because he was good03:10
barryotoh, bigjools is going to graduate03:10
jmlcool.03:10
mwhudsonhow many non-reviewers do we have currently?03:11
barrymwhudson: i was just looking that up03:11
thumperI'd like to get abentley onto the team shortly03:11
barryexcept i can't get into the directory :(03:11
barrythumper: good idea03:11
mwhudsonaaron, mars, leonard ?03:11
thumperI'll follow it up with him first03:12
barrythumper: sounds good03:12
thumperto make sure he is up for taking it on now03:12
thumper(or after 2.0)03:12
* mars stirs03:12
barrymwhudson: those are the next logical choices i think03:12
mwhudsonoh, al-maisan isn't a review either i guess03:13
mwhudsonreviewer03:13
thumperand rockstar03:13
thumperrockstar is still very new though03:13
barryso is al-maisan?  i haven't seen many of either's branches.  have you guys seen any of them?03:13
jmlal-maisan is still pretty new03:14
jmlI just reviewed one of his branches.03:14
mwhudsoni doubt al-maisan or rockstar are ready yet03:14
* jml agrees.03:14
rockstarYes, I am not ready...03:14
mwhudsonbut yeah, i guess we should bully the three i first mentioned i guess03:14
barry[TOPIC] mentoring update :)03:15
MootBotNew Topic:  mentoring update :)03:15
barrymwhudson: all we need to do is find mentors for them03:15
barrywith bigjools graduating, i can take someone else on03:15
barryal-maisan is euro?  rockstar, you're us right?03:16
jmlbarry: al-maisan is in .de03:16
rockstarYup, US03:16
barryi know mars is ca, eastern03:16
barryjml: cool03:16
barryleonard is us eastern too03:16
jmlbarry: abentley is .ca -- my geography doesn't extend that far north though03:17
barry:)03:17
mwhudsoni _guess_ one of us could do one of the new guys, but the difference is a bit much03:17
jmlyeah.03:17
mwhudson(until the dst thing happens again)03:17
jmlbetter to get someone from atlantis03:17
barryyeah it's tough when there's so little overlap03:17
jmlI mean AMEU03:17
barryjml: unless you can convince someone to move!03:17
jmlbarry: I would like Australia to move :)03:18
barry:-D03:18
spivI'm not sure what the real estate market in Atlantis is like...03:18
barryspiv: you can get great stuff cheap these days03:18
* thumper seemed to miss 5 mintutes03:18
mwhudsonjml: http://www.satirewire.com/news/jan02/australia.shtml03:19
spivbarry: I'd worry about home owners going under.03:19
barryspiv: you haven't heard about our real-estate crash?  it's only going to bring down the entire world economy03:19
jmlmwhudson: seen it :)03:19
mwhudsonjml: good :)03:19
jameshmaybe we need some reviewers in hawaii03:19
barrymwhudson: :)03:19
barryit's a great time to /buy/ a house, a horrible time to sell one03:19
barryanyway, all good suggestions, thanks03:20
thumperI checked out the cost of a house in hawaii03:20
thumperit isn't cheap03:20
* spiv would want to bouy a house if he lived in Atlantis03:20
thumperwe seem to be somewhat off topic03:21
mwhudson:)03:21
jameshspiv: there are people who will sell one to you03:21
barry[TOPIC]  * Review process03:21
MootBotNew Topic:   * Review process03:21
barry  * Module alternatives - do we really want them?03:21
jmlbarry: what's a module alternative?03:21
barrylets see if i can swap this one in03:21
thumperwhat is this exactly?03:22
barryintellectronica brought this up03:22
barrywhether we want to wrap imports of say, from cFoo import Foo in try/excepts03:22
barryor just do the import03:22
barryand expect them to work03:22
jameshjust import03:22
mwhudsonoh just import03:23
* jml seconds jamesh03:23
thumperjust import03:23
jameshhave you found a Python installation without cStringIO or cPickle?03:23
mwhudsonwe control our environment03:23
spivWe know what dependencies we have, don't we?  So just import.03:23
jameshand what mwhudson said03:23
spivs/have/have installed/03:23
barrythat's basically what we decided.  i think there was some question about forward-proofing etree, elementree and the like03:23
mwhudsonmmm03:24
jameshthe one place I think a try/except might be useful is for module name changes going 2.4 -> 2.503:24
thumpermwhudson: wasn't there something that you wanted to bring up at the review meeting?03:24
jameshe.g. ElementTree03:24
mwhudsonthumper: it's on the agenda :)03:24
* jamesh is too slow03:24
barryjamesh: some talk about having a canonical.alternatives package for hiding the 2.4/2.5 differences03:24
thumpermwhudson: I didn't see it on the agenda03:24
mwhudsonwell i added it03:24
barryanyway, we're all agreed, just import it03:25
barryand upgrade to 2.5 when we do :)03:25
barry * (mwhudson) What are page tests for?03:25
barrymwhudson: the floor is yours03:25
mwhudsonoh, it's just a proposed item03:25
mwhudsonthis came from some conversations i had with jml and thumper03:26
mwhudsonbasically, writing and maintaining pagetests is a pain03:26
mwhudsonand i think we are a bit muddled as a team as to what the purpose of a page test is03:26
mwhudsonsome of them are 'customer stories'03:27
mwhudsonand some of it is just testing that the templates work03:27
mwhudson(and most are some mixture of both)03:27
mwhudsonso i'd like to encourage a wider conversation on the topic03:27
spivMy first reaction is that both are useful, but keeping them separate would be a good idea.03:27
thumpersome try to do exhaustive testing of alternatives03:27
mwhudsoni guess i should mail the list about this, but let's have a short argument here first :)03:28
thumperI'd prefer to see template testing move to unitests03:28
barryspiv: that's my first reaction too03:28
thumpercustomer stories are fine03:28
jmlthumper: +103:28
jmlspiv: +103:28
mwhudsonif they are customer tests, we should consider not running them on every landing03:28
barryone question i've often had is how much should we be sneaking around the web u/i in a pagetest?03:28
spivBasically: for tests the key question iswhat is the intent of the test, and for docs the key question is what is the audience of the document.03:28
thumpermwhudson: not sure about that03:28
spiv(And for doctests, there's also the question of "is this a doc or a test?")03:29
barrythumper: i agree, i'd hate to stop running some of our important tests03:29
spivI think being clear about the answers to those will help us figure out how to organise our pagetests.03:29
jameshmwhudson: for a while, it wasn't possible to do testbrowser stuff outside of the pagetests03:29
barryspiv: very good point.  i love doctests for everything, but some are documentation and some are not03:29
mwhudsonthumper: this pre-supposes that all the important things are tested in non customer tests03:30
thumperI think that trying to do exhaustive tests of alternatives should never be in a doctest or pagetest03:30
jameshdue to some required setup/teardown being done in the FunctionalDocFileSUite03:30
mwhudsonjamesh: oh, interesting03:30
jameshthat is fixed now though, so there isn't any technical reason not to do testbrowser in unittest code now03:30
spivbarry: I *will* persuade you that doctests for everything is bad at some point, I promise :)03:30
mwhudsonjamesh: i have written unittests that use testbrowser :)03:30
barryspiv: :)03:30
thumperspiv: I'm sure doctests are good somewhere03:30
jameshmwhudson: and that worked because I moved the test setup to the layers03:30
mwhudson(it's still a pain because you have to log in and out all over)03:31
mwhudsonjamesh: i shall buy you a beer for that at some point03:31
thumpermwhudson: what about setting the unitest in the pagetestlayer?03:31
barrythumper: i have this theory that we can use the doctest format for everything (and that it's better than python tests)03:31
thumperbarry: ew, NO!03:31
mwhudsonthis is a separate punch-up03:31
mwhudson:)03:31
barryyeah, let's not get distracted :)03:32
jameshthese days, there isn't any special setup done for doc tests, other than default globals, iirc03:32
barryjamesh: right, and we're trying to discourage magical globals in doctests anyway03:32
marsbarry, +1 :)03:32
jameshyep03:32
thumperare we?03:32
thumperI just added one03:32
* mwhudson shall have to buy xUnit Test Patterns for everyone on the launchpad team, it seems03:32
barryi've had exactly one case where i think it's justified, but other than that, the imports are good to put in the doctest!03:33
thumperat least it makes it clear where things are coming from03:33
mwhudsonso, should i mail the launchpad list about the page test thing?03:33
spivmwhudson: ideally with a short proposal about what to do about it03:33
jmlmwhudson: I think that's a good idea.03:33
barrythumper: yeah, i hate having to go hunting for the harness that sets up a doctest just to figure out what some global actually is03:34
spivmwhudson: just to try to limit the inevitable bike-shedding a little03:34
mwhudsonand say that launchpad/pagetests should be stories03:34
barrymwhudson: +1, spiv +103:34
mwhudsonand that doc/ should be documentation03:34
spivmwhudson: +103:34
mwhudsonand tests (whether .py or .txt) should be in a tests directory?03:34
barrymwhudson: +103:34
spivmwhudson: +1 +1 +103:34
mwhudsonok03:34
barryand can we for gawd's sake please do something about tests, testing, and ftests?03:35
spivRename ftests to f'ing tests?03:35
mwhudsonwell, testing is for scaffolding03:35
jmlbarry: tests & testing is a sensible split03:35
jameshstuff in ftests can go to tests03:35
mwhudsonddaa tried to land a branch that moved everything in ftests into tests03:35
barryjml: yes, maybe just get rid of ftests.  i would be so much happier03:35
thumpertesting is infrastructure03:35
jameshthe tests / testing split is good03:35
jmljamesh: sometimes it needs to go to testing :)03:35
spivjamesh: +103:35
jameshjml: right03:36
barryjamesh: +103:36
mwhudsonbut it's a conflict nightmare03:36
mwhudsonok, i can add this to my mail too :)03:36
thumpereach team should move its own tests03:36
thumperfrom ftests to tests in the appropriate place03:36
* barry has a secret plan for montreal :)03:36
thumperwe file a bug03:36
thumpercreate tasks for each team03:36
thumperand JFDI!03:36
barrythumper: right!  i want a special pqm tag for that03:37
thumper:)03:37
thumperbarry: why a pqm tag?03:37
jmlthumper: I think you'll find that one team has already done it :P03:37
thumperjml: not quite03:37
barrythumper: well, when i want to jf land a branch :)03:37
thumperjml: there are some older tests still in c.l.ftests03:37
spivSome people claim "Jedi" as their religion.  thumper's religion is "JFDI".03:37
jmlthumper: let us continue this team-specific discussion outside of the meeting.03:38
barry2007's motto was "canonical fuck yeah!".  2008's should be JFDI03:38
thumperbarry: can you add a mootbot task for that?03:38
barry[ACTION] mwhudson to start discussion on page test purpose03:38
MootBotACTION received:  mwhudson to start discussion on page test purpose03:38
thumperbarry: I was meaning a bug for ftests -> tests03:38
barry[ACTION] thumper to submit a bug for moving ftests contents to tests03:39
MootBotACTION received:  thumper to submit a bug for moving ftests contents to tests03:39
barryanything else on this topic mwhudson?03:39
mwhudsonnot for today i think03:39
mwhudsoni can hear jml's stomach rumbling from here :)03:40
barry:)03:40
jml:D03:40
barryokay, one quick last one03:40
jmlThe "D" represents my gaping maw.03:40
barry * (bigjools) On-call reviewers to remind devs to be available during the review.03:40
jmlthat's a good idea.03:40
mwhudson+103:40
jmlI'll do that in future.03:40
barrybigjools brought up to me that some people are using on-call requests to jump ahead of the review queue03:40
jameshwe've got way too much obsolete test infrastructure still in tree03:40
barryi.e. they request an on-call review then disappear03:41
mwhudsonjamesh: yes03:41
jmlbarry: yeah, this has happened to me.03:41
barryi told bigjools that if that happens, you are allowed to reject the ocr request and move on to someone who is present03:41
barrythe whole point of ocr is to have a dialog with the dev03:41
mwhudsoni think i've done this03:41
spivThis makes good sense to me.03:42
mwhudsonat least, if i have two reviews to do and the developer is there for one of them, he gets done first03:42
barryanybody disagree?03:43
thumpernope03:43
mwhudsonnope03:43
barrygreat.  that's it for me.  shall we end 2 minutes early and let jml get some food?03:43
jmlI think we should discuss it first :)03:44
barryjml: but only for 1 more minute :)03:44
barry#endmeeting03:44
MootBotMeeting finished at 21:47.03:44
barrythanks everyone!03:44
jmlbarry: thanks!03:44
mwhudsonthanks barry03:44
spivbarry: thanks03:44
=== barry is now known as barry-away
=== Moot2 is now known as MootBot
=== mwhudson_ is now known as mwhudson
=== mpt_ is now known as mpt
=== mwhudson_ is now known as mwhudson
=== salgado-afk is now known as salgado
=== mrevell_ is now known as mrevell-lunch
=== mrevell-lunch is now known as mrevell
barry#startmeeting15:00
MootBotMeeting started at 09:03. The chair is barry.15:00
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]15:00
barryhi everybody.  welcome to this week's ameu reviewers meeting15:00
barrywho's here today?15:00
sinzuime15:00
EdwinGrubbsme15:00
gmbme15:00
bigjoolsme15:00
intellectronicame15:01
bacme15:01
barrydanilos, BjornT ping15:01
barryflacoste: ping15:01
danilosme15:01
flacosteme15:01
BjornTme15:01
danilosbarry: thanks15:01
allenapme15:02
barrysalgado: ping15:02
barry[TOPIC] agenda15:02
MootBotNew Topic:  agenda15:02
salgadome15:02
barry== Agenda ==15:02
barry * Roll call15:02
barry * Next meeting15:02
barry * Action items15:02
barry * Queue status15:02
barry * Mentoring update15:02
barry   * bye to statik15:02
barry   * bigjools graduates15:02
barry   * new recruits?  (leonardr, abentley, mars)15:02
barry * Review process15:02
barry   * (bigjools) On-call reviewers to remind devs to be available during the review.15:02
barry   * (gmb) Wrapping long argument lists: What's the agreed style?15:02
barry   * (mwhudson) What are page tests for?15:02
barry   * thumper moving ftests contents to tests15:02
barry[TOPIC] next meeting15:02
MootBotNew Topic:  next meeting15:02
* barry kicks mootbot15:02
jtvme15:03
statikme15:03
barryjtv: hi!  statik hi!15:03
jtvbarry, hi!15:03
barrynext week, same time and place?  anybody know they will be sprinting or away?15:03
barrycool15:04
barry[TOPIC] action items15:04
MootBotNew Topic:  action items15:04
barry * intellectronica to file bug on lint issue regarding elementtree import15:04
intellectronicasorry, i didn't. let's carry this on15:04
barryintellectronica: np15:04
barry * mwhudson to start discussion on page test purpose15:04
barryi will proxy mwhudson :)15:05
barryhe's going to start a ml thread on the purpose of page tests.  more in a moment15:05
barry * thumper to submit a bug for moving ftests contents to tests15:05
barrymore on this in a bit15:05
barry[TOPIC] queue status15:05
MootBotNew Topic:  queue status15:05
barryany comments?  i was freaking out on monday, but i've calmed down by now.  thanks everyone for cranking away on reviews!15:06
sinzuiStub has reviewed my two branches now; he has not updated the statuses15:06
barrysinzui: are they merge-approved?15:07
sinzuiyes15:07
barrysinzui: cool. i'll ignore those and you can just remove them when they land15:07
barrymy branch that kiko reviewed is still trying to land15:07
* barry won't even mention testsuite2 :)15:08
barryanything else on the queue?15:08
sinzuiWe seem to have extra missing branches this week15:08
barrysinzui: missing where?15:09
salgadoyeah, I'm nagging stub about my oauth-context branch, which has a DB patch15:09
sinzuibarry: The red branches are missing. It implies they were removed from the repo, or renamed15:09
barrysinzui: yeah, people are not updating PR15:10
sinzuigmb and intellectronica have missing branches15:10
sinzuiand schwuk15:10
barryeveryone, remind your reviewees to clean up PR when their branch lands!15:10
bigjoolsamen to that15:10
* bigjools cleaned 4 of other people's out this morning15:10
intellectronicasinzui: oh right, i cleaned my repo but not PR, i guess. i'll sort it out15:11
barrybigjools: yes, feel free to clean out any that you see15:11
* barry is a culprit too15:11
bigjoolsI don't like doing it though, it makes devs lazy!15:11
barrybigjools: hmm, maybe refuse to review any new branches until they clean out their old ones :)15:11
bigjoolslol15:11
barryanyway...15:12
barry[TOPIC]  * Mentoring update15:12
MootBotNew Topic:   * Mentoring update15:12
gmbOr have PQM check for red branches and rejecting anything until they're gone...15:12
barryso first, we say goodbye to statik who is moving off the lp team and won't be accepting any more reviews.  i was tempted to go down to florida to camp on his doorstep until he changed his mind but it's a long train trip15:13
barrystatik: thanks and good luck!  you're welcome to come do reviews any time you're bored :)15:13
statikthanks!15:13
barrynext up: bigjools graduates.  congratulations bigjools!15:14
jtvcongrats bigjools!15:14
* flacoste cheers bigjools15:14
intellectronicacongrats bigjools!15:14
bachurrah15:14
* bigjools takes a bow15:14
gmbHurrah!15:14
bigjoolsthanks guys15:14
barryi will send an official email after this meeting15:14
bigjoolsBarry is a great mentor - thanks to him also15:14
barryremember, give all your hard branches to bigjools now :)15:14
bigjoolsoof15:14
barry:)15:15
barrybigjools: thanks15:15
flacostebut has it easy, being a soyuz developer15:15
* bigjools considers retracting the last statement :)15:15
jtvtoo late15:15
flacostethe worst branch are his :-p15:15
barryflacoste: no kidding!15:15
bigjoolsflacoste: lol15:15
barryi think we can accept a few more recruits now.  i'm certainly happy to mentor again.  i think the next three potential candiates are leonardr, abentley, and mars15:16
barryi talked to thumper and i'm thinking about mentoring abentley15:16
barrywe need mentors if we're going to accept anybody else, though i propose we do not accept until after 2.015:16
barryso if you would like to volunteer to mentor leonardr or mars, please send me an email15:17
intellectronicai'm happy to mentor again, after 2.015:17
barryintellectronica: awesome15:17
gmbI'll be happy to do the same15:17
barrygmb: great, thanks!15:17
barrybtw, we mentioned rockstar and al-maisan but we want to give those guys a bit more time dev'ing for now15:17
barry[TOPIC]  * Review process15:18
MootBotNew Topic:   * Review process15:18
barry   * (bigjools) On-call reviewers to remind devs to be available during the review.15:18
barrywe talked about this last week...15:18
bigjoolsok15:18
bigjoolsI've noticed a few instances where developers are not available during on call reviews15:19
barrybut i just wanted to mention that asiapac was all for the idea that it's okay to reject an ocr if the dev disappears15:19
bigjoolsthe primary reason for OCR is to speed up reviews15:19
intellectronicawell, if they're not available then they're not available, what can you do? just postpone the review for later15:19
bigjoolsnot as a means to jump the general queue15:19
bigjoolsintellectronica: put them in the GQ15:19
barrybigjools: exactly15:20
intellectronicabigjools: yeah, exactly15:20
jtvIt's a bit annoying when you're in Asia though15:20
bigjoolsjtv: we could prioritse people who find it hard to be around at the same time as OCRs15:20
barryjtv: who is affected by that?15:20
bigjoolsanyway - we should remind devs, when they ask for a review, to be around, otherwise refuse the review15:21
jtvAgreed—if you ask for it, you ask for it.15:21
barrythe one hitch is when someone asks for  review and you can't get to it for several hours because your dance card is full.  they might disappear by the time you're free15:21
bacthis tends to happen to me when europeans ask for reviews in my early afternoon.  often by the time i get to the review it's pretty late where they are.  happened last night.15:22
barrythis has happened to me when euros get bumped to the end of my list15:22
barrybac: yep15:22
bigjoolsif you're not sure you can get to it, I don't think it should be accepted15:22
barryi think it's okay to reshuffle your queue15:22
bigjoolsmaybe we need to consider doubling up reviewers on some shifts?15:22
barryi.e. give some priority to those east of you if it helps speed the review15:23
bigjoolslike some already do15:23
bacand, if you're approaching the end of your work day, don't ask someone just b/c they have a few hours left15:23
barrybac: good pont15:23
bac'you" being a dev, not a reviewer15:23
barryer, point15:23
barrybigjools: i'm not sure we have enough coverage as it is atm15:23
bigjoolswhen I've been on call on Monday mornings it's quite thin most of the time, I could move to a different day15:24
barryi.e. wednesday we only have intellectronica and allenap in euro time15:24
intellectronicaonly?15:24
sinzuiWe need to send rockstar to NZ once he is a reviewer to take the Wednesday slot15:24
barryintellectronica: not to disparage you guys!  you all do great, but we have no america coverage on wednesdays15:24
intellectronicaah, of course. well, i think we'll have to relocate someone15:25
barrybtw, the asiapacsters don't feel to bad about the current situation, i.e. they are neither overloaded nor seeing their branches languish15:25
bigjoolsdoes this mean we need more Americas reviewers?15:25
barrybigjools: leonardr, abentley and mars are all here so getting them on board will improve coverage eventually15:26
intellectronicaif we get leonardr on board it will help, though, so let's try to convince him to start after 2.015:26
bigjoolsrockin'15:26
barryintellectronica: +115:26
barrybigjools: we have good euro coverage, so if you want to stay on monday that's cool.  it's nice to have a little overlap in our days.  otherwise, definitely feel free to pick a slot later in the week and double up with someone15:27
salgadowe also have EdwinGrubbs, who's being mentored by myself15:27
barrybigjools: maybe friday so sinzui's load gets lightened.  i always feel bad that sinzui reviews into his weekend :)15:28
bigjoolsI don't mind either way.  I'll stay where I am for now and we can check which periods are most busy15:28
salgadoonce he graduates we'll have one more reviewer in america15:28
barrysalgado: good point!15:28
bigjoolsbarry: yeah, there's nobody on Friday mornings15:28
barrybigjools: sounds good15:28
bigjoolsEurope time that is15:28
sinzuibarry: You do not. I'm taking the load off of you15:28
flacostebarry: well, if doesn't review into the week-end, he'll code, which increase the review load so...15:29
barry:)15:29
* sinzui looks forward to this Friday with PQM in top form to screw developers whose nicks are not gmb15:29
barryanyway, moving on...15:29
gmb*mumblemumble*15:29
barry   * (gmb) Wrapping long argument lists: What's the agreed style?15:29
gmbRight.15:29
gmbSo, my question is pretty simple.15:29
gmbWhen we come across a method definition with a really long list of arguments, how do we want it wrapped.15:30
sinzuiWe agree to wrap two ways as we see fit15:30
gmbI've seen three styles:15:30
gmbdef spam(eggs, ham, jam, lamb, spam15:30
gmb    foo, bar):15:30
gmbdef foo(15:30
gmb    here, is, a, nother, long, list):15:31
gmbor15:31
gmbdef bar(15:31
gmb    this,15:31
gmb    looks,15:31
gmb    really,15:31
gmb    ugly):15:31
salgadoI think the basic rule should be to have all the arguments aligned so that they stand out from the rest15:31
sinzuiI choose neither15:31
salgadothere's also15:31
intellectronicaiiuc the first one is not kosher, but you can choose wither of the last two15:31
bigjoolsthere's a 4th!15:31
salgadodef bar(foo, bar, baz,15:31
salgado       nah):15:31
sinzuiI choose salgado's15:31
flacostei thought that was the agreed style actually15:32
barrysalgado: with the 'nah' lined up under 'foo'?15:32
salgadobarry, yep15:32
flacostebarry: yes15:32
jtvThat's PEP-815:32
barrysalgado: +115:32
gmbjtv: Good enough for me.15:32
BjornTi think the 4th one is the most common one in our code15:32
* bigjools is using non-prop fonts here so it all looks ugly15:32
jtvPersonally I like the double-indent for continued parameter lists.15:32
bacsalgado: +115:32
salgadoI personally prefer the second example of gmb15:33
salgadobut I'm strongly opposed to the first one15:33
gmbsalgado: That's the one I usually use, but I'm happy to follow prevailling wisdom15:33
gmbs/usually/15:33
salgadohence my saying that the basic rule should be to have all the arguments aligned so that they stand out from the rest15:33
jtvShould we put this on a wiki page (where we know it's in nonproportional fonts) and vote?15:33
salgadoif that was the rule all three options would be allowed, which I think is fine15:33
salgadomaybe not the third one as it looks quite ugly15:34
baci'm against any style that lines up the arguments with the body of the method15:34
gmbI think the third one takes up unnecessary space.15:34
intellectronicabac: i very much agree15:34
barrybac: i agree too15:35
jtv+1 for bac15:35
danilosI'd be for the current prevailing style "de salgado" (at least in this meeting)15:36
barrydanilos: +115:36
jtvBut verily it sucketh with long method names.15:36
barry[VOTE] adopt salgado's suggestion for parameter indents: aye +1 or nay -115:36
MootBotPlease vote on:  adopt salgado's suggestion for parameter indents: aye +1 or nay -1.15:36
MootBotPublic votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot15:36
MootBotE.g. /msg MootBot +1 #launchpad-meeting15:36
barry+115:37
MootBot+1 received from barry. 1 for, 0 against. 0 have abstained. Count is now 115:37
bigjools+115:37
MootBot+1 received from bigjools. 2 for, 0 against. 0 have abstained. Count is now 215:37
salgado+115:37
gmb+115:37
allenap+115:37
MootBot+1 received from salgado. 3 for, 0 against. 0 have abstained. Count is now 315:37
MootBot+1 received from gmb. 4 for, 0 against. 0 have abstained. Count is now 415:37
MootBot+1 received from allenap. 5 for, 0 against. 0 have abstained. Count is now 515:37
bac+115:37
sinzui+115:37
MootBot+1 received from bac. 6 for, 0 against. 0 have abstained. Count is now 615:37
MootBot+1 received from sinzui. 7 for, 0 against. 0 have abstained. Count is now 715:37
danilos+115:37
MootBot+1 received from danilos. 8 for, 0 against. 0 have abstained. Count is now 815:37
flacoste+115:37
MootBot+1 received from flacoste. 9 for, 0 against. 0 have abstained. Count is now 915:37
danilosho-hum, what was that discussion about in the first place? :)15:37
statik+115:37
MootBot+1 received from statik. 10 for, 0 against. 0 have abstained. Count is now 1015:37
jtvdanilos: car repairs.15:37
barry#endvote15:38
flacostejtv: don't use long method names :-)15:38
barryer, whatever mootbot15:38
barryflacoste: right15:38
* bigjools aims a kick to mootbot's nads15:38
barrygmb: can you update PythonStyleGuide and send a quick email to the ml?15:38
gmbbarry: Will do.15:38
flacostejtv: seriously, i think we should allow starting the argument lists on the next line with a double-indent for long method names15:39
barry[ACTION] gmb to update PSG for parameter indents and email launchpad@15:39
MootBotACTION received:  gmb to update PSG for parameter indents and email launchpad@15:39
bigjoolsbarry: I will do the same about the OCR topic15:39
danilos#startsomethingtoendvote15:39
jtvflacoste: +1 for that15:39
barry[ACTION] bigjools to email launchpad@ about devs sticking around for their ocr15:39
MootBotACTION received:  bigjools to email launchpad@ about devs sticking around for their ocr15:39
barryflacoste, jtv yes, it's okay if there are exceptions for superCrazyMegaUltraLongMethodNamesThatTakeUpTonsOfSpace15:40
barry   * (mwhudson) What are page tests for?15:40
sinzuiuse cases15:41
barrymwhudson: brought up some questions about the purpose of page tests. are they customer stories or do they test our templates15:41
sinzuicustomer acceptance tests15:41
barryright now, the stuff in pagetests is some of both15:41
* sinzui tests templates in doc/*-pages.txt15:41
salgadoI test views in there15:42
salgadoI mean doc/*-pages.txt15:42
sinzuisalgado: So do it, but I recently added template tests since I did not think it was relevant to the use case15:42
barrysinzui: i think we mostly agree, so mwhudson is going to start a ml thread about it and begin to get people to separate these15:42
bigjoolsI think customer stories should involve all aspects of the template, otherwise what is that part the template doing there?15:42
flacostesinzui: testing template in doc/*-pages is not our standard, although it might make a good idea15:43
BjornTsinzui: do you have an example?15:43
* sinzui thinks15:43
flacostebigjools, sinzui: sometimes you have to test all the possibilities in a template15:43
flacostebut that's not relevant to the user stories15:43
flacosteas a dev, you know that these three cases involved three different code paths15:44
intellectronicai think that it's ok to mix the two purposes, as long as you get sufficient coverage15:44
flacostebut from the point of view of the user, it's one sue-case15:44
intellectronicathat's in line with our not doing unit tests for everything15:44
flacosteintellectronica: which i think is wrong15:44
jtvintellectronica: but is that a good thing?15:44
flacostebut that's just me15:44
sinzuiBjornT: I checked the calls to the search form in launchpad-search-pages. the form is a technical matter, not a use case.15:44
intellectronicajtv, flacoste: i'm not sure myself, i just note that this is how we do it. mostly, it means that we have to pay attention closely to make sure that we get full coverage from the mix of tests we do have15:45
sinzuithe pagetests need reorganisation, and normalisation15:45
jtvsinzui: +115:46
bigjoolsif your template is *that* complicated it has multiple code paths, should it not be simplified and stuff put in the view?15:46
danilosas do all our other tests15:46
bigjoolsmy eyes bleed over some templates15:46
barrysinzui: right.  thumper is going to start a thread about test reorg, and especially moving ftests stuff to tests15:46
sinzuibigjools: right. We don't have as many doc/*-pages.txt as we should have, I think a lot of pagetests are checking the view's behaviour15:47
barrybigjools: reviewing pts are incredibly painful15:47
bigjoolsexactly15:47
danilosif we are to reorganize tests, we should make as clear separation and categorization as possible, covering all testing15:47
bigjoolsand if more stuff is in the view, it can be tested separately15:47
bigjoolsand more efficiently15:47
bigjoolsthus speeding the test suite15:47
flacostebigjools: different code paths simply means different conditions15:48
flacosteso the logic is in the view15:48
BjornTintellectronica: it's not really how we do it. basically, we treat our tests for DB classes as 'unit tests'. they should have have as much coverage as possible.15:48
flacostebut you still need coverage that the template is using the view correclty15:48
bigjoolsflacoste: agreed15:48
flacostebarry: ftests/tests is an historical separation15:48
barryflacoste: s/historical/hysterical/ :)15:49
barrybut yeah15:49
sinzuibarry: +115:49
barryanyway, we've gone over.  my apologies for that.  we'll continue this discussion on the list when mwhudson starts it15:49
barry#endmeeting15:49
MootBotVote is in progress. Finishing now.15:49
MootBotFinal result is 10 for, 0 against. 0 abstained. Total: 1015:49
MootBotMeeting finished at 09:52.15:49
barrythanks everyone!15:49
jtvbarry: thank you, nice seeing you again :)15:50
intellectronicathanks barry15:50
bacthanks barry & mootbot15:50
barryjtv: you too!  you're welcome to stop by any time :)15:50
=== salgado_ is now known as salgado
=== salgado is now known as salgado-lunch
=== salgado-lunch is now known as salgado
=== _thumper_ is now known as thumper
=== salgado is now known as salgado-afk

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