[12:14]  * MacSlow -> lunch
[13:55] <MacSlow> SiDi, just trying to get my record straight... you're Steve Dodier aren't you?
[13:56] <MacSlow> SiDi, the same person behind -> http://www.youtube.com/user/SiDi35 ?!
[14:13] <SiDi> MacSlow: i am ;)
[14:13] <SiDi> its me too
[14:13] <SiDi> sidi was taken :D
[14:14] <MacSlow> SiDi, ok... it always hard trying to keep up with IRC-nicks and peoples real names if they are not you colleagues
[14:14] <SiDi> indeed
[14:15] <SiDi> especially when you're on 10 channels all with their own people inside :)
[14:15] <SiDi> oh btw MacSlow i think i heard of chances in the way sync notifications are used, do you mind explaining me what changes please ?
[14:19] <MacSlow> SiDi, atm not sure what you are refereing to there... got an URL with some comment on the issue?
[14:19] <SiDi> i mean, you said on an ML (not sure which) that there would be changes in g-s-d and g-p-m regarding the notifications
[14:19] <SiDi> if i understood well, MacSlow 
[18:40] <macvr> SiDi: changes have been made to the notify-osd guidelines, but i'm not sure if those were the ones you were looking for
[18:45] <SiDi> macvr: do you know which changes ?
[18:46] <SiDi> i wanna make sure it wont break xfce4-volumed which uses volume synchronous notifications
[18:47] <macvr> SiDi: mostly size specs >http://wiki.ubuntu.com/NotifyOSD?action=diff&rev1=154&rev2=155
[19:09] <djsiegel1> bratsche: do you think this could be treated as a paper cut? https://bugs.edge.launchpad.net/hundredpapercuts/+bug/389929
[19:10] <bratsche> What kind of popup menu is this talking about?  I tried a right-click menu in Firefox and I can't reproduce it.
[19:14] <djsiegel1> bratsche: a gtk choice dropdown thing
[19:14] <djsiegel1> I forget what it's called
[19:15] <bratsche> djsiegel1: If I'm reading this correctly, it kind of seems like a bad idea.  I mean, a popup is just a menu and you can already define accelerator keys on menus.
[19:16] <bratsche> So if you're typing to access a menu by the first character of the menuitem.. you've already got a potential conflict between that first character and the accelerator.
[19:17] <bratsche> Or maybe it's a combobox widget.. it's hard to tell what he means.
[19:17] <bratsche> I think that's what he means.
[19:19] <djsiegel1> yes
[19:19] <djsiegel1> combobox, bratsche
[19:19] <djsiegel1> that's it
[19:19] <bratsche> Yeah, I think that would be a cool thing to do.  I think people have talked about this before, not sure if there are any patches floating around yet.
[19:23] <bratsche> I won't have any time to work on it this week as I'm starting on a UNR project with Neil, but if it's not urgent then I could look into it later in next week if you want.
[19:34] <bratsche> djsiegel1: I linked to http://bugzilla.gnome.org/show_bug.cgi?id=310931
[19:35] <djsiegel1> bratsche: thanks, will check now
[19:50] <mrooney> djsiegel1: wow, two aggressive papercuts :) the replace dialog and unable to unmount issue
[19:58] <djsiegel1> mrooney: yeah
[19:58] <djsiegel1> mrooney: the replace dialog has a great patch available, so all it might need is a push
[19:58] <djsiegel1> mrooney: and the unable to unmount issue might not be solvable, but we can at least make it more friendly for novice users
[20:05] <magcius> The unable to unmount would be an excellent papercut to solve.
[20:05] <magcius> I think using DeviceKit and PolicyKit can solve this.
[20:06] <magcius> If you want to make an aggressive change like that.
[20:09] <djsiegel1> magcius: well, that wouldn't be a paper cut solution
[20:09] <djsiegel1> sounds like a lot of work
[20:09] <ScottK> Much of which is already planned for Karmic.
[20:09] <ScottK> The question would be what's the additional work required.
[20:10] <mrooney> djsiegel1: did you see my comment about the replace dialog? I wasn't sure if you needed help (I could get out a PPA) or if someone at Canonical was working on that
[20:10] <djsiegel1> mrooney: always assume that I need help, please :)
[20:11] <djsiegel1> ScottK: oh, cool
[20:11] <djsiegel1> ScottK: can you add anything to the bug report to that effect?
[20:11] <ScottK> djsiegel1: You might discuss it with pitti as IIRC he's doing some of that work.
[20:11] <djsiegel1> ok, thank you
[20:11] <ScottK> djsiegel1: I don't know enough of the details to say anything meaningful.
[20:11] <mrooney> alright I'll try to get out a nautilus 2.27 PPA with that patch, for jaunty within the next day or two
[20:12] <djsiegel1> cool, mrooney
[20:12] <djsiegel1> https://edge.launchpad.net/hundredpapercuts/trunk -- we have 50 now
[20:12] <djsiegel1> I am going to blog and email and tweet on Friday, hopefully we can get people looking at them
[20:12] <djsiegel1> I need to become a nautilus hacker
[20:13] <djsiegel1> so many of these are in nautilus
[20:13] <ScottK> Your time is probably better spent trying to attract nautilus hackers.
[20:13] <djsiegel1> ScottK: but it would be so much easier if I could just fix these myself...
[20:13] <djsiegel1> :)
[20:15] <djsiegel1> ScottK: do you have any suggestions for attracting nautilus hackers? I wonder how many people are knowledgeable enough about the codebase to fix these.
[20:15] <djsiegel1> 10 people? 100? 2?
[20:16] <djsiegel1> The last thing I want is all of these bugs bombarding a handful of people upstream, who get overwhelmed and ignore them.
[20:16] <djsiegel1> Many of them are 20, 30 line fixes that have been sitting around for 5+ years
[20:16] <djsiegel1> because upstream is just backlogged
[20:16]  * ScottK is a KDE guy.  No idea.
[20:21] <mrooney> if there are upstream patches the best thing is probably an email to the list or pinging in IRC, if there hasn't been any feedback on the tracker
[20:23] <magcius> Most developers track the mailing list but not IRC.
[20:23] <magcius> Just my personal experience.