[02:34] <nigelb> maco, yeah, compiz.  I'll take care of it :)
[15:44] <nhandler> vish: I doubt ! o p s would work in here anyway (reply is a bit late, sorry). It would most likely use the generic, non-channel-specific factoid. You can view a list of OPs with /msg chanserv access #ubuntu-reviews list
[15:46] <nigelb> for changing topic?
[15:47] <nhandler> nigelb: It was during that conversation that vish suggested using the factoid to find out who was an op here
[15:47] <nigelb> that's a very disturbing way to find out who's ops :D
[15:49] <nhandler> Yes it is. Especially when it won't work ;)
[15:51] <nigelb> it wont work?
[15:51]  * vish likes to frighten people ;p
[15:51]  * nigelb tries
[15:51] <nigelb> !ops
[15:51] <ubot3> Help! Channel emergency! (ONLY use this trigger in emergencies) -  elky, Madpilot, tritium, Nalioth, tonyyarusso, PriceChild, Amaranth, jrib, Myrtti, mneptok, Pici, jpds, gnomefreak, bazhang, jussi01, Flannel or ikonia!
[15:51] <nigelb> ouch
[15:52] <nigelb> okay, it doesn't work the way its supposed to work
[15:52]  * jussi01 smacks nigelb on the hand
[15:52] <nigelb> sorry jussi01
[15:52] <nhandler> Yes it did nigelb
[15:52] <vish> nhandler: off topic question alert.. evilnhandler is also your id?
[15:52] <nhandler> vish: Yes
[15:52] <vish> ;)
[15:52] <nigelb> vish, thats his bot to pad the number of members here
[15:52] <nigelb> :D
[15:53] <nhandler> nigelb: Nope. Just another client I keep connected
[15:53] <nigelb> nhandler, j/k
[15:53] <jussi01> vish: most freenode staff have an "evil$nick"
[15:53] <vish> jussi01: oh , they do.. interesting..
[15:54] <nigelb> vish, jussi01 won't need one I guess.... since he's Evil by Default (tm)
[15:54]  * jussi01 has an eviljussi01... a remnant from the days of being on staff...
[15:54] <jussi01> nigelb: ssshhh
[15:54] <vish> well, they are all evil ;p
[15:54] <jussi01> vish: including you...
[15:54] <jussi01> :P
[15:54] <nigelb> jussi01, o_0 you were on staff?
[15:55] <jussi01> for a short time, yes. Moving on.
[15:55] <nigelb> haha
[17:56] <nigelb> nhandler, you'll be around?
[17:58] <nhandler> Yes
[17:58] <nigelb> I'm drafting a mail to -devel about patch day
[17:58] <nigelb> would appreciate a review once done :)
[17:58] <nhandler> Sure
[17:59] <nigelb> there are really not many people working on reducing the review queue
[18:04] <nigelb> vish, hows the icon work going?
[18:08] <nigelb> nhandler, http://etherpad.com/vcw73H8SoA
[18:08] <nigelb> anyone else would like to help review the mail to -devel please see ^
[18:09] <nhandler> nigelb: Can you poke me when you are done? I'll look at it then
[18:09] <nigelb> nhandler, I'm not getting much of ideas
[18:10] <vish> nigelb: next week
[18:10] <nigelb> vish, great.  thanks :)
[18:10] <vish> np.. ')
[18:11] <vish> ;)
[18:18] <nigelb> nhandler, take a look now.  I've put in what I can
[18:22] <nhandler> nigelb: I made a few changes
[18:22] <nigelb> nhandler, I noticed :)
[18:22]  * nhandler goes to watch a movie
[18:22] <nigelb> I think now we need to sign up as contacts
[18:22] <nigelb> (to set an example)
[20:25] <mpontillo> nigelb: [gotta run out but quick comment/question] - how is "critical enough" defined? does it vary based on risk / where we are in the development cycle?
[20:25] <nigelb> mpontillo, for example a bug that crashes X every 10 minutes would be critical but corrects the spelling in package description would not be
[20:26] <nigelb> and yes, it varies based on where we are in the cycle and what the patch does
[20:26] <nigelb> you ask in -motu or -devel as appropriate about the critical-ness of the patch
[21:10] <cjohnston> nigelb: ping
[21:10] <nigelb> yes?
[21:10] <cjohnston> :-P
[21:10] <nigelb> oh...makin a point :D
[21:14] <bdrung> mpontillo: and it depends on how many people are affected.