Hi John,
John Spackman-3 wrote > But why do we need a new mechanism? As opposed to just a web page and a > Git/SVN url? > > As I understand it, the need for a custom contrib mechanism was only > because there was (is?) a goal to not require the developer to have Git, > SVN, or any other kind of VCS installed - but Qooxdoo has no problem with > having other prerequisites (e.g. python, node and npm) so what’s the > problem with one more? Especially as many devs will have Git or SVN > installed already. The main reason is discoverability and version management. Of course, you can use any location you want as long as there is a zip file that can be downloaded. You can also inform through this list that you have published a new contribution or updated an existing one. But not everybody is a subscriber, and not everybody wants to touch their config.json each time a small bug is fixed. There is a state of the art for central registries and version management and it is implemented in systems like bower or npm. They take care of these things and they are simple to use - that is why they are so successful. All you would need to do is to integrate them into the contrib registry, for example, and get rid of the cloning and pull request stuff. I would shut up and be happy. Cheers, C. -- View this message in context: http://qooxdoo.678.n2.nabble.com/qooxdoo-contrib-again-tp7586131p7586173.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
