Hi Stefan, my issue is strictly about maintaining and distributing contributions in a way that is not as cumbersome as the current process (having to clone the registry, send pull-requests, create checksums, wait for merging) that has no added value at all for me as developer. Updating my contribs should be a one-step process, just like it is when using npm. I am not advocating to change the way qooxdoo is distributed, that is a separate issue.
C. -- View this message in context: http://qooxdoo.678.n2.nabble.com/qooxdoo-contrib-again-tp7586131p7586167.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
