=== ubottu is now known as ubotuu === ubotuu is now known as ubottu === cprov-afk is now known as cprov === salgado-afk is now known as salgado === mrevell is now known as mrevell-lunch === mrevell-lunch is now known as mrevell [14:58] To the tune of _Doe a deer_: [14:58] Dough, the thing that buys my beer [14:58] Ray, the guy that pours my beer [14:58] Me, the guy that drink my beer [14:59] Fa, the sound i make when i drink too much beer [15:00] So, I'll have another beer [15:00] Tea? No thanks I'll have a beer [15:00] #startmeeting [15:00] me [15:01] mootbot's pushing up daisies so we're kicking this old school [15:01] who's here today? [15:01] me [15:01] me [15:01] me [15:01] me [15:01] me [15:01] me [15:01] me [15:01] me [15:02] salgado: ping [15:02] bigjools: ping [15:03] == Agenda == [15:03] * Roll call [15:03] * Next meeting [15:03] * Action items [15:03] * Queue status [15:03] * Mentoring update [15:03] * Review process [15:03] * How to manage workload of reviewing (intellectronica, sinzui? gmb?) [15:03] * comparing strings with `is` (stevea) [15:03] * overly broad `KeyError`s (stevea) [15:03] * adding lpreview to sourcecode? [15:03] * People should be updating sampledata when they add columns to tables (gmb). All too often I find myself running make newsampledata only to discover a bunch of changes that are nothing to do with me and which merely do things like setting new fields to NULL. This inflates the linecount of a diff and, worse, makes sampledata harder to debug. People should be running make newsampledata on their DB patch branches, or at least on the c [15:03] ode branches that descend from the DB patches. [15:03] * Perhaps add a check to the lint report? -- GavinPanella [15:03] * Next meeting [15:03] today += weeks(1) ? [15:04] anybody know you'll be missing? [15:04] wouldn't miss it for anything [15:04] great! [15:04] * Action items [15:04] * barry drive to decision about multiline sequences [15:05] i suck, but i will do this today or tomorrow [15:05] * gmb to add lpreview to sourcecode and hack rf-setup to link it in [15:05] Haven't touched this since last week what with roll-out coming up [15:06] But mthaddon was having trouble branching it for sourcecode. [15:06] I'll tackle this once rollout is complete. [15:06] gmb: sounds great, thanks [15:06] * bigjools to email list about cleaning up after branches land [15:06] me [15:06] bigjools is mia, but i /think/ this was done, wasn't it? [15:06] sorry for being late [15:06] salgado: no worries [15:07] barry: It was done [15:07] sinzui: ok, thanks [15:07] * gmb to prod mwh again about the 800-line limit patch [15:07] FAIL. [15:07] Will do it today. [15:07] we'll just continue this one [15:08] * intellectronica to add js style guide link to TipsForReviewers [15:08] i'm pretty sure i did this last week, let me check [15:08] i did [15:09] intellectronica: thanks! [15:09] * sinzui to update js style guide page with helpful resources [15:09] Not Done [15:09] no worries, we'll just continue this one [15:09] * Queue status [15:10] * barry can't get to the PR wiki [15:11] my sincere apologies for not doing any PR reviews (and rejecting a few on irc). i must finish some stuff before the release [15:11] ah there it is [15:11] intellectronica: it happens [15:11] leonard's is the only one in the general queue. i didn't have time to get to it yesterday [15:11] and he just added it to the GQ [15:12] maybe we should just assign leonard's branch to someone? [15:12] anybody have time to review it? [15:13] barry: I will after today. [15:13] gmb: great, thanks [15:14] gmb: can i put it in your queue? [15:14] sure [15:14] cool [15:14] anything else on the queue? [15:14] * Mentoring update [15:14] bac: wanna do the honors? [15:15] yes [15:15] Today we're graduating Gavin. Well done and hoorah. [15:15] * gmb applauds [15:15] * allenap does \o/ [15:15] \o/ [15:15] go allenap! [15:15] congratulations allenap! [15:15] Thanks bac :) [15:15] \o/ [15:16] it was my pleasure [15:16] allenap: congrats! [15:16] Thanks everyone. [15:17] now that we have an open slot and EdwinGrubbs has been nominated for recruitment, we need a mentor for him though [15:17] salgado: do you think you can mentor him? [15:18] barry, I was thinking about that [15:18] salgado: you don't have to answer right now. just let me know [15:18] salgado: if you can't that's cool, we'll find another mentor for him [15:18] if I mentor him, what happens with my on-call term? [15:18] while mentoring is important, I think we should also feel comfortable taking a month off from mentoring, to avoid burnout [15:19] can EdwinGrubbs take it over and I only mentor him during that day? [15:19] salgado: EdwinGrubbs would be oncall with you and he would do most if not all of the reviews. you would mentor his reviews, but hopefully not do too many of your own [15:19] statik: do you think we should do that team-wide, or just for a particular mentor? [15:19] salgado: That is essentially what I have done working with schwuk [15:20] barry: I just wanted to mention it, we all sometimes need to hear that it is ok to say no :) [15:20] okay, I can do it, then [15:20] statik: right you are [15:20] just like rejecting branches, it is okay to say no! [15:20] salgado: awesome, thanks [15:20] no [15:21] intellectronica: not you though [15:21] :) [15:21] EdwinGrubbs, you start tomorrow. ;) [15:21] :) [15:21] anything else on mentoring? [15:21] moving on... [15:22] * Review process [15:22] * How to manage workload of reviewing (intellectronica, sinzui? gmb?) [15:22] i apologize for not remembering who wanted to talk about this [15:22] the floor is open (just let me know when you're done) [15:22] i think it isn't really about work load [15:22] more about work scheduling [15:22] the work load is not something we can influence, anyway [15:23] I have concluded that schwuk reads 1.5 faster than I do, so he can easily over whelm me. I'm not taking reviews while he is reviewing. [15:23] the problem i identified, is that having a whole day dedicated to reviewing in the middle of the week is often too distracting for me [15:24] me - late, sorry :( [15:24] it means that i have to drop whatever i was doing on the days before that, and can't respond to anything other than reviews [15:24] i was wondering if anybody has any thoughts about this, or ideas for managing it better [15:24] how others who are on-call middle-of-week feels about that? [15:25] intellectronica: would it make sense to rotate ocr days every now and then? i find mondays are nicely segmented, but when it rains, they can be triply depressing :) [15:25] :) [15:25] yes, i can imagine mondays and firdays are a bit better [15:25] Friday works well for being on call, but I can see what intellectronica is talking about. [15:25] my problem is my on-call day spills over and eats most of the next morning, which sinzui has discussed before. [15:26] I prefer to have one day in which I concentrate on reviews than to do reviews for a couple hours every day [15:26] tuesday has not been a problem [15:26] salgado: right, so it's a matter of personal preference. not really something we can generalise [15:26] my biggest fear is that we'll burn out on doing reviews. maybe we need a reviewer's vacation? [15:27] bac: I would stop early if I felt I had too many needs-reply [15:27] sinzui: yes. it gets more difficult when you're working with a mentee. i just need to manage the time better. [15:28] barry: that's a nice option, but with the current work load, it risks only increasing the work for other reviewers [15:28] intellectronica: Europe is now filled with on-call reviewers, so it is possible for one to take a week off [15:28] maybe we can fast-track extra reviewers? [15:28] do we have enough reviewers now for people to be on call every two weeks instead of every week? [15:28] i'll note that if someone is really swamped, we've done one-time skips of ocr or switch days [15:29] sinzui: well, i'm pretty much doing this today [15:29] I did that last week. [15:29] statik: i don't think that is feasible yet [15:29] allenap: You will be sharing a slot I think [15:29] sinzui: Fine with me. [15:29] * sinzui is looking at https://launchpad.canonical.com/OnCallReviewers [15:29] allenap: what slot are you taking? [15:29] bac: you're right, because of timezones [15:30] * intellectronica notices that he's got the only slot that doesn't have anyone before or after it [15:30] intellectronica: right! [15:30] it could be that this contributes to my workload, and that other shifts are not as problematic [15:30] bac: I guess I could do Thursday with intellectronica. [15:30] intellectronica: maybe allenap can share or overlap with you? [15:31] allenap: what do you say? i'd like that [15:31] intellectronica: Me too :) Done deal. [15:31] allenap: or even wednesday with intellectronica [15:31] bac: Oh yeah, doh :) [15:31] intellectronica: rockstar_: and abentley would have to emigrate to fill those AsiaPac slots [15:31] allenap: great, please update OnCallReviewers [15:31] barry: Done. [15:32] maybe we should keep track of how many reviews are done in each term [15:32] allenap: you're not keeping your tuesday slot though, right? [15:32] barry: No, I just deleted that. I'm not doing well today. [15:32] that could help balancing the workload [15:33] allenap: thanks [15:33] salgado: that came up in asiapac. i know i keep track of my review time (using gtimelog) but we're not gathering those statistics any more [15:34] right, that's why I suggested number of reviews, which is way easier to track [15:34] maybe just filling a googledocs spreadsheet would do for now [15:35] let's do this: if you have a suggestion for improving the review process, email me or the list. i'll try to put together a couple of concrete proposals and we can try them out for a cycle or two and see what we like [15:35] I mean, it's better than nothing and we don't have to go through launchpad-reviews counting email messages [15:36] we've got two more issues, hopefully quick ones [15:36] * comparing strings with `is` (stevea) [15:36] * overly broad `KeyError`s (stevea) [15:37] these were things steve saw in a branch he was rc'ing and he wanted me to just mention them here so you all are aware of them [15:37] first, nobody should ever compare strings with 'is' or 'is not' [15:37] i think the code example was: if foo is 'bar': [15:37] always use == and != to compare strings [15:38] any questions about that one? [15:38] cool [15:39] second one is really about putting too much code in the try clause of a try/except [15:39] there was a case where inside the try, it wasn't clear which line of code the KeyError was trying to catch, so it would be possible to mask bugs [15:40] so watch out for too much stuff inside the try and encourage coders to use an else clause or to put the success code outside the try/except (as appropriate) [15:40] does that make sense/ [15:40] er, sense? [15:40] * sinzui mutters Py 2.5 [15:40] how 2.5 affects this? [15:41] No, not specifically. I recall see nested trys because of else and finally [15:41] and it will be great to have conditional expressions [15:42] yes, you can get rid of most of your nested try/finally try/excepts [15:42] intellectronica: and with statements! [15:42] sinzui, I wouldn't mind. I've been instructed by the other half to think real estate in NZ next week. [15:42] anyway. that's all i have today. we've got 3 more minutes, so i'll open the floor [15:42] barry: sampledata [15:42] gmb: dang, right [15:42] gmb: take it [15:43] It's on the agenda, but it's pretty self explanatory. [15:43] rockstar_: really? I thought the antipodeans only accepted full reviewers. [15:43] If you see a branch that hangs off a DB patch can you check that the developer has updated sampledata appropriately? [15:43] * barry was looking at the wrong tab [15:43] Many of these will be fixed in the DB review anyway. [15:43] * sinzui notes that they traded mpt for mwhudson [15:43] BUt if a new field can be NULL and defaults there to then developers don't always make newsampledata [15:44] Which makes it hard work for the poor schmuck that does. [15:44] (And his reviewer, not incidentally). [15:44] right, so that needs to be part of the review 'checklist', i guess [15:44] Yes. [15:44] barry: I'll update that. [15:45] it could even be automated [15:45] gmb: thanks [15:45] make newsampledata and no changes should appear [15:45] with the previous one [15:45] flacoste: I'm not sure I understand you. [15:45] yeah, that'd do a nice test [15:45] flacoste: as part of make lint? [15:45] yes [15:45] or another test by review-submit [15:46] It'd be nice to make it part of make lint. [15:46] flacoste: That's a clever idea [15:46] +1 [15:46] flacoste: wanna take a crack at it? [15:46] i don't think we should enforce creating new sample data when submitting the branch for review [15:46] * flacoste looks at sinzui - another good reason to replace jamesh lint [15:47] if it's not needed, it will produce a much larger diff, and the branch will be prone for conflicts [15:47] Why do we need to replace jamesh? [15:47] Oh, wait. [15:47] screen was being silly. [15:47] much better to generate the sample data just before submitting the branch to pqm [15:47] Carry on. [15:47] BjornT: problem is that we delay the price [15:47] BjornT: that's also good [15:47] i thought you were suggesting not updating sampledata at all [15:47] unless absolutely needed [15:48] if that's what we want we can make the test suggested by flacoste part of our test suite [15:48] sinzui, I don't really get that joke... :( [15:49] okay, sorry, we're 3 minutes over now. let's think about the sampledata test and i'll put it on the list for next week [15:49] #endmeeting [15:49] thanks everyone! [15:49] thanks everybuddy [15:49] thanks barry [15:49] thanks barry [15:49] (everyone except mootbot) [15:49] rockstar_: the only person who was ANZ not a review was mpt, He moved to UK. mwhudson who became a reviewer moved to NZ [15:50] Ah, I see. [15:50] rockstar_: The antipodeans seem to prefer, for lack of a better word, 'rockstars' [15:50] * rockstar_ goes to learn the reviewer secret handshakes... :) [15:50] rockstar_: don't forget to sacrifice the goat first. [15:50] sinzui, perfect! The only problem now is that I've only been around for a week and a half now. [15:50] I think ibex is the animal of choice [15:51] sinzui: oh, i thought we were keeping them for ubuntu sacrifices. [15:52] Hobbsee: We like Ubunut [15:52] Hobbsee: We like Ubuntu [15:52] sinzui, our move would be solely based upon U.S. politics. :) [15:52] sinzui: so you should sacrifice things to make it work properly, no? [15:52] apparently we're out of zebras. [15:53] Shit! Who do we talk to in order to get more? [15:54] rockstar_: I've been thinking on Montreal for similar reasons [15:54] sinzui, you're in AsiaPac? [15:56] rockstar_: No. I loved living in Australia as a child. I work on the Foundations team so I should be stay on the East coast of North America, Caribbean, or South American [15:57] Oh crap, I would totall be down in the Carribean... [15:58] I lived there for a while. I'd think about going back, but that'd be a step in the wrong direction... [15:58] rockstar_: Consider Hawaii. Fiji has some bad politics [15:58] Hawaii is still the U.S. [15:58] Half is owned by Nippon [15:59] Hawaii? [15:59] yeah? 50% of land and business is owned by Japanese investors I believe [16:00] So it's not U.S. soil> [16:00] * rockstar_ grumbles and the things the U.S. "fails to mention" in public school... [16:01] rockstar_: I learned to study a nation's history in another nation. [16:02] sinzui, good idea. Living in Texas 'til I was 11, I only ever learned Texas history. No U.S. history even. [16:02] rockstar_: France has little to say about Napoleon. The US does not mentioned Native Americans and genocide very often [16:02] rockstar_: Texas is it's own state of mind. [16:03] Yea, we killed a lot of Mexicans... [16:03] And stole a lot of land [16:03] * rockstar_ redacts the "we" and adds "they" [16:06] rockstar_: Australia just officially apologised for taking generations of children from their families. NZ is in rights disputes with the Maori. There is a lot of crime to redact 'we' with 'they' [16:08] sinzui, well, problems are problems. It's more about the "looking forward" solution. At least the Australians apologized... [16:09] rockstar_: I agree. === salgado is now known as salgado-lunch === salgado-lunch is now known as salgado