move support issues to a new repository #5739

Closed
othiym23 opened this Issue Jul 21, 2014 · 2 comments

Projects

None yet

2 participants

@othiym23
Contributor

As stated on #5214, I propose npm/support-issues as the name for the new support issue repository. As #5662 (somewhat snottily) implies, the usefulness of this issue tracker is hampered by the number of non-actionable user support issues on the repo. It would be a lot easier to deal with both set of issues if they were separated and then treated with their own individual triage processes.

Ideally this would be done with a tool that uses GitHub's API, so we can move them en masse and without losing comments or issue details. It would also be great if we were able to do this with both open and closed issues. However, keeping it simple to start is probably wise, because this is a large project.

@othiym23 othiym23 added the hard label Jul 21, 2014
@othiym23 othiym23 removed the hard label Oct 7, 2014
@smikes
Contributor
smikes commented Nov 17, 2014

Ok to close this. We no longer need a reminder to do this project, as it is under way.

@othiym23 othiym23 closed this Nov 20, 2014
@othiym23 othiym23 removed the ready label Nov 20, 2014
@othiym23
Contributor

Closing as resolved!

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