You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by ra...@gmail.com on 2018/08/11 07:30:49 UTC
[DISCUSS] [Github Issues] Support questions in GitHub issues
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
Re: [DISCUSS] [Github Issues] Support questions in GitHub issues
Posted by Gearóid M <de...@gearoid.me>.
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 course, some people ignore the template and file issues looking for support anyway, but having the clear template means we can just close the issue and point them again in the right direction.
[1] https://raw.githubusercontent.com/OnsenUI/OnsenUI/master/.github/ISSUE_TEMPLATE.md
On Sat, 11 Aug 2018, at 16:30, raphinesse@gmail.com wrote:
> 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-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: [DISCUSS] [Github Issues] Support questions in GitHub issues
Posted by Jan Piotrowski <pi...@gmail.com>.
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
<jc...@gmail.com>:
>
> 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 <jc...@gmail.com>
> escribió:
>
> > 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 <pi...@gmail.com>
> > escribió:
> >
> >> > 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 <ra...@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-unsubscribe@cordova.apache.org
> >> For additional commands, e-mail: dev-help@cordova.apache.org
> >>
> >>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: [DISCUSS] [Github Issues] Support questions in GitHub issues
Posted by julio cesar sanchez <jc...@gmail.com>.
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 <jc...@gmail.com>
escribió:
> 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 <pi...@gmail.com>
> escribió:
>
>> > 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 <ra...@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-unsubscribe@cordova.apache.org
>> For additional commands, e-mail: dev-help@cordova.apache.org
>>
>>
Re: [DISCUSS] [Github Issues] Support questions in GitHub issues
Posted by julio cesar sanchez <jc...@gmail.com>.
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 <pi...@gmail.com>
escribió:
> > 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 <ra...@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-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>
Re: [DISCUSS] [Github Issues] Support questions in GitHub issues
Posted by Jan Piotrowski <pi...@gmail.com>.
> 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 <ra...@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-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org