[Matplotlib-devel] please be slower to close bug reports from first-time reporters

[Paul Hobson]

I think this is a great approach, Tom.

Sorry I haven't been super active lately. But what little review I do, I'll
keep this in mind.
-Paul

On Thu, Nov 1, 2018 at 8:24 AM Thomas Caswell <tcaswell at gmail.com> wrote:

> Folks,
>
> We have had a number of bug reports come in recently from first-time
> reporters (you can tell if you mouse over their icon) that have been
> quickly closed.  On one hand, they have been technically correct, however
> on the other we should try to be more welcoming to new contributors.
>
> I propose that in "we think this is not a bug" cases instead of
> immediately closing, we ask the OP if they are ok closing as not a bug and
> leave the issue open for a few days (there has been discussion of using one
> of the auto-close bots for stale issues / PRs which I am in general
> against, but I think a "waiting for feedback" label + a bot that either
> removes the label on the next comment or auto-closes after N days would be
> useful).
>
> We should also consider changing some of those issues into documentation
> issues.  It can be useful to ask the OP "where would you have expected this
> to be documented?".
>
> Tom
>
> --
> Thomas Caswell
> tcaswell at gmail.com
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20181101/30a00e4e/attachment.html>