Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support npm's forthcoming Ecosystems and Collections #64

Open
4 tasks
unscriptable opened this issue Sep 27, 2014 · 2 comments
Open
4 tasks

Support npm's forthcoming Ecosystems and Collections #64

unscriptable opened this issue Sep 27, 2014 · 2 comments

Comments

@unscriptable
Copy link
Contributor

Follow-on from #59. See http://blog.npmjs.org/post/94662089625/the-future-of-the-npm-website-lets-map-this-road

Seems like we need to do the following when the new npm-www is ready:

  1. register an npm Ecosystem
  2. prompt existing extension and starter authors to indicate that their packages belong to the the "rave" ecosystem
  3. Create docs / instructions for authors about how to be included in the "rave" ecosystem
  4. Encourage authors to create npm Collections based on their starters (and extensions in some cases?)
@phated
Copy link

phated commented Sep 27, 2014

👍 ecosystems!

@briancavalier
Copy link
Contributor

+1 Looks like some really great opportunities for rave. Let's stay on top of this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants