To Gnome or not to Gnome

Yioryos Asprobounitis mavrothal at
Fri Mar 26 04:10:02 EDT 2010

--- On Thu, 3/25/10, Bernie Innocenti <bernie at> wrote:

> From: Bernie Innocenti <bernie at>
> Subject: Re: To Gnome or not to Gnome
> To: "Martin Langhoff" <martin.langhoff at>
> Cc: "Yioryos Asprobounitis" <mavrothal at>, "Devel" <devel at>, "Fedora OLPC" <fedora-olpc-list at>
> Date: Thursday, March 25, 2010, 10:19 PM
> On Thu, 2010-03-25 at 09:33 -0300,
> Bernie Innocenti wrote:
> > More than protecting them, which is very hard or
> impossible, I'd add an
> > option to reset them to defaults without the need to
> reflash.
> It just occurred to me that GNOME actually provides some
> ways to
> lock-down settings, useful for implementing kiosks or
> internet cafes.
> Guess who wrote the documentation for it? I guess we
> already have the
> internal expertise :-)
> Unfortunately, the only feature useful to us seems to be
> blocking the
> panel. It would be cool if Nautilus offered an option to
> prevent
> deleting dot files.
> Perhaps the same could be achieved with ACLs? Or chattr -i?
> A smart and
> determined user could disable these mandatory protections,
> but we only
> need to make it fool-proof not hacker-proof!

I really think that the Gnome desktop is a valuable addition for the XO but mostly for the end user. Is not a coincidence that people use it. So openness and robustness should be implemented there too.
If the problem is the video driver for example, this is what it should be fixed, not hampering its use.
I can see blocking as a temp measure but only in combination with an increased gnome-bug-fixing priority.
Any user can mess-up its installation. Let's not forget that the usual "fixing" for sugar is... reflashing. But here we are talking bugs/inadequacies. Bug-fixing should be the way, instead of blocking features and Sugar-robustness claims.

> -- 
>    // Bernie Innocenti -
>  \X/  Sugar Labs       -


More information about the Devel mailing list