Hi Fritz! On Fri, 2009-12-18 at 10:44 +0100, Fritz Zaucker wrote: > Of course, a bit more structure below qoxxdoo-contrib would make it more > feasable, e.g. > > qooxdoo-contrib/Bugs > qooxdoo-contrib/0.7 > qooxdoo-contrib/0.8 > qooxdoo-contrib/1.0 > > (compatibility is the issue). > > If I remember right, there is a Bugzilla enhancement request about that, > already.
Hmm, maybe you mixed something up? From a contribution's point-of-view (and that of its maintainers) IMHO it is still preferable to have an entire contribution (i.e. including all its versions) physically live in one folder. What you are absolutely right about, though, is to make the orthogonal aspect (i.e. framework compatibility) accessible much more easily from a user's perspective (e.g. through a web interface). This means it doesn't have to be how the code repository is organized. This, as well as some other valid points (Bugs area), is something we started to think over already and plan to figure out (with the contributors) early next year to further improve the qooxdoo-contrib infrastructure. There are parts in qooxdoo-contrib currently to allow for a maximum of collaboration (like bug fixing) and transparency. Well, that could benefit from a more radical separation of the concerns, also given that the contribs themselves are going to flourish and qooxdoo-contrib to grow, right. ;-) TTYL, Andreas -- Andreas Ecker Project Lead http://qooxdoo.org ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
