[00:02] i think i'm off to sleep now [00:02] see you tomorrow [00:10] See ya, have a good one! [11:51] madnick, thanks for sending the email :) [11:51] * knome is off until late [11:51] see you [12:09] cya === yofel_ is now known as yofel [18:18] i haven't upgraded in a while (always did clean installs), it's really a bit scare when icons and gtk disappear :) [18:19] s/scare/scary [18:19] luckily the cli still looks the same [18:33] ochosi: I've been meaning to file a bug, I get the offline icon now for network applet on precise when I'm connected [18:41] micahg: in the tray/indicator or in the notification-bubble? [18:42] i don't know exactly what version of elementary-xfce you're using, the first upload had a few small bugs (so this might be fixed in bzr already) [18:42] indicator [18:42] 12.04.0 of xubuntu icon theme [18:43] hm, so i guess it's still the initial version [18:43] :/ [18:43] are there upstream releases of elementary xfce? [18:43] knome: I updated the Website wiki page todo list [18:43] no, i'm releasing/maintaining it [18:43] ochosi: is this work beneficial for others [18:43] so, in that respect yes: since i'm upstream =) [18:44] i don't think anyone else uses elementary-xfce yet [18:44] I'm just wondering if we should give it its own source [18:44] ah [18:44] hm, maybe ask the studio-guys [18:44] i dunno what icon-theme they're using [18:44] but if they're using elementary then they'll be in trouble in precise [18:44] that way other derivatives as well as other distros can easily include it [18:44] (elementary-upstream decided to drop a shitload of symlinks, so... breakage) [18:45] yeah, i agree that giving it its own source might make sense [18:45] although it might be odd for lubuntuers to use a theme called elementary-xfce :p [18:45] (iirc they also use elementary) [18:45] brb [18:51] re [19:14] micahg: seems -studio guys haven't decided yet what icon-theme to go with. still it might be a good choice to put the icon-theme in a separate package. any opinions on the matter mr_pouit ? [19:14] ScottL: you around? [19:14] this something i know we were discussing [19:15] ochosi: ill make sure i get this in the dev channel, or get you guys talking at some point [19:16] k, thanks [19:16] g2g now [21:30] ochosi: why not, I don't really mind [21:31] ochosi: btw, I think the bluetooth systray icon (e.g. with blueman) is missing from elementary-xfce-dark. I tried quickly on my debian here, and it's the only icon that stayed dark on the dark panel ;> [21:35] mr_pouit: ah, good to know, i never use blueman/bluetooth devices [21:39] gah, I still need to update/SRU that [21:40] what? [21:42] blueman [21:44] ah [21:46] mr_pouit: in case i forget about the bluetooth-thing, feel free to poke me again... (sry, got a lot of things in my head atm) [21:50] ochosi: hey, don't forget about the bluetooth-thing [21:50] * mr_pouit hides [21:50] lol [21:50] well e.g. remind me @fosdem after a few beers. i'm sure i'll remember it then ;) [21:51] huhuhu [21:51] ok, so green light on putting the icon theme in a separate source then [21:52] mr_pouit and/or micahg: feel free to get on with it then ;) [21:52] ochosi: you need to make an upstream release first ;) [21:52] hihi [21:52] ok, i guess i'll maintain it in github then [21:52] unless you prefer bzr (it's soo slow...) [21:53] no, bzr isn't slow, it's all the other that are faster ;-) [21:53] * mr_pouit runs [21:54] :) [21:55] can you do a shimmer-themes compilation too? I'm too lazy to fetch all shimmer themes separately for the shimmer-themes package :3 [21:55] you mean in github? [21:57] mmh, maybe not if you have to duplicate everything [21:57] well, it's not a big deal [21:57] i can even move all themes to one repo [21:57] the only downside is that if $users want to download a tarball they always get all the themes [21:58] ochosi: you can do multiple tarballs (source format 3 FTW) [21:58] oh, I forgot about that [21:59] micahg: hmm, true, i think i can add individual tarballs to the download-section in github. but i think they wouldn't be up-to-date [21:59] ochosi: you make an upstream "release" when you want to, we pull that in, what's not up-to-date [22:01] micahg: sounds good [22:03] I'll put albatross+bluebird+greybird in shimmer-themes then [22:03] what's the status of shearwater? [22:04] it's stalled (or even abandoned) [22:04] ok [22:04] we'll revamp albatross first and make a gtk3 version [22:04] * Unit193 perks up at greybird [22:04] i don't think shearwater is going to happen unless someone else steps up [22:05] Unit193: you just tought me a new word .) [22:05] ochosi: My mind s/greybird/blackbird/ :P [22:05] hehe [22:05] ochosi: fyi, it's included in murrine-themes [22:05] mr_pouit: what, shearwater? [22:05] yeah ^_^ [22:06] mr_pouit: oh lord... iirc it was in a very early state. i mean i guess it's usable, but not exactly pretty [22:07] (heh, you should ping Corsac about that) [22:08] yeah, probably should do that... otoh if he likes it why not [22:08] i think there are more themes in that package that are unmaintained and underdeveloped [22:10] micahg: with 3.0+multiple tarballs, the drawback is that I've to invent a version number for the compilation ;-) [22:11] no problem, can do :) [22:11] mr_pouit: indeed :), that depends on whether or not the "upstream" releases are in sync [22:11] i think we discussed that earlier, that we need a version number for shimmer-themes anyway [22:11] we'll make it 1.1 (target for 2.0 is having full gtk3 for all three themes) [22:12] mr_pouit: I haven't merged murrine-themes as I wasn't sure if our version of greybird was newer than Debian's [22:13] ochosi: yeah, I hope you don't mind tarballs like shimmer-themes_1.1.orig-{albatross,bluebird,greybird}.tar.gz [22:14] micahg: indeed, I don't remember either. The current plan is to split the shimmer themes to a shimmer-themes package, as we don't want so many murrine-themes by default (that's the clean-up-something-blueprint) [22:14] sounds good [22:15] I assume Corsac is ok with this in Debain as well? [22:15] Good point, I haven't asked him yet :[ [22:22] right, i'm off for tonight, too tired to get more work done [23:32] Anyone tried installing from desktop today? Our tester reports ubiquity crashing.