[00:32] <jono> nigelb, ping?
[00:52] <persia> Might be a bit early yet (5:00 local time there)
[03:19] <nigelb> jono: pong
[03:24] <jono> hey nigelb
[03:25] <nigelb> hello :)
[03:31] <nigelb> ugh, I hate bugs with 25 differnt tasks just because its the same problem but they all have different solutions :?
[03:31] <nigelb> :/
[04:12] <nigelb> hyperair: hey, got a min to review a patch for indicator thingy?
[04:13] <hyperair> nigelb: not at the moment. maybe this weekend.
[04:13] <hyperair> nigelb: what's it about anyway/
[04:13] <nigelb> hyperair: that big bug with lots of duplications and some 100 tasks about icons having a color aroudn them
[04:13] <hyperair> that's no indicator, that's notification area!
[04:13] <nigelb> oh, yeah, that one
[04:14] <nigelb> whatever, ayatana territory :D
[04:14] <hyperair> lol
[04:14] <hyperair> not really. ayatana is gearing towards purging the notification area
[04:14] <hyperair> nigelb: what app is the patch for anyway?
[04:14] <hyperair> nigelb: and does it work?
[04:15] <nigelb> I think it should be rejected, I wanted your thoughts ;)
[04:15] <nigelb> bug 403135
[04:15] <nigelb> best of luck reading the comments :D
[04:16] <persia> Actually, the "ugly colors around the icons in the notification area" class of bugs should be fixed in the individual applications.
[04:16] <persia> It's just adding appropriate alpha-channel hinting to the icons used for the notification area.  Most of these should be sent upstream.
[04:17] <persia> Trying to hack around it in the notification implementation is not ideal.
[04:17] <nigelb> yes, because each of them have a separate fix and not one magical fix for every application
[04:17] <nigelb> Most of the fixes are in individual apps. This patch is from upstream I think but I totally cannot figure out their repos
[04:18] <nigelb> So, I figured out a way for Project Cleansweep to make a worklist, finally
[04:19] <nigelb> On one hand, we have the usual subscription, adding a patch tag and subscribing us.
[04:20] <nigelb> So, we'd want the same script subscribing us to the same subset without adding a patch tag and without the date.
[04:20] <nigelb> Just run it once and all the subscribed bugs will be the ones we have to clear out
[04:21] <persia> I think that's risky, because lots of old bugs have the patch tag.
[04:21] <nigelb> Well, I'm getting to that ;)
[04:22] <nigelb> Let me get the query
[04:22] <nigelb> https://bugs.launchpad.net/ubuntu/+bugs?field.subscriber=ubuntu-reviewers&field.tag=-patch-needswork -patch-forwarded-upstream -patch-forwarded-debian -patch-accepted-upstream -patch-accepted-debian -patch-rejected-upstream -patch-rejected-debian -patch-rejected&field.tags_combinator=ALL
[04:22] <nigelb> That ^ should work
[04:22] <persia> That mixes new and old bugs.
[04:22] <nigelb> so all bugs that are not in buckets
[04:22] <persia> Which means that you don't have a nice line in the sand to target.
[04:23] <nigelb> Unfortunately, it was decided to draw a line in sand
[04:23] <hyperair> persia: actually banshee's notif-area upstream has the appropriate alpha-hinting, but for some reason it doesn't work in lucid.
[04:23] <nigelb> Instead, I'll be counting everything after a particular date.
[04:23] <nigelb> So, we know how many new came in
[04:23] <hyperair> persia: considering that the same code works perfectly in karmic for most of these apps, i'm thinking there's a regression happening in gtk+, or the theme engines
[04:23] <hyperair> persia: or even gnome-panel
[04:23] <persia> hyperair: Ah, yeah, that would be a regression.
[04:24] <hyperair> persia: and it's been happening over and over for years.
[04:24] <hyperair> persia: every time we have a new ubuntu release, this regression happens again, and gets fixed somewhere along the line.
[04:24] <hyperair> just that lucid was unfortunate enough to not get a fix
[04:25] <persia> nigelb: I think that's extra work for you, and not as visible to others, but if you like.  Were I doing it, I'd modify the script to add the "cleansweep" tag and not subscribe anyone, and tell cleansweepers to remove the cleansweep tag when they hit the bug./
[04:25] <hyperair> i don't know who or what fixes it, or even why it occurs.
[04:25] <hyperair> we have cleansweepers?
[04:25] <hyperair> and wasn't cleansweep a trademarked name by some windows product or something...
[04:26] <nigelb> persia: I thought of that first.  But that would generate a tremendous amoutn of mail.  At least 1500 bugs with a bunch of subscribers and dups, etc
[04:26] <xnox> hyperair, we are in totally different business =) unless that trademark is owned by Microsoft.....
[04:26] <nigelb> hyperair: Norton
[04:26] <hyperair> xnox: there we go. Norton.
[04:26] <xnox> =(
[04:26] <nigelb> well, this is not a product name
[04:26] <hyperair> shouldn't we change the name to avoid violating the trademark?
[04:26] <nigelb> Its a Project Name
[04:26] <hyperair> it isn't?
[04:27] <hyperair> it's the same isn't it, for trademarks?
[04:27] <hyperair> if i went and created a team called firefox, that had not relations to mozilla firefox, mozilla would scream.
[04:27] <nigelb> Oh grr
[04:28] <nigelb> lets think of that later
[04:28] <nigelb> Now, workflow
[04:28] <nigelb> persia: That line, i.e. the new bugs with patches can be measured using a script.
[04:29] <persia> Yes, but while it can be measured, it cannot easily be seen.
[04:29] <nigelb> I'll ask dholbach to make an image for us that changes every day like the meter
[04:29] <persia> So there's no way for anyone to know how close they are to target except by reading whatever posts you choose to make.
[04:30] <nigelb> Showing the stats is also on my worklist items.  I'm still the processing of figuring out how
[04:30] <nigelb> *in the process of
[04:31] <nigelb> dholbach made a meter image, I'm thinking of making multiple meters with different numbers, so all those should be satisifed and it can be displayed on some blog for the project, etc
[04:31] <nigelb> or everyone can display it
[08:39] <nigelb> Well, at least I figured out why colors changed.  My client restarted.
[13:44] <nigelb> persia: will you be around later in the night?
[13:45] <persia> My intention is to not be (I want to get up early), but I may well :)
[13:46] <nigelb> persia: I'd like you to be around when I talk to brian today, it would be nice if you were there or I'll just take the talk to mail.
[13:47] <persia> Hrm.  We've a awkwardness here.  I'm not sure if I'll be around at that point, so I can't usefully inform you if you can send mail or not, which forces you to not send mail, just in case, which then makes you unhappy (regardless of whether I'm around later).
[13:48] <persia> I'll suggest you just send mail, if you're likely to do that anyway, as this will be easier.  If you and I both happen to be around later, the discussion can be based on the mail.  If not, then the mail can stand alone.
[13:48] <nigelb> Ok.
[13:49] <persia> And I don't have to feel like I should stay up, and you don't have to wonder if I will :)
[13:50] <nigelb> I'll be staying for a very simple reason, I fell asleep in the afternoon and jumped up thinking its morning, so I doubt if I'll sleep at usual time.
[13:50] <persia> heh.  I know how that goes.
[13:50] <persia> At least for me, it happens that way more often this time of year because of the weather.
[13:51] <nigelb> Yeah, weather is awesome here too.  A little bit rainy, so kind of cool.  Very pleant to hear the rain and sleep :)
[17:17] <duanedesign> nigelb: was going to put start putting together some information for the Development FG. Are there any other links other thank what is in the topic that might be good?
[17:18] <duanedesign> than*
[17:49] <nigelb> duanedesign: I'm working on updating the docs, so you can start linking up by next week
[17:56] <duanedesign> nigelb: that'll be perfect. Thank you
[17:56] <nigelb> :)
[17:57] <nigelb> duanedesign: also, think of the apport hook writing project which I'm starting to coordinate
[17:57] <nigelb> The idea is to get hooks for as many main applications as possible, especially the ones against which bugs are reported
[17:58] <nigelb> You must've seen mails in the bugsquad list
[17:58] <duanedesign> nigelb: i will! All that stufff would be perfect to get the development FG connected up better with the community.
[17:58] <nigelb> duanedesign: yep.  so now you have 2 activity which the community wants help.  If you guys want to take over the apport project I'd be happy with that too.
[18:01] <duanedesign> ill update the councils 'bug' on this and get feesback. Thank you
[18:02] <duanedesign> feedback*
[18:02] <nigelb> ok :)
[19:47] <nigelb> BlackZ: if you see a new bug with a patch attached, you need not tag it patch and subscribe reviewers.  It will be done automatically
[19:52] <nigelb> and if its not, let me know.  we'll have to look at what happened there
[19:52] <BlackZ> OK nigelb