Darren Kenny wrote: >Is there a definition of that is acceptable as a core GNOME application - other >than it's based on consensus? I think we are badly in need of a definition that >defines the needs of the core GNOME Desktop? > > There is no doubt we need to establish a definition of what constitute GNOME core application/platform and create some layered modules which are loosely coupled rather than tightly coupled dependency. In approach currently, because there is a nice application, we pull in the the whole dependency. And in the next release, someone write any nice application with plaftform X, we pull in another platform. In no time at all, GNOME will become so overly bloated in terms of foot print and performance. Of course, we can't define what platform can go in or not go in until we the community define what constitute the core apps/platform the GNOME release is made up of. But who are the people can/should establish this?
-Ghee >That's just my thoughts on things... > >Thanks, > >Darren. > >Elijah Newren wrote: > > >>Hi everyone, >> >>As per the release schedule (http://live.gnome.org/TwoPointFifteen), >>it's time to heat up the module inclusion discussion. So, time to >>flame, argue, etc., etc. this week and see if we can reach consensus. >>The release team will try to meet next week about new module decisions >>with community input up to then so that the new modules can be >>announced in time for module freeze. We're actually optimistic enough >>(deluded enough?) to think we can make that deadline this time. :) >> >>So, to start of the discussion, the proposed modules AFAIR are: >> * orca (as a replacement to gnopernicus) >> * alacarte >> * gnome-power-manager >> * Tomboy >> * Gtk# >> >>There's one additional issue to address as well: >> * Okay to have desktop modules depend on gtk# bindings? >> >>Here's my biased guess (feel free to dispute) at where things stand: >> >>orca appears to be an uncontroversial choice with strong support, and >>which even the gnopernicus team is supporting. (There have been a >>number of threads and lots of comments; >>http://mail.gnome.org/archives/desktop-devel-list/2006-June/msg00009.html >>seems like the best overview) >> >>There have not been many comments on alacarte; just a couple notes >>that looked like preliminary reviews in the thread where it was >>proposed >>(http://mail.gnome.org/archives/desktop-devel-list/2006-April/msg00305.html). >> So we definitely need thoughts and comments from the community. >> >>gnome-power-manager seems to have lots of support and it appears it's >>getting picked up by all the major distributors (or already has been >>for some time now). Didn't find a clear overview email and there's >>been lots of threads. I guess >>http://mail.gnome.org/archives/desktop-devel-list/2006-April/msg00366.html >>works. >> >>Tomboy was proposed here: >>http://mail.gnome.org/archives/desktop-devel-list/2006-April/msg00253.html. >> Comments were very positive for the most part, but there are gtk# >>dependency issues that need to be resolved first (see e.g. >>http://mail.gnome.org/archives/desktop-devel-list/2006-April/msg00332.html). >> >>gtk# was proposed here: >>http://mail.gnome.org/archives/desktop-devel-list/2006-April/msg00457.html. >> There was one big (IMO) issue, mentioned in the thread (namely, >>wrapping API which had no stability guarantee) >> >>And the big question: We currently allow desktop modules to depend on >>the pygtk bindings, but no others. Should we extend that to include >>the gtk# ones (assuming, of course, that gtk# is added to the bindings set)? >> >> >>Cheers, >>Elijah >>_______________________________________________ >>desktop-devel-list mailing list >>[email protected] >>http://mail.gnome.org/mailman/listinfo/desktop-devel-list >> >> > >_______________________________________________ >desktop-devel-list mailing list >[email protected] >http://mail.gnome.org/mailman/listinfo/desktop-devel-list > > _______________________________________________ desktop-devel-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/desktop-devel-list
