ch and maintain. However,
>>> > unlike slack workspace, it seems no existing popular product could be
>>> > leveraged easily.
>>> >
>>> > Thus, I am +1 to create an Apache Flink slack channel. If the ASF slack
>>> > cannot be joined ea
o the benefit
>> > of a
>> > >>>>>>>> >> self-driven user community. I'd really love to see if we can
>> > >>>>>>>> bring such
>> > >>>>>>>> >> success to the global English-s
gt;> [1] https://zapier.com/
> > >>>>>>>> >>
> > >>>>>>>> >>
> > >>>>>>>> >>
> > >>>>>>>> >> On Sat, May 7, 2022 at 9:50 AM Jingsong Li <
> > >>>>&g
ily for most of users, I prefer to set up our own slack
> workspace.
>
> Best
> Yun Tang
> --
> *From:* Jingsong Li
> *Sent:* Thursday, May 12, 2022 10:49
> *To:* Xintong Song
> *Cc:* dev ; user
> *Subject:* Re: [Discuss] Creating an Apache
set up our own slack workspace.
Best
Yun Tang
From: Jingsong Li
Sent: Thursday, May 12, 2022 10:49
To: Xintong Song
Cc: dev ; user
Subject: Re: [Discuss] Creating an Apache Flink slack workspace
Hi all,
Regarding using ASF slack. I share the problems I saw in
://druid.apache.org/community/
>>>>>>>> >> >
>>>>>>>> >> > On Fri, May 6, 2022 at 10:06 PM David Anderson <
>>>>>>>> dander...@apache.org>
>>>>>>>> >> > wrote:
>>&
>> >> > platform where the responses can be searched and shared.
>>>>>>> >> > >
>>>>>>> >> > > It is currently the case that good questions on stack overflow
>>>>>>> >> > frequently go unanswered because no one with the nec
ack as another way for users to request
>>>>>> help
>>>>>> >> from
>>>>>> >> > those who are already actively providing support on the existing
>>>>>> >> > communication channels might just lead to burnout.
>>>>>>
>>>>> something
>>>>> >> > like slack is much better suited than email or stack overflow.
>>>>> >> > >
>>>>> >> > > David
>>>>> >> > >
>>>>> >> > > On Fri, May 6, 2022 at 3:04 PM Becket Qin >>>> >
gt; > >>
>>>> >> > >> Personally I am open to having such a slack channel. Although
>>>> it has
>>>> >> > drawbacks, it serves a different purpose. I'd imagine that for
>>>> people
>>>> >> who
>>>> &
is the right tool for the
job. IMO it works
>> > great as
>> > >>>> an adhoc tool for discussion between developers,
but it's not
>> > searchable
>> > >>>> and it&#x
t; > >>
>>> >> > >> One step further, if the channel is maintained by the Flink PMC,
>>> some
>>> >> > kind of code of conduct might be necessary. I think the suggestions
>>> of
>>> >> > ad-hoc conversations, reflecting back to the emails are good
>> >> > >>
>> >> > >> On Fri, May 6, 2022 at 8:55 PM Martijn Visser <
>> mart...@ververica.com
>> >> >
>> >> > wrote:
>> >> > >>>
>> >> > >>> Hi everyone,
>> >> > &
t as a potential option to create a more active community.
> >> > >>>
> >> > >>> A concern I can see is that users will start DMing well-known
> >> > reviewers/committers to get a review or a PR merged. That can cause a
> >> lot
> >&g
gt;> > >>> Martijn
>> > >>>
>> > >>> [1] https://airflow.apache.org/community/
>> > >>>
>> > >>> On Fri, 6 May 2022 at 13:59, Piotr Nowojski
>> > wrote:
>> > >>>>
>> > >>
between developers, but it's not
> > searchable
> > >>>> and it's not persistent. Between devs, it works fine, as long as the
> > result
> > >>>> of the ad hoc discussions is backported to JIRA/mailing list/design
> > doc.
> > >>&
d, because nobody can search for it .
> >>>>
> >>>> I'm +1 for having an open and shared slack space/channel for the
> >>>> contributors, but I think I would be -1 for such channels for the
> users.
> >>>>
> >>>> For user
t; thread, because nobody can search for it .
>>>>
>>>> I'm +1 for having an open and shared slack space/channel for the
>>>> contributors, but I think I would be -1 for such channels for the users.
>>>>
>>>> For users, I would
channels for the users.
>>>
>>> For users, I would prefer to focus more on, for example, stackoverflow.
>>> With upvoting, clever sorting of the answers (not the oldest/newest at
>>> top)
>>> it's easily searchable - those features make it fit our us
>> it's easily searchable - those features make it fit our use case much
>> better IMO.
>>
>> Best,
>> Piotrek
>>
>>
>>
>> pt., 6 maj 2022 o 11:08 Xintong Song napisał(a):
>>
>> > Thank you~
>> >
>> > Xintong
searchable - those features make it fit our use case much
> better IMO.
>
> Best,
> Piotrek
>
>
>
> pt., 6 maj 2022 o 11:08 Xintong Song napisał(a):
>
> > Thank you~
> >
> > Xintong Song
> >
> >
> >
> > -- Forwarded message ---
archable - those features make it fit our use case much
better IMO.
Best,
Piotrek
pt., 6 maj 2022 o 11:08 Xintong Song napisał(a):
> Thank you~
>
> Xintong Song
>
>
>
> -- Forwarded message -
> From: Xintong Song
> Date: Fri, May 6, 2022 at 5:07
Thank you~
Xintong Song
-- Forwarded message -
From: Xintong Song
Date: Fri, May 6, 2022 at 5:07 PM
Subject: Re: [Discuss] Creating an Apache Flink slack workspace
To: private
Cc: Chesnay Schepler
Hi Chesnay,
Correct me if I'm wrong, I don't find this is *
23 matches
Mail list logo
