-
Notifications
You must be signed in to change notification settings - Fork 29
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
Help repo. #18
Comments
I'm a huge fan of the issues workflow with this type of exchange. It allows
|
Also, I think the github api would allow for us to feature some of these
|
Yup, and on the DL, GitHub is working on a "discussions" feature that will be a good swap out for Issues so we may want to hold off on API integration until that happens. |
So keep it simple for now. Word. On Tue, Jan 14, 2014 at 10:52 AM, Mikeal Rogers [email protected]:
|
Cool -- should we make a |
definitely :) |
could someone make me a collaborator on that one so that I can edit the readme :) |
oh shoot! On it. Lo siento. On Tue, Jan 14, 2014 at 2:59 PM, Mikeal Rogers [email protected]:
|
Like. I love websites, and git. But why reinvent the wheel over something like stack overflow? |
Because you can go somewhere that has topical relevance to the question /me shrugs. I get it.
|
Stack Overflow is pretty particular about the specificity of the questions you ask. You can't, for instance, say "I'm having a hard time understanding async flow control" you can only ask a question like "How do I do parallel IO with require('async')" While there is certainly a community on Stack Overflow it's pretty weak on node.js expertise. Being that the node.js is heavily invested in GitHub it makes a lot more sense to have community communications be here. It's easy to get people's attention by mentioning people, issues and projects and having the interlinking between projects and people be so easy and encouraged also improves the discourse. If you look at the NodeSchool discussions repo you'll see what I'm talking about. They've done a great job helping people very new to node.js when they hit bumps in the workshopper courses. I'd like to extend that to discourse outside of just those courses and eventually replace the node.js Mailing List (which is just awful). |
+1000 to the Mailing List going the way of the dodo. On Fri, Jan 17, 2014 at 10:53 AM, Mikeal Rogers [email protected]:
|
@mikeal seems reasonable. Thanks for the thoughtful reply. |
The mailing list is basically a place where people ask innocent questions and are trolled by people who want to promote a library they wrote.
I've been pushing for a while to build an alternative to the mailing list for people that need actual node help. As a start, I think a repo on knode would be a good start. We could use the issue tracker for people asking questions and eventually build a friendlier frontend that indexed threads and made it easier for newbies to ask questions.
NodeSchool has been using a repo as a discussion forum for a while with a lot of success and they are already getting questions outside the scope of nodeschoo.
What do you think?
The text was updated successfully, but these errors were encountered: