<br><br>On Wednesday, October 3, 2012 1:04:45 AM UTC-7, Jesper Louis Andersen wrote:<div> </div><blockquote class="gmail_quote" style="margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;">> I couldn't disagree with that much more ... npm/Node.js is cluttered with
<br>> packages of dubious quality that are not maintained in the slightest, and
<br>> while this "Wild West" they prefer may seem exciting, I do not think it
<br>> bodes well for the long-term stability of projects that depend on these
<br>Two ideas spring to mind immediately.
<br>First, one should definitely not make the package repository a dump. You want to make package rules. Does it have documentation? Does it have a test suite? Can the test suite be run automatically? Semantic versioning? And so on. Is the package experimental, does it have real world uses?
<br>Furthermore, we could definitely adopt the ideas from the haskell-platform: A set of well-defined and stable packages are made into a basis library. Packages from the dump "graduate".
<br></blockquote><div><br></div><div>I believe in giving people simple and flexible tools and let them build the rules later on. This is basically why, after doing my work on Agner, I recently launched EXPM (http://expm.co, http://rashkovskii.com/2012/10/01/expm-or-meet-agner-2/) that is much simpler and much more flexible. EXPM allows to host your own repos very trivially, therefore allowing to build any combinations, including the one suggested by you.</div><div><br></div><div>So far I am just running a "dump" index at expm.co to bootstrap this system (after all, publishing got magnitudes easier with expm comparing to Agner), but I can very much see how we can eventually add another repository (say, stable.expm.co) that will only "host" graduated packages.</div><div><br></div><div>Yurii.</div>