=== mwhudson_ is now known as mwhudson === daniloff is now known as danilos === mrevell is now known as mrevell-lunch === mrevell-lunch is now known as mrevell [15:00] #startmeeting [15:00] Meeting started at 09:00. The chair is bac. [15:00] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [15:01] Hi, welcome to the Launchpad Reviewers Meeting serving Europe and the Americas. Who is here? [15:01] me [15:01] me too [15:01] also me [15:02] me [15:02] me [15:02] me [15:02] me [15:02] sinzui, EdwinGrubbs: ping [15:02] or should I say, moi aussi [15:02] me [15:02] me [15:03] danilos: ping [15:03] Registry Team is here! [15:03] me [15:03] me [15:03] gary_poster: ping [15:03] bac: me [15:03] flacoste: ping [15:03] me [15:04] TLs ping your peeps [15:04] me [15:04] bac: I did ping my TL [15:04] me [15:04] ;) [15:04] [topic] agenda [15:04] New Topic: agenda [15:04] soyuz here [15:04] me [15:05] * Roll call [15:05] * Agenda [15:05] * Outstanding actions [15:05] * New topics [15:05] * YUI namespacing for lp specific items should start with lp (rockstar) [15:05] * Peanut gallery [15:05] [topic] outstanding actions [15:05] New Topic: outstanding actions [15:05] [topic] * gary_poster to do timing tests for try/except, examine current usage of check_permission, and we'll discuss again 3-Mar. [15:05] New Topic: * gary_poster to do timing tests for try/except, examine current usage of check_permission, and we'll discuss again 3-Mar. [15:05] any progress gary_poster? [15:06] let's take it off the list, and I'll ping when I do it [15:06] that would be a no :-) [15:06] gary_poster: ok. [15:06] [topic] * salgado to update the wiki page to encourage reviews with sufficient context. [15:06] New Topic: * salgado to update the wiki page to encourage reviews with sufficient context. [15:07] oh, crap. haven't done it yet [15:07] sorry [15:07] np. i keep meaning to harass people with items on mondays but i keep forgetting. [15:07] [topic] bigjools to start ML discussion about community reviewers and committers. (done 24-Feb) [15:07] New Topic: bigjools to start ML discussion about community reviewers and committers. (done 24-Feb) [15:07] thanks bigjools -- you're our star today [15:08] I don't suck! [15:08] next action on you to talk to legal? [15:08] and on a related note: [15:08] [topic] * bac to seek opinion of IS and Legal wrt community reviewers and committers. (due 10-Mar). [15:08] New Topic: * bac to seek opinion of IS and Legal wrt community reviewers and committers. (due 10-Mar). [15:08] i agreed to do this task yesterday but haven't gotten to it yet. [15:09] bac, do you want it to be an action or a topic? [15:09] martin pool made the reasonable request that we/I write a statement on the wiki about the fact we're looking into the issue in the interim [15:10] [action] bac to update wiki re: interim status of community reviewers and committers [15:10] ACTION received: bac to update wiki re: interim status of community reviewers and committers [15:10] danilos: i use -topic- for old items and -action- for new ones. not that it matters much as mootbot is mostly useless [15:11] new stuff [15:11] [topic] YUI namespacing for lp specific items should start with lp (rockstar) [15:11] New Topic: YUI namespacing for lp specific items should start with lp (rockstar) [15:11] rockstar has sacrificed his morning bike ride to be with us today [15:12] Yes, but I would half-assed the ride anyway. [15:12] he'd only get hit by a car anyway ;) [15:12] hi rockstar [15:12] step away from the car deryck [15:12] heh [15:12] So the current rule in YUI namespacing for launchpad is to start with the app it's being used on. [15:12] rockstar, good morning, I'd be +1 on your suggestion [15:12] (not that I heard it fully :) [15:13] I think that's a little inconsistent with the way we precede lazr-js widgets with lazr. [15:13] So I propose that javascript namespaces start with lp. [15:14] rockstar, do you have an example of the old way, and the new way? [15:14] That way, if/when we start using third party widgets (yes please), there's no confusion which ones, are lp specific. [15:14] +1 [15:14] what about existing code? [15:14] mars, no, unless you count what we have as the old way, and what I have sitting in a branch as the new way. [15:15] intellectronica, I assume we migrate as we can. There are already open bugs that EdwinGrubbs filed because namespaces are wrong is some places already. [15:15] it's a lovely suggestion rockstar. i wish you'd made it about a month ago... :) [15:15] I should also mention that I'm in the process of doing away with lib/canonical/launchpad/javascript. [15:15] EdwinGrubbs: how many of those bugs have been done? [15:17] rockstar: you rock [15:17] bac: I know that I did the one for the registry. I don't know about any of the other ones except that rockstar worked on one which I reviewed, so the inconsistencies between the ways we completed it are fortunately being brought to the meeting. [15:17] star [15:17] bac, we talked about this change at the lazr-js sprint, but apparently it got changed before it made it to the reviewers. [15:17] any other thoughts? [15:18] I'd be happy to help other teams get their javascript in order. [15:18] yes please :) [15:18] rockstar: thanks [15:18] (specifically the teams that have no javascript) [15:18] :) [15:18] lol [15:18] lol [15:18] so, it looks like we're in favor of the change. [15:19] thanks for the idea and bringing it up rockstar [15:19] I'm +1 and we still have the other renaming for bugs to do anyway. [15:19] deryck, I'll just comment on your bugs with the new change. [15:19] rockstar, excellent, thanks! [15:20] rockstar: can i get you to update he existing bugs EdwinGrubbs opened and open new ones for the apps that have already been converted? [15:20] bac, yeah, I committed to that at the UI meeting when I first proposed this. [15:21] Also, updating the style guide. [15:21] [action] rockstar to update bugs to reflect new naming convention and will update the style guide [15:21] ACTION received: rockstar to update bugs to reflect new naming convention and will update the style guide [15:21] [topic] peanuts [15:21] New Topic: peanuts [15:21] anything to discuss that wasn't on the agenda? [15:21] New reviewer to join me for Thurs Euro? [15:21] Now with al-maisan leaving soon, I'll be all on my own again :) [15:22] (leaving launchpad that is) [15:22] Do we have a ui-reviewers team? [15:22] noodles775, do you really get busy on Thursday in Euro? [15:22] The last two weeks yes, pretty much my whole day (handing a queue to you), but the week before was only one, so it varies. [15:23] abentley, we are discussing about how to graduate more UI reviewers. Curtis is practically ready to graduate, he just hasn't assumed the crown yet :) [15:23] noodles775: most slots only have single-person coverage [15:23] bac: just checked, yeah right, only Monday and Weds have 2. OK. [15:23] mars, that seems only tangentially related to my question. [15:24] https://dev.launchpad.net/ReviewerSchedule [15:24] noodles775: jelmer wants to start reviewing and he might collar to be a mentor [15:24] Sounds great! [15:24] collar you, that is [15:24] abentley: UI reviewers are marked under the "specialties" column on the wiki i posted [15:25] abentley: other than that no real team [15:25] abentley, then the answer is no: we do not have a team [15:25] abentley, the list of reviewers ann process can be found here: https://dev.launchpad.net/UI/Reviews [15:25] bac, mars: I would like to be able to request a ui review from the ui-reviewers team. [15:26] ah, interesting idea [15:26] Its non-existence makes that hard :-) [15:26] abentley: ok, so you're talking about a team in launchpad for use in merge proposals. [15:26] bac, yes. [15:26] abentley: so the answer is "not now" but it seems easy enough to do [15:26] bac, having a team might overlap with that wiki page. [15:27] But it might also be a nice way to find a ui reviewer. [15:27] abentley: would you like to coordinate getting that team established? [15:27] abentley, I'm your ui reviewer. Never forget that. :) [15:27] rockstar, :-) [15:27] bac, sure. [15:27] abentley, we can discuss it at the next UI call, if you wish [15:28] mars, okay. [15:28] [action] mars to discuss UI reviewers team on UI call [15:28] ACTION received: mars to discuss UI reviewers team on UI call [15:28] any other topics? [15:29] ok, thanks for coming everyone. [15:29] Why would we need to discuss making a UI reviewers team? Couldn't we just JFDI? [15:29] #endmeeting [15:29] Meeting finished at 09:29. [15:29] thanks bac [15:29] thanks! [15:30] rockstar, I don't think throwing a UI review at a team will necessarily stick. "If everyone owns it, no one owns it" [15:30] Unless we all agree to pick up team reviews [15:30] mars, well, it'll stick as well as throwing a code review at a team. [15:30] rockstar: i agree with mars. making you chase a real person is going to help make sure the review actually gets done promptly [15:31] We've never just "thrown" the UI at a team. It's assigned to a team, and then we go find a member of that team to do it. [15:31] Er, "thrown" a review at a team. [15:32] well, you do throw it at them, but you know there is someone over there looking for things to catch :) [15:32] rockstar: the problem is that assignment means something very specific in Launchpad. it means 'this person is going to do that' [15:32] mars, if someone were to just assign a review to me, it's not likely I would do it. I'd expect them to come to me and say "Hey, I assigned this review to you. Can you do it?" [15:33] if that person is not really a person then it's confusing [15:34] rockstar, right. There is a social convention, or contract, there. The UI reviewers team has not actually talked about said contract yet, so how would we know what to do when other people, not ourselves, invoke it? [15:34] We do this on a regular basis with canonical-launchpad [15:35] rockstar: good point [15:35] but we always also go find a reviewer [15:35] Team or Individual, there's already an existing social contract. [15:36] rockstar, but not between "anyone in launchpad" and the UI Reviewers team [15:36] if you just created that team tomorrow, and assigned a review to it, nothing would happen [15:37] But if you assigned a review to it, pinged someone and they weren't able to do it, other people would be aware of the need? [15:37] because we, the UI reviewers, don't know what to do yet. Who should pick up the review? Who can safely ignore it? [15:37] Creating the team allows you to see who you can track down. [15:37] noodles775, maybe, depends if that happens already. Is creating a team just paving cowpaths? Or creating a new contract? [15:38] I can safely ignore any review that no one specifically asked me to review. If you don't track down a specific reviewer, obviously your review isn't a high priority. [15:38] rockstar, true, but so does the UI Reviewers wiki page. And the page tells you what skill people have. [15:39] mars, we don't need a wiki to make people honest. I know I haven't graduated (a theme that constantly irks me). [15:39] I'll make sure to say something like "you'll need to get another review from " [15:40] We already have "social contracts" that work fine, and ARE working. [15:41] rockstar, so the reason I think we should talk about this a bit at the meeting is so we all know what to do when we get notified that someone assigned a review to the UI Reviewers team. You may know, but I, for example don't. [15:41] mars, what do you do when someone assigns a code review to canonical-launchpad? [15:41] If you know, great, then you can tell everyone on the team about during the the UI call :) [15:41] rockstar, absolutely nothing [15:42] mars, now you know, and knowing is half the battle. [15:42] We're not changing anything here. We're not doing anything new. [15:42] rockstar, so why have the team at all then? What does it do? [15:43] If no one does anything when it is assigned to the team, then what is the point? [15:43] mars, what's the point of canonical-launchpad then? [15:43] mars, It allows me to flag the fact that it needs ui-review before I know who my ui-reviewer is. [15:44] abentley, ah! ok, *that* makes sense. [15:45] rockstar, so the point of canonical-launchpad is just a placeholder as well. Just a flag of intent. [15:46] rockstar, abentley, you see, I thought you meant that some action on our part was implied by assigning a review to the ui-reviewers team. [15:46] mars, currently people are not notified when their team is requested to perform a review, but there has been pushback about that, so we may change it. [15:46] That is not the case [15:46] abentley, ah [15:49] So, I don't think you can just assume everyone will know to do the same thing in the new ui-reviewers team as what happens with canonical-launchpad. You have to spell it out. It's a new team, with a new contract. (That just happens to be the same as what we do for canonical-launchpad.) [15:50] mars, yeah, so it's not new. Do we have any UI reviewers who aren't also code reviewers? [15:50] rockstar, nope [15:50] rockstar, wait, /me checks [15:51] mars, here's a compromise. Let's not "talk" about it at the UI reviewers meeting. Let's just say "we're creating a group, you're in it, do what you do with code reviews" [15:51] Done. [15:52] rockstar, sure, since we already talked about it here :) [15:53] rockstar, you should at least ask for agreement from the other team members though. You can lay it all out on a silver platter, but don't shove it down people's throats :) [15:57] rockstar, fwiw, mrevell is a UI reviewer, but not a code reviewer. === salgado is now known as salgado-lunch [16:03] rockstar, mind if I add the UI call topic in your name? [16:05] mars, probably ought to do it in your name. [16:05] ok [16:06] done [16:22] * mrjazzcat is away: Auto-away after 30 mins idle (gone at 3rd Mar, 09:22:12) === mrjazzcat is now known as mrjazzcat`afk === mrjazzcat`afk is now known as mrjazzcat === salgado-lunch is now known as salgado === danilos is now known as daniloff === gary_poster is now known as gary-lunch === EdwinGrubbs is now known as Edwin-lunch === gary-lunch is now known as gary_poster === salgado is now known as salgado-afk [21:31] hi mwhudson, thumper, rockstar [21:31] bac: hi [21:31] bac: hi [21:31] how's your morning thumper? [21:31] pretty good [21:31] #startmeeting [21:31] Meeting started at 15:31. The chair is bac. [21:31] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [21:31] hi michael [21:32] hi [21:32] hi rockstar [21:32] bac, I guess I'm doing double duty today. :) [21:32] a twofer [21:32] rockstar: heck you should just lead the meeting [21:32] bac, :) [21:33] the only excitement from this morning was rockstar's proposal for changing (again -- :) ) the JS naming conventions [21:33] bac, in my defense, this was what was originally intended. :) [21:33] rockstar: you want to summarize your idea? [21:33] Okay, so basically all YUI namespacing for lp specific modules now starts with lp. [21:34] So for the code team, our modules would be namespaced as "lp.code.whatever" [21:34] The code team has more specifics to the namespace, but those aren't lp wide. [21:34] the previous new convention had just been "code.whatever", right? [21:35] there wasn't much discussion since everyone thought it was a reasonable idea [21:36] abentley brought up the idea of creating a launchpad-ui-reviewers team in LP for use in assigning a reviewer in a MP [21:36] both those things make sense to me [21:37] mars was going to bring it up on the UI reviewers call. after the meeting ended there was some discussion about whether it made sense or not, but i couldn't hang around for the outcome [21:37] i guess we'll learn more next week [21:38] (the outcome is that we're going to talk about creating a team instead of JFDI'ing :) [21:38] and from the mailing list discussion about community involvement in reviews and landing i took the assignment to check with legal and IS as to whether it is feasible or not from a corporate standpoint [21:39] rockstar: yeah, it seemed a bit wankish but i guess there is no need to create a team if in the end it's not going to be useful [21:40] so, that was basically all we discussed. nothing too controversial. [21:40] either of you have anything to talk about? [21:40] i thought rob's mail on the the community reviewer thread expressed my position pretty well [21:41] hey, i have a question. i see in merge proposals the "reviewed version" is being set of us. was that a recent fix? [21:41] bac: yes [21:41] mwhudson: cool [21:42] * bac tries to remember what exactly rob's point was [21:43] well, partly that it was a strange limit to try to hold, given that there is plenty of community in ubuntu-core-dev [21:43] but i didn't really want to restart the discussion here :) [21:43] no, thanks for that [21:44] well, that's all i've got [21:44] me too [21:44] thanks for coming. [21:44] #endmeeting [21:44] Meeting finished at 15:44.