-
Notifications
You must be signed in to change notification settings - Fork 0
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
Kickoff! #1
Comments
@mikeal Sweet. I was a bit confused about the different repos, as it seems a single wiki page on some official node repo was enough for this. Is there a larger plan here? Taking from your above suggestion, we could probably do wiki pages for each thing: Companies, Events, Projects, Trainings, etc — to avoid polluting everything on one page. This makes sense for its own repo. |
The "people" wiki page that the official node repo had didn't really scale, I don't think most people know about it or edit it anymore. For events we have a couple things, nodeschool uses a public google spreadsheet and sheetsee to produce a map, knode events (formerly nodemeatspace) is just a markdown file with a travis build that makes the gh-pages website on every change. The more structured the data the more we can do (maps, infographics, etc) but in many cases requiring people to submit structured data is a barrier to entry. |
I think it's a great idea to show off more of the Node ecosystem. If the purpose of such a page / site is to enable those new to the platform to find stuff easier, would it make sense to group things based on what they might look for?
|
This project was started because almost nobody has a clear picture of breadth of the Node ecosystem.
To kick this off I'd like to hear suggestions for what constitutes the ecosystem (people, event, companies, technologies). Is it all of these things together or can we get a pretty good picture of the scope just by tackling a few?
Once we finish that discussion we can move on to the best tools to use that will encourage participation from the community to help us build this out.
People I know are interested in this:
@balupton
@JedWatson
@rvagg
The text was updated successfully, but these errors were encountered: