@izs this is more of a gesture than an actual pull-request: put this where-ever you see fit. There were a few folks on other parts of the Internet that were asking for more visibility and since the roadmap we discussed over the summer for this post:
was approved by you I saw no problem duplicating the copy in the repository to make it more accessible.
cc/ @maxogden @rvagg @domenic @luk @jden
[doc] Added ROADMAP.md from http://blog.nodejitsu.com/npm-innovation-…
Thanks! Considering that there are currently 41 pending pull requests (including this one), it can be intimidating for new contributors to approach the project and wonder if their contributions are relevant or worthwhile, or whether their ideas are worthwhile developing into full blown PRs. A well groomed backlog of issues and/or a ROADMAP.md file like this make it easier for new contributors to join existing projects. Given the value of npm to the node community as a whole (as demonstrated by the crowdfunding campaign to support npm), it is important to make sure that this project is accessible to the community at large and that any community members with the time and talent to contribute feel welcome to do so. +1 to including the roadmap alongside this repo.
We should target 0 PRs if possible...
It's not just the PR's, a few months ago I had the intention of getting more intimate with npm. First thing that failed was the make doc-generation command. Just double checked and it is working now, so that's nice! :)
Now running tests, failed on 115 To test publishing: npm config set npm:publishtest true. If that's a prerequisite it should be done by a makefile or some test-script
To test publishing: npm config set npm:publishtest true
My point is (perhaps a no brainer), basics should just work, minimize hurdles etc.
I'd rather keep talking about stuff in these issues, and on http://blog.npmjs.org/ rather than putting Yet Another top-level file in the repo which will tend to rot.
Thanks for the gesture.