13:44:48 #startmeeting openSUSE GNOME Meeting 13:44:48 Meeting started Thu Dec 16 13:44:48 2010 UTC. The chair is vuntz. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:44:48 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:45:03 nmarques, we will take care of it. we - I and you 13:45:09 after the meeting 13:45:10 #topic Project Update 13:45:17 psankar, that's a plan +1 13:45:18 ok, project update 13:45:24 DimStar: anything? :-) 13:45:35 project update? Hmm.. 13:45:52 only the usual: packages are up-to-date... vuntz fixed a big bunch of build failures 13:46:00 gnome:next ? 13:46:44 from my side, I see a few things: 13:46:46 a few new apps that were packaged and pushed to factory (waiting for legal review) 13:46:53 I probably need to update the wiki page for that 13:47:07 we're up-to-date, as DimStar said 13:47:26 we did a few maintenance updates for 11.3 recently, which is good 13:47:35 we could do more -- if people want to help, that's welcome 13:47:55 and we have GNOME:Next which we just started 13:48:04 it will contain GNOME 3 in the future 13:48:09 regarding gnome:next, is this the project that will be used to supply end-users with a stable 3.0 once it is released? 13:48:12 hopefully, it'll be ready before the end of the year 13:48:28 badshah400: GNOME:Next is explicitly not for end-users -) 13:48:41 once 3.0 will be ready, we'll move it to G:S:3.0 13:48:56 I don't think we should ever have users use gnome:next.... it should more serve us our 'devel bed' while factory is closed... we will probably make a GNOME:STABLE:3.0 for the users 13:48:57 vuntz: ok, so this is a test-bed sort of 13:49:14 badshah400: yeah, it's for developers/packagers 13:49:25 Do we plan to create anything for tumbleweed ? can gnome-next be used there ? 13:49:26 fwiw, I explicitly mentioned in the title of the project that it's not for end-users :-) 13:49:36 ah, tumbleweed, that's another good topic 13:49:45 tumbleweed should use the latest G:S:* 13:50:06 did we/you SR it already? 13:50:09 I wanted to check with DimStar, but I think we're ready to submit all of G:S:2.32 13:50:31 DimStar: :-) If you're fine with it, we can sr it 13:50:37 there is a small list of packages that could get an update in G:S:2.32... volunteers? :) 13:50:41 I'm not aware of any issue in G:S:2.32 13:51:02 stability wise it seems to be fine.. I don't see much complaining about it. 13:51:06 DimStar: good point 13:51:17 most of them can be taken from G:F, though ;-) 13:52:24 DimStar, can you mail the list about the list of packages needing help ? 13:52:30 DimStar: these are just minor version upgrades, nothing big right? so I can look into them 13:52:52 psankar: osc collab todo --project GNOME:STABLE:2.32 13:53:28 vuntz, ah yes. I forgot that 13:53:46 badshah400: note that for most of them, we can just take the version from G:F. It's just a matter of copying them, which I can trivially do after the meeting 13:53:55 vuntz: ok then 13:53:59 there's just glib2 which will require manual work 13:54:03 as far as I can tell 13:54:22 badshah400: so you can take this one, if you want 13:54:56 vuntz: glib2 for G:S:2.32? ok 13:55:17 badshah400: yep 13:56:55 ok 13:57:31 coming back to GNOME:Next and Tumbleweed: 13:57:45 if people want to help with either of those, you're most welcome 13:57:56 for Tumbleweed, especially, we'll likely need testers, I guess 13:58:11 * psankar volunteers 13:58:19 I am very much interested in tumbleweed 13:58:22 vuntz, you know my help is very limited but within the boundaries of what I can help, feel free to send some my way if you think I can handle it (no coding) 13:58:49 I am planning to run it in my laptop also, so I will give feedback for gnome as well 13:59:24 psankar: that's cool 14:00:18 nmarques: well, if you have time to update packages, test stuff, triage bugs, etc. you're always welcome. It's up to you to choose how you want to help :-) 14:00:37 ah, I forgot to take action items and info 14:00:51 #info GNOME in Factory is up-to-date and (mostly) builds fine now 14:01:02 vuntz: im going to be testing the graphics apps no matter what :) 14:01:08 sorry for taking so long 14:01:12 #info we got some new apps again (most are waiting for legal review) 14:01:33 #info we got some maintenance releases, we could do more if people can help 14:01:37 vuntz, me and bugs don't work very well ;) I always end up embarassing myself when I try to help... but once I get some more 'bearing' with packages I'll help update packages 14:01:47 vuntz: make me in the updates 14:02:12 #info GNOME:Next got created; it will track 3.0 for now. It's not for end-users though (it will move to G:S:3.0 when it will be ready) 14:02:31 #info we'll push G:S:2.32 to Tumbleweed 14:02:48 #action psankar to install Tumbleweed and look for GNOME issues there 14:03:00 #action badshah400 to update glib2 in G:S:2.32 14:03:13 #action vuntz to copy latest 2.32 versions from G:F to G:S:2.32 14:03:21 #action vuntz to sr G:S:2.32 to tumbleweed 14:03:25 phew 14:03:30 I hope I didn't miss anything ;-) 14:03:37 vuntz: any specific packages for 11.3 updates you r thinking about? 14:03:54 metalgod, badshah400: we need to look at the various bugs 14:04:10 I know there's a big libwebkit update to do (for 11.1, 11.2, 11.3), though 14:04:31 it's a big big task, so I'm unsure how hard it will be :/ 14:04:35 i've been taking care of applications that loose functionality ie. empathy connection to msn, pidgin icq etc... 14:04:59 badshah400: do you want to try to do a simple update next time? 14:05:08 it's very important to keep "stable" users with all functionality ok 14:05:46 vuntz: yes, sure i can do the easy ones 14:05:49 cool 14:06:19 #info metalgod and badshah400 are willing to help for maintenance updates 14:06:29 #action vuntz to look for next maintenance updates to do 14:06:31 cool 14:06:44 so, let's move to the next topic :-) 14:06:53 right on time 14:06:59 * psankar has not done his AIs and feels shameful about it 14:07:02 the action items are always on the topic 14:07:19 well, not right now :-) 14:07:23 eheh 14:07:41 I shall complete my action items by this weekend for sure. was stuck in some busy things in dayjob . sorry. 14:07:45 last meeting: http://community.opensuse.org/meetings/opensuse-gnome/2010/opensuse-gnome.2010-11-25-13.45.html 14:07:51 that's right 14:08:08 so I did my AI, and sent the info to psankar :-) 14:08:12 :-) 14:09:03 so just to keep the old AI alive: 14:09:11 #action psankar Talk with the security team about gnomesu replacement for Yast 14:09:21 #action psankar ask ajorg (mono team) if someone can SR smuxi to G:Apps 14:09:42 actually, looking at some old minutes... 14:09:46 #action vuntz to discuss with legal team how to make the licensing-related bugs open by default 14:10:23 ok 14:10:26 anything else on AI? 14:10:52 I take it as a no :-) 14:10:59 :) 14:11:31 so we need to triage this: 14:11:33 https://features.opensuse.org/query/tag?tag=gnome 14:12:15 unfortunately, this lists features that are done too (?) 14:12:18 but yeah 14:12:30 ideally, I'd like some of us to do it together 14:12:40 vuntz, https://features.opensuse.org/308271 14:12:48 vuntz, I have packaged software to do this 14:13:12 nmarques: where is it? Did you sr it to G:A? 14:13:14 vuntz, but it has 1 problem... it only works with images, not with .xml stuff like we use :( 14:13:21 #info we need to triage https://features.opensuse.org/query/tag?tag=gnome 14:13:22 nmarques, that is AWESOME. it works with latest gdm ? 14:13:26 vuntz, I haven't submitted it because of that 14:13:28 nmarques: which .xml stuff? 14:13:29 psankar, yes 14:13:45 nmarques, cool. Thanks. 14:13:55 vuntz, the software displays a preview of the current wallpaper... if the wallpaper is something like IK.xml 14:14:04 vuntz, it blows up... that aside, it works pretty nice 14:14:24 vuntz, I haven't done python, but I can try to hack it ;) 14:14:25 ah 14:14:30 nmarques: well, we need to fix it 14:14:46 nmarques: did you file a bug for this? 14:14:48 it's a 10 min thingie for someone proeficient with python ;) 14:15:01 vuntz, yeah... no reply... ubuntu fan stuff 14:15:18 nmarques, that package is not in upstream git ? 14:15:27 nmarques, but just in ubuntu's repos ? 14:15:39 nmarques: let's talk about this after the meeting, if you don't mind 14:15:54 sure :) 14:16:01 https://bugs.launchpad.net/gdm2setup/+bug/682868 14:16:02 Malone bug 682868 in gdm2setup "default wallpaper, not an image..." [Undecided,New] 14:16:17 so, would people be available to do some feature triage day? 14:16:28 IF it is in a weekend, I can 14:16:28 psankar, https://features.opensuse.org/308271 14:16:30 to be honest, I'd expect it to only take a few hours 14:16:54 vuntz: yes, this weekend would be fine for me too 14:17:17 vuntz, I have one volunteer for helping with GNOME who actually is starting on GTK, anyone available to get him on the team's workflow ? :) 14:17:41 I probably can't help this week-end, fwiw 14:17:53 nmarques: can we discuss this in Q&A? :-) 14:18:04 nmarques: (just trying to follow the meeting agenda) 14:18:37 vuntz, sry 14:20:00 vuntz, weekdays are ruled out for me. unless they are after 1300 UTC 14:20:31 is there anyone who would like to take care of the organization of such a day? :-) 14:20:31 but after 1300 UTC any day should be fine I guess (unless there are some critsits / exceptions) 14:20:47 it's mostly just defining a date/time 14:20:57 * psankar proposes badshah400 14:21:56 i am not around next week, but if it is this weekend or something, yes I can do it I guess 14:22:30 badshah400: oh, it's just finding date+time, no need to even be available for the day :-) 14:22:58 #action psankar & badshah400 to find a date/time for the feature triage day 14:23:02 ::-) 14:23:05 vuntz: ok, then 14:23:06 :) 14:23:10 ok, next 14:23:14 vuntz, or is it a good idea 14:23:17 vuntz, if 14:23:21 yes? 14:23:29 ok 14:23:34 vuntz, you can propose the list of triage guideliens ? (what to pick / reject Etc.) 14:23:45 nmarques: the volunteer direct him to me 14:23:48 so that everyone can do it in their own time ? 14:23:58 i'll help him with packaging and gtk stuff 14:24:02 will not be coordinated but will get some more eyeballs 14:24:04 psankar: well, I'm afraid we don't have such guidelines at the moment, that's the issue 14:24:21 vuntz, oh okay. we will get the date and will let you know 14:24:30 metalgod, will do... I'll talk to you later and I'll introduce you to him... thanks for doing it :) 14:24:34 psankar: I think we need to do a first pass together, and that will help us define guidelines to do what you propose afterwards 14:24:47 nmarques: np 14:24:47 vuntz, neat 14:24:48 nmarques: so, ayatana? 14:25:06 about ayatana... the libs are no problem and there are 4 base libs already done 14:25:35 indicators, we can use a few without changes... others we shouldn't even look for them because they demand deep core patching (gnome-power-* and other wicked stuff) 14:25:47 I do have a couple of problems with one or another package 14:25:59 specially vala related, but it's on track 14:26:18 #info libs are no problem, and mostly done 14:26:27 the stuff that's done, works out of the box 14:26:42 needs polishing most 14:26:53 nmarques: what was your motivation to implement this stuff if gnome will move to 3.0 14:26:56 #info some indicators are already fine, but some should probably be ignored (require core patching) 14:26:59 even ubuntu will abandon that design ? 14:27:16 #info polishing is needed 14:27:19 metalgod, because I staying with GNOME2 for 1 or 2 more cycles 14:27:52 metalgod, old habbits die hard... panel for 12 years... hard to ditch now ;) 14:28:28 nmarques: and what about unity ? you will package it too ? 14:28:50 metalgod, I will try, but I will wait a bit to see what Adam will do on fedora ;) 14:28:57 iirc yeah he offered to. but wanted some packaging help as well 14:29:00 metalgod, and some of this libs will be required for it ;) 14:29:01 nmarques: ok sounds good 14:29:07 i meant nmarques not adam, btw ^ 14:29:26 currently there's only a group of people working this out 14:29:29 on Arch Linux 14:29:43 I'm also following their advancements and checking how they are doing it :) 14:30:00 vuntz, I'm done, it's not much to say really :) 14:30:17 vuntz, only 1 patch needed on GTK 14:30:21 vuntz, the one I told you about 14:30:30 right 14:30:32 vuntz, if that happens... then all of this will work 14:30:38 I want federico to look at it 14:30:42 vuntz, some indicators will not work, but those we don't need them 14:30:47 because GNOME offers better by default 14:30:59 that's the case for battery indicator and nm-applet 14:31:19 and ubuntu's solution for nm-applet replacement does rely on Intel's Connection Manager 14:31:23 nmarques: do you need any specific help? 14:31:49 vuntz, just maybe a fix on the package I sent for the list, and for reviewing my packages so that I know they are properly done 14:32:00 vuntz, that aside... I'm going cool :) 14:32:04 so, yeah, the usual stuff 14:32:12 okay 14:32:18 thanks, let's move to the next topic :-) 14:32:39 nmarques: the plan is to include in G:A or stay on G:Ayatana ? 14:32:39 * psankar sits straight 14:32:39 fcrozat: hop 14:33:00 i think fcrozat have some interesting news for us ;) 14:33:34 metalgod, some like base libs and some apps which don't require mess up... can go to G:A, the rest of the stuff that needs patching I would rather have a separate repo so I can provide the patched apps in parallel for users who want to check that out 14:33:49 metalgod, but I don't plan to merge it with openSUSE's default GNOME offer 14:34:00 metalgod, just as an option for whoever wants 14:34:14 nmarques: awesome :) 14:34:31 so, I've started to use source services to get GNOME3 (mainly gnome-shell) working on a "stable" platform ie 11.3 14:34:45 but it is still a bit problematic to get everything built 14:34:54 so, I'm going to do the work in two phases 14:35:12 first, branch packages from :Next to my gnome3 to get tarball release built against 11.3 14:35:23 build ISO based on that 14:35:45 and then, enable source service on packages, so the iso (and packages) can be update easily 14:36:14 the idea is to not brand the iso too much as openSUSE, since the plan is to be used by GNOME upstream folks too 14:36:18 (to test gnome3) 14:36:27 good news 14:36:49 I'll try to merge back the source service changes needed in specfile back to next 14:37:12 (additional build requirements and so on) so the work would not be lost when gnome3 is released 14:38:31 fcrozat: why don't you use 11.4m5 to build gnome-shell ? 14:38:48 metalgod: because too much things changed and aren't stable 14:39:05 it should be easier to build 14:39:08 ok 14:39:14 fcrozat, IIUC, is this for using latest GNOME 3 on 11.3 ? 14:39:15 #info the idea is to use use source services to easily provide a live image 14:39:18 it isn't that difficult 14:39:26 good to know that we will have a openSUSE livecd to get tested by GNOME upstream 14:39:35 #info we want the image to be usable by upstream, so it shouldn't be branded openSUSE too strongly 14:39:41 psankar: yep.. 14:39:48 #info this work will be merge with the G:N work 14:39:48 fcrozat, neat okay. thanks. 14:39:49 psankar: at least until 11.4 is released 14:39:53 got it 14:40:06 I might push updated drm / mesa stuff there too 14:40:19 but first things first :) 14:40:51 fcrozat: another question.... any plans to integrate opensuse OBS with gnome buildbots ? 14:41:09 metalgod: can't be done.. 14:41:21 metalgod: but if you want to donate a system to run jhbuild 14:41:27 there is no problem :) 14:41:42 fcrozat: ehehe too much power for my machine :) 14:42:09 fcrozat: similar to what people did in the past with deb's 14:42:30 #action vuntz to investigate if we can find some server that can be used as build bot for build.gnome.org 14:42:32 gnome buildbots aren't using packages but jhbuild.. what is needed is "raw power" 14:43:15 anything else on the GNOME 3 git packages? 14:43:25 no 14:43:35 good, next topic :-) 14:43:43 fcrozat, It may be a stupid suggestion but I have heard that icecream does distributed builds and uses multiple machines cpu power etc. may be it can help ? 14:44:10 psankar: it could.. we "just" need a "master" server somewhere 14:44:21 (and the icecream nodes would need to be on the same network) 14:44:38 fcrozat, yeah. 14:45:06 issue with M5: no banshee, tomboy, gnome-do; imo better coordination is required with mono repos so that such a problem can be avoided 14:45:24 #info with M5: no banshee, tomboy, gnome-do 14:45:51 vuntz: the gnome-keyring bug counts ? :) 14:45:57 that's quite a big issue 14:46:03 anybody willing to talk to mono people about this? 14:46:14 i can ask gabaug1 about banshee 14:46:36 and see if he want's to get 1.9.1 in factory 14:47:11 metalgod: the gnome-keyring issue is quite bad, but we need to be able to reproduce it :/ 14:47:33 metalgod: re banshee: unless 1.10 is released in February, we'll have to stay with 1.8 14:48:16 why not have the banshee build in gnome:apps (it is our default player) instead of its own repo (which upstream can use as usual)? 14:48:22 vuntz: banshee development version have been very stable and since banshee is developed "in-house".... 14:48:26 but yeah i agree with you 14:48:31 badshah400: the banshee people like it this way 14:48:45 metalgod: banshee is not developed "in-house" 14:48:46 vuntz: that's 2.0 and not 1.10 you are talking about :) 14:48:57 it's a community project, with contributors from various distros :-) 14:49:06 vuntz: right :) 14:50:22 ok 14:50:35 vuntz: put the action on me 14:50:39 mono apps 14:50:43 ok 14:50:58 #action metalgod to find a solution for the mono apps not being in M5 14:51:03 anything else? 14:51:16 banshee failed to build on factory last night 14:51:30 vuntz: the packagekit updater applet issue 14:51:31 as far as I can tell, things are mostly fine. There are a few things that need to be polished, but no big issue 14:51:33 vuntz: we deal with the theme too ? 14:51:52 badshah400: I'd like to see if the new PackageKit helps 14:51:53 badshah400: what's wrong with the updater ? 14:51:58 badshah400: I have 0.6.11 coming soon 14:52:33 impressive PK from factory updates packages from all repositories 14:52:45 thanks for who did that 14:53:44 metalgod: that's the issue; it is a BIG change from 11.3 and needs to be mentioned in the release notes in capital letters to make it clear to everyone 14:53:59 metalgod, mine seems to be following the repo priority ;) 14:54:16 badshah400: i think it's pretty cool 14:54:34 this way deals with 11.4-updates and packman packages at the same time 14:54:38 which makes sense 14:55:14 finally PK does something useful besides updates 14:55:34 metalgod: it deviates from the vendor stickiness policy of openSUSE 14:55:40 bug 637764 14:55:42 openSUSE bug 637764 in openSUSE 11.4 (GNOME) "Packagekit updater applet in GNOME sees upgrades/updates from all repositories irrespective of vendor changes" [Major,New] https://bugzilla.novell.com/637764 14:56:05 badshah400: I forgot. Does pkcon works correctly? 14:56:32 badshah400: the old behavior was only to search for updates and perform updates 14:56:49 i don't think it's bad but look 14:56:56 vuntz: i don't know at least with the latest mileston 14:57:18 if you have G:S:2.32 and packman PK will try to update your packages that have a version lower than the current repositories 14:57:37 vuntz: i will get back to you with some testing later then? 14:57:54 badshah400: cool 14:58:10 metalgod: re "we deal with the theme too ?" 14:58:16 metalgod: what did you ean? 14:58:18 mean 14:58:21 metalgod: i am complaining about the fact that pk-applets behaviour has gone from doing zypper patch to zypper up 14:58:43 vuntz: mean if we decide which artwork (theme and icons) goes to gnome 14:58:49 #info there's some discussion on https://bugzilla.novell.com/637764, a change in the behavior of the packagekit updater 14:59:03 #action badshah400 to check if pkcon exhibits the same behavior as the updater applet 14:59:18 metalgod: where can we see the proposed artwork? 14:59:23 metalgod, I agree with you in one way... but I also hold reservations 14:59:30 vuntz, hold, I link 15:00:01 http://karl-tux-stadt.de/ktuxs/?p=2677 15:00:01 vuntz: someone is already getting new stuff on factory 15:00:05 the grey one is for GNOME 15:00:06 but gnome stuff is still on 11.3 15:00:10 I find it very depressing 15:00:11 :( 15:00:30 also while we are on theming, who is maintaining sonar since jimmac left? upstream or us? 15:00:48 vuntz, Gnokii also keeping sonar 15:01:04 badshah400: i think mmeeks can give you a help with PK 15:01:06 let's move to the next topic and keep discussing this :-) 15:01:21 #info should we move to the new theme? http://karl-tux-stadt.de/ktuxs/?p=2677 15:01:28 I believe sonar is in upstream . no ? 15:01:35 badshah400: we are maintaining sonar 15:01:44 psankar, upstream is clearlooks I think 15:01:46 IOW, jimmac still mainains it ? 15:02:02 vuntz, I would suggest we upgrade default icon set to Faenza 15:02:09 nmarques, what I mean is, the theme is not in suse repos but still maintained by jimmac 15:02:09 vuntz, I can maintain it if needed 15:02:10 well 15:02:12 psankar: no, jimmac doesn't maintain the opensuse theme stuff anymore 15:02:18 vuntz, oh okay 15:02:25 we should stick with this theme for 11.4 15:02:28 so, let's first discuss the background 15:02:29 and get a new one for 12.0 15:02:33 because of GNOME 3.0 15:02:34 gnokii joined us for that :-) 15:02:44 nmarques: to change it not has something todo with the respect of jimmacs work so plz, I also like faenza more 15:02:50 brb 15:03:02 gnokii, jimmac isn't here... we are 15:03:30 nmarques: that ppl not are here have nothing to do with not respect there work! 15:03:35 gnokii, and blind allegiance won't take us far when our desktop is ugly as hell, specially with icon sets ;) 15:03:41 please please please 15:03:41 * mmeeks emphatically can't do everything and PK/zypp was just a rescue-from-the-flames scenario I've moved on from ;-) 15:03:51 metalgod: AFAIR there was some intel-ite who was maintaining that now, cf. the git log. 15:03:53 can we just focus on the background right now? :-) 15:04:00 vuntz +1 15:04:30 gnokii: my main worry about this background is that it's the upstream KDE one 15:04:51 (and well, the grey is depressing, but that's something else :-)) 15:05:05 mmh kde has an celadon one now 15:05:19 vuntz, gnokii nmarques : I am a bit lost. What is the proposal ? we should change the theme ? or wallpaper ? or both ? 15:05:33 psankar, ignore my previous remarks 15:05:46 psankar: the proposed background is http://karl-tux-stadt.de/ktuxs/?p=2677 (left one) 15:05:47 psankar: the problem is the theme, sonar has a dark green in it 15:05:59 vuntz thas was a long time ago 15:06:07 give me a fe seconds 15:06:16 * psankar waits for gnokii 15:06:31 * nmarques pulls the whip and grins 15:07:42 fwiw, something to consider for GNOME theming: 15:07:49 vuntz, so if there is nothing else, we can close the topic 15:07:50 we could switch to gnome3 theme, for gtk2 ? (if it is fixed correctly for metacity and gtk2) 15:08:08 for 11.4+1, when we'll have GNOME 3, I think we should keep the upstream theme (there's a big push upstream to have one theme used in all distros) 15:08:33 so my personal opinion is that, except maybe for the background, we should keep the current theming for 11.4 15:08:38 vuntz, there is a sonar for gnome-shell 15:08:48 psankar: we're waiting for gnokii :-) 15:09:01 http://img.susepaste.org/59475213 15:09:08 * psankar looks 15:09:18 nmarques: I know, I packaged it. But still, we should move to the upstream theming when we get GNOME 3, imho 15:09:40 that is what KDE wanted, so that wallpaper now contains also colors they are used in sonar 15:10:24 vuntz, gnokii I would prefer a little more brighter wallpaper. but artists know the minds of people better than programmers. so I leave it to you :-) 15:10:50 btw, my current wallpaper is : http://eng.hebus.com/image-208954.html (so I may be biased by my current wallpaper) 15:10:56 psankar the fun is the grey one was loved from many ppl its in right now 15:11:13 gnokii: my issue is still that it's based on the upstream kde thing 15:11:27 gnokii, oh okay. 15:11:47 gnokii: so why couldn't we do the same thing for the upstream gnome background? 15:11:48 may be we can have a wallpaper voting ? ;-) 15:11:56 vuntz no it should not the upstream from KDE (nuno dont like them) 15:12:14 vuntz but for make sure its not we can ask will 15:12:20 mmeeks: ok, we were talking about the current behavior which is a bit different from the behavior on 11.3 15:12:32 which is http://git.gnome.org/browse/gnome-themes-standard/tree/themes/Adwaita/backgrounds/stripes.jpg 15:12:42 err, http://git.gnome.org/browse/gnome-themes-standard/plain/themes/Adwaita/backgrounds/stripes.jpg 15:12:48 mmeeks: imo makes sense the current behavior that is tracking all repos instead of tracking only the updates 15:13:53 vuntz who created that? 15:14:01 vuntz, that looks better to me 15:14:39 i love the background http://karl-tux-stadt.de/ktuxs/?p=2677 15:14:41 gnokii: jimmac 15:14:43 very futuristic 15:14:51 but it doesn't deal with sonar :/ 15:15:12 psankar: I also like that one more, but KDE needs for there theme more differences in the wallpaper with lights 15:15:14 metalgod, I find it very depremoted of 'life', like a 'walking corpse' 15:15:40 gnokii, oh okay 15:16:10 nmarques, I suggest not to speak in such a way (corpse), especially when the creator is around :-) (even otherwise also) 15:16:11 metalgod, my opinion is that our artwork should favor joy and fun... and not be melancholic or have a 'sick' look 15:16:16 nmarques: well i see your point... live colors are much nicer 15:16:17 vuntz can the gnome team live with the celadon one from KDE? 15:16:25 but the background feels very futuristic 15:16:55 gnokii: http://ivan.fomentgroup.org/blog/2010/08/12/distribution-branding-and-stripes/ indicates that the wallpaper is the kde one 15:17:00 nmarques: well ubuntu artwork is dark and melancholic too... reminds me of macosx 15:17:02