Also one thing I wanted to note. I feel it should be okay to answer simple `what does this mean` type of questions in slack and move debugging type of questions to GH issues. What do you all think?
Thanks, Sudha On Thu, Apr 2, 2020 at 11:45 AM Bhavani Sudha <bhavanisud...@gmail.com> wrote: > Agree on using GH issues to post code snippets or debugging issues. > > Regarding mirroring slack to commits, the last time I checked there was no > options that was readily available ( there were one or two paid products). > It looked like we can possibly develop our own IFTT/ web hook on slack. Not > sure how much of work that is. > > > Thanks, > Sudha > > > On Thu, Apr 2, 2020 at 8:40 AM Vinoth Chandar <vin...@apache.org> wrote: > >> Hello all, >> >> Actually that's how we have been using GH issues.. Both slack/ml are >> inconvenient for sharing code and having long threaded conversations. >> (same >> issues raised here). >> >> That said, we could definitely formalize this and look to move slack >> threads into GH issue for triaging (then follow up with JIRA, if real bug) >> before they get too long. >> >> >>slack has some answerbot to auto reply and promote users to create GH >> issues. >> Worth looking into.. There was also a conversation around mirroring >> #general into commits or something for indexing/searching.. ? >> >> >> On Thu, Apr 2, 2020 at 1:36 AM vino yang <vinoy...@apache.org> wrote: >> >> > Hi Lamber-Ken, >> > >> > Thanks for rasing this problem. >> > >> > >> 3. threads cann't be indexed by search engines >> > >> > Yes, I always thought that it would be better to have a "users" ML, but >> it >> > is not clear whether only the Top-Level Project can have this ML. >> > >> > Best, >> > Vino >> > >> > >> > Shiyan Xu <xu.shiyan.raym...@gmail.com> 于2020年4月1日周三 上午4:54写道： >> > >> > > Good idea to use GH issues as triage. >> > > >> > > Not sure if slack has some answerbot to auto reply and promote users >> to >> > > create GH issues. If it can be configured that way, that'd be great >> for >> > > this purpose :) >> > > >> > > On Tue, 31 Mar 2020, 10:03 lamberken, <lamber...@163.com> wrote: >> > > >> > > > Hi team, >> > > > >> > > > >> > > > >> > > > >> > > > Many users use slack ask for support when they met bugs / problems >> > > > currently. >> > > > >> > > > but there are some disadvantages we need to consider: >> > > > >> > > > 1. code snippet display is not friendly. >> > > > >> > > > 2. we may miss some questions when questions come up at the same >> time. >> > > > >> > > > 3. threads cann't be indexed by search engines >> > > > >> > > > ... >> > > > >> > > > >> > > > >> > > > >> > > > So, I suggest we should guide users to use GitHub issues as much as >> we >> > > can. >> > > > >> > > > step1: guide users use GitHub issues to report their questions >> > > > >> > > > step2: developers can pick up some issues which they are interested >> in. >> > > > >> > > > step3: raise a related JIRA if needed >> > > > >> > > > step4: add some useful notes to troubleshooting guide >> > > > >> > > > >> > > > >> > > > Any thoughts are welcome, thanks : ) >> > > > >> > > > >> > > > Best, >> > > > Lamber-Ken >> > > >> > >> >
