[09:09] <jcastro> klattimer: ok see if you can assign the ibus bug to "canonical desktop team"
[09:09] <jcastro> it should
[09:09] <oLoyoli> My date-time indicator says it's Saturday still...
[09:10] <klattimer> I'm assuming that it would be a really obvious link
[09:11] <klattimer> I can't see it at all :/
[09:11] <jcastro> klattimer: there should be a yellow ! next to your name  in the assignee column
[09:11] <jcastro> at the top of the bug
[09:12] <klattimer> yeah
[09:12] <klattimer> I see that
[09:12] <klattimer> ... not so obvious
[09:12] <jcastro> welcome to launchpad!
[09:13] <klattimer> it says, select a team of which you're a member of
[09:13] <klattimer> with a search box
[09:13] <jcastro> "canonical desktop team" in there
[09:13] <klattimer> if I search canonical desktop team, nothing comes up
[09:13] <jcastro> sigh, same problem I have
[09:13] <klattimer> :(
[09:13] <jcastro> ok fixed
[09:14] <jcastro> so basically after you do each one this is to say "ok ken your turn to put it in the distro"
[09:14] <klattimer> k
[09:15] <jcastro> ok while those are out of the way, the dx team is having a call right now and will find what bugs to give you
[09:15] <jcastro> klattimer: are you familiar with how merges and merge proposals work in launchpad?
[09:16] <klattimer> nope
[09:16] <jcastro> ok
[09:16] <jcastro> https://help.launchpad.net/Code/Review
[09:20] <jcastro> klattimer: you can snag the code like so
[09:20] <jcastro> bzr branch lp:notify-osd
[09:20] <jcastro> and just familiarize yourself with it while I hunt down some workflow docs for you
[09:21] <klattimer> k
[09:21] <klattimer> well I've used bzr a few times
[09:21] <klattimer> so that's all good
[09:21] <klattimer> merge requests not sure of so familiarising myself
[09:22] <jcastro> https://help.launchpad.net/Code
[09:22] <jcastro> that's the start
[09:22] <jcastro> it will be easier to do it that way because the dx team works all in launchpad, so they'll be able to review your changes and commit directory to the upstream project
[09:28] <jcastro> klattimer: examples: https://code.edge.launchpad.net/notify-osd
[09:37] <jcastro> klattimer: unless assigned otherwise here's the buglist https://bugs.edge.launchpad.net/notify-osd/+bugs
[09:37] <jcastro> hi njpatel
[09:37] <njpatel> jcastro, hey dude
[09:38] <jcastro> njpatel: klattimer is reading up on bzr, lp, and notify-osd
[09:38] <jcastro> he's basically here to polish it off
[09:38] <njpatel> ah nice, hey klattimer
[09:38] <jcastro> njpatel: but he needs bugs assigned to him
[09:39] <njpatel> Right, I think davidbarth  mentioned it this morning
[09:39] <jcastro> njpatel: also I'm asking him to read up on merge proposals, etc.
[09:39] <jcastro> if he's going to be doing all this dx work then he might as well do it the way you guys do it
[09:39] <njpatel> jcastro, awesome
[09:39] <njpatel> What, badly? ;)
[09:40] <jcastro> heh
[09:41] <njpatel> Cool, I'm awaiting a call from david to do some triaging anyway, so I'll make sure to do go through the notify-osd ones too
[09:41] <MacSlow> jcastro, regarding n-osd... you can point klattimer towards me, should any technical questions arise
[09:41] <klattimer> hey ho MacSlow
[09:41] <klattimer> :)
[09:41] <MacSlow> klattimer, small is the world :)
[09:41] <jcastro> also, mpt pointed to this: https://wiki.ubuntu.com/NotifyOSD#duration
[09:42] <jcastro> and these: https://wiki.ubuntu.com/NotifyOSD#position
[09:42] <jcastro> do you guys know if there are bugs open for these features?
[09:42] <jcastro> and can we confirm which parts of those are implemented?
[09:42] <MacSlow> jcastro, yup... but I don't know htem by heart (by number) :)
[09:42] <jcastro> MacSlow: as long as you know how to assign them to him. :D
[09:42] <MacSlow> jcastro, :)
[09:44] <MacSlow> klattimer, jcastro: https://wiki.ubuntu.com/NotifyOSD#position regarding that position... this gconf-key selecting the position-option is not implemented
[09:45] <MacSlow> klattimer, jcastro: https://wiki.ubuntu.com/NotifyOSD#duration is very tricky/involved... to get it all done
[09:46] <jcastro> is the position gconf key as important as the duration ones?
[09:46] <MacSlow> jcastro, I'd say (and I think mpt would so too) that timing is more important
[09:47] <MacSlow> jcastro, klattimer: but that I'd check with mpt first before proceeding... just to be sure
[09:47] <MacSlow> jcastro, klattimer: the whole gconf-position option is certainly easier to implement
[09:49] <jcastro> yeah but it's not really user visible
[09:49]  * jcastro thinks that gconfable options are probably not a good use of resources
[09:53] <MacSlow> jcastro, the general problem with gconf-options is getting an equal amount of testing for each code-path behind each option and get any potential side-effects covered testing-wise
[09:53] <MacSlow> hm... does the above sentence make sense to you? :)
[09:53] <jcastro> it does
[09:53] <jcastro> which is why I think bugfixing and duration makes more sense
[09:54] <MacSlow> that's my view too
[09:59] <klattimer> until there's a UI to configure notifications, adding gconf keys ends up being in the hands of the distribution... of which I'm only aware of one shipping notify-osd for notifications (unless something's changed) so unless ubuntu is going to vary between spins then there really is little point doing a gconf key for position
[10:05] <davidbarth> klattimer: hi, yeah; i'm doing tons of bug reshuffling and milestoning right now
[10:06] <klattimer> davidbarth: cool
[10:06] <davidbarth> klattimer: there are couple of mem leaks in n-osd first, then some patches waiting to be reviewed and integrated, and then some multi-monitor issues (if not fixed by the former) to merge in
[10:07] <davidbarth> klattimer: and when you get bored, a request to try and improve the test suite to support unattended tests
[10:07] <klattimer> k
[10:07] <davidbarth> we have some xvfb-based framework in dbusmenu, and i'd love to see if you have ideas to use that i n-osd as well
[10:08] <davidbarth> klattimer: once i've assigned the bugs, can you take a look and give me some estimates
[10:08] <klattimer> k
[10:08] <davidbarth> the goal being to do a fair but reasonable investment in doing the necessary cleanups
[10:09] <davidbarth> but not block you for too long on that, because there are other app. indicators bugs that should be fixable once the design is refined (keyboard in particular)
[10:12] <jcastro> davidbarth: he's just finished ibus, do you have any opther app indicator bugs in mind?
[10:19] <sense> jcastro: I've asked before, but hplip works now?
[10:19] <sense> If that has problems still he could take a look at that.
[10:21] <jcastro> sense: we decided that it's best to wait for upstream Qt to implement KSNI
[10:21] <sense> ok
[10:33] <davidbarth> jcastro: the keyboard one, but that'll require that some validation from mpt; i think we came up with a good approach last week, but i'd prefer him to finish commenting on that in the bug reports he's on
[11:43] <klattimer> davidbarth: any word on those bugs?
[11:44] <klattimer> I'm going to head out to lunch in a bit and would like some new stuff to get my teeth into this afternoon
[13:21] <klattimer> mpt about?
[14:08] <davidbarth> klattimer: back on n-osd bugs, so can you look at all the high & medium prio bugs in https://bugs.launchpad.net/notify-osd/+bugs, except #428509 and give me a ballpark time estimate?
[14:08] <klattimer> I'll take a look through them
[14:08] <davidbarth> klattimer, jcastro: then i think it makes sense to invest ~2-3 days to start with
[14:08] <klattimer> k
[14:33] <klattimer> davidbarth: a rough guess would be something like 6 days for high + medium on there
[14:34] <klattimer> as long as I don't hit any major trouble along the way
[14:34] <klattimer> lets say probably 9 is a safe estimate
[14:37] <davidbarth> klattimer: ok, with automating testing being harder or easier than leaks?
[14:39] <klattimer> easier, there seems to be better pointers in total, but memory leaks are ok too
[14:39] <klattimer> pointers to resources I mean :)
[14:43] <bratsche> Morning.
[14:44] <klattimer> afternoon
[15:58] <bratsche> jcastro around?
[15:59] <jcastro> bratsche: yep
[16:00] <bratsche> jcastro: Oh hey dude.. was wondering if you have any priority bugs in the queue that ayan could work on?
[16:00] <jcastro> ayan?
[16:01] <bratsche> He's finished up the bugs assigned to him and was wondering if I know of anything else he can hack on that's desktop related.
[16:01] <jcastro> give me a minute
[16:01] <jcastro> any specific area?
[16:02] <jcastro> or just ayatana bugs in area
[16:02] <bratsche> jcastro: I figure just any ayatana bugs that you've been watching.  If not it's no big deal, I just didn't have any specific bugs I could think of so I figured I'd ask you.
[16:02] <jcastro> on the phone, give me 2 minutes.
[16:03] <bratsche> Sure, no worries.
[16:06] <jcastro> bratsche: any of these would be great: https://wiki.ubuntu.com/NotificationAreaTransition/CompatibilityFixes
[16:07] <bratsche> ayan ^
[16:08] <jcastro> that's like a ton of stuff in the archive
[16:08] <jcastro> so best thing to do is do a cost/benefit analysis of how popular something might be
[16:08] <jcastro> ie. start porting apps that are most used.
[16:09] <jcastro> you'll need to cross reference http://popcon.ubuntu.com/ ftw
[16:10] <jcastro> the bugs themselves are tagged with "trayaway" in lp: https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=trayaway
[16:10] <jcastro> (or should be tagged with that)
[16:14] <jcastro> also, any papercut: https://edge.launchpad.net/hundredpapercuts/maverick
[16:14] <jcastro> ayan: is that enough? ;)
[16:15] <jcastro> vish: feel free to jump in here, heh
[16:15] <vish> yay!
[16:17] <jcastro> sense: you too!
[16:24] <vish> ayan: what happened to  Bug #8949 ? any luck with that one?
[16:25] <sense> jcastro: Most certainly not right now! :P
[19:34] <kelelsai> hi, I'm new here. I missed the section or documentation that says where to get the code from to Fix bugs. Does anyone here know the link that references how to do so?
[19:37] <vish> kelelsai: https://wiki.ubuntu.com/Bugs/HowToFix  ?
[19:39] <kelelsai> thanks
[20:29] <htorque> hi, can anyone familiar with the unity design tell me, where that dark line at the bottom of the panel comes from?
[20:29] <htorque> http://img.xrmb2.net/images/792578.png