/srv/irclogs.ubuntu.com/2010/04/08/#ubuntu-reviews.txt

nigelbhyperair, hey :)02:39
nigelbnhandler, can you sign up on the wiki for the hours that you can ... helps me when i try to convince another person :)02:56
nhandlerI'll take a few more.03:10
nigelbperfect.03:18
* nigelb moves to next target :D03:18
nhandlerI might need to reschedule a slot, but I'll leave it the way it is for now03:23
nigelbah, thanks, so thats less slots to fill in03:24
nigelbI think I'll make it standard format to put IRC nick as display :)03:25
nigelbmaco, 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:30
nigelbbut it would really help me when I'm trying to recruit when a few people have already signed up03:33
maconigelb: saturday may 5th?03:41
maconigelb: check your calendar03:41
dholbachgood morning08:07
dholbachwow10:44
dholbachthe patch day is getting more and more publicity10:44
dholbachit's on major german news sites10:44
dholbachwe better ramp up docs and stuff a bit10:44
nigelbdholbach, you wanted a rewrite of the review guide (was reading logs earlier today) ?14:17
nigelbmaco, oops.  thanks, I'll correct it now :)14:17
dholbachnigelb: not rewrite it, but add examples, etc14:24
nigelbdholbach, ah, I'll try to work it in today :)14:25
nigelbdholbach, I need some help with rectruiting too14:26
dholbachnigelb: I suggest that before we start recruiting, we have a look at the docs together14:26
dholbachlike all of us14:26
nigelbdholbach, I already started.  I'll put the docs into an etherpad :)14:27
dholbachI 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 answered14:27
dholbachbut hey, we can always send another announce :)14:27
nigelbI did the announce hoping I'd get to work on the wiki in a few hours14:28
nigelbbut yday was a bad day at work + no power here14:28
nigelband yes we can do another announce, since I missed the last classroom session I planned due to now power :(14:28
persiaDocs first.  Another announce later.14:30
nigelbyup14:30
nigelbhttp://pad.ubuntu-uk.org/qIEl4uiI8v14:30
persiaSaturday, May 5th needs some help though :)14:30
nigelbhere's the etherpad.. lets dive in14:30
nigelbI'm getting to the saturday thing14:30
nigelbI lost power before I saw her reply14:30
persiaheh.  You're good at that, but you can't catch me this evening.14:30
nigelbpersia, busy evening?14:31
persiaI have a few things I want to get done for tomorrow.14:31
nigelbsure, daniel's around :)14:32
dholbacherrr :)14:32
dholbachI'll try, need to get a few other things out of the way first14:32
nigelbI'll work on it, you folks can review when you get the time :)14:32
dholbachsuper :)14:32
nigelbpersia, i'm so sorry I wasn't around for the class last night14:44
persiaHappens sometimes.  No worries.  Just reschedule it.14:46
nigelbyea, I have reschedule around some uncertain power situations.14:46
nigelbbtw, did you get time to take a look at the script?14:46
nigelbI have so many things to change in that...14:47
nigelbok, 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
persiaI thought the decision was that we didn't bother, and changed the process, since LP was cooler than previously thought.14:51
nigelbwhat irks me is since I can see the code, why not change it14:52
persiaExtra work for no extra value?14:53
nigelbI need to get a few changes in anyway14:53
nigelblike that pacakge bryce said we can ignore14:54
persiaEither way.14:54
nigelbso, the thing is... I want to know comments on this line15:06
nigelbAs 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
nigelbdoes the last bit stay or go?15:06
persiaI like it, but I tend to be over-verbose when concision would be more effective.15:08
nigelbum.. the last bit of first line :D15:09
nigelbmotu-sru is kinda gone right?15:09
nigelbalso is ubuntu-ma-sponsors?15:10
nigelbso, can I have the script ignore redudant teams?15:12
persianigelb: 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
persiaWorkflow there is probably: subscribe the right team, remove the patch tag.15:59
nigelbpersia, ouch15: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
persiaouch?15:59
nigelbbut we could probably have another script based on this one to subscribe new teams for the old bugs?16:00
persiaI 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:01
dholbachhttp://people.canonical.com/~dholbach/resubscribe maybe?16:02
persiaThat'd be it :)16:02
nigelbwell, if that works, then I can remove the old teams?16:02
nigelbdholbach, or you can have that run with this script too :)16:03
persiaI'd check with the team owners.  I'd be pleased if ubuntu-universe-sponsors was automatically unsubscribed when ubuntu-sponsors was subscribed.16:03
persiaI can't say for other teams.16:03
nigelbI thought dholbach 's script did that?16:03
dholbachif ubuntu-{universe,main}-sponsors are subscribed to an open bug, they'll be unsubscribed and ubuntu-sponsors will be subscribed instead16:05
persiaRight, but the trick is to check with other potentially obsolete team owners before doing the same thing to those teams.16:06
dholbachoh sure, it's just for that use-case16:06
nigelbpersia, ah.  that way, so talk to other obsolete team owners and get their teams to work the same way, gotcha :)16:06
persiaBut 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:06
persianigelb: You probably want to get the other team owners to run the script themselves every once in the while.16:07
persiadholbach: IN case I haven't said so recently: thanks for including u-u-s in your script :)16:07
nigelbpersia, I'll add that to my things to do :D16:08
dholbachpersia: it was since the beginning - it just wasn't executed because of a bug :)16:09
persiadholbach: Still, I appreciate you running it so I needn't :)16:10
nigelbI've pushed my changes, so take a look16:11
dholbachno worries :-)16:11
nigelbhttp://bazaar.launchpad.net/~nigelbabu/ubuntu-qa-tools/patch-review-script/annotate/head%3A/launchpadlib-scripts/patch-subscriber.py16:12
persianigelb: You might also want to add linux-ti-omap to the subscribe-JFo set.16:16
nigelbaha, getting done.. minute16:16
* persia hopes we have a good plan for kernel reduction for one of the next cycles: too many trees is too confusing16:17
* nigelb refuses to go into kernel, even though tempting16:18
persiaNo, 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:20
nigelbthe temptation to fix broken stuff is highly tempting16:21
nigelbwonder how core-devs manage to control the impulse :D16:21
nigelbok, so added and new revision16:21
nigelbhttp://bazaar.launchpad.net/~nigelbabu/ubuntu-qa-tools/patch-review-script/annotate/head%3A/launchpadlib-scripts/patch-subscriber.py16:21
nigelbdholbach, ok, I need some idea of what kind of examples you're looking for...16:27
nigelblike add a test scenario to each case?16:27
dholbachnigelb: 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
dholbachif you've never done it it will be hard to figure out for you what you need to do16:31
nigelbdholbach, um, those statuses are sort of dynamic16:31
nigelbso by the time someone actually looks into it patch-needswork will be patch-forwarded-upstream or patch-accepted-upstream16:31
dholbachyes16:31
dholbachI thought that a bug which tells a story of "here's what happened" might be helpful in teaching that16:32
nigelbah, I'll look for those16:32
dholbachI'll have a look over it tomorrow16:33
nigelbso, I'll add specific examples below the current ones16:33
nigelbi.e. the current rule-stlyle ;)16:33
nigelbdholbach, I'll nag persia to look at it today :D16:33
dholbachawesome16:33
* dholbach has to head out and tend to a few other things16:33
dholbachso have a great rest of your day16:33
dholbachand see you soon again! :)16:34
nigelblater dholbach :)16:34
dholbachrock on16:34
nigelbpersia, how long more will you be up?16:36
persialonger than you.16:36
nigelbcan talk to brian about my edits?  I'm dead on sleep already.16:37
nigelbjames_w, can you sign up for a few hours of review leading? https://wiki.ubuntu.com/PatchDay16:37
james_wnot right now16:37
nigelbwell 1 hour is fine too :)16:37
james_wI'll look closer to the time16:38
nigelbsure, thank you :)16:38
persianigelb: Sure.16:38
nigelbpersia, thank you :)16:38
* nigelb is off. rest of wiki edits in the morning16:38
=== yofel_ is now known as yofel

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