Nope, the last few days convinced me that we do not want that ;)
But it gave a nice impression what we should add to the issues
templates so bug reports are actionable.
Am Mi., 22. Aug. 2018 um 01:21 Uhr schrieb julio cesar sanchez
:
>
> I just had a quick look and around 90% of new issues are
I just had a quick look and around 90% of new issues are tagged with
support label. Do we really want that? Real issues will be buried with this
volume of support issues.
El sábado, 11 de agosto de 2018, julio cesar sanchez
escribió:
> I have always closed the issues that weren’t issues and
I have always closed the issues that weren’t issues and pointed people to
SO or slack. Same for when ask questions on the dev mail list.
El sábado, 11 de agosto de 2018, Jan Piotrowski
escribió:
> > I think we should make that clear in the issue template
> > and direct people to slack or
> 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
I agree, Github issues should only be for bug reports and feature requests. For
Onsen UI, we have an issue template [1], which specifically explains where to
go for support. Additionally, the template is geared towards bug reporting,
which further discourages people from asking for support. Of
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
