Hi Christian, interesting point of view. It surely would motivate contrib authors if all such automation would exist and I'm not denying the usefulness of such an infrastructure. But if I would be a contrib author (which I am not) I would also welcome as much freedom as I can get, i.e. I wouldn't need that.
IMO the contrib demo browser is a good tool, but it also brings obligations with it. For example a rigid demo directory structure. Furthermore there is a dependency between us and you, which shouldn't be there. If you want to change your demo you should be able to do so and publish it right away. There should be no established process, where you have to wait for a cronjob or the like. You've mentioned npm: I think the success of npm and Node.js lies in it's simplicity, there is not much which could be removed because barely anything is superfluous. Also keep in mind, that we have to balance our time between moving the framework itself forward and amongst other things building an infrastructure for contributors. In my mind we attract more people with a great framework itself than with a great infrastructure around it. The latter is without doubt important but the former is crucial. To sum up in the context of contribs: I would rather remove cumbersomeness than write code for more convenience. :) Best Richard ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/NeoTech _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
