Sounds great, should we start establishing a todo list for this merge? What can be done on our side right now?
I guess I'll start isolating the hardware detection code into another application. What should be done with the plugin versioning? Diogo Ferreira playerX On 3/31/07, Dennis Kasprzyk <[EMAIL PROTECTED]> wrote:
Hi, as long we don't know what will happen to the community merge, I would like to share with you my idea, what could do now. 1. Me make an official statement that we merge the core and that we are not a compiz fork anymore. We could also add that we TRY to merge the communities too. (Maybe we should also change the name to "Berly a compiz community"). 2. We create a 0.2 beryl repo (not sure that we can split out only the 0.2 branch) for fixes to this stable tree (It should also be in the announcement that we will still provide bugfixes for the stable tree). 3. We move that what is beryl 0.3-git now to a readonly legacy directory. 4. We create a beryl-plugins / beryl-plugins-unstable / beryl-plugins-unsupported repositories with all our already ported plugins. The compiz plugins that are still a part of the compiz fdo tree should not be hosted in these directories. We should move them in if david decides to move them out of the fdo tree. (Every developer can still have his devel versions of the compiz plugins in the user git directory.) 5. We port our applications (beryl-manager ...) 6. We should also announce that each developer is free to choose a own plugin license, but it has to be a free license. 7. We finish libbs and port beryl-settings to it. (Discussion about the internal option handling is needed here. See current discussion on the compiz ML) 8. We create a beryl application that does the syschecks (that are currently included in beryl) and starts compiz with the right options automatically. 9. We reset trac and add a 0.2 legacy category and new beryl 0.3categories to it. What do you think about it? Dennis _______________________________________________ beryl-dev mailing list beryl-dev@lists.beryl-project.org http://lists.beryl-project.org/mailman/listinfo/beryl-dev
_______________________________________________ beryl-dev mailing list beryl-dev@lists.beryl-project.org http://lists.beryl-project.org/mailman/listinfo/beryl-dev
