diff options
author | Kat Marchán <kzm@zkat.tech> | 2018-07-13 02:21:29 +0300 |
---|---|---|
committer | GitHub <noreply@github.com> | 2018-07-13 02:21:29 +0300 |
commit | f0a372b074cc43ee0e1be28dbbcef0d556b3b36c (patch) | |
tree | 8ea0da08e6b76308f8cf8928e6b3ffae6c5f994d /CONTRIBUTING.md | |
parent | 4c32413a5b42e18a34afb078cf00eed60f08e4ff (diff) |
docs: replace references to the old repo or issue tracker (#5)
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r-- | CONTRIBUTING.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index f85afbbe2..f412dc93e 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -59,15 +59,15 @@ Collaborators who become inactive for 3 months or longer may have their collabor * Only answer questions when they know the answer, and provide a reference to the answer. * If collaborators aren't totally confident about their answer, please leave the issue and try another one. * If they've responded to an issue, it becomes their responsibility to see it to resolution. -* Close issues if there's no response within a month. * Defer to fellow Collaborators & npm employees for answers (Again, please don't @ collaborators or npm employees, thank you!) -* Make sure to search for [the troubleshooting doc](./TROUBLESHOOTING.md) and search on the issue tracker for similar issues before opening a new one. +* Make sure to search [the troubleshooting posts on npm.community](https://npm.community/c/support/troubleshooting) and search the rest of the forum for similar topics. ### npm, Inc Employees Folks who work at npm, Inc, who have a responsibility to ensure the stability and functionality of the tools npm offers. #### Abilities + * Label/triage new issues * Respond to ongoing issues * Close resolved issues |