On 01/11/2012 05:05 PM, panyasan wrote: > Just the idea of a central catalog and the ease of use. Of course, given > that the config.json inform the generator about libraries, it makes little > sense so install contribs like you install npm modules, so generate.py > install XYZ is not needed. But I liked the idea of "generate.py publish XYZ" > ;-) > >
>>> This would also allow to remove >>> older, non-functional contribs automatically without cluttering the >>> "available contribs" page, thus also making clear how many functional >>> ones >>> really exist. >> How could that be? >> > For example, contribs that are not compatible with the current release > should not even appear in the "available contributions", just as in the > contrib demobrowser. Not all contribs have demos, so the demobrowser is not > always enough. I want to be able to flag my old an non-functioning contribs > in the Manifest, so they automatically disappear from view and nobody bugs > me about them anymore ;-) > > Ok, I think I'm getting at it. You envision some kind of structured information that is maintained with the contribution itself (lets call it its "catalog entry"). And you want a convenient way of pushing this information to the online catalog. And the information should cover e.g. which versions you want to be 'public' (as opposed to exposing all the <version> subdirectories which you currently have in qooxdoo-contrib). Is that right? - I'm fine with having a convention of maintaining contrib meta-data in a dedicated file with certain structure. - I'm fine with generator support to push this information to the online catalog (though maybe not in the first step :). - I think the filtering of contributions for any particular qooxdoo version should be done on the contrib catalog side; the current release could be the default. But I think you have to allow for people using older qooxdoo releases to filter for their release version as well. - As for old and dysfunctional contribs, there should be a means to retract them from the catalog entirely. - As for old and dysfunctional *versions* of a contrib, this should be apparent from the particular version itself (e.g. by setting the Manifest.json/info/qooxdoo-versions to '[]'). - But I wouldn't want to give up on the contrib directory structure we have in qooxdoo-contrib, also for the download actions. > >> - Finally, even an automatic test suite would be possible, alerting >>> contributors about failures. This would force contrib developers to >>> better >>> maintenance and improve the quality of the contributions (or remove them >>> from the list if they fail). >> I'm not sure I understand what you mean. One issue in the area of >> general tooling I see is the Contribution Demobrowser. What would an >> automatic test suite do? It would run through the contribs and run their >> individual tests, right? Because the automatic test suite can only run >> tests the developer has written, right?! But that would be quite a >> topic, as we would not only need 'generate.py test' but also >> 'generate.py test-run' in each contrib, right?! >> > I know this is very complicated and is certainly not at the top of my > priorities. I was brainstorming about ways of inducing developers like > myself who are lazy and need some nudges in order to keep their (unpaid) > work in high quality. An automatically generated email saying "your contrib > XYZ has no unit tests, please provide them" and later "your contrib XYZ has > failed the tests with qx version x.y even though the manifest file says it > is compatible" would certainly help. But that's really just a fantasy, > nothing that is urgently needed. Ok. Keep it in the back of your mind, so we might address this in a second or third step :). T. ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
