[00:14] <pace_t_zulu> dobey
[00:14] <pace_t_zulu> try turning off the "expand" property of your panel
[00:14] <pace_t_zulu> then "killall gnome-panel"
[00:14] <pace_t_zulu> then turn expand back on
[00:14] <pace_t_zulu> then "killall gnome-panel" again
[00:17] <pace_t_zulu> dobey: you there?
[02:31] <rickspencer3> robert_ancell: hi
[02:31] <robert_ancell> rickspencer3: hi rick
[02:46] <rickspencer3> kenvandine_wk: check it out
[02:46] <rickspencer3> robert_ancell is a bot
[02:46] <rickspencer3> try it, it's pretty good at the turing test
[02:47]  * robert_ancell is a bot.  The real Robert is at the beach
[02:48] <rickspencer3> robert_ancell: what are good turing test questions
[02:48]  * rickspencer3 gets meta on the bot
[02:48] <kenvandine> yo yo
[02:49] <kenvandine> http://dl.getdropbox.com/u/102212/f-spot-with-friends-mockup.png
[02:49] <rickspencer3> kenvandine_wk: in terms of blueprint for U1 photo sharing
[02:49] <rickspencer3> you might as well slap one together real quick
[02:49] <kenvandine> yeah... i think it would rock
[02:49] <kenvandine> and really help U1 shine
[02:49] <kenvandine> with some cool facebook integration
[02:49] <kenvandine> etc
[02:49] <rickspencer3> pitti and I will sort them out later, worse case is we don't accept it for UDS, but that doesn't mean it would stop your project
[02:50] <kenvandine> should i be creating wiki pages for each blueprint?
[02:50] <rickspencer3> kenvandine: so you're thinking FB friends for the contacts?
[02:50] <kenvandine> well... that and other u1 services
[02:50] <rickspencer3> or perhaps that could be plugable
[02:50] <kenvandine> yeah
[02:50] <kenvandine> any way we can get your friends
[02:51] <kenvandine> and LP can interface with them somehow
[02:51] <rickspencer3> like a list of checkboxes for different sets of contacts to share with
[02:51] <kenvandine> but in this mockup
[02:51] <kenvandine> if you had shared photos
[02:51] <kenvandine> i could just select you in the drop down
[02:51] <kenvandine> and i would see your photos that you shared
[02:51] <kenvandine> nicely integrated in the desktop :)
[02:51] <rickspencer3> and when a new picture was shared, it could rip a notification and use the indicator applet :P
[02:51] <kenvandine> sure
[02:51] <kenvandine> :)
[02:52] <kenvandine> and if you wanted to comment on someones photos
[02:52] <kenvandine> all the friends can see it... like on your wall
[02:52] <kenvandine> etc
[02:52] <kenvandine> like flickr meets f-spot meets u1 meets facebook
[02:52] <kenvandine> all on your desktop
[02:52] <kenvandine> and this could tie into the desktop content library idea
[02:53] <kenvandine> which has a blueprint
[02:53] <kenvandine> when are you and pitti reviewing the blueprints?
[02:53] <kenvandine> i wish there was U1 api docs... i have no idea how hard this would be
[02:55] <rickspencer3> kenvandine: there's a session planned for UDS on U1 integration
[02:55] <rickspencer3> so that might be a good time to discuss with them
[02:55] <kenvandine> i know
[02:55] <kenvandine> i think this is big enough for a separate discussion
[02:56] <rickspencer3> kenvandine - right
[02:56] <kenvandine>  i wish more people were working on u1 services already... but maybe that is me just being overly excited about cool stuff :)
[02:56] <rickspencer3> however, keep in mind that the desktop team will have *plenty* of work for Karmic
[02:56] <kenvandine> i know :)
[02:56] <rickspencer3> we're not really looking for more features to implement ;)
[02:56] <kenvandine> it would be quite a bit of work... i suspect
[02:57]  * robert_ancell can hear the crack of rickspencer3 s karmic whip already :)
[02:57] <kenvandine> but would really rock
[02:57] <kenvandine> imagine users never needing to backup their photos :)
[02:57] <rickspencer3> that
[02:57] <rickspencer3> s already supported with U1, right?
[02:57] <rickspencer3> just pop your photos in there
[02:57] <kenvandine> not really
[02:57] <kenvandine> yes
[02:57] <kenvandine> that part is
[02:57]  * rickspencer3 whip cracking noises
[02:57] <kenvandine> but not the metadata... like tags
[02:57] <kenvandine> etc
[02:58] <rickspencer3> hmm
[02:58] <kenvandine> and it requires you to put it in the right directories
[02:58] <kenvandine> etc
[02:58] <rickspencer3> are those your kids? cute
[02:58] <kenvandine> and of course doesn't do any of the social stuff :)
[02:58] <kenvandine> yup :)
[02:58] <kenvandine> thx
[02:58] <kenvandine> last weekend at the zoo :)
[02:58] <rickspencer3> those pants are going to be covered in grass stains and dirt in about 15 minutes, right?
[02:58] <kenvandine> yup
[02:59] <rickspencer3> heh
[02:59]  * kenvandine is still waiting for that mockup to sync to u1
[02:59] <rickspencer3> I'll be interested to see the blueprint, perhaps you could whip up some community energy around the project, or
[02:59] <kenvandine> maybe :)
[02:59] <rickspencer3> even interest the f-spot upstream devs to take a look
[03:00] <rickspencer3> alright, this is getting annoying ...
[03:00] <robert_ancell> You guys may like this.  My handy beta tester (my dad) was happy with the Jaunty upgrade because his built in wireless started working so he could chuck away his USB WiFi card.  He's had more stuff work every release
[03:00] <kenvandine> i'll try to get it done tonight... any minute my wife is going to hand the baby to me
[03:00] <rickspencer3> I can't figure out how to get evo to actually apply my filters
[03:00] <kenvandine> robert_ancell: awesome!
[03:00] <rickspencer3> after joining the U1 list thingy, I *need* my filters
[03:00] <kenvandine> ctrl-y
[03:01] <kenvandine> rickspencer3: in a week the bugs will be public... so you can be removed from the team :)
[03:01] <kenvandine> rickspencer3: it is nuts, sometimes there are hundreds an hour
[03:01] <kenvandine> i've been getting these mails since i started :)
[03:01] <rickspencer3> what does ctrl-y do?
[03:01] <kenvandine> runs filters
[03:01] <kenvandine> ctrl-a then ctrl-y
[03:02] <rickspencer3> yeah!
[03:02] <rickspencer3> I assumed they were automatically aplied ...
[03:02] <rickspencer3> like *every other email program ever*
[03:02] <kenvandine> well... i think they can be
[03:02] <kenvandine> but i hate that
[03:02] <kenvandine> i don't think it is the default
[03:02]  * calc notes that OOo 3.1.0~rc2 is now pending on a bunch of syncs
[03:02] <kenvandine> calc: long live gnome office
[03:02]  * kenvandine ducks
[03:02] <calc> kenvandine: heh :)
[03:03] <rickspencer3> calc: are you going to get that puppy ready for us before you start your OEM tour tomorrow?
[03:03] <rickspencer3> :)
[03:03] <calc> kenvandine: i'm hoping oracle creates the foundation later this year so we can fix the Sun braindamage
[03:03] <rickspencer3> get it into Karmic and don't look back :)
[03:03] <kenvandine> calc: that will take years... to convert that kind of braindamage
[03:03] <calc> rickspencer3: doesn't look like it will be done by then unfortunately unless someone wants to sync a bunch of packages for me
[03:03] <rickspencer3> robert_ancell: thaks for the note about your dad, btw, good to hear
[03:04] <rickspencer3> calc: you'll still have 20% time to work on it, I think
[03:04] <calc> kenvandine: they decided to essentially fork a bunch of java libraries which i now have to wait on a sync for :\
[03:04] <rickspencer3> 20% of 80 hours is 25 hours, so really, no problems
[03:04] <calc> ok
[03:04] <kenvandine> :/
[03:04] <kenvandine> hehe
[03:04] <calc> haha
[03:04] <kenvandine> rickspencer3: that isn't enough to maintain OOo
[03:04] <calc> ~ 80hr a week is around enough for OOo by itself yea ;-)
[03:05] <rickspencer3> kenvandine: ack, but I think for Karmic we might actually not want to do too much, let the dust settle with Sun purchase and such
[03:05]  * calc was putting close to that in for the past couple months anyway
[03:06] <calc> it has gotten much easier to get good quality packages by not trying to cram in the new OOo at the last minute though :)
[03:06] <calc> with intrepid and jaunty and we are now nearly caught up on bug triage for OOo :)
[03:07] <calc> it also lets novell do most of bug shake out for us with the new releases, heh :)
[03:07] <rickspencer3> calc: have there been any complaints from users about not having 3.1 in Jaunty?
[03:07] <calc> i think they try to line up their suse releases to be a few months after OOo release as well
[03:07] <rickspencer3> I wouldn't think so given that it's still in Rc
[03:08] <calc> rickspencer3: haven't heard anything yet... of course 3.1 still isn't even out yet, heh
[03:08] <calc> rc2 just came out this week
[03:08] <calc> they are planning i think to just throw whats there out as final next week... warts and all
[03:08] <rickspencer3> ug
[03:08] <calc> but there will be a 3.1.1 in a couple months that we will get in for karmic
[03:09] <rickspencer3> so we should probably get 3.1 into Karmic early, and hope we get good bug fixes from upstream while you are on your OEM tour
[03:09] <calc> generally .0 releases by OOo aren't very good, they are going to try to improve that this next cycle for 3.2
[03:09] <calc> yea
[03:10] <calc> i think i can probably handle the packaging aspect for 3.1 if some other people can help with the bug triage
[03:10] <calc> i doubt i can do both in 20% time, heh
[03:11] <rickspencer3> calc: right
[03:11] <calc> though it won't be as bad as this past cycle since i had lots of bugs to go through and verify and send upstream
[03:11] <rickspencer3> don't worry, we've got your back
[03:12] <calc> bug verification does take extra time for OOo since we have to have a good enough bug to reproduce it ourselves then test on Sun OOo, if it doesn't show up on Sun OOo then forward to Novell (if we know its not our fault), if seen in Sun OOo send to them, otherwise fix it ourselves
[03:13] <rickspencer3> calc: have you documented these practices?
[03:13] <calc> combined with the fact that most bug reports aren't very good quality initially it can take a while to triage bugs, :\
[03:14] <calc> rickspencer3: i think so, but i will check on the wiki and add/update as needed
[03:14] <rickspencer3> that would be helpful
[03:14] <calc> in the past i did ~ 95% of the triage so i did document it at one time but since few other people do it may be out of date
[03:15] <rickspencer3> calc: do we have to get 3.1.1 for Karmic?
[03:15] <rickspencer3> can't we just stick with 3.1.0, or will it be too buggy?
[03:16] <calc> 3.1.0 should be fine... but afaik 3.1.1 is expected before FF and is just a minor bugfix release
[03:16] <calc> the .1 releases are to fix bugs they didn't get around to for the .0 release (and newly found bugs as well)
[03:18] <calc> generally getting things working from a .0 to .1 release packaging wise isn't much trouble, getting the initial .0 working on Ubuntu can be a lot of work though
[03:18] <rickspencer3> kenvandine what about a U1 app that let's you share desktop wallpaper?
[03:18] <calc> i think i have 3.1.0 almost ready doing a test build at the moment, and need the packages synced for its build-deps
[03:18] <rickspencer3> calc: noted
[03:18] <kenvandine> that would be pretty simple i would think
[03:19] <rickspencer3> could the app that sets the desktop wallpaper be amended to look in a certain place and pick a random wall paper?
[03:25] <kenvandine> https://blueprints.launchpad.net/ubuntu/+spec/desktop-karmic-photo-ubuntuone
[03:25] <kenvandine> rickspencer3: yes it could
[03:25] <kenvandine> it could actually follow a rss feed (with some hacking)
[03:25] <rickspencer3> seems maybe simpler than the f-spot thing ;)
[03:25] <kenvandine> but not nearly as cool
[03:25]  * rickspencer3 is so subtle
[03:28] <kenvandine> ok... baby time.... later folks1
[03:29] <rickspencer3> 'night kenvandine
[03:29] <rickspencer3> good night all!
[03:29] <rickspencer3> see you tomorrow
[12:29] <maxb> How incredibly bizarre.
[12:29]  * maxb has found a 1-pixel wide line in xchat which appears to allow scrollwheel events to pass through and hit the desktop root window
[12:30] <maxb> the right edge of the channel list in treeview mode, ftr
[19:43] <calc> what was the default KDE in hardy, was it KDE 3.5 or 4.x?
[19:48] <james_w> 3
[19:55] <calc> james_w: thanks