Agree. The triaging process makes sense to me.
Balaji.V
On Monday, April 6, 2020, 09:54:24 AM PDT, Vinoth Chandar
<[email protected]> wrote:
Hi,
I feel there are couple of action items here..
a) JIRA to track work for slack-ML integration
b) Document the support triaging process : Slack (level 1) -> Github Issues
(level 2 , triage, root cause) -> JIRA (level 3, file bug, get resolution)
.
P.S: Mailing List is very similar to Slack as well IMO.. i.e mostly level 1
things (w.r.t to triaging issues). Do you all agree?
Thanks
Vinoth
On Sat, Apr 4, 2020 at 3:03 AM leesf <[email protected]> wrote:
> Sorry to chime in so late, in fact we did discussion integrate slack with
> dev ML before [1], but seems like it needs some other work before working,
> in order to reduce repetitive workload, I am +1 to move some debugging
> question to GH issues, which could be easily searched.
>
> [1]
>
> https://lists.apache.org/thread.html/r0575d916663f826a5078363ec913c53360afb372471061aa60fd380c%40%3Cdev.hudi.apache.org%3E
>
> lamber-ken <[email protected]> 于2020年4月4日周六 上午12:47写道：
>
> >
> >
> > Thanks you all,
> >
> >
> > Agree with Sudha, it's ok to answer simple questions and move debugging
> > type of questions to GH issues.
> > So, let's try to guide users who asking debugging questions to use GH
> > issues if possible.
> >
> >
> > Thanks,
> > Lamber-Ken
> >
> >
> >
> >
> >
> > At 2020-04-03 07:19:26, "Bhavani Sudha" <[email protected]> wrote:
> > >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 <[email protected]>
> > >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 <[email protected]>
> > 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 <[email protected]>
> 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 <[email protected]> 于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, <[email protected]> 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
> > >>> > >
> > >>> >
> > >>>
> > >>
> >
>
