+1 for the proposal
Thanks Harsh for your initiative to improve the productivity of the
community.
I agree with Sheng that care needs to be taken using the proposed label
appropriately.
Having a committer to actually close the issue is therefor a good gate.
However, I'm in favor of such label an
I believe having this label - [suggest-closed] is helpful.
1. Adding this label is not an automated bot script that marks stale
issues. A bot script would definitely be unwelcoming and also miss major
issues just because it is stale.
2. This label is simply a way to identify issues that can be clo
Thanks, Harsh. I saw that this was created and used on several issues and I
removed it for now because:
- the issues that they are used on issues that don't seem to be resolved.
- it leaves the impression to the requesters that people think their issues
are not worth people's attention in this co
Hey all,
To help with how we handle issues for MXNet, I am proposing a new label be
created called: [suggest-closed]. I, alongside many others, observe many
stale issues which can be candidates for closure and searching for these of
the 800+ issues we have is a daunting task. This label is meant to
Thanks for this useful contribution Harsh!
+1 to an updated issue template
and +1 to Marco's idea as well
Anything that helps the community triage and make it easier for folks that
file issues is greatly appreciated
Hagay
On Thu, Nov 8, 2018 at 4:05 PM Marco de Abreu
wrote:
> Great job, Harsh!
Great job, Harsh!
That's a very good idea, Naveen. Harsh, Qing and I have been thinking about
the bot "welcoming" the user when they create an issue or pull request by
creating a comment as soon as the thread gets created. This message could
contain basic instructions like these commands, recommen
Great job!, this is very helpful to triage issues!, users when creating a
new Issue could themselves tag the issues. May be we should add that to the
issue template?
On Thu, Nov 8, 2018 at 3:54 PM Harsh Patel
wrote:
> Hey all,
> The upgraded label bot has been pushed into production. Current
> f
Hey all,
The upgraded label bot has been pushed into production. Current
functionality includes
add, delete, and update.
(i.e. @mxnet-label-bot add ['label']
@mxnet-label-bot remove ['label']
@mxnet-label-bot update ['label'])
Users should feel free to leave suggestions and any potential issues. T
