John:
John Spackman-3 wrote > I don’t agree that npm is better at version management than Git - IMHO > it's the opposite. What do you mean by discoverability? The user still > has to “discover" the contrib on a webpage somewhere to find out that they > want to use it. Yes, exactly. If you have a registry of contributions which you can filter by the intended target (for example "qooxdoo-4.0.X"), you can "discover" all the contributions that work with that target. That's how the current contrib registry works, but the process of updating this registry is so convoluted that hardly anyone uses it. That is my point. Git and npm are not directly comparable, as you know - Git is a source control tool (version management at the file level), and npm is a package manager (version management at the package level). As I said, all I want to do is to publish new contribs and update old ones in a simple, one-step process, and provide versioned packages that are fed into the registry. John Spackman-3 wrote > The only advantage I can think of is if you want to automatically make > sure that your app is using the latest version of all contribs - however > this can be dangerous because of potential compatibility issues (esp as > many contrib authors do not keep their contribs up to date with current > Qooxdoo releases). Personally, I would rather update them individually. I would not want automatic upgrade, but there are good technologies to prevent this (e.g. semantic versioning and versioned dependencies in package.json). That is what I mean with state-of-the-art -> the problem has been solved already - we don't need to reinvent the wheel. And you are right - the number of contribs we are talking about is very small and might not warrant such lengthy discussion. But contrary to those who think qooxdoo's time is over my own experience is that it is a rock-solid foundation for thick web clients. On top of this, a healthy contribution ecosystem could be established, but this will only happen if maintaining contribs doesn't involve a process that I, at least, find rather convoluted.... -- View this message in context: http://qooxdoo.678.n2.nabble.com/qooxdoo-contrib-again-tp7586131p7586179.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
