I'm OK with that. I will ask the infra to transfer if no one objects. Wenli
On Fri, Aug 30, 2019 at 2:26 PM Sheng Wu <wu.sheng.841...@gmail.com> wrote: > OK. That should be good. > Only one suggestion, consider moving your personal repo to Apache, as from > the project name(echarts-robot <https://github.com/Ovilia/echarts-robot>), > it is very related to ECharts project. > > Sheng Wu 吴晟 > > Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin > Twitter, wusheng1108 > > > Ovilia <oviliazh...@gmail.com> 于2019年8月30日周五 下午2:24写道： > > > It's a GitHub App [1]. I asked Apache infra to give the write aceess. > > > > [1] https://github.com/apps/echarts-robot/ > > > > Wenli > > > > > > On Fri, Aug 30, 2019 at 2:22 PM Sheng Wu <wu.sheng.841...@gmail.com> > > wrote: > > > > > Sorry I haven't made myself clear. > > > I mean, does the bot account really exist? Does it use your > > > account authority? (I am assuming this because you said it could close > > the > > > issue, look like write permission to me) > > > > > > Sheng Wu 吴晟 > > > > > > Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin > > > Twitter, wusheng1108 > > > > > > > > > Ovilia <oviliazh...@gmail.com> 于2019年8月30日周五 下午2:18写道： > > > > > > > The project is available at https://github.com/Ovilia/echarts-robot > > > > > > > > It's hosted on http://glitch.com which works pretty much like GitHub > > > > Pages, > > > > only that it can have server-side logic. In our case, we use it to > host > > > > Node.js bot. > > > > > > > > Wenli > > > > > > > > > > > > On Fri, Aug 30, 2019 at 1:49 PM Sheng Wu <wu.sheng.841...@gmail.com> > > > > wrote: > > > > > > > > > One question, > > > > > Where is the bot? How it works? > > > > > > > > > > Sheng Wu 吴晟 > > > > > > > > > > Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin > > > > > Twitter, wusheng1108 > > > > > > > > > > > > > > > Yi Shen <shenyi....@gmail.com> 于2019年8月30日周五 上午11:25写道： > > > > > > > > > > > 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. > > > > > > > > > > > > > > > > > > > > >
