Hi Wenli. Telling developers they can reopen the issue is better from my perspective.
On Fri, Aug 30, 2019 at 11:16 AM Ovilia <oviliazh...@gmail.com> wrote: > I found a technical problem with Clement's approach. > If we don't close those issues that are not created using the template, the > only thing a user should do is to open the issue helper to create a new > template. > Thus, the previous issue will have no use, so it's better to be closed. > > Previously, when a user reopens an issue, the bot will also check if it's > created using the template. > If not, it will be closed again. > I changed this behavior so that if the user believes his question should > not follow the template and he can well make his point without the > template, he can still reopen the issue. > And I put this information in the comment of the bot to let the creator > know about it. > > Wenli > > > On Mon, Aug 26, 2019 at 10:01 PM Ovilia <oviliazh...@gmail.com> wrote: > > > That's a good idea. It can be easily implemented with our bot and may > help > > the both side. > > > > Wenli > > > > > > On Mon, Aug 26, 2019 at 9:47 PM Clement Ho <clem...@gitlab.com.invalid> > > wrote: > > > >> Perhaps there is a more gentler way for this bot to help foster more > >> collaboration such as only closing issues on a weekly basis, applying a > >> label, asking the issue author to change their issue description rather > >> than auto closing > >> > >> On Mon, Aug 26, 2019 at 2:38 AM Ovilia <oviliazh...@gmail.com> wrote: > >> > >> > I think perhaps we should keep how the bot works now. > >> > If we hear anything from the community complain about this problem, we > >> > should discuss with the community to know what a better solution may > be. > >> > Otherwise, we are just assuming their inconvenience. Because from my > >> > own experience, I don't mind creating the issue again following the > >> > community's rules as long as my issue can be resolved ASAP. > >> > So in the meantime, we should provide more help and be nicer to the > >> > community to help them fix the problems. > >> > > >> > Wenli > >> > > >> > > >> > On Mon, Aug 26, 2019 at 3:23 PM Yi Shen <shenyi....@gmail.com> wrote: > >> > > >> > > I agree with Wenli. > >> > > > >> > > Besides, we can keep improving the experience of editing an issue > with > >> > > template, like the issue helper we are using. > >> > > Also it's necessary to give a clear and nice guidance to encourage > >> > > developers how to create a new one with right format if his issue is > >> > > closed. > >> > > > >> > > > >> > > On Mon, Aug 26, 2019 at 11:09 AM Ovilia <oviliazh...@gmail.com> > >> wrote: > >> > > > >> > > > Hi all, > >> > > > > >> > > > Our GitHub bot currently automatically closes issues that didn't > >> create > >> > > > using our issue helper [1] because hose who open issues tend to > >> forget > >> > > > important information like what's expected, what's wrong, demos to > >> > > > reproduce, and etc. > >> > > > > >> > > > The main considerations were: > >> > > > When that information is missing, we cannot help them. So we have > to > >> > ask > >> > > > them to provide that. But some people don't come back to GitHub > >> until a > >> > > few > >> > > > days or weeks passed. Then, they provide some information. But > most > >> > > likely, > >> > > > they missed something this time again, so that we still cannot fix > >> > their > >> > > > problems. > >> > > > > >> > > > But I agree this is not the best experience we could provide to > our > >> > > users. > >> > > > So please give your advice on how to improve the experience as > well > >> as > >> > > keep > >> > > > the maintaining job efficiently. > >> > > > > >> > > > > >> > > > [1] https://ecomfe.github.io/echarts-issue-helper (This will be > >> moved > >> > to > >> > > > Apache domain within a week.) > >> > > > > >> > > > Wenli > >> > > > > >> > > > >> > > > >> > > -- > >> > > Yi Shen > >> > > Senior Developer > >> > > Baidu, Inc. > >> > > > >> > > >> > > > -- Yi Shen Senior Developer Baidu, Inc.
