[05:43] <nigelbabu> eww, while we were not watching, review queue jumped from 50s to 60s to 293
[05:47] <hyperair> whoa
[05:47] <hyperair> that's large.
[05:47] <nigelbabu> well, compared to cleansweep project, no
[05:48] <nigelbabu> total number of patches awaiting review by ubuntu-reviewers is 1955
[05:49] <hyperair> ._.
[05:49] <hyperair> wha
[05:49] <nigelbabu> yeah
[05:49] <nigelbabu> 1955 patches to be reviewed in 6 months - possible/
[05:49] <nigelbabu> ?
[05:50] <hyperair> well, if we try very hard...
[05:50] <hyperair> i think...?
[05:50] <nigelbabu> I think if we can go 1 patch a day and gather lots of people to do that
[05:50] <nigelbabu> entirely possible
[05:50] <hyperair> once i get my new kernel and btrfs working, i'll start poking the review queue
[05:50] <hyperair> yaeh it's possible.
[05:50] <hyperair> but the queue will also grow.
[05:51] <nigelbabu> There has been really steady growth this month.
[05:51] <nigelbabu> I'll be keeping track of new patches coming in, so we can get the exact progress
[05:55] <nigelbabu> hyperair: oh joy! I'm PM-ing myself to keep track of things to do
[05:56] <hyperair> nigelbabu: lol!
[05:57] <hyperair> use tomboy notes =p
[05:57] <hyperair> or some todo list or other, say gtg, evolution's calendar, rainlendar, or sunbird/lightning
[05:57] <nigelbabu> and sync them? No thanks
[05:57] <nigelbabu> This is easier, whatever I have to do in the evening, PM my usual nick
[06:15] <ajmitch> nigelbabu: that's quite a few new patches
[06:15] <nigelbabu> ajmitch: we're having project clean sweep - to clean all the old patches against ubuntu
[06:16] <nigelbabu> so one patch a day and mobilize large number to do it
[06:16] <nigelbabu> before maverick release, we want the 1955 number to 0
[06:16] <ajmitch> good luck with that :)
[06:16] <nigelbabu> ajmitch: well, obviously, I want you to help out too
[06:16] <ajmitch> trying to check that old patches can be applied to newer versions can be tedious
[06:17] <nigelbabu> ajmitch: well, then patch-needswork and move on ;)
[06:17] <ajmitch> but that requires me to do work :P
[06:17] <nigelbabu> step 1 though is to make sure that the bug is reproducible
[06:18] <ajmitch> you may end up with a lot in patch-needswork, and noone willing to refresh the patch
[06:18] <ajmitch> if someone submitted a patch 3 years ago & we're only just getting to it, they probably won't be motivated to pick it up again
[06:19] <nigelbabu> yes, have to write a lot of standard replies for a lot of use cases
[07:04] <nigelbabu> ajmitch: I just saw a patch workflow which might help us
[07:04] <nigelbabu> want to take a look at it
[07:04] <nigelbabu> ?
[07:04] <nigelbabu> Its the workflow used by the drupal community for their patches.  I just saw it when I was opening a ticket there for some issues I was facing http://drupal.org/node/156119
[08:08] <dholbach> good morning
[08:20] <nigelbabu> dholbach: also, I'd like to show you http://drupal.org/node/156119
[08:20] <nigelbabu> this is what drupal community uses for their patch review thing
[08:21] <dholbach> looks a bit like what we'd have if we had proper patch statuses in Launchpad :)
[08:21] <dholbach> but at least we have it for code reviews
[08:21] <nigelbabu> yup ;)
[10:51] <nigelbabu> vish: can you modify my time from 16:30 to 15:30 UTC? 1530 = 2000 IST right?
[10:51] <nigelbabu> (I'm at work, can't play with wiki
[12:03] <nigelbabu> ddecator: poke
[13:16] <vish> nigelbabu: 15:30 = 21:00 IST
[13:17] <nigelbabu> vish: no, I want it to be 2000 to 0000 UTC
[13:17] <nigelbabu> err
[13:17] <nigelbabu> IST
[13:17] <vish> nigelbabu: IST - 5:30 UTC
[13:17] <vish> err , +
[13:18] <vish> +5:30
[13:18] <nigelbabu> nope
[13:18] <nigelbabu> on UTC, its +4:30
[13:18] <vish> hmm , oh well , IST = +5:30 GMT
[13:18] <vish> utc you can figure out ;p
[13:19] <nigelbabu> oh, I wish there was a desktop TZ converter
[13:20] <nigelbabu> @now
[13:21] <vish> nigelbabu: see , +5:30 ;p
[13:21] <nigelbabu> vish: agreed, but whole of uds, i calculated +430 and thats what worked
[13:21] <nigelbabu> ok, then I've calculated correct right?
[13:21] <nigelbabu> I mean on the wiki
[13:33] <vish> nigelbabu: nope , 16:30 - 20:30 UTC = 22:00 - 02:00 IST
[13:34] <nigelbabu> vish: ewww.. change that to 2000 to 0000 IST please?
[13:34] <vish> nigelbabu: k
[13:34] <dholbach> I always use: "date; date -u" to check :)
[13:35] <dholbach> nigelbabu: is there anything we should get done from the blueprints before the announce?
[13:35] <dholbach> nigelbabu: or just go and do it=?
[13:35] <dholbach> https://blueprints.edge.launchpad.net/ubuntu/+spec/community-m-patch-review-initiative
[13:35] <dholbach> https://blueprints.edge.launchpad.net/ubuntu/+spec/community-m-patch-review-process
[13:35] <dholbach> (probably rather the other way around :-))
[13:36] <nigelbabu> dholbach: publish the workflow perhaps? wiki.ubuntu.com/OperationCleansweep
[13:36] <dholbach> nigelbabu: publish in which way? what did you have in mind?
[13:36] <nigelbabu> well, there's nothing there, we have to write
[13:36] <nigelbabu> same as the workflow in reviewguide, except there won't be a patch tahg
[13:36] <nigelbabu> tag
[13:37] <nigelbabu> Also, need to work on standard replies for use cases that we hit
[13:40] <dholbach> nigelbabu: I included the graph on https://wiki.ubuntu.com/OperationCleansweep
[13:40] <dholbach> nigelbabu: I personally wouldn't copy the docs again
[13:40] <dholbach> either link to it very prominently or use Include()s
[13:40] <nigelbabu> dholbach: just linking up would be fine
[13:40] <dholbach> ok great
[13:40] <nigelbabu> dholbach: Also, can you make the image horizontal instead of vertical?
[13:41] <nigelbabu> A lot of people would be putting it on the side bar of their blog, its nicer if its horizontal
[13:44] <dholbach> nigelbabu: I'll have a look into it
[13:44] <nigelbabu> dholbach: nothing urgent.  Just came across it when I was looking into putting it on my blog
[13:54] <nigelbabu> dholbach: you can't merge into the ubuntu-review-overview trunk?
[13:54] <dholbach> nigelbabu: I prefer to use merge proposals
[13:54] <dholbach> I think there's a lot of worth others looking over my changes :)
[13:55] <nigelbabu> but you know python and launchpadlib better than me :)
[13:55] <vish> dholbach: nigelbabu : is there some way to make/review papercut patches faster?  could we ping here to get them through quicker?
[13:55] <vish> do note , those would be smaller/simpler patches
[13:55] <nigelbabu> vish: *glee* or your could do them youself
[13:55] <dholbach> still, if there's stuff in there where you go "what the hell? this doesn't make any sense! none of the variable names make sense", etc. then that's useful
[13:56] <nigelbabu> dholbach: haha
[13:56] <vish> nigelbabu: well , i dont know all the packages do i ;)
[13:56] <dholbach> vish: what do you mean by "get them through"?
[13:57] <vish> dholbach: getting the review done for those bugs faster
[13:57] <vish> clearing them out of review queue
[13:57] <dholbach> vish: so get them upstream and stuff?
[13:57] <vish> yup
[13:57] <dholbach> vish: then yes
[13:57] <vish> dholbach: cool , thanks :)
[13:57] <dholbach> I hope the reviewers team can help with that once we have a few more people on board
[13:58] <dholbach> and make cleansweep happen
[13:58] <nigelbabu> yeah, we need to work on getting the patches that we carry back to upstream and debian too
[13:58] <dholbach> first let's get cleansweep done :)
[13:59] <nigelbabu> well, first lets get it started!
[14:03] <dholbach> nigelbabu: proposed the merge
[14:03] <nigelbabu> dholbach: awesome, i'll look at it when I get home
[14:03] <nigelbabu> its raining like crazy today though, so it might be some time :/
[14:03] <dholbach> nice
[14:04] <dholbach> take it easy
[14:05] <dholbach> nigelbabu: https://wiki.ubuntu.com/OperationCleansweep
[14:06] <nigelbabu> dholbach: yay!
[14:06] <dholbach> glad you like it :)
[14:07] <nigelbabu> Also, I need to correct a lot of stuff on that wiki page.  I've but in a lot of blunders
[14:10] <nigelbabu> s/but/put
=== etali1 is now known as etali
[15:52] <ddecator> nigelb: ouch
=== yofel_ is now known as yofel