[01:50]  * mrooney gives everyone a wave-a-rooney
[10:07] <eeejay> hi
[10:07] <eeejay> what does this channel do?
[10:08] <njpatel> eeejay: this is the main channel for dx now, not #dx
[10:09] <njpatel> we're trying to get people here, but can't change the topic in #dx :)
[10:09] <eeejay> njpatel: ah cool, so all the directx and opendx hackers are hanging out here?
[10:09] <eeejay> ;)
[10:09] <njpatel> hehe :)
[12:22] <jens-25621> I wrote some feedback for you at: https://answers.launchpad.net/indicator-applet/+question/66834
[12:27] <james_w> jens-25621: hi, there is a /Comments page on the wiki that you could leave your feedback on
[12:27] <james_w> I'm not sure which they would prefer
[12:28] <jens-25621> I could't do that, because I don't have the right to change the page
[12:28] <james_w> the /Comments page?
[12:28] <jens-25621> mm
[13:06]  * MacSlow -> lunch
[15:32]  * popey pats mpt 
[15:32] <mpt> woof
[15:33]  * popey wonders if mpt is bored of "that" bug report yet :)
[15:34] <mpt> popey, oh, you could tell? :-)
[15:34] <tedg> jcastro: Sorry, I was on a call.
[15:35] <tedg> jcastro: I'm just saying that people aren't in the mood to commit to more this week :)
[15:35] <jcastro> tedg: oh no worries
[15:35] <jcastro> I'll just keep bugging you until you capitulate
[15:36] <tedg> jcastro: I should probably talk about indicating in applications.... not sure exactly if I can do that for a full hour, but I can try :)
[15:36] <jcastro> tedg: this is openweek so it'd be more user-targetted stuff, like how to use things
[15:37] <jcastro> save the "how to use libindicate" for developerweek please!
[15:37] <kenvandine_wk> tedg: we will find a way to indicate to you  if you become boring
[15:37] <tedg> jcastro: Hmm, okay.  Users... are those the people who comment on bug reports? ;)
[15:37] <jcastro> I know it's hard for you ted
[15:37] <popey> tedg: http://meow.popey.com 
[15:39] <tedg> I am trying to think of something that would be interesting to users though.  The difficult parts of the messaging indicator are all non-user issues.
[15:39] <tedg> popey: I have no clue why you sent me a picture of a cat, but it's a cute one :)
[15:42] <kenvandine_wk> tedg: well... i think an introduction to the messaging indicator for the users would be great
[15:42] <kenvandine_wk> although, i would be happy to do that too
[15:42] <kenvandine_wk> seems there are lots of folks that still don't get it 
[15:42] <kenvandine_wk> and i do love talking about it :)
[15:43] <kenvandine_wk> tedg: so if you don't want to talk about how users use the MI... and how it affects them... i can do that... but of course you get dibs 
[15:44] <tedg> kenvandine_wk: Sure, you should talk about it.  I think that'd be cool.  And the session will probably be sometime reasonable US time so I can be there :)
[15:44] <kenvandine_wk> ok
[15:44] <tedg> jcastro: Is someone going to talk about software updates and the changes there?
[15:44] <tedg> I can volunteer to take the slings and arrows there if need be.
[15:45] <kenvandine_wk> jcastro: ok, i signed up :)
[15:46] <jcastro> tedg: that sounds great!
[15:47] <tedg> mpt: Do you want to talk about the update-manager changes in Open Week?
[15:47] <mpt> What's Open Week?
[15:48] <tedg> mpt: Hour long slots to talk about various user facing issues.
[15:48] <tedg> mpt: https://wiki.ubuntu.com/UbuntuOpenWeek/Prep
[15:50] <mpt> hm
[15:50] <mpt> Neither that page nor the main UbuntuOpenWeek page seem to mention who the target audience is
[15:51] <kenvandine_wk> jcastro: you should define the audience on the wiki page
[15:52] <mpt> jcastro, perhaps explain a bit more what the purpose is, e.g. is it to excite users (or at least the sort of users who use IRC), or attract new Ubuntu contributors, or what
[15:53] <jcastro> mpt: I was just getting to that
[15:53] <jcastro> that was missing on the boilerplate
[15:54] <jcastro> that's usually on the announcement
[15:55] <mpt> ok
[15:56] <jcastro> kenvandine_wk: feel free to claim a time slot in the grid
[15:57]  * mpt reads jcastro's e-mail announcement :-)
[15:58] <mpt> tedg, after reading that, I don't think talking about the software update changes would be relevant to attracting new contributors
[15:58] <tedg> mpt: Okay, don't read that then ;)
[15:59] <tedg> mpt: I think that it is a user face issue, and one that would probably benefit from being discussed in a "lecture type" format because we could go through it all, where as everyone has looked at minute pieces otherwise.
[15:59] <tedg> user facing that is.
[16:32]  * mpt puts another 10 minutes of his life into bug 332945
[16:47] <popey> :(
[16:47] <kenvandine_wk> bratsche: do you have a version of your bluez-gnome patch for gnome-bluetooth?
[16:47] <kenvandine_wk> upstream requested it... so i guess that means they will accept this patch :)
[16:48] <bratsche> No, but I'd be glad to make one after the release.
[16:48] <kenvandine_wk> great
[16:48] <kenvandine_wk> please do... it would probably be rather trivial now since it was just forked
[16:49] <kenvandine_wk> then upstream has to maintain it :)
[16:49] <bratsche> Yeah, true.
[16:49] <bratsche> :)
[16:50] <bratsche> Is there a bug open for it upstream yet?
[16:53] <bratsche> If there is, just CC me on it or assign it to me or something.
[16:53] <bratsche> My bugzilla is bratsche@gnome.org
[16:55] <kenvandine_wk> bratsche: no bug... but an email
[16:56] <bratsche> Okay, I'll file it.
[16:57] <kenvandine_wk> right... gnome-bluetooth is in bz?
[16:57] <bratsche> I don't know yet. :)
[16:57] <bratsche> Do you still know the Ubuntu bug# for this?
[16:59] <bratsche> I think I found it..
[16:59] <bratsche> https://bugs.launchpad.net/ubuntu/+source/bluez-gnome/+bug/337219 right?
[17:03] <bratsche> http://bugzilla.gnome.org/show_bug.cgi?id=578396
[17:08] <kenvandine_wk> yeah
[17:08] <kenvandine_wk> thx
[17:09] <kenvandine_wk> bratsche: i will point the guy that requested it at that bug
[17:09] <kenvandine_wk> thx
[17:09] <kenvandine_wk> oh... he did that via launchpad :)
[17:39] <tedg> bratsche: How does the removing the escaping in pidgin-libnotify effect notification-daemon?
[17:40] <bratsche> tedg: I'm thinking it's probably a good idea, because then we can keep all this filtering shit in one place at least.
[17:48] <tedg> bratsche: So should I unmerge your patch?
[17:48] <bratsche> Do you have the bug# handy that it came from?  I forgot what it looks like now.
[17:49] <bratsche> Oh oh, the one that I just did?
[17:49] <bratsche> https://bugs.launchpad.net/ubuntu/+source/pidgin-libnotify/+bug/356147 ?
[17:49] <tedg> bratsche: Yes.
[17:51] <bratsche> tedg: But then after unmerging you want to remove all the markup escaping right?
[17:51] <bratsche> Oh wait.
[17:51] <bratsche> You said how would it affect notification-daemon
[17:52] <bratsche> I keep getting confused because that's such a generic name that I'm still thinking notify-osd
[17:52] <bratsche> tedg: So actually, we may need to keep that.  Perhaps we should ask mpt
[17:52] <tedg> bratsche: Yeah, I'm thinking that notification-daemon needs the escaping.
[17:52] <bratsche> Yeah I'm thinking so too.
[17:52] <tedg> So we can't remove it, or it'll break there.
[17:53] <tedg> So we have to handle it on the notify-osd side.
[20:51] <kenvandine_wk> eeejay: ping
[21:06] <bratsche> mpt around still?
[21:06] <bratsche> Err.. actually, nevermind.. not yet. :)
[21:18] <tedg> bratsche: So I should drop your non-escaping headers patch, right?
[21:18] <tedg> bratsche: In pidgin-libnotify
[21:19] <tedg> Sorry I keep asking, I just want to be sure - and I keep getting interrupted :)
[21:20] <maco> the  "Joe&apos;s phone is online" thing?
[21:20] <tedg> maco: Yes.
[21:21] <bratsche> tedg: No, I think you should keep it.  Because we want to keep escaping things to make pidgin-libnotify operate decently with notification-daemon, right?  And this patch basically makes it so it only escapes body text, and not summary text.. right?
[21:21] <maco> is it possible to escape based on which is in use?
[21:21] <tedg> bratsche: It makes it so that we don't escape the header.
[21:21] <bratsche> I didn't test g_markup_escape_text() exactly yet, but the Pango markup escaping is fucking up certain things.
[21:22] <bratsche> tedg: Right, we should not be escaping the header.
[21:22] <tedg> bratsche: If we don't, then what does notification-daemon do with it?
[21:22] <bratsche> tedg: mpt was very clear about this, that the spec specifically says that the header/summary text should be as-is.  So if applications are sending markup to the header, it's a bug in the application.
[21:23] <tedg> maco: It should be one standard... fixing one app means that all others are broken.  notify-osd needs to be a drop in replacement for notification-daemon.
[21:23] <tedg> bratsche: Ah, okay.
[21:23] <maco> good point
[21:24] <bratsche> tedg: Dude, the Pango markup stuff is so broken.  I've almost got a series of GRegex's to make this work.  This is killing me. :)
[21:24] <bratsche> I didn't test g_markup_escape_text() in particular, but I'm going to have to remove the Pango markup escaping from notify-osd.
[21:24] <tedg> bratsche: Heh -- so glad I didn't get assigned that bug ;)
[21:25] <tedg> The Pango markup is a little weird, I don't get why it's so different.
[21:25] <maco> well hey i wanted to ask about when you have 1 person with 2 accounts and the same alias grouped in pidgin, if they sign on and have a multi-protocol client too (so both accounts come online) it says something like "Joe is online is online" but since they're grouped, i think it ought to be treated as one thing
[21:25] <bratsche> tedg: It's not finished yet, but check out this hotness: http://launchpadlibrarian.net/25059106/356659-1.diff
[21:26] <tedg> maco: That makes sense.  We don't detect the grouped buddies at all though.  It'd be a relatively big change at this point in the release cycle.
[21:26] <tedg> bratsche: Heh.  Crazy.
[21:27] <bratsche> I've got one more to do next.
[21:27] <maco> something to mark down as a "would be nice for karmic"?
[21:27] <tedg> maco: Yes, a wishlist bug would be cool.
[21:27] <maco> kk
[21:28] <bratsche> tedg: For Karmic I'm thinking about trying to change Pango's markup parser to be more extensible.  I need to talk to behdad about that, but it's something I was thinking about trying to do for a gtk+ feature I want to do anyway.
[21:31]  * tedg thinks it was nice knowing the sane-bratsche
[21:32] <bratsche> I don't think it'll be that bad.
[21:32] <bratsche> The thing in gtk+ I was going to do was have GtkLabel support <a href> links.
[21:34] <bratsche> I already wrote extensible Pango attributes (so you could define a Link attribute that extends the Pango underline attribute, for example)
[21:34] <bratsche> Then to be able to extend the markup parser seems like it would be useful to go along with that.
[21:38] <tedg> Sounds good to me.  I'm not sure where I'd use it, but I'm sure I'll figure out something :)
[21:39] <bratsche> Well, I think it might have made this html filtering stuff easier for notify-osd.
[21:39] <bratsche> Maybe not though. :)
[23:26] <eeejay> bratsche: man, i am glad you took the html filtering :)
[23:57] <bratsche> heh