Closed smikes closed 9 years ago
I strongly disagree that we should block users from using npm/npm's issue tracker for support requests. We should guide them here, but I'm not in favor of making people jump through hoops to communicate with us.
The primary purpose of this repository is to accept automatically generated support requests coming from npm report
; it is not the intention that we are going to force anyone to report support issues only to this repo.
OK. I misunderstood; I thought the goal was to get all support issues here. The goal you are setting is much more reasonable.
On Thu, Nov 20, 2014 at 12:48 PM, Forrest L Norvell < notifications@github.com> wrote:
I strongly disagree that we should block users from using npm/npm's issue tracker for support requests. We should guide them here, but I'm not in favor of making people jump through hoops to communicate with us.
The primary purpose of this repository is to accept automatically generated support requests coming from npm report; it is not the intention that we are going to force anyone to report support issues only to this repo.
— Reply to this email directly or view it on GitHub https://github.com/npm/support-cli/issues/6#issuecomment-63867702.
I wasn't thinking clearly before when I said that closing github.com/npm/npm/issues is "to be avoided" and "the nuclear option". It's actually a necessary step because --
Every npm <= 2.1.9 in the wild says
npm/npm/issues
is where bug reports goThe only practical way to stop people reporting issues there is to block issue creation, or limit it to project collaborators.
I think that'll be okay, actually, provided people get enough warning about it and this new repo is up and running. Possibly worth waiting a few weeks after all pointers still under our control have been updated to npm/support-cli --
npm irc channel title
Thoughts? Please tell me I'm wrong about this. I really don't like the idea; it just seems like it'll be necessary.