Hi, I'd like to propose a simplification to our current repo structure, based on the way development is going. It seems like a lot of the structure of the project was impacted by the political development of compiz and this is proving to be a high barrier to entry to people who want to get started on compiz.
1. fold libcompizconfig into core: I can't think of anybody that uses the legacy gconf and ini plugins now. compizconfig provides this functionality just fine. We would still have a libcompizconfig library for the backends to link to and for external applications to use to configure compiz. It also means that we can drop some of the behaviour that the gconf backend used to track the gconf plugin, such as copying keys around on profile change. 2. fold the backends into core under gnome/ and kde/ . Again, there is no need for more repositories for these things. We already maintain the decorators as part of core, the backends can be done in core as well. 3. fold plugins-main into core, move plugins-extra and plugins-unsupported into plugins-community. The main plugins are what distributions are shipping with, so keep them. The extra and unsupported plugins are community things. 4. fold compizconfig-python into core: There isn't any reason these day to ship python bindings separately. The individual plugins will still remain in their own repos. This is useful because it allows those components to have different release schedules and development methods. For everything else, developers should be able to branch one project and get started right away. If nobody objects to this, I'll start doing it within the next few days. Cheers, Sam -- Sam Spilsbury _______________________________________________ dev mailing list [email protected] http://lists.compiz.org/mailman/listinfo/dev
