[02:39] <nigelb> hyperair, hey :)
[02:56] <nigelb> nhandler, can you sign up on the wiki for the hours that you can ... helps me when i try to convince another person :)
[03:10] <nhandler> I'll take a few more.
[03:18] <nigelb> perfect.
[03:18]  * nigelb moves to next target :D
[03:23] <nhandler> I might need to reschedule a slot, but I'll leave it the way it is for now
[03:24] <nigelb> ah, thanks, so thats less slots to fill in
[03:25] <nigelb> I think I'll make it standard format to put IRC nick as display :)
[03:30] <nigelb> maco, um... if your schedule permits, can you sign up for a few hours on the patch wiki?  If its too undecided, later is fine too :)
[03:33] <nigelb> but it would really help me when I'm trying to recruit when a few people have already signed up
[03:41] <maco> nigelb: saturday may 5th?
[03:41] <maco> nigelb: check your calendar
[08:07] <dholbach> good morning
[10:44] <dholbach> wow
[10:44] <dholbach> the patch day is getting more and more publicity
[10:44] <dholbach> it's on major german news sites
[10:44] <dholbach> we better ramp up docs and stuff a bit
[14:17] <nigelb> dholbach, you wanted a rewrite of the review guide (was reading logs earlier today) ?
[14:17] <nigelb> maco, oops.  thanks, I'll correct it now :)
[14:24] <dholbach> nigelb: not rewrite it, but add examples, etc
[14:25] <nigelb> dholbach, ah, I'll try to work it in today :)
[14:26] <nigelb> dholbach, I need some help with rectruiting too
[14:26] <dholbach> nigelb: I suggest that before we start recruiting, we have a look at the docs together
[14:26] <dholbach> like all of us
[14:27] <nigelb> dholbach, I already started.  I'll put the docs into an etherpad :)
[14:27] <dholbach> I would have preferred them to be in tiptop shape before we announce, so that people who look at it directly get it and get all their questions answered
[14:27] <dholbach> but hey, we can always send another announce :)
[14:28] <nigelb> I did the announce hoping I'd get to work on the wiki in a few hours
[14:28] <nigelb> but yday was a bad day at work + no power here
[14:28] <nigelb> and yes we can do another announce, since I missed the last classroom session I planned due to now power :(
[14:30] <persia> Docs first.  Another announce later.
[14:30] <nigelb> yup
[14:30] <nigelb> http://pad.ubuntu-uk.org/qIEl4uiI8v
[14:30] <persia> Saturday, May 5th needs some help though :)
[14:30] <nigelb> here's the etherpad.. lets dive in
[14:30] <nigelb> I'm getting to the saturday thing
[14:30] <nigelb> I lost power before I saw her reply
[14:30] <persia> heh.  You're good at that, but you can't catch me this evening.
[14:31] <nigelb> persia, busy evening?
[14:31] <persia> I have a few things I want to get done for tomorrow.
[14:32] <nigelb> sure, daniel's around :)
[14:32] <dholbach> errr :)
[14:32] <dholbach> I'll try, need to get a few other things out of the way first
[14:32] <nigelb> I'll work on it, you folks can review when you get the time :)
[14:32] <dholbach> super :)
[14:44] <nigelb> persia, i'm so sorry I wasn't around for the class last night
[14:46] <persia> Happens sometimes.  No worries.  Just reschedule it.
[14:46] <nigelb> yea, I have reschedule around some uncertain power situations.
[14:46] <nigelb> btw, did you get time to take a look at the script?
[14:47] <nigelb> I have so many things to change in that...
[14:51] <nigelb> ok, I'm still unsure.  do we edit the script to make sure it recognizes patch-* tag (now that I can see the script code) or we dont do it?
[14:51] <persia> I thought the decision was that we didn't bother, and changed the process, since LP was cooler than previously thought.
[14:52] <nigelb> what irks me is since I can see the code, why not change it
[14:53] <persia> Extra work for no extra value?
[14:53] <nigelb> I need to get a few changes in anyway
[14:54] <nigelb> like that pacakge bryce said we can ignore
[14:54] <persia> Either way.
[15:06] <nigelb> so, the thing is... I want to know comments on this line
[15:06] <nigelb> As you complete each step of the process, you will mark your process by adding an appropriate 'patch-*' tag and removing the old one, however the 'patch' tag is NEVER removed from the bug.  Make sure to ALWAYS include a comment when you change the tag just like you would if you changed the bug status, so it's clear to later reviewers what happened.
[15:06] <nigelb> does the last bit stay or go?
[15:08] <persia> I like it, but I tend to be over-verbose when concision would be more effective.
[15:09] <nigelb> um.. the last bit of first line :D
[15:09] <nigelb> motu-sru is kinda gone right?
[15:10] <nigelb> also is ubuntu-ma-sponsors?
[15:12] <nigelb> so, can I have the script ignore redudant teams?
[15:59] <persia> nigelb: Rather than ignoring outdated teams, we especally want to know about those so we can move stuff to the right teams (and then ignore them).
[15:59] <persia> Workflow there is probably: subscribe the right team, remove the patch tag.
[15:59] <nigelb> persia, ouch
[15:59] <persia> (because with the right team subscribed, the script would then ignore the bug)
[15:59]  * nigelb doesn't know enough of LP API to get this right :)
[15:59] <persia> ouch?
[16:00] <nigelb> but we could probably have another script based on this one to subscribe new teams for the old bugs?
[16:01] <persia> I think dholbach has a script that does that: maybe we should extend that, and have the reviewers team script continue to ignore the old teams.
[16:02] <dholbach> http://people.canonical.com/~dholbach/resubscribe maybe?
[16:02] <persia> That'd be it :)
[16:02] <nigelb> well, if that works, then I can remove the old teams?
[16:03] <nigelb> dholbach, or you can have that run with this script too :)
[16:03] <persia> I'd check with the team owners.  I'd be pleased if ubuntu-universe-sponsors was automatically unsubscribed when ubuntu-sponsors was subscribed.
[16:03] <persia> I can't say for other teams.
[16:03] <nigelb> I thought dholbach 's script did that?
[16:05] <dholbach> if ubuntu-{universe,main}-sponsors are subscribed to an open bug, they'll be unsubscribed and ubuntu-sponsors will be subscribed instead
[16:06] <persia> Right, but the trick is to check with other potentially obsolete team owners before doing the same thing to those teams.
[16:06] <dholbach> oh sure, it's just for that use-case
[16:06] <nigelb> persia, ah.  that way, so talk to other obsolete team owners and get their teams to work the same way, gotcha :)
[16:06] <persia> But I think it's sharable to e.g. motu-release or motu-sru, assuming someone does the porting and legwork to communicate with the team owners.
[16:07] <persia> nigelb: You probably want to get the other team owners to run the script themselves every once in the while.
[16:07] <persia> dholbach: IN case I haven't said so recently: thanks for including u-u-s in your script :)
[16:08] <nigelb> persia, I'll add that to my things to do :D
[16:09] <dholbach> persia: it was since the beginning - it just wasn't executed because of a bug :)
[16:10] <persia> dholbach: Still, I appreciate you running it so I needn't :)
[16:11] <nigelb> I've pushed my changes, so take a look
[16:11] <dholbach> no worries :-)
[16:12] <nigelb> http://bazaar.launchpad.net/~nigelbabu/ubuntu-qa-tools/patch-review-script/annotate/head%3A/launchpadlib-scripts/patch-subscriber.py
[16:16] <persia> nigelb: You might also want to add linux-ti-omap to the subscribe-JFo set.
[16:16] <nigelb> aha, getting done.. minute
[16:17]  * persia hopes we have a good plan for kernel reduction for one of the next cycles: too many trees is too confusing
[16:18]  * nigelb refuses to go into kernel, even though tempting
[16:20] <persia> No, leave that to the kernel folks.  We just have *lots* of different kernel trees.  Last UDS we managed to kill one (linux-lpia), but we got more.
[16:21] <nigelb> the temptation to fix broken stuff is highly tempting
[16:21] <nigelb> wonder how core-devs manage to control the impulse :D
[16:21] <nigelb> ok, so added and new revision
[16:21] <nigelb> http://bazaar.launchpad.net/~nigelbabu/ubuntu-qa-tools/patch-review-script/annotate/head%3A/launchpadlib-scripts/patch-subscriber.py
[16:27] <nigelb> dholbach, ok, I need some idea of what kind of examples you're looking for...
[16:27] <nigelb> like add a test scenario to each case?
[16:31] <dholbach> nigelb: like bug X with a patch that needed some work, like bug Y with a patch that needed to go to debian, was forwarded there, etc.
[16:31] <dholbach> if you've never done it it will be hard to figure out for you what you need to do
[16:31] <nigelb> dholbach, um, those statuses are sort of dynamic
[16:31] <nigelb> so by the time someone actually looks into it patch-needswork will be patch-forwarded-upstream or patch-accepted-upstream
[16:31] <dholbach> yes
[16:32] <dholbach> I thought that a bug which tells a story of "here's what happened" might be helpful in teaching that
[16:32] <nigelb> ah, I'll look for those
[16:33] <dholbach> I'll have a look over it tomorrow
[16:33] <nigelb> so, I'll add specific examples below the current ones
[16:33] <nigelb> i.e. the current rule-stlyle ;)
[16:33] <nigelb> dholbach, I'll nag persia to look at it today :D
[16:33] <dholbach> awesome
[16:33]  * dholbach has to head out and tend to a few other things
[16:33] <dholbach> so have a great rest of your day
[16:34] <dholbach> and see you soon again! :)
[16:34] <nigelb> later dholbach :)
[16:34] <dholbach> rock on
[16:36] <nigelb> persia, how long more will you be up?
[16:36] <persia> longer than you.
[16:37] <nigelb> can talk to brian about my edits?  I'm dead on sleep already.
[16:37] <nigelb> james_w, can you sign up for a few hours of review leading? https://wiki.ubuntu.com/PatchDay
[16:37] <james_w> not right now
[16:37] <nigelb> well 1 hour is fine too :)
[16:38] <james_w> I'll look closer to the time
[16:38] <nigelb> sure, thank you :)
[16:38] <persia> nigelb: Sure.
[16:38] <nigelb> persia, thank you :)
[16:38]  * nigelb is off.  rest of wiki edits in the morning