[03:55] <rickspencer3> desktoppers - get your blueprints registered!!
[03:55] <rickspencer3> https://blueprints.edge.launchpad.net/ubuntu/?searchtext=desktop-maverick
[03:55] <rickspencer3> should be showing up on that list ^
[03:59] <TheMuso> Thats on my agenda for this afternoon.
[04:01]  * rickspencer3 whip cracking noises
[04:01] <rickspencer3> ;)
[05:22] <RAOF> robert_ancell: I see you've registered a colour-management spec.  I look forward to working that out - I was going to register one of those, too :)
[06:07] <robert_ancell> RAOF, please flesh it out :)
[07:37] <pitti> Good morning
[07:45] <RAOF> Good morning pitti
[07:46] <pitti> hey RAOF< how are you?
[07:46] <RAOF> Pretty good.
[07:47] <RAOF> I've got access to an espresso machine at my brother's flat.
[07:47] <RAOF> This is good :)
[07:50] <RAOF> Yourself?
[07:50] <RAOF> I hope that a huge plume of volcanic ash is providing magnificent sunsets/sunrises?
[07:51] <pitti> so they say, but I didn't actually watch it yesterday
[07:51] <pitti> too many houses around me
[07:51] <pitti> but perhaps this evening I should do a bicycle tour uphill, and watch it from there
[07:53] <pitti> in fact I was on the bike yesterday evening on the way to Taekwondo, but sundown was later on while I was in the gym already
[07:55] <RAOF> Sounds like a plan to me!
[07:56] <RAOF> Take a camera :)
[07:56] <pitti> absolutely
[07:56] <pitti> today it's cloudy, but forecasts look great from tomorrow on
[07:57] <TheMuso> I sincerely hope things calm down for UDS.
[08:05] <RAOF> Maybe there could be a huge plume on Tuesday evening so we can get a nice sunset, and then clear by Wed so that all the flights can be cleared by the time we need to go home? :)
[08:10] <TheMuso> Yes, but getting there in the first place.
[08:10] <RAOF> Well, that too.
[08:10] <RAOF> It looks like it should hopefully be ok to get there.
[08:12] <TheMuso> yeah
[08:18] <didrocks> good morning
[08:18] <RAOF> Morning, didrocks
[08:19] <didrocks> hey RAOF, how was your day?
[08:19]  * RAOF has just noticed that he mentally pronounces “didrocks” as “didierocks” for some reason :)
[08:19] <didrocks> (it's done on purposer didrocks == Didier Roche) ;)
[08:19] <RAOF> didrocks: It involved much intel driver madness, a nice lunch, and an espresso machine.  All in all, pretty good.
[08:19] <didrocks> espresso machine sounds good :)
[08:29] <seb128> hello there
[08:31] <didrocks> salut seb128
[08:31] <seb128> lut didrocks
[08:31] <seb128> en forme ?
[08:31] <seb128> bien dormis ?
[08:31] <pitti> bonjour seb128
[08:31] <seb128> hey pitti, how are you ?
[08:32] <pitti> bit tired (woke up too early), but fine; thanks! how are you?
[08:32] <seb128> I'm good thanks
[08:32] <seb128> when did you woke up?
[08:32] <pitti> around 7
[08:32] <pitti> but I went to bed at 0:30
[08:32] <seb128> oh, short night then ;-)
[08:33] <seb128> brb quick session restart after upgrade
[08:34] <didrocks> seb128: nuit courte également, mais bien dormis :) et toi?
[08:35] <seb128> j'ai bien dormis et 8h ce qui est correct ;-)
[08:35] <pitti> dormis -> dormant -> sleeping? :-)
[08:35] <seb128> yes
[08:36] <seb128> I slept well and 8 hours
[08:36] <pitti> je parlez francais!
[08:36] <seb128> so I can't complain ;-)
[08:36]  * didrocks install French to pitti :)
[08:39] <seb128> hum, glib 2.25 with gsettings has a tarball
[08:40] <pitti> seb128: wanting to try new crack? :-)
[08:40] <didrocks> I guess it's the good time for an upload :-)
[08:40] <seb128> pitti, wanting new crack in lucid!
[08:40]  * seb128 ru;-)
[08:41] <seb128> ups, running and forgetting to type letters ;-)
[08:41] <pitti> it's just glib, what could possibly go wrong
[08:45] <seb128> with some luck the update might give us debug symbols too who knows ;-)
[08:50] <pitti> seb128: (looking at create-dbgsym now)
[08:50] <pitti> we don't actually treat udebs in any special way
[08:51] <seb128> ok
[08:56] <seb128> bah my one liner crash fixers from yesterday have been rejected
[08:56] <seb128> didn't we use to accept some fixes between rc and stable?
[09:03] <pitti> yes, we usually did
[09:06] <baptistemm> bah glib 2.25 is just glib 2.24 but better, right ? :)
[09:06] <baptistemm> so you have my approval for an upload :)
[09:07] <RAOF> Oooh!  Oooh!  Can I use that reasoning, too?
[09:13]  * Ng wonders if the order of Fn-F7 has intentionally changed. The first poke used to extend onto my external monitor, now it mirrors and the second poke extends
[09:14] <pitti> seb128: argh, I got it, I think
[09:14] <seb128> pitti, oh?
[09:14] <pitti> $ echo "libglib2.0-0-refdbg libglib2.0-udeb" | grep -wq 'libglib2.0-0'
[09:14] <seb128> Ng, they are not meant to have assigned action but to cycle between available configs
[09:14] <pitti> grep -wq matches "libglib2.0-0" on "libglib2.0-0-refdbg" (which is referenced with -N)
[09:15] <seb128> oh
[09:15] <Ng> seb128: what controls the ordering of those configs? It doesn't really matter that it's changed, I'm just curious if this is a deliberate thing or if maybe no ordering is guaranteed and it's going to keep changing on each reboot or something
[09:16]  * pitti wants grep to understand Perl's "WORD"s
[09:16] <pitti> anyway, I'll write a test case and figure it out
[09:16] <seb128> Ng, I'm not sure if xorg returns the info in a deterministic way
[09:16] <seb128> pitti, thanks
[09:16] <Ng> fair enough :)
[09:48] <chrisccoulson> hello everyone
[09:48] <james_w> morning chrisccoulson
[09:49] <chrisccoulson> hey james_w, how are you?
[09:49] <james_w> good thanks, you?
[09:49] <pitti> hey chrisccoulson, hello james_w
[09:49] <chrisccoulson> hey pitti, how are you?
[09:49] <james_w> hey pitti, how are you?
[09:49] <didrocks> hey chrisccoulson and james_w :)
[09:49] <james_w> jinx!
[09:49] <chrisccoulson> james_w - yeah, i'm good too thanks
[09:49] <chrisccoulson> hey didrocks
[09:49] <james_w> salut didrocks
[09:50] <pitti> great, thanks! how about you guys?
[09:51] <chrisccoulson> pitti - yeah, good thanks. had quite an early night last night, so i'm quite refreshed today
[09:55] <pitti> dpkg-deb: Baue Paket »libglib2.0-0-dbgsym« in »../libglib2.0-0-dbgsym_2.24.0-0ubuntu2_amd64.ddeb«.
[09:55] <pitti> hah
[09:55] <pitti> seb128: ^
[10:02] <seb128> pitti, \o/
[10:02] <pitti> uploaded, will talk to Steve
[10:02] <seb128> pitti, thanks
[10:10] <chrisccoulson> hey everyone, firefox 3.6.4 is in the u-m-s PPA now. please test :-)
[10:10] <chrisccoulson> pitti seb128 didrocks ^^
[10:10] <seb128> what is u-m-s?
[10:11] <seb128> can you give the ppa:url there? ;-)
[10:11] <didrocks> ubuntu-main-sponsor has a ppa?
[10:11] <chrisccoulson> seb128 - i can, when my internet catches up ;)
[10:11] <seb128> didrocks, I think it's rather a ubuntu-mozilla-something
[10:12] <chrisccoulson> ppa:ubuntu-mozilla-security/pp
[10:12] <chrisccoulson> a
[10:12] <chrisccoulson> oops ;)
[10:12] <didrocks> I was surprised too :)
[10:12] <seb128> thanks
[10:12] <chrisccoulson> wow, my internet is going super slow today, it's maxed out by a torrent going at 60kB/s
[10:32] <pitti> seb128: is glib2.0 in bzr/
[10:32] <pitti> ?
[10:32] <seb128> pitti, I don't think so
[10:32] <pitti> seb128: merci
[10:33]  * pitti prepares another no-change upload
[10:33] <seb128> pitti, de rien
[10:33] <seb128> pitti, danke
[10:33]  * seb128 refresh sru procedure knowledge and get ready to start on lucid sru uploads
[10:33] <seb128> since lucid-proposed is supposed to be open let's see how it works today ;-)
[10:43] <Zdra> does someone knows why I don't get French spell checker in thunderbird on Lucid?
[10:43] <Zdra> had it on Karmic before the upgrade
[10:44] <didrocks> seb128: didn't you fix a similar issue recently? ^
[10:45] <seb128> didrocks, I fixed it for GNOME, I don't know about thunderbird
[10:46] <seb128> Zdra, is thunderbird-locale-fr installed?
[10:46] <Zdra> yep
[10:46] <Zdra> version 1:3.0.4-0ubuntu1
[10:46] <seb128> ok so I don't know
[10:46] <seb128> I don't use thunderbird
[10:46] <seb128> #ubuntu-mozilla might know
[10:46] <Zdra> I have hunspell-fr installed too
[10:47] <seb128> does spellchecking works in i.e gedit?
[10:47] <seb128> bug #
[10:47] <seb128> 509248
[10:47] <Zdra> seb128, working in gedit/empathy
[10:47] <seb128> bug 509248
[10:48] <Zdra> seb128, thanks :)
[10:48] <seb128> could be the same issue
[10:49] <seb128> let me know if the workaround described in the bug works for you
[10:56] <Zdra> seb128, installing manually a thunderbird extention to have the dictionnaire works ;)
[10:57] <seb128> did you try what was described in the bug?
[10:58] <seb128> would be useful to get the issue fixed rather than having to install things manually to workaround the bug
[11:00] <Zdra> seb128, the link works too
[11:00] <seb128> Zdra, thanks for testing
[11:00] <Zdra> sudo ln -s /usr/share/myspell/dicts/ /usr/lib/thunderbird-3.0.4/dictionaries
[11:03] <Zdra> seb128, would be great if you/someone can make an upload to lucid with that fix
[11:04] <chrisccoulson> can usb-creator only create startup disks for ubuntu?
[11:04] <seb128> Zdra, I will see what we can do
[11:04] <chrisccoulson> you want a thunderbird bug fixing?
[11:05] <chrisccoulson> that one looks pretty trivial actually
[11:06] <Zdra> trivial to fix, but nasty for users
[11:06] <pitti> chrisccoulson: usb-creator> question for ev, I think
[11:06] <chrisccoulson> pitti - i can't seem to make it create a fedora startup disk :(
[11:06] <chrisccoulson> i wanted to try some things on their latest beta ;)
[11:07] <pitti> chrisccoulson: just boot it in kvm?
[11:07] <chrisccoulson> pitti - i'm trying, but the performance is so bad on my laptop now that it's almost impossible to use
[11:07]  * hyperair wishes his cpu has kvm support
[11:07] <pitti> chrisccoulson: oh? WDYM with "now"?
[11:08] <chrisccoulson> pitti - my laptop has sucked really bad since the weekend
[11:09] <seb128> chrisccoulson, did you reboot it since?
[11:10] <seb128> I got some very slow io issue which went away after reboot
[11:10] <chrisccoulson> seb128 - several times. my issue seems to fix itself temporarily after a reboot, but then it comes back again
[11:10] <seb128> chrisccoulson, bug #509248 seems not restricted to ppa build and should be fixed in lucid or lucid updates, can you check with micahg if he's working on it?
[11:11] <chrisccoulson> seb128 - i'll probably just push the fix straight to bzr, as micahg is not around until later anyway
[11:11] <seb128> chrisccoulson, right, I got it several times too, I reboot my laptop once a day at the moment though and it didn't come back this week yet
[11:11] <seb128> chrisccoulson, ok thanks
[11:14] <seb128> shrug
[11:14] <seb128> bryceh, when you start the weekly meeting wikipage could you use the template?
[11:15] <pitti> oh, need to prep my report, too
[11:15] <pitti> seb128: you're the team meeting master today, right?
[11:15] <seb128> pitti, yes, I'm setting the wiki page and about to send the reminder
[11:20] <seb128> pitti, ok, let's see if I got this contact the team right ;-)
[11:20] <seb128> https://wiki.ubuntu.com/DesktopTeam/Meeting/2010-04-20 online too
[11:21] <cassidy> seb128, FYI I just release Empathy 2.30.0.2
[11:22] <seb128> cassidy, I've noticed thanks, too late for lucid but we will get it in a stable update
[11:22] <cassidy> you're fast :)
[11:22] <cassidy> I released it like, 5 minutes ago
[11:22] <didrocks> cassidy: didn't you know? seb128 is behind you ;)
[11:22] <cassidy> ah!
[11:23] <seb128> cassidy, I've seen the commit 12 minutes ago on #commits
[11:23] <cassidy> ahhh :)
[11:23] <seb128> ;-)
[11:23] <seb128> I like watching #commits ;-)
[11:24]  * didrocks joins, can be interesting sometimes to see what should be backported if needed
[11:25] <seb128> didrocks, do you want to do the empathy update as a sru? no hurry you have a good week before it's going to be reviewed or approved anyway now
[11:26] <didrocks> seb128: sure, did you previous uploads to -proposed succeeded?
[11:26] <seb128> didrocks, yes, I did one to try
[11:26] <seb128> it seems to have worked fine I got the waiting for moderation email
[11:27] <didrocks> ok, doing it for empathy so before eod :)
[11:36] <pitti> yep, there are two proposed uploads on https://edge.launchpad.net/ubuntu/lucid/+queue?queue_state=1
[11:41] <chrisccoulson> so, the fedora accountsdialog tool is quite nice
[11:41] <chrisccoulson> and it configures gdm options like auto-login too
[12:27] <chrisccoulson> seb128 - are people just registering blueprints now? should i create a list of blueprints somewhere first before registering them?
[12:28] <seb128> chrisccoulson, hum, what do you mean by just now?
[12:28] <seb128> chrisccoulson, you didn't get the reminder from rick some days ago about those?
[12:28] <seb128> chrisccoulson, to reply to the question no need to create a list somewhere, just follow the convention as described on the wikipage in the meeting reminder
[12:29] <chrisccoulson> seb128 - i did. but i wasn't sure whether to register the ones i have or create a list somewhere first
[12:29] <chrisccoulson> but, that answers my question anyway
[12:29] <chrisccoulson> thanks
[12:29] <seb128> yw ;-)
[13:13] <chrisccoulson> hey Zdra, do you have thunderbird-gnome-support installed?
[13:14] <chrisccoulson> (just saw your comment on bug 543064)
[13:14] <Zdra> chrisccoulson, no and I learnt about it 10s earlier from bug 526290
[13:14] <chrisccoulson> Zdra - cool, does it work then?
[13:14] <Zdra> didn't check yet, let me try
[13:14] <chrisccoulson> (not having -gnome-support after upgrade is an issue_
[13:17] <Zdra> chrisccoulson, fixed the issue, yes
[13:18] <Zdra> \o/
[15:13] <seb128> cassidy, hey
[15:14] <seb128> cassidy, how likely is proxy support going to go in next cycle and for which telepathy components? ;-)
[15:14] <cassidy> it's merged in tp-butterfly but not released yes
[15:14] <seb128> cassidy, is there anything we can do to help making that happens
[15:14] <cassidy> we have done lot of work improving libproxy and adding proxy support to gnio
[15:15] <cassidy> once it's done it should be pretty easy to hook it into Gabble
[15:15] <staz> seb128: did you update the libproxy version finally or not?
[15:15] <cassidy> seb128, best to ask to Maiku on #telepathy
[15:15] <seb128> staz, to 0.3.1 which is what debian has, the newest version broke abi and changed soname
[15:16] <seb128> cassidy, ok thanks, seems likely to go in next cycle then
[15:16] <staz> seb128: that should be enought for telepathy-butterfly then
[15:16] <staz> seb128: do you want me to make a release or will you just merge the patch in the package?
[15:16] <seb128> staz, good, I was just checking for other protocols since some users are vocal on that bug
[15:17] <seb128> staz, we are frozen for lucid now, I will consider options for stable updates if we want that after lucid
[15:17] <cassidy> seb128, like I said...
[15:17] <seb128> ie in a good week from now
[15:17] <cassidy> not sure for haze though
[15:17] <staz> seb128: oh too bad :/
[15:17] <cassidy> rahh felipe is already pissing me off
[15:18] <seb128> cassidy, ignore him
[15:18] <cassidy> that's what I tend to do :)
[15:18] <seb128> Oh, you know him? ;-)
[15:18] <cassidy> a bit..
[15:18] <cassidy> "I don't know who proxies work in libpurple/haze" isn't that clear enough ?
[15:18] <cassidy> (with s/who/how)
[15:20] <staz> I was going to make the remark ;)
[15:20] <staz> (on *how)
[15:49] <seb128_> vish, hum, what do you mean by banshee is being considered default player for next cycle?
[15:51] <vish> seb128_: there was a chat here that banshee is being considered, dj_siegel1  and robbie_w or rick,  i guess
[15:51] <vish> seb128_: something about users testing and discussing in the UDS
[15:51] <hyperair> there's a blueprint about it too
[15:52] <seb128_> vish, where, when?
[15:52] <hyperair> i just don't remember where
[15:52] <seb128_> we are not going to have this discussion are uds most likely
[15:52] <hyperair> lucid's UDS highlighted a few blocking issues.
[15:52] <vish> seb128_: 2days back , let me find the logs
[15:52] <seb128_> shrug
[15:52] <seb128_> I guess some lobbying from banshee users again
[15:53]  * hyperair wonders if there were any more outstanding issues.
[15:56] <vish> seb128_: http://irclogs.ubuntu.com/2010/04/15/%23ubuntu-desktop.html#t16:06  .. not much though ;)
[15:56] <seb128_> we should start by asking if there is any outstanding reason to switch
[15:56] <seb128_> rhythmbox is as actively worked as banshee nowadays
[15:56] <seb128_> it got syncing support in git now which was one of the main reason to consider banshee
[15:56] <tjaalton> does rb support proper syncing with portable players=
[15:56] <tjaalton> ?
[15:57] <tjaalton> that's the only usecase of banshee for me
[15:57] <seb128_> well, "proper", I'm not sure how buggy the new code git is since it's new
[15:57] <seb128_> +in
[15:57] <seb128_> but rhythmbox got syncing yes
[15:57] <seb128_> also rhythmbox is written in a language most people in the desktop team know
[15:57] <tjaalton> :)
[15:57] <hyperair> seb128_: by the way, indicator-application is still pending upload.
[15:58] <seb128_> rather than in one which we might move out of the CD because having it to maintain it for 1 application installed by default is costy
[15:58] <tjaalton> also, it should use the cover.FOO found on the disk and not fetch some random image from the net
[15:58] <seb128_> hyperair, can you get ted to merge the change and suggest this for upload?
[15:58] <tjaalton> but I guess that's filed already
[15:58] <hyperair> tedg: ^^
[15:58] <seb128_> tjaalton, rhythmbox? it does that, the provider there were using cut them because it was creating too much load
[15:59] <kenvandine> seb128_, what do you think about bug 566909
[15:59] <kenvandine> worth patching and trying to get in post RC?
[15:59] <tjaalton> seb128_: yes rb, need to check how it works in lucid
[15:59] <seb128_> kenvandine, is there anything to think?
[15:59] <seb128_> kenvandine, no
[15:59] <didrocks> kenvandine: fixed in 2.30.0.2
[15:59] <seb128_> kenvandine, didrocks did the update for a sru after lucid
[15:59] <kenvandine> is .2 released yet?
[15:59] <kenvandine> at!
[15:59] <kenvandine> great
[15:59] <kenvandine> thx
[15:59] <seb128_> tjaalton, device syncing is not in the lucid version though
[16:00] <tjaalton> seb128_: ok
[16:00] <tjaalton> my ipod is broken anyway :)
[16:08] <tedg> hyperair: Which one is missing?  I thought we were on 0ubuntu4, right?
[16:10] <desrt> hey dudes
[16:10] <tedg> Ah, I see.  seb128_ can you merge this please?  https://code.edge.launchpad.net/~indicator-applet-developers/indicator-application/lucid/+merge/23591
[16:10] <desrt> looks like we don't have to cancel UDS :D
[16:10] <kenvandine> hey desrt
[16:10] <desrt> *the cloud lifts*
[16:10] <kenvandine> :)
[16:11] <didrocks> hey desrt
[16:11] <desrt> kenvandine, didrocks; hi hi
[16:11] <ccheney> desrt: no more ash?
[16:11] <desrt> looks like flights are starting to move
[16:12] <kenvandine> i read this morning that over half of the .eu flights have resumed
[16:12] <kenvandine> the UK might not until the end of the week
[16:12] <ccheney> well i guess as long as there isn't a third eruption
[16:12] <desrt> in a couple of weeks there will be no problem i'm sure
[16:12] <kenvandine> ccheney, true :)
[16:12] <desrt> ccheney: find some wood and knock on it now, plz.
[16:12] <ccheney> desrt: heh :)
[16:12]  * kenvandine knocks
[16:12] <seb128_> hey desrt
[16:13]  * didrocks still says that he never had a so beautiful weather in Paris since this volcanic cloud is here :)
[16:13] <desrt> seb128_: hey
[16:13] <desrt> seb128_: got some good news for you
[16:13] <desrt> you asked me two questions at last UDS
[16:13] <desrt> 1) will GVariant be done?    2) will GSettings be done?
[16:13] <desrt> i tell you today that they're both done and merged :p
[16:14] <didrocks> (congrats for the gsettings hackfest BTW, nice work ;))
[16:14] <desrt> ya.  total success.
[16:14] <kenvandine> desrt, woot!
[16:14] <desrt> vuntz, mclasen and i were like robots
[16:14]  * kenvandine high fives desrt
[16:15] <seb128_> desrt, well done, I need to look how the gconf gsettings backend is working now ;-)
[16:15] <desrt> seb128_: don't.
[16:15] <desrt> seb128_: it's not for you.
[16:15] <seb128_> desrt, I still think having GNOME ported to gsettings in one cycle is very optimistic
[16:15] <seb128_> desrt, is there any other working backend right now?
[16:15] <desrt> seb128_: nope :)
[16:15] <mclasen> seb128_: we can do it if you help...
[16:15] <desrt> dconf will be along in a week or so
[16:16] <desrt> seb128_: i think it's well within our capabilities to get the entire live CD ported
[16:16] <desrt> ie: no gconf in the default install
[16:16] <desrt> -very- attainable goal for maverick
[16:16] <seb128_> desrt, you are an optimistic man ;-)
[16:17] <desrt> seb128_: how long have you known me that you just figure this out now? :)
[16:17] <seb128_> desrt, did you include proper configuration migration in that estimation ?
[16:17] <desrt> seb128_: we already have a reasonable story for that
[16:17] <seb128_> mclasen, let's see
[16:17] <desrt> mclasen wrote a nice program there
[16:17] <desrt> it's already merged into gconf git
[16:18] <seb128> right, I noticed some changes in gconf which is way I wanted to look at the gconf backend ;-)
[16:18] <desrt> the gconf backend is only a porting tool
[16:18] <desrt> so that app authors can have their app in a half-using-gconf/half-using-gsettings state and still use it and test it
[16:18] <desrt> rather than having to hold their breath for the whole port and hoping it works out at the end
[16:19] <desrt> it's never meant to be deployed
[16:19] <seb128> ok
[16:19] <seb128> anyway I want to play with it
[16:19] <seb128> I doubt landing a new tech and having stable with everything ported to it in one cycle will work though
[16:19] <seb128> but I'm wanting to be proved wrong
[16:20] <seb128> you always hit annoying cases on the road or things which don't work well for easy porting and need some slight design changes
[16:20] <seb128> or bugs, or limitations
[16:20] <seb128> less than one cycle is very challenging to code through all those roundtrips
[16:21] <seb128> like it took years to go from libglade to gtkbuilder
[16:21] <seb128> and there was not so many migration concerns there, just the code changes to port to the new api
[16:24] <staz> seb128: maybe there wasn't much motiviation from the devs to do it, like gtkbuilder didn't provide enough advantage to make spending time to port it worth
[16:25] <Nafai> Good morning
[16:26] <seb128> staz, or lot of people are busy with real life and can't always manage to run current git for all platform and jump on new techs in one cycle
[16:26] <Nafai> I keep getting left out of the template for the team meeting :(
[16:27] <seb128> staz, also I'm a bit concerned that one cycle to porting an hundred sofware it's jumping on new techs before having them reasonably tested which complicate any change that would be required
[16:28] <staz> theses are valid point
[16:30] <pitti> seb128: would you mind bzr pushing the latest evince update?
[16:34] <seb128> pitti, done
[16:37] <chrisccoulson> Zdra - micahg - fixed the thunderbird dictionary issue in bzr now
[16:47] <chrisccoulson> is thunderbird seeded anywhere?
[16:47] <pitti> DVD certainly?
[16:48] <chrisccoulson> pitti - thanks. so, any fixes will have to wait until after RC now?
[16:49] <pitti> yes
[17:00] <mandel> aquarius, ping
[17:00] <aquarius> pong
[17:05] <mandel> aquarius, got the mono lib for dektopcouch finished, is there anywhere where it can be announced ? your are the media guy ;)
[17:07] <aquarius> mandel, er...on your blog, and I'll blog about it too? I don't have a masively obvious place for stuff like this. on the DC mailing list as well, of course!
[17:08] <mandel> aquarius, ok, I'll write some examples and will do... i'd be nice to have a place to do this things..
[17:08] <aquarius> mandel, I agree :)
[17:12] <bryceh> rickspencer3, I've got a dentist appt this afternoon so will be attending the morning meeting
[17:12] <seb128> didrocks, you need to add a debdiff for the update to your sru bug
[17:12] <pitti> bryceh: uh, good luck
[17:13] <seb128> didrocks, you might also want to lp close some others bugs
[17:13] <seb128> bryceh, hey, rickspencer3 is not officially there today but noted ;-)
[17:14] <seb128> bryceh, btw when you start the wiki page please use the template next time
[17:14] <didrocks> seb128: the debdiff is pretty big, but that can be added. What do you mean by "you might also want to lp close some others bugs" ?
[17:15] <seb128> didrocks, the first one listed had an apport looking title but was already listed as closed in 2.30.0.1 not sure why it's in the NEWS again, ignore that comment
[17:15] <didrocks> seb128: that's why I didn't listed it :)
[17:15] <seb128> didrocks, I usually filter out documentation, translations and autotools files in a simplified debdiff
[17:15] <didrocks> haven't*
[17:15] <seb128> ie debdiff --exclude configure ...
[17:16] <didrocks> ok, can do
[17:16] <seb128> and gzip it
[17:16] <seb128> didrocks, you might also want to set it as wishlist
[17:16] <seb128> didrocks, oh and next time when it closes an open bug you can use that one for the update rather than opening a new version update bug
[17:16] <didrocks> seb128: I wasn't sure about the priority, wishlist seems good, will do as well
[17:17] <didrocks> seb128: oh sweet, I was thinking that wasn't allowed for SRU (it needed its own bug report with the debdiff, and so on for making the paperwork easier). I'll do that next time.
[17:17] <seb128> didrocks, and for the testcase you can use a "use the new version and make sure it still works correctly" ;-) (SRU usually need a testcase)
[17:18]  * didrocks updates the bug report now and generates the debdiff
[17:19] <seb128> didrocks, thanks
[17:27] <seb128> desktop team meeting in 3 minutes
[17:29]  * kenvandine waves
[17:30] <seb128> ArneGoetje, ccheney, chrisccoulson, didrocks, kenvandine, Nafai, pitti, Riddell, tseliot: meeting?
[17:30] <Nafai> o/
[17:30] <pitti> o/
[17:30] <chrisccoulson> hey
[17:30] <ArneGoetje> o/
[17:30] <chrisccoulson> \o
[17:30] <chrisccoulson> just to be different ;)
[17:30] <didrocks> hey o/
[17:30] <Riddell> hi
[17:30] <seb128> I hope everybody is doing well
[17:31] <pitti> lucid! lucid! lucid!
[17:31]  * tseliot waves
[17:31] <seb128> rickspencer3 is not available to lead the meeting today so I will do that ;-)
[17:31] <seb128> so let's get started
[17:31] <seb128> not outstanding actions
[17:31] <seb128> no
[17:31] <seb128> kenvandine, partner update?
[17:31] <kenvandine> sure
[17:32] <kenvandine> OLS had a few last minute bug fixes, which have been uploaded and slangesek said he would accept after the RC is done
[17:32] <kenvandine> pyinotify, ubuntuone-client and desktopcouch
[17:32] <pitti> will they fix getting mp3s from teh music store by any chance? :-)
[17:32]  * ccheney here
[17:32] <kenvandine> nothing else in the pipe
[17:32] <kenvandine> pitti, hehe... known bug?
[17:32]  * pitti has "Transferring to your Ubuntu One storage" for half a day now
[17:33] <kenvandine> the u1-client update includes a fix for a bug that would delete files if there was an interupted download
[17:33] <kenvandine> pitti, that would be server side... not sure if there is a current known problem
[17:33] <kenvandine> i'll ask
[17:33] <kenvandine> :)
[17:33] <ogra> pitti, are you sure its not already in your music folder ? i had that too but seems that only the store UI wasnt properly updating
[17:33] <pitti> kenvandine: (anyway, let's discuss that off-meeting)
[17:33] <seb128> kenvandine, ok, seems good, thanks
[17:34] <pitti> ogra: yes
[17:34] <seb128> is gwibber behaving now btw?
[17:34] <kenvandine> yes... with this desktopcouch update
[17:34] <seb128> I stopped getting gwibber-service crashes at every login
[17:34] <kenvandine> desktopcouch was frequently dieing on suspend
[17:34] <seb128> but I'm not sure if that's just because pitti turned apport off :p
[17:34] <seb128> ok good
[17:34] <kenvandine> and desktopcouch wouldn't try to start it again
[17:34] <kenvandine> this fix makes it start as needed :)
[17:34] <seb128> nice
[17:34] <seb128> thanks kenvandine
[17:34] <seb128> let's get moving
[17:34] <chrisccoulson> pitti - i had a different issue. it took 2 days for my purchase to be sync'd with U1 ;)
[17:34] <kenvandine> thx
[17:35] <seb128> Riddell, kubuntu update?
[17:35] <Riddell> we're all good as far as I can tell
[17:35] <Riddell> my notes are on my other machine which is currently doing install testing
[17:35] <Riddell> but we're down to three milestoned bugs
[17:35] <Riddell> http://tinyurl.com/yjybcx9
[17:35] <seb128> ok, seems good
[17:35] <Riddell> of which I'm only worried about 1
[17:35] <pitti> Riddell: how's kubiquity now? there were still quite a few issues last week?
[17:35] <seb128> urg, another oem setup issue?
[17:36] <seb128> and a french hating one!
[17:36] <pitti> looks good
[17:36] <Riddell> pitti: still that 1 issue but we have a good track record of sorting out ubiquity issues so I'm confident we'll crack it :)
[17:36] <pitti> good luck!
[17:36] <seb128> Riddell, good work!
[17:36] <seb128> Riddell, thanks ;-)
[17:37] <seb128> next, release status
[17:37] <seb128> http://people.canonical.com/~pitti/workitems/canonical-desktop-team-ubuntu-10.04.html
[17:37] <seb128> seems we are mostly good there
[17:37] <pitti> that generally looks fine
[17:37] <pitti> today we got two more WIs for fonts, but they are being sorted out
[17:37] <seb128> ArneGoetje, what is the status on your 2 todo items there?
[17:38] <pitti> they got FFE approval, and the actual fonts are all settled now I think
[17:38] <seb128> pitti, is that likely to make any difference on CD space?
[17:38] <pitti> just needs some langauge-support-* updates
[17:38] <pitti> seb128: yes, it saved .5 MB in total, I think
[17:38] <seb128> good ;-)
[17:38] <seb128> as long as it's going in the good direction
[17:38] <ArneGoetje> language-support-fonts-ja has just been uploaded with the changes... will upload the fontconfig changes in language-selector later tonight.
[17:38] <seb128> I would chase anybody trying to get french langpacks out of the CD now :p
[17:39] <pitti> also, release-wise I'm pretty happy about the bug situation; we got some 12 RC bugs fixed last week, and the remaining 5 are SRUable
[17:39] <seb128> ArneGoetje, ok, thanks
[17:39] <pitti> ArneGoetje: sweet
[17:39] <seb128> pitti, note that I marked my work item for lpi to DONE since I uploaded that yesterday
[17:39] <pitti> seb128: *nod*
[17:39] <pitti> FYI, https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus got updated yesterday
[17:40] <pedro_> seb128, pitti that means we can start to update the documentation regarding the -> report a problem item ?
[17:40] <seb128> right, none of the bugs remaining on this list seem to be too much of an issue for lucid
[17:40] <seb128> pedro_, yes, it will be in lucid after rc
[17:40] <pedro_> we mean the qa team
[17:41] <pedro_> alright i'll work on that, thanks
[17:41] <pitti> pedro_: I got sign-off from mdke that it doesn't touch the documentation
[17:41] <seb128> pitti, bugs status look good indeed
[17:41] <seb128> pitti, it does touch wiki bug triaging documentation
[17:41] <seb128> pitti, not ubuntu documentation
[17:41] <pitti> ah
[17:41] <pitti> pedro_: right, that could need an update then
[17:41] <pedro_> pitti, sorry i mean the wiki documentation
[17:41] <pedro_> yeah
[17:42] <seb128> pitti, anything else to add on the lucid status?
[17:42] <seb128> seems not, let's get moving
[17:43] <seb128> great work everything, lucid will be a great Ubuntu milestone!
[17:43] <seb128> let's keep focussed on testing images until next week and watch for any raising issues but we are in good shapre
[17:43] <seb128> shape
[17:43]  * tseliot nods
[17:43] <seb128> next topic, blueprints
[17:44] <seb128> I see lot of those registered on https://blueprints.edge.launchpad.net/ubuntu/?searchtext=desktop-maverick, great
[17:44] <seb128> let's go quickly through the team member and registered blueprints
[17:44] <seb128> using the order on https://wiki.ubuntu.com/DesktopTeam/Meeting/2010-04-20
[17:44] <seb128> tseliot, ok, I skip you since you are moving back to oem next cycle
[17:44] <tseliot> thanks
[17:44] <seb128> tseliot, it was great to have you in the team this cycle, good work ;-)
[17:45] <tseliot> it was a pleasure to work with all of you :-)
[17:45] <seb128> thanks tseliot ;-)
[17:45] <seb128> ArneGoetje,
[17:45] <seb128> https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-language-selector
[17:45] <bryceh> tseliot, thanks for all the X help :-)
[17:45] <ArneGoetje> yes
[17:45] <seb128> you registered this one
[17:46] <seb128> seems a good topic for UDS and maverick
[17:46] <tseliot> :-)
[17:46] <pitti> tseliot: you did awesome work, thanks again! you'll be missed!
[17:46] <seb128> it will probably require design recommendation I guess
[17:46] <seb128> did you talk to anybody about that yet?
[17:46] <ArneGoetje> seb128: yep
[17:46] <ArneGoetje> seb128: not yet
[17:46] <Riddell> yes thanks tseliot
[17:46] <seb128> ok, let's see if we can get somebody from the design team to help there
[17:46] <seb128> not now though ;-)
[17:47] <ArneGoetje> seb128: :)
[17:47] <seb128> ArneGoetje, do you have any other spec or uds topic?
[17:47] <ArneGoetje> seb128: not as a feature, no.
[17:47] <seb128> and as non-feature? ie things that need discussion at uds maybe?
[17:48] <ArneGoetje> I'm not sure if it needs discussion at UDS, more like debugging... fontconfig needs some love
[17:49] <ArneGoetje> I think that does not qualify for uds, though
[17:49] <seb128> right
[17:49] <Riddell> jonathan thomas might be doing work on language selector's kde frontend if his gsoc project gets approved, might be good to have ArneGoetje and him review that at UDS
[17:49] <seb128> let's discuss that out of the meeting later
[17:49] <ArneGoetje> Riddell: +1
[17:49] <seb128> Riddell, who would mentor the SoC? but yeah, good idea
[17:49] <ArneGoetje> seb128: ok
[17:49] <seb128> ArneGoetje, thanks
[17:49] <seb128> ccheney, hey
[17:50] <ccheney> seb128: yea
[17:50] <seb128> ccheney, I see you registered 3 openoffice specs
[17:50] <ccheney> yes
[17:50] <ccheney> a general planning one, an packaging optimization one, and one about getting java pulled in by OOo on use
[17:50] <Riddell> seb128: me but nice to have ArneGoetje for consulting
[17:50] <seb128> do you think you need sessions for each at uds?
[17:50] <seb128> Riddell, ok
[17:51] <ccheney> the general planning one would be good for UDS but i don't know if the other two need to be scheduled
[17:51] <seb128> ok, that's what I was thinking
[17:51] <seb128> I will check with rickspencer3
[17:51] <seb128> ccheney, any other UDS topic you want discussed or anything to add?
[17:51] <ccheney> i probably need some help with determining how to do the java part but i think just talking with some of you guys about something like packagekit (i guess) should be enough for that
[17:52] <ccheney> nope that is all
[17:52] <seb128> ccheney, ok, thanks
[17:52] <rickspencer3> ccheney, they need blueprints even if sessions don't need to be scheduled
[17:52] <ccheney> rickspencer3: yea they are already on the blueprint page
[17:52] <seb128> rickspencer3, hey ;-)
[17:52] <seb128> chrisccoulson, hello
[17:52] <chrisccoulson> hey seb128
[17:53] <seb128> you registered https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-search-and-indexing
[17:53] <seb128> and https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-user-accounts-dialog
[17:53] <chrisccoulson> i did :)
[17:53] <seb128> good desktopish topics ;-)
[17:53] <chrisccoulson> hopefully :)
[17:53] <seb128> not sure the second one really require a session or rather offline review, let's talk about that later
[17:54] <seb128> any other spec or topic you want to bring for uds?
[17:54] <seb128> I guess you should have some about web browsers
[17:54] <chrisccoulson> yeah, i wasn't sure about that. it seems to be a case of just speccing out the work items and getting on with it
[17:54] <chrisccoulson> as long as we all agree to the change ;)
[17:54] <glatzor> ccheney, I hope to get sessioninstaller ready for maverick: https://edge.launchpad.net/sessioninstaller
[17:55] <seb128> hey glatzor
[17:55] <chrisccoulson> that was the other thing i was going to ask about actually
[17:55] <seb128> glatzor, should that have an uds discussion or blueprint?
[17:55] <seb128> chrisccoulson, sure, ask ;-)
[17:55] <chrisccoulson> i wasn't sure whether to register a blueprint for that
[17:55] <glatzor> ccheney, I will provide the packagekit session api and use aptdaemon as a backend. the final bits required in aptdaemon (dependency handling) will land soon in the main branch
[17:55] <seb128> chrisccoulson, if you want something discussed register a blueprint
[17:55] <ccheney> glatzor: ok
[17:56] <glatzor> sessioninstaller will provide ...
[17:56] <seb128> chrisccoulson, we can mark it informational after uds if required
[17:56] <ccheney> glatzor: not sure if i will be actually using packagekit or something else like it since OOo doesn't directly use gtk except as interface wrapper, but will definitely look into that, thanks :)
[17:56] <seb128> chrisccoulson, I guess you would need at least one about firefox schedule for next cycle
[17:57] <chrisccoulson> seb128 - yeah, possibly. although it's mostly just tracking upstream releases really
[17:57] <seb128> chrisccoulson, and maybe one to discuss the default web-browser since chromium seems to get increasing userbase
[17:57] <chrisccoulson> i need to talk about firefox towards the end of the meeting anyway ;)
[17:57] <chrisccoulson> seb128 - i think that's covered by the default app selection one
[17:58] <seb128> ok
[17:58] <seb128> sounds good then
[17:58] <seb128> thanks chrisccoulson
[17:58] <seb128> didrocks, salut
[17:58] <didrocks> bonsoir seb128 :)
[17:58] <seb128> didrocks, so oneconf, quickly, une app selection
[17:59] <seb128> seems quite good topics for UDS and for maverick work
[17:59] <didrocks> yeah, should be interesting sessions :)
[17:59] <seb128> is there anything else you want to add there?
[17:59] <didrocks> I think it should be enough on my side, I'll fill them with ideas little by little
[17:59] <seb128> ok, good work, thanks didrocks
[17:59] <Nafai> And I'll probably help some on quickly and une :)
[18:00] <didrocks> thanks seb128 :)
[18:00] <seb128> Nafai, hey
[18:00] <seb128> since you are there let's look at yours too
[18:00] <Nafai> Hi :)
[18:00] <seb128> btw I noticed you were not in the meeting template
[18:00] <seb128> let's get that fixed for next week
[18:00] <rickspencer3> I assigned some to Nafai
[18:00] <Nafai> yeah, thanks
[18:01] <kenvandine> hey rickspencer3!
[18:01] <seb128> rickspencer3, thanks
[18:01] <seb128> https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-desktop-for-app-developers
[18:01] <seb128> https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-quickly-widgets
[18:01] <chrisccoulson> seb128 - i'm only half in the meeting template too ;)
[18:01] <seb128> are the ones I see on the list
[18:01] <seb128> chrisccoulson, Nafai: https://wiki.ubuntu.com/DesktopTeam/MeetingTemplate btw
[18:01] <seb128> feel free to fix errors
[18:01] <Nafai> I'm excited for both of them, particularly the first one
[18:01] <chrisccoulson> yeah, i should probably add me to it
[18:02] <seb128> Nafai, seems to be 2 interesting topics indeed
[18:02] <Nafai> For the first one, I imagine we might want some input from the design team, just because we are working on developer stuff doesn't mean the UI has to be good :)
[18:02] <seb128> right
[18:03] <didrocks> seb128: oh btw, can we already ping formally the design team for input? I ping mpt later today for oneconf but he wanted someone assigned by ivanka?
[18:03] <Nafai> Do we typically involve them at UDS for these things?  Or is that a post-UDS thing?
[18:03] <seb128> let's see what specs we need design input on and talk to them before uds
[18:03] <Nafai> cool
[18:03] <seb128> didrocks, I think we should rather build a list of what we need and talk to rickspencer3 about how to handle that
[18:03] <didrocks> great :)
[18:03] <kenvandine> good to at least give them a heads up for the things we might be needing their time for
[18:04] <seb128> if you need design input please note that for next meeting
[18:04] <seb128> or in the spec summary
[18:04] <seb128> so we can build a list of those and coordinate with the design team
[18:04] <seb128> Nafai, anything else you wanted to add for uds or next cycle topics?
[18:04] <Nafai> not that I can think of
[18:04] <seb128> Nafai, ok, thanks
[18:04] <seb128> Riddell, hey
[18:04] <Riddell> hi'
[18:05] <Riddell> https://blueprints.edge.launchpad.net/ubuntu/?searchtext=kubuntu-maverick is our list
[18:05] <seb128> Riddell, I don't see any spec of ours on https://blueprints.edge.launchpad.net/ubuntu/?searchtext=desktop-maverick ?
[18:05] <seb128> oh, they start with kubuntu-, right ;-)
[18:05] <Riddell> I should also register one on kubuntu council
[18:05] <seb128> ok
[18:05] <Riddell> and gsoc projects depending on language selector
[18:05] <seb128> seems you have a good list of topics and things on track as usual ;-)
[18:06] <Riddell> glatzor: dantii is coming, I don't know if you want to battle out apt vs aptcc backend for packagekit
[18:06] <seb128> glatzor, mvo: do we need a session about packages installation from the desktop at uds?
[18:07] <seb128> Riddell, ok, seems your list is on shape, anything to add?
[18:08] <seb128> Riddell, thanks ;-)
[18:08] <seb128> let's keep moving
[18:08] <seb128> kenvandine, hello
[18:08] <kenvandine> hey!
[18:08] <seb128> you registered those
[18:08] <seb128> https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-empathy-indicator
[18:08] <seb128> https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-gwibber-test-suite
[18:08] <seb128> https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-social-api
[18:08] <seb128> cleaning patches we have and adding testsuites, I like that ;-)
[18:09] <kenvandine> empathy-indicator wouldn't need a discussion, it is just dropping the empathy patch and creating the service to replace it
[18:09] <seb128> do you think the first 2 need discussion?
[18:09] <kenvandine> assuming telepathy is ready for it
[18:09] <kenvandine> no
[18:09] <seb128> ok
[18:09] <kenvandine> social-api will though
[18:09] <seb128> right, I assumed so
[18:09] <kenvandine> want to extend the usefulness of what we did this cycle
[18:09] <seb128> can you try to look at what we need from telepathy before UDS?
[18:09] <kenvandine> yes
[18:09] <seb128> I know some of the telepathy guys will be there
[18:10] <kenvandine> :)
[18:10] <seb128> so it's a good opportunity to discuss that directly with them
[18:10] <kenvandine> yeah
[18:10] <kenvandine> that is all i have
[18:10] <seb128> ok, looks good
[18:10] <seb128> thanks kenvandine
[18:11] <seb128> pitti, no spec for you since you will be on rotation
[18:11] <pitti> right, I'm lazy this time :)
[18:11]  * seb128 hugs pitti
[18:11] <seb128> we still like you though
[18:11]  * pitti hugs the team
[18:11]  * chrisccoulson hugs puttu
[18:11]  * chrisccoulson hugs pitti, even
[18:11] <pitti> chrisccoulson: who's that dude?
[18:11] <chrisccoulson> lol
[18:11] <seb128> don't hesitate to stay around while you are rotation!
[18:11] <chrisccoulson> pitti OOI, where are you rotating too?
[18:11] <didrocks> pitti is telling us that not being in the desktop team is being lazy? :)
[18:12] <seb128> ok, so I think we covered everybody but rickspencer3 who is not officially there and me
[18:12] <seb128> I've https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-overriding-defaults-on-upgrade listed with my name there
[18:12] <rickspencer3> seb128, could folks please subscribe ivanka to blueprints that need design input?
[18:12] <seb128> rickspencer3, ok
[18:13] <rickspencer3> (sorry to interrupt)
[18:13] <seb128> rickspencer3, you don't, don't worry ;-)
[18:13] <pitti> chrisccoulson: OEM
[18:13] <seb128> rickspencer3, want to have a look at your blueprints or were you just passing by quickly?
[18:14] <seb128> so the overriding defaults is about dealing with user configuration tweaking on update cleanely
[18:14] <seb128> I also need to register one about gnome3
[18:14] <kenvandine> wouldn't that be related to oneconf?
[18:14] <seb128> to discuss what we will want to do exactly for maverik
[18:14] <rickspencer3> seb128, just checking in when I can
[18:14] <chrisccoulson> the configuration one is interesting
[18:14] <Nafai> rickspencer3: Should we indicate in the summary what specifically we need design input for?
[18:14]  * rickspencer3 turns back to presentation
[18:15] <rickspencer3> Nafai no, just subscribe for now
[18:15] <seb128> gnome3 has several aspects, one is porting code to the new apis, ie helping on gconf -> dconf for example
[18:15] <seb128> one is to know what we want to ship next cycle, what we want to experiment with and what we want to delay
[18:16] <seb128> I need to check with mvo too if we need one about package installation in the desktop
[18:16] <didrocks> kenvandine: oneconf is not on update but using multiple machines or reinstalling one. seb128's proposal is more on "updating to find if the user still has the default" (for instance, if you change your theme and choose back the default, you currently aren't considered as having the default setting and won't be migrated)
[18:16] <chrisccoulson> we definately need something for that, so we can start taking advantage of all the packagekit integration in gnome
[18:16] <chrisccoulson> i feel like we're missing out a little bit
[18:16] <seb128> yes
[18:16] <seb128> I'm just not sure if glatzor and mvo have it all sorted
[18:17] <seb128> or if that needs discussion
[18:17] <seb128> what didrocks said about the oneconf, the desktop-maverick-overriding-defaults-on-upgrade one is rather how to deal with things like adding an indicator to the gnome-panel config on upgrade
[18:17] <seb128> or changing the theme if the user is using the standard one
[18:18] <seb128> ok
[18:18] <seb128> so that was about it for me
[18:18] <Nafai> can someone help me out of meeting about how much detail should be in the spec summaries, etc before UDS?
[18:18] <seb128> I think I will be busy enough with doing techlead work and looking to GNOME3 desktop changes with robert_ancell
[18:19] <seb128> Nafai, did you read https://wiki.ubuntu.com/DesktopTeam/10.10/BlueprintingSchedule about that?
[18:19] <pitti> Nafai: it should be enough to understand what the session is about and what the goal is
[18:19] <didrocks> (I still can give an hand there so that you can still focus on your techlead role, as we talked together)
[18:19] <seb128> Nafai, we can chat after meeting sure
[18:19] <seb128> didrocks, thanks
[18:19] <Nafai> seb128: I'll re-read that and then ask questions, thanks
[18:19] <seb128> ok, I think we covered the specs for the team
[18:19] <seb128> anybody has anything to add about specs or uds topics?
[18:20] <seb128> before I hand the mic to chrisccoulson about firefox testing
[18:20] <rickspencer3> seb128, just real quick ...'
[18:20] <rickspencer3> if you have to choose between making Lucid solid and doing UDS prep
[18:20] <rickspencer3> choose Lucid
[18:20] <rickspencer3> ;)
[18:20] <seb128> ;-)
[18:20] <seb128> rickspencer3, thanks
[18:20] <seb128> ok, seems there is nothing to add
[18:21] <seb128> chrisccoulson, you wanted to raise firefox quickly?
[18:21] <chrisccoulson> yeah, 2 things
[18:21] <chrisccoulson> so, firefox 3.6.4 is now in the ubuntu-mozilla-security team PPA, and this will become the first security update in lucid
[18:22] <chrisccoulson> i would appreciate everybody helping out with testing that, and also blogging about it where possible so we can get lots of people involved
[18:22] <chrisccoulson> it's not a minor update like most point-releases normally are ;)
[18:22] <seb128> can you give us the ppa:... url again?
[18:22] <chrisccoulson> yeah, it's ppa:ubuntu-mozilla-security/ppa
[18:22] <seb128> thanks
[18:23] <seb128> everybody, add that to your sources and install the update
[18:23] <chrisccoulson> the second issue might be better outside of the meeting actually
[18:23] <seb128> so we get good testing before it hits lucid-security
[18:23] <seb128> ok
[18:23] <seb128> so let's wrap up and discuss the other one
[18:23] <seb128> anybody having anything to add?
[18:24] <chrisccoulson> ccheney, you were working on all the backporting efforts to prepare supported releases for the major firefox updates weren't you?
[18:24] <chrisccoulson> where are we with that now?
[18:24] <seb128> seems not
[18:24] <seb128> thanks everybody
[18:24] <pitti> thanks everyone
[18:24] <kenvandine> thanks, maverick is gonna be fun :)
[18:24] <ccheney> chrisccoulson: for epiphany, getting back to it this week as it appears i finally got all the OOo issues resolved for lucid
[18:24] <didrocks> thanks everyone
[18:24] <chrisccoulson> ccheney, 3.0 is now officially EOL by mozilla
[18:25] <ccheney> chrisccoulson: ok
[18:25] <seb128> kenvandine, yeah, but let's make sure lucid rocks as much it can before that and stay focussed on it for an another week (or a bit extra time for sru polish too)
[18:25] <chrisccoulson> so, updating hardy to 3.6 is becoming urgent
[18:25] <kenvandine> :)
[18:25] <kenvandine> seb128, yeah i think we will be giving lucid lots of attention in the next few weeks
[18:25] <ccheney> chrisccoulson: yea, will jump over to the ubuntu mozilla channel and see if i can get it finished up
[18:25] <seb128> I plan to stay on lucid until after uds
[18:25] <Nafai> chrisccoulson: security update?
[18:25] <seb128> I need a stable laptop for UDS anyway
[18:25] <pitti> chrisccoulson: I have 3.6.4+build1+nobinonly-0ubuntu0.10.04.2, is that the latest one?
[18:25] <seb128> and always good for the first sru rounds
[18:26] <chrisccoulson> pitti - yeah, that's the latest
[18:26] <pitti> ah, seems I added that PPA a long time ago, back when asac asked us to
[18:26] <pitti> chrisccoulson: I didn't notice anything, I guess that's a good sign :)
[18:26] <chrisccoulson> pitti - yeah ;)
[18:27] <chrisccoulson> pitti - try watching a video in youtube and then killing the plugin-container process
[18:27] <chrisccoulson> you should get a nice message about flash crashing ;)
[18:27] <ccheney> yipee!
[18:27] <chrisccoulson> that's the big change in the latest version (running plugins out-of-process)
[18:27] <chrisccoulson> but only flash is enabled currently
[18:27] <seb128> chrisccoulson, pitti: rickspencer3: is the firefox security update in karmic something we should be concerned about now? ie should it be ready and lagging behing on schedule and require actions or something?
[18:27] <Nafai> chrisccoulson: awesome, that's one of my motivations for using Chromium
[18:28] <pitti> chrisccoulson: hm, seems swfdec doesn't work any more
[18:28] <pitti> chrisccoulson: could be a youtube problem or a ffox problem, not sure
[18:28] <seb128> pitti, downgrade to lucid firefox and check if it works?
[18:28] <chrisccoulson> seb128 - karmic is not as urgent as hardy, as 3.5 is still supported
[18:28] <seb128> chrisccoulson, I meant hardy there, autofinger bug ;-)
[18:28] <chrisccoulson> pitti - ok, i will try and reproduce
[18:29] <chrisccoulson> heh ;)
[18:29] <chrisccoulson> yeah, that's pretty urgent now, as 3.0.x will get no more releases from mozilla
[18:29] <seb128> hum
[18:30] <seb128> what is missing for us to be able to do the update in hardy?
[18:30] <pitti> chrisccoulson: hm, it starts to play for 3 s, then goes away and says "Go upgrade!"
[18:30]  * pitti downgrades
[18:30] <chrisccoulson> seb128 - that's what i'm not sure about yet, as i've not been tracking the work that ccheney has been doing
[18:30] <ccheney> seb128: epiphany for one so we can drop the old xulrunner
[18:30] <glatzor> ccheney, The PackageKit session API is also provided by KPackageKit on KDE desktops. So this would be quite desktop agnostic.
[18:30] <ccheney> chrisccoulson: need to coordinate with asac about what else is left other than epiphany
[18:31] <ccheney> glatzor: ok
[18:31] <pitti> chrisccoulson: ok, same problem with 3.6.3, so nevermind
[18:31] <chrisccoulson> ccheney, yeah, no worries. i think micahg has been working on porting stuff as well, so we probably all need to get together at some point
[18:31] <chrisccoulson> pitti - ok, thats good ;)
[18:32] <ccheney> chrisccoulson: epiphany was almost there when i last worked on it, was having some trouble with the way i backported a class with callbacks, after that is fixed it should work (hopefully) epiphany did run but crashed when trying to enter a different url from debian.org
[18:32] <glatzor> Riddell, Sorry, but I won't be at UDS this time because of my main work. But there isn't any need to battle.
[18:32]  * Nafai lunches and errands
[18:32] <chrisccoulson> ccheney, ok, so it seems there is still a bit of work to do. i should be able to free up some time to help out with this now
[18:33] <ccheney> chrisccoulson: ok, i can get you a copy of the most recent source to have you see if it is obvious how to fix it, i have all the rest of my bits in ppa
[18:33] <chrisccoulson> thanks
[18:33] <ccheney> chrisccoulson: someone more familiar with gtk object code could probably fix it fairly quickly, i'm still learning how it works :)
[18:34] <chrisccoulson> heh :)
[18:35] <ccheney> chrisccoulson: will take the rest of the discussion over to mozilla channel
[18:35]  * kenvandine -> lunch
[18:36] <seb128> dinner there, bbl
[18:36] <glatzor> seb128, would be definitely a good idea to have a spec about desktop package installation.
[18:36] <seb128> glatzor, ok thanks
[18:37]  * ccheney -> lunch
[18:38] <didrocks> well, enjoy the evening with my family :) see you tomorrow
[18:46]  * pitti -> dinner
[19:05] <jcastro> kenvandine, how stable is the m-i integration in xchat for you?
[19:05] <jcastro> mine is not very good. :-/
[19:11] <rickspencer3> jcastro, I have a logged a bug based on a crasher I experienced
[19:11]  * rickspencer3 looks
[19:11] <rickspencer3> oops
[19:11]  * rickspencer3 has to pay attention here
[19:11] <crimsun> mvo: I'm not sure what you'd like me to do in bug 567148; it seems like an archive admin decision.
[19:50] <baptistemm_> james_w, hi
[19:50] <james_w> hi baptistemm
[19:50] <kenvandine> jcastro, well.. it just crashed for me
[19:51] <jcastro> kenvandine, when you select on the person who messaged you?
[19:51] <kenvandine> just now yes
[19:51] <baptistemm_> james_w, is there a way with bzr bd to use a svn revision instead a released tarball
[19:51] <kenvandine> but i have only had it crash like twice
[19:51] <kenvandine> but it happened just now when you highlighted me :)
[19:51] <james_w> baptistemm_: yes, but currently you have to create the tarball yourself
[19:51] <james_w> baptistemm_: then you can just pass that to merge-upstream
[19:52] <baptistemm_> okay, let use that :)
[19:52] <james_w> baptistemm_: we need a hook point for running autofoo or whatever to do it more elegantly than that
[19:57] <mvo> crimsun: i just recorded it for now, i will sub ubuntu-archive
[19:57] <crimsun> mvo: ok, thanks for the clarification.
[19:58] <mvo> thank you
[20:21] <seb128> mvo, still there?
[20:21] <seb128> rodrigo__, hey
[20:21] <mvo> seb128: sort of
[20:21] <mvo> yes
[20:22] <seb128> mvo, did you read my questions from the meeting before?
[20:22] <mvo> seb128: no
[20:22] <seb128> mvo, do we need a session about making easy to install packages in the desktop at uds?
[20:22] <mvo> seb128: session-installer?
[20:22] <seb128> mvo, dunno what session installer is
[20:22] <mvo> seb128: a packagekit like api?
[20:23] <mvo> seb128: yeah, we should talk aobut it
[20:23] <seb128> mvo, we current have things g_spawning synaptic or gnome-app-install
[20:23] <mvo> yeah
[20:23] <seb128> mvo, it seems suboptimal compared to what upstream GNOME is doing
[20:23] <mvo> we need a dbus api
[20:23] <seb128> right
[20:23] <mvo> compatible to packagekit
[20:23] <seb128> right
[20:23] <mvo> :)
[20:23] <seb128> I was not sure if that was solved issue waiting on glatzor's work to land
[20:24] <seb128> or if that still needs a session
[20:24] <seb128> so you say we can use an uds session?
[20:24] <seb128> do you have a blueprint already about this on launchpad?
[20:25] <glatzor> seb128, lp:sessioninstaller
[20:25] <mvo> no, but glatzor has some code
[20:25] <mvo> (code > blueprint)
[20:25]  * mvo hugs g'hawk-eye'latzor
[20:25] <seb128> mvo, well blueprint = required for uds scheduling
[20:25] <glatzor> seb128, mvo you can already run sessioninstaller and use the test.py for a first impression
[20:26] <seb128> glatzor, nice, thank you
[20:27] <glatzor> seb128, you have to call python core.py in the sessioninstaller to run the daemon from the source code directory
[20:28] <glatzor> seb128, mvo, currently it makes use of synaptic for the installation
[20:30] <glatzor> seb128, mvo! see you guys! nice evening
[20:30] <mvo> you too glatzor
[20:30] <seb128> glatzor, thanks, you too
[20:30]  * mvo waves
[20:30]  * glatzor makes winke winke
[20:58]  * Nafai stretches
[21:19] <Technoviking> btw, Wil Wheaton (Star Trek fame) says kudos for Simple Scan, It worked where OSX failed:)
[21:57] <asac> seb128: heya ... any gnome batches planned till final? ;)
[21:57] <seb128> asac, hey
[21:57] <seb128> asac, no
[21:58] <seb128> asac, .1 is too late for lucid and will be sru-ed
[21:58] <asac> good :)
[21:58] <seb128> asac, I think out of maybe some small fixes on applications we are set for lucid
[21:58] <seb128> ie no platform or gtk upload before lucid
[21:59] <asac> seb128: yeah. if you see any armel ftbfs in main when uploading after or for RC, ping us directly so we dont loose half a day ;)
[21:59] <seb128> ok
[21:59] <asac> if possible. thanks!!!
[21:59] <seb128> is armel on shape right now?
[21:59] <seb128> or do you need help looking to some build issues?
[21:59] <asac> main is clean
[21:59] <seb128> ok, good
[21:59] <asac> universe could be better, but MOTU is still working on requeueing builds
[22:00] <seb128> I was asking for desktop, I don't intend to work on universe build issues ;-)
[22:00] <asac> based on some graphs they made, so it will go down a bittoo still
[22:00] <asac> seb128: libgphoto2 upload will happen
[22:00] <seb128> iz pitti bog ;-)
[22:00] <asac> thats the only ftbfs ... locks up somewhere in doxygen generating images
[22:00] <asac> we will disable graphviz on armel and seems to be fine (just verifying)
[22:00] <seb128> ok, good
[22:06] <rodrigo__> seb128, ping
[22:12] <chrisccoulson> asac - i have an armel gjs build failure ;)
[22:16] <seb128> rodrigo_, hey
[22:16] <rodrigo_> seb128, so, you were looking for me earlier on?
[22:17] <seb128> rodrigo_, just reading you gsettings g-c-c email
[22:17] <rodrigo_> seb128, ah, agreed on it?
[22:17] <seb128> rodrigo_, desrt recommended against using the gconf gsettings backend
[22:17] <rodrigo_> seb128, oh yes, it is for testing now, as I understood from mclasen's mail
[22:17] <seb128> he said that was something to use by hackers while porting not something to use
[22:17] <rodrigo_> yeah, right
[22:18] <seb128> I think we should also sort the other refactoring going on
[22:18] <rodrigo_> sorry, that's what I meant, sorry I wasn't clear enough
[22:18] <seb128> rather that start working on codebases that will change
[22:18] <rodrigo_> the extensible shell you mean?
[22:18] <seb128> yes
[22:18] <seb128> + cleaning in capplets we might want to drop or simplify
[22:18] <rodrigo_> yes, thomas just answered that
[22:18] <seb128> ok, I did read replies on the list
[22:19] <rodrigo_> yeah, sounds good
[22:19] <mclasen> rodrigo_: the gconf  backend is to get you off the ground wrt to porting, but not something that we want to use in the next stable release
[22:19] <seb128> "didn't"
[22:19] <rodrigo_> mclasen, yes, that's what I understood, sorry if my mail wasn't clear :)
[22:20] <seb128> rodrigo_, ok, so sorry about the gconf gsettings confusion, my comment was mainly a suggestion to start looking to land other refactoring first maybe to avoid working on a codebase that will change and do the work again later
[22:21] <rodrigo_> seb128, yeah, answering now to Thomas's mail with your suggestions
[22:22] <seb128> ok, good, thanks
[23:04] <TheMuso> Good morning.
[23:05] <rickspencer3> Hi TheMuso
[23:05] <Nafai> Good morning TheMuso
[23:33] <RAOF> Good morning all.
[23:33] <TheMuso> Morning RAOF.