By renaming the label, you also renamed it for all existing issues.
Now many labels that were just questions of users (both open and
closed) indicate that info is needed - which might be true or not.

Please undo all renaming of labels, both to `info-needed` and `query`.
Please undo the changes to the label documentation as well.

On the other hand, we all seem to agree that a new additional
`info-needed` is valid and needed, so to create that and document it
is totally fine.

It takes some additional effort to maintain labels like this (as you
of course want to remove it after the user replied), but as I assume
one/you would only apply the label when also asking for the
information, you should get a GitHub notification and be able to take
care of that when reading the response.

Regarding the "question" label, I understand what you mean, but don't
agree. But that is a topic for a new thread then where we can
elaborate.

-J


Am Mi., 17. Juli 2019 um 18:47 Uhr schrieb Chris Brody <chris.br...@gmail.com>:
>
> This work was not done 100% correctly, please accept my apologies.
>
> I will try to explain why it was not done 100% correctly so we can
> decide what we want to do next.
>
> In general, I have found the standard “question” label to be confusing
> since different repos in the wild, including Cordova repos, have used
> this label in different ways:
>
> * on some repos the “question” label was used to indicate that further
> input was needed from the author of the issue
> * on some other repos the “question” label was used to indicate that
> someone was just asking a question
>
> On those repos where the “question” label was used to indicate that
> further input was needed from the user, I took a shortcut and just
> changed the label to “info-needed”. I thought this was better than
> changing the label on every single issue where more info was needed.
>
> On some other repos I renamed the “question” label to “query”. I think
> we need either rename the label again, or completely remove this label
> and change the label on all issues affected.
>
> Since I have seen the “question” label used in multiple ways, I now
> find it confusing. At this point I would favor that we do not use the
> “question” label due to the potential for confusion.
>
> In cases where I renamed the “question” label to “info-needed”, I
> would like to propose that we do nothing else since the problem is
> already solved.
>
> Over and out.
>
> Chris
>
> On Wed, Jul 17, 2019 at 2:01 AM Hazem Saleh <haz...@apache.org> wrote:
> >
> > I think this is an Excellent idea.
> >
> > Thanks and Best Regards
> >
> > > On Jul 15, 2019, at 11:07 PM, Chris Brody <chris.br...@gmail.com> wrote:
> > >
> > > We receive a number of support issues where I think we need an
> > > explicit label such as “info needed”, to make it clear that more
> > > information is needed before we can provide any support. I think we
> > > need to add this label to a number of repos such as apache/cordova,
> > > cordova-android, cordova-ios, etc.
> > >
> > > Any objections if I would add this label to some of the repos on GitHub?
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > > For additional commands, e-mail: dev-h...@cordova.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Reply via email to