-
Notifications
You must be signed in to change notification settings - Fork 131
Add node-forward/mentors to iojs website? #280
Comments
Holding off on this (from a technical level) until #276 lands. We can start adding dynamic pages like this -- and my long longed for versions page -- once we have the new content infrastructure in place. It would be interesting to add an extra "languages spoken" field to this data, so that we/people can filter to fit the localization being viewed. For example, I wouldn't have us filter the list to show only German-speakers on the German localization (for example,) but we might sort German speakers to the top. And let users filter the list based on location, language(s), etc. |
Good point! |
The mentors repo is pretty dead. I don't think it's very successful as an experiment in how to arrange mentors and mentees. We should try something else, something new, I have a few ideas that I'll post on the evangelism repo in the next few days along with a post mortem of the prior effort. |
Mentorship among millennials, genXers and younger has generally fallen to I've found that people in the JavaScript/node/io communities fall into The first we will almost never be able to approach because governance is The second group is much easier to approach when we are all open accepting, I hate to make sweeping generalizations, but we live in a world with tons Modern day mentorship is bourne of an old world ideal. We first see our Information is now widely available, direction and wisdom in the form of Nodeschool is great for this, I have never been part of such a That's my take anyways. Farrin A. Reid |
Okay, I'm closing this. |
I was just watching @mikeal's recent talk and noticed the node-forward resources (especially the mentors idea). There were already discussions if a simple list of names in a README is the best way to handle mentors and there are a bunch of unmerged PRs going back to last year.
What do you think of transforming the list into a JSON file, add a filterable data table widget and put it on the iojs website? I believe this is a great way to get people started with node/iojs, who then might in turn become contributors to the project and its ecosystem as well.
The text was updated successfully, but these errors were encountered: