> I think we should make that clear in the issue template > and direct people to slack or stackoverflow.
I personally don't really think that's necessary. The issue volume for Cordova is very low (at least on JIRA and at least since Github issues were enabled), so having a few support requests bring some activity (and in the best case positive outcome for the users) is actually a good thing. Another aspect: The moment you introduce a restrictive policy, the issues work as a maintainer tends to get very negative - most people ignore the issue template anyway and post their support requests anway, which you have to close and post a canned reply. Which of course doesn't mean that the "Support Request" issue template should not direct people to StackOverflow and Slack, and definitely include some fields to fill out so we have something to work with (OS, versions etc.). But that's a thing for the other mailing list thread. If the volume or benefit of support requests ever gets overwhelming, we can still change that policy. > We might still use a support label as closing reason. If the majority of maintainers really wants to disallow support requests, this would be a nice way to categorize those requests and enable a discussion in the closed issue anyway. -J 2018-08-11 9:30 GMT+02:00 <raphine...@gmail.com>: > Jan proposed a support label for issues more than once. That fit me > thinking. Do we really want to allow support questions like this one [1] in > the issues? > > I'm definitely against it. I think we should make that clear in the issue > template and direct people to slack or stackoverflow. We might still use a > support label as closing reason. > > What do you think? > > [1]: https://github.com/apache/cordova-android/issues/474 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
