On Wed, Nov 14, 2007 at 09:45:55PM +0100, Simon TRENY wrote: ... > As I said, imo devs should agree on a common project. Now, if a new > sub-project doesn't respect the project's definition or if it is > redundant with an existing project, it should not be a part of our > common project. That would be the rule to apply with new sub-projects. > For existing projects, the problem is more complex, as you can't decide > and say to a developer that his own project no longer belongs to our > project. But I think that sooner or later, we will have to make > choices. There is no good reason to have three different toolkits in > the same project, as there is no good reason for several video players > or several image-viewers. An application should follow the guidelines > set by the project-definition, and there should not be two > applications/libraries with the same purpose belonging to the same > project. >
Thanks! I perfectly agree with what you said above, finally some unity (at least a wish for one). A desktop environment shouldn't have multiple choices for the same thing.. imagine M$ having two web browsers, or two media players, then windows would just suck (redundant sentence, isn't it?:p) ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
