In search opinions on GNOME Games module games
The GNOME Games maintainers, Andreas and I, are planning to deprecate one GNOME Games game which is unpopular and difficult to maintain during the 2.18 release cycle and replace it with a more popular game with better, more maintainable code. To this end, we are seeking input from our users to decide which game to remove and also opinions on which game to include. This is also a PR opportunity - a way to directly involve end users in driving a very visible change to their desktops' features. So, we would like to get this message out as widely as possible. Feel free to post this on any forum or mailing list which has a majority of GNOME users on it. Users interested in participating in driving this decision can do so at: http://live.gnome.org/GnomeGames/NewGamesPlan signature.asc Description: This is a digitally signed message part ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Clarius
The default theme for 2.16 has been changed from Clearlooks to Clarius. This is apparently just Clearlooks without the glossy scrollbars. Rant the first: This change was made on August 8th: http://cvs.gnome.org/viewcvs/libgnome/schemas/desktop_gnome_interface.schemas.in?rev=1.26view=log That's after every freeze we have except the hard code freeze. And yet, I saw no discussion or announcement on d-d-l or the documentation list. Yes, even the name of the default theme is a big deal. What is so hard about keeping us informed? Rant the second: What's the point of the name change, really? The Clearlooks theme isn't even in CVS anymore: http://cvs.gnome.org/viewcvs/gnome-themes/gtk-themes/Clearlooks/ So we're only installing Clarius with gnome-themes. How does dropping the glossy blue scrollbars constitutes a name change? Those glossy blue scrollbars weren't even in the old Clearlooks that I originally pushed through as the new default theme some release cycles back. I'm going to coin a new term: key churn. This is when people make frivolous and unnecessary changes to GConf keys or their default values. It sucks for large deployments. Gnome is bigger than your personal desktop. Rant off. -- Shaun ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Contribution
Maxim Udushlivy wrote: Random thought: opposition to a commercial software project is a capitalism while opposition to a community-based foss project is sometimes like a revolt. :) Yet another thought: I think you certainly need to reorient Gnome from politics towards technology. Such things as 10x10 and spreadgnome.org looks very political. But gnome-tech.org for example is much better I think. Software-as-a-servant, not software-as-an-idol. And about that HIG: guidelines have a tendency slowly but steadily to transform into constraints. It's much better to have principles instead of constraints. And that principle about Gnome simplicity - it's good, but it should not be achieved at the expense of functionality. Being simple does not mean being less functional. For example credit card is quite simple, but its functionality surpass imagination ;) ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Clarius
Hey, Shaun McCance wrote: I'm going to coin a new term: key churn. This is when people make frivolous and unnecessary changes to GConf keys or their default values. It sucks for large deployments. Gnome is bigger than your personal desktop. I don't really care too much about the name change, but what I do care about is the migration story between themes as new engines/icons/whatever are dropped in and out. This stuff isn't as smooth as it should be - hopefully Calum can provide details of what currently happens [we documented this for an ARC case recently]. Glynn ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Clarius
On Tue, 2006-08-29 at 10:01 +1200, Glynn Foster wrote: Hey, Shaun McCance wrote: I'm going to coin a new term: key churn. This is when people make frivolous and unnecessary changes to GConf keys or their default values. It sucks for large deployments. Gnome is bigger than your personal desktop. I don't really care too much about the name change, but what I do care about is the migration story between themes as new engines/icons/whatever are dropped in and out. This stuff isn't as smooth as it should be - hopefully Calum can provide details of what currently happens [we documented this for an ARC case recently]. I don't care about the name change out of some phonetophilic adoration of the word Clearlooks. I care because of the problems it introduces. Scenario 1) I have, at some point, explicitly set my theme to Clearlooks, rather than getting Clearlooks from the GConf default value. I upgrade to Gnome 2.16. What happens? Interim 1) I utter some choice words about the ugly boxiness of the default GTK+ rendering. But I'm pretty clever, so I go to the theme manager, find Clarius, and switch. Clarius is now explicitly set as my theme in GConf. Scenario 2) I go to use another machine that's mounting the same NFS home directory, or is otherwise getting the same GConf values. This machine is running Gnome 2.14, which doesn't include Clarius. Interim 2) I utter some choice words and post a flame to Slashdot and/or OSNews. I go to the theme manager and change my theme back to Clearlooks. Scenario 3) I go back to do some work on the machine that's running Gnome 2.16. See scenario 1. Friends don't let friends churn keys. -- Shaun ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
