GNOME as the default desktop (was Re: Fedora Board Meeting Minutes - 2010-12-06)
"Jóhann B. Guðmundsson"
johannbg at gmail.com
Wed Dec 15 17:56:08 UTC 2010
On 12/15/2010 04:51 PM, Christoph Wickert wrote:
> Some examples of what this means:
>
> * Desktop SIG defines the default GTK theme and hardcodes the
> theme as dependency.
> * Desktop SIG defines gnome-icon-theme as the default icon theme
> and hardcodes it too.
> * These two pull in other gnome packages. It is impossible to
> install a desktop without having fedora-gnome-theme or
> gnome-icon-theme
> * Some more examples of painful dependency bloat:
> https://bugzilla.redhat.com/show_bug.cgi?id=depchain
> * Removal of hal-storage just a few days before beta freeze.
> * Removal of the legacy icon names shortly before beta freeze
> resulting in many missing icons.
> * Removal of the notification area which and the resulting API
> changes in libnotify 0.7.0 breaks all other desktop bug
> gnome-shell.
> * Change from Nodoka to Clearlooks. Many people objected, after
> FPL spoke up the GNOME SIG promised to revisit the decision and
> keep us informed. This did not happen.
> * Black notifications that looked like a Ubuntu ripp-of. Again
> many people objected, but again GNOME SIG did not care.
Is this not something FESCO can deal with and act upon?
> And now there is
> http://nicubunu.blogspot.com/2010/12/second-class-citizens.html
>
Yeah this came as a bit surprise and the Design meeting log are really
interesting and bit revealing as well.
From the looks of it is time for a Design SIG to emerge to prevent
corporate monopolist.
> This really makes me wonder if Fedora is a distribution to work on for
> people who are not using the one and only true desktop that must not be
> named but called "the Fedora desktop" [1].
Yeah that's a question that every contributor in every corner of the
project needs to be asking himself at this moment and perhaps a meeting
between the contributors and the followers of all spins of every purpose
with equal rights *vision* in the community needs to be held and the
matter discussed as in what they can do within the project or whether
they unite and fork off or find a new home within another distro.
JBG
More information about the advisory-board
mailing list