Skip to content

Instantly share code, notes, and snippets.

@othiym23
Last active May 22, 2020 04:48
Show Gist options
  • Star 2 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save othiym23/9886289 to your computer and use it in GitHub Desktop.
Save othiym23/9886289 to your computer and use it in GitHub Desktop.

The Node.js group is a tool to announce cool things you've built, discuss cool things you're working on, and get help with things that are confusing you. It is a great forum for swapping knowledge. It is part of Node's large, loose network of resources. But it's not the only one – there are other resources that might be a better place to seek help or ask questions:

  • Stack Overflow is a great place to get help with specific technical questions about Node! If you post a question there, please wait a few days before crossposting it to the list, as many of the people who answer questions about Node on SO are also here. Also, crosspost with a link rather than the whole text of the question, to keep things tidy and to keep discussion of the issue in one place.
  • The development of Node itself is largely handled through Github. If you think you've encountered a bug in Node itself, it's best to file an issue there.
  • Likewise, the development of npm is handled by the npm team, also on Github, and npm bugs should be filed there.
  • For a more conversational approach to figuring things out, #node.js and #libuv on freenode IRC are great realtime resources for help with Node.

That said, here are the rules governing the list:

  1. No personal attacks or harassment. This group is governed by the Conference Code of Conduct, and violating its terms will get you barred from the list permanently, at the moderators' discretion.
  2. No spam. Self-promotion is fine, and major updates of projects to which you've contributed merit a mention, but this is a technical forum, not a marketplace.
  3. Large chunks of source will work much better if posted to a requirebin, jsbin, gist, or generic pastebin of some kind.

In addition, there are some more informal guidelines that, if followed, will make everyone's lives more pleasant:

  • There are certain arguments that recur with monotonous regularity. Bikeshedding is a major part of hacker culture, but there is no one true solution to any of the problems that are regularly brought up on the list (promises vs callbacks vs coroutines vs generators vs CPS transforms vs ∞, JavaScript vs CoffeeScript, etc). What works best for you may not work well for somebody else.
  • Not everybody comes to Node with the same background. One of Node's touted advantages is that it unifies server-side and front-end developers. Sometimes people need a little help crossing the gap. Be charitable.
  • Even though Google Groups makes it easy, it's a little weird to revive a message thread that's more than a few months old. Start a new thread that summarizes the old one if you want to revisit a dead thread.

These rules and guidelines will be enforced at the moderators' discretion. We will do what we can to ensure they are applied consistently and fairly, but having a useful forum trumps arguing over precise observance of the rules. The final say about moderation decisions sits with Node's maintainers, but TJ is busy, so be reasonable.

This policy augments, rather than supersedes, the old posting guidelines. Most of what's on that page pertains to these guidelines as well.

@kosit-orngsri
Copy link

สวัสดี

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment