=== Ursinha-nom is now known as Ursinha === cprov is now known as cprov-zzz === salgado-afk is now known as salgado [15:00] #startmeeting [15:00] Meeting started at 09:00. The chair is barry. [15:00] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [15:00] welcome to this week's ameu reviewer's meeting. who's here today? [15:00] me [15:00] me [15:00] me [15:00] deryck sends his apologies [15:01] me [15:01] me [15:01] me [15:01] me [15:02] me [15:02] jtv: ping [15:02] me [15:02] me [15:02] leonardr: ping [15:02] barry: thanks :) [15:02] :) [15:02] me [15:02] cprov, gary_poster, gmb, noodles775 ping [15:03] me [15:03] me, sorry [15:03] me [15:03] me [15:03] barry: OTP at the moment; apologies are on the schedule. [15:03] :-) [15:03] * barry reloads the page [15:03] lol [15:03] gmb: are you sure you committed your draft? :) [15:04] danilos, allenap, rockstar ping [15:04] me [15:04] me [15:05] [TOPIC] agenda [15:05] New Topic: agenda [15:05] * Roll call [15:05] * Action items [15:05] * Mentoring update [15:05] * Peanut gallery (anything not on the agenda) [15:05] [15:06] [TOPIC] action items [15:06] New Topic: action items [15:06] * intellectronica to report on relevant summary of ui reviewers meeting here [15:06] intellectronica: tell us some good news! [15:07] i think there has been some kind of misunderstanding [15:07] there aren't really any ui reviewers meetings [15:07] intellectronica: ui phone call maybe? [15:08] i suppose the most interesting thing i can tell you is that martin is planning on beefing up the guidelines and in particular, start collecting case reports for interesting branches that went through ui review [15:08] so if you're working on a ui branch from either side and think the process was interesting and other can learn from it, consider compiling a case report [15:09] yes [15:09] oh, we should have talked about a million dollars [15:09] :) [15:09] beuno: intellectronica was giving us a summary of the ui call [15:09] i suppose the most interesting thing i can tell you is that [15:09] martin is planning on beefing up the guidelines and in [15:09] particular, start collecting case reports for interesting [15:09] branches that went through ui review [10:08] [15:10] so if you're working on a ui branch from either side and [15:10] think the process was interesting and other can learn from [15:10] it, consider compiling a case report [15:10] [15:10] intellectronica: thanks; beuno do you have anything you want to add? [15:10] well [15:10] my goal is for the team to do it's own reviews [15:11] and have teh UX team help with the long-term changes [15:11] and I'm not sure how to get there, but I'm starting to [15:11] one other thing we talked about was adding a 'ui' specialty to ReviewerSchedule for people who have graduated from ui mentat [15:12] so if anyone has suggestions, ideas, comments, anything, I'd be very grateful [15:12] yes, it's on my ToDo [15:12] beuno: cool, thanks [15:12] beuno: do you want to join this meeting regularly? i could add 'ui reviewer report' to the agenda [15:13] barry, I would like to try, yes [15:13] * barry will be pingmaster :) [15:13] beuno: awesome, thanks. i'll remove intellectronica's action item then [15:14] anything else on ui reviewing, from anybody? [15:14] cool, moving on [15:14] [TOPIC] mentoring update [15:14] New Topic: mentoring update [15:15] i think i'll remove this topic for now. when wgrant wants to become a reviewer we can add it back [15:15] aren't we all reviewing now? i think this item can be skipped until some community members start reviewing [15:15] [TOPIC] peanut gallery [15:15] New Topic: peanut gallery [15:15] intellectronica: yes, we are all reviewers! [15:15] so, does anybody have anything not on the agenda? [15:16] yes [15:16] i guess that's it then! [15:16] almost :) [15:17] intellectronica: go4it [15:17] barry: (I'm not going to be OCR on Wednesday because of team lead duties) [15:17] 6 mo. :-) [15:17] a reminder to everyone that python branches with a diff > 800 lines and javascript branches with a diff > 1600 lines are exceptional, and need to have a review sorted in advance. OCRs will often not be able to take them just like that [15:18] gary_poster: gotcha. EdwinGrubbs will have to carry the west [15:18] k [15:18] intellectronica: thanks, and remember as a reviewer you always have a right to kick the branch back [15:19] anything else today? [15:19] 5 [15:19] * cprov feels guilty and hides. [15:19] 4 [15:19] 3 [15:19] 2 [15:19] 1 [15:19] #endmeeting [15:19] Meeting finished at 09:19. [15:19] thanks everyone! [15:20] thanks barry [15:20] thanks barry [15:20] thanks barry === Ursinha is now known as Ursinha-food === gmb is now known as gmb-afk === gmb-afk is now known as gmb === salgado is now known as salgado-lunch === bigjools is now known as bigjools-afk === Ursinha-food is now known as Ursinha === gary_poster is now known as gary-lunch === EdwinGrubbs is now known as Edwin-lunch === salgado-lunch is now known as salgado === gary-lunch is now known as gary_poster === danilos is now known as danilo-afk === Edwin-lunch is now known as EdwinGrubbs === salgado is now known as salgado-afk === cprov is now known as cprov-afk [23:30] #startmeeting [23:30] Meeting started at 17:30. The chair is barry. [23:30] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [23:30] hello and welcome to this week's asiapac meeting, who's here today? [23:31] thumper, rockstar ping [23:31] hey [23:32] thumper: hi. i think it's just the three of us today, right? [23:32] should be a quick meeting i think [23:32] yep, although rockstar is out for a walk right now, so maybe just me [23:32] did rockstar go to the earlier one? [23:32] nope, he's joining us now [23:33] s'okay, we can start (and maybe finish without him :) [23:33] ok [23:33] not much to report from ameu; gary_poster will suspend ocr duties while he fills in for flacoste, who's filling in for kiko [23:33] * thumper nods [23:33] that's really about it. got anything on your mind today? [23:34] * thumper thinks [23:34] mainly just 3.0 redesign [23:34] although... [23:34] there was a question earlier by gmb [23:34] about "do mechanical 3.0 changes need a ui review" [23:34] I was under the impression that mechanical ones don't [23:35] new pages/designs do [23:35] those are up to the reviewer+dev. if they feel it doesn't need another ui review, they're fine [23:35] ok [23:35] that's it for me [23:35] One thing... [23:35] Not sure where is appropriate, though. [23:35] shoot [23:36] ask away [23:37] It seems to me that contributors should always get a reviewer from the team that their branch targets, because otherwise the team has no chance to object. [23:37] The dev wiki just says to poke an OCR, but that probably often isn't right. [23:37] wgrant: I think it depends on the change [23:37] wgrant: that should be okayedin a pre-imp call, likely with a team member [23:38] wgrant: if it is something trivial, then I'd be happy to OK a bugs or soyuz change [23:38] we're all /supposed/ to be be able to review anything [23:38] but if it is not trivial, or requires more specialised knowledge [23:38] I'll pass it on, like I have done [23:38] oops. [23:38] Hi [23:38] rockstar: hi [23:38] thumper: yep [23:38] wgrant: does that make sense? [23:39] barry: It says to do the pre-imp chat with the OCR, but I suppose in most cases they'll just defer to a member of the right team, in which case that's fine. [23:39] It does. [23:39] wgrant: cool, yep [23:39] Thanks. [23:40] wgrant: it's great to see you here, and fantastic to see your branches landing. how is the processing going for you? [23:40] er, process [23:40] barry: Very well, apart from the opacity of PQM and ec2test. [23:40] wgrant: well, at least we feel your pain there too :) [23:41] wgrant: we are wanting to move to LP queues [23:41] The actual review stuff is fine. [23:41] wgrant: which will make at least that part more visible [23:41] But after the review, it goes into a black hole and sometimes doesn't appear again. [23:41] And once we're on queues, tarmac. [23:41] rockstar: ftw [23:41] rockstar: maybe ;-) [23:41] There's also the problem of security branches, but I believe you're working that out elsewhere. [23:41] That hit me today. [23:41] thumper, don't toy with my emotions like that... :) [23:41] I'm supposed to come up with a plan [23:41] wgrant: because you can't make private branches? [23:42] but I've not had time right now with the 3.0 stuff [23:42] barry: Correct. [23:42] we are planning the ability for anyone to be able to have a private branch [23:42] to fix security bugs [23:42] barry: I got spm to make it private, but then had to go back to him to get it visible to ~launchpad. [23:42] but there are issues about who gets emailed when [23:42] I'm not a member of ~launchpad, so I can't subscribe them to my private branch. [23:42] thumper: would they have to be tied to security bugs? [23:42] barry: possibly [23:42] barry: we are lacking some ui ability [23:42] wgrant: yep, that's losa territory [23:43] barry: it may just work, but I'm not convinced, and will have to look at the tests [23:43] cool. rockstar anything on your mind for today? [23:44] barry, nope, not really. I think the UI review for mechanical changes thing was the only thing. [23:44] if there's nothing else from thumper, wgrant... [23:44] Is devpad.info going to be public at some point? [23:44] nope [23:45] buildbot is moving [23:45] It's annoying getting buildbot failures with me in the blamelist, and not being able to actually see what went wrong. [23:45] Ah. [23:45] wgrant: lpbuildbot.canonical.com [23:45] wgrant: but I'm not sure on the visibility of it [23:45] It should be public. [23:46] thumper: Aha! [23:46] But no, it's not public. [23:47] i think we're done... [23:47] #endmeeting [23:47] Meeting finished at 17:47. [23:47] thanks barry [23:47] thanks everyone