On Wed, 2007-04-25 at 20:20 +0100, Andrew Sobala wrote: > My personal reaction is that it would be more useful to have a GNOME > "distribution" (such as something jhbuild or garnome derived) which can > act as a testbed of next-generation technologies - and where people can > happily make different modules work together, or swap out the panel for > something else, for example - than to take a selection of modules and > put them in another formal release set.
That is really all this release set is. A signal to jhbuild and garnome that they should have these in the build. It would be an easy to reference list with pointers to all the projects home pages and how they fit into GNOME. It would also be nice to get updates for every release. > Another release set opens a real can of worms - what's the criteria for > inclusion? Are we creating an artificial barrier that a cool project has > to get over before it is taken seriously? Would any degree of conformity > to a 6-month cycle would be expected - this could just be a pain for > modules that want to focus on breaking everything together while they > still can. We are here to figure out what those criteria are. The point is not a conformity to the 6 month cycle but a forward moving process that would eventually get the project into the more formal releases. Most of it is just getting all the information into one spot so projects can start to work together even before they become part of the release. I know this happens organically but it doesn't hurt if we organize it more. Freedesktop has shown if you publicize projects in one place there is a higher experimental and adoption rate. There is also more discussion instead of having invisible projects that only a few people hear about. -- John (J5) Palmieri <[EMAIL PROTECTED]> _______________________________________________ desktop-devel-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/desktop-devel-list
