Hi, I know that this is on the agenda (talked about Andreas about this before), but I want to press the point again since it is fitting the current discussion: I agree with flj that I don't think contribs should be included too quickly into the framework. After all, being included in the framework means having to support it by the core team, and that's not possible for most of the contribs.
On the contrary, what I would like to see is a "contrib-forge"-like infrastructure for the contribs. Some sort of web application where one could manage the contribs, where all information (Description, API documentation, wiki, online-demo, version, compatibility, etc.) is in one place and can easily be searched and displayed. This information could all be generated from the Manifest.json. This would make the contribs more transparent, accessible, easier to maintain, and would help "marketing" them better. I find it cumbersome to manually update the wiki with contrib information after working on the code, since I hate doing things that could be automatically be generated from information in my source. The work on the contribs would feel more "appreciated" this way. C. -- View this message in context: http://qooxdoo.678.n2.nabble.com/speed-of-development-tp5168583p5176400.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
