and fully-managed. Airflow[1] and Next.JS also use GitHub
> > Discussion
> > > as
> > > > >> their forum.
> > > > >>
> > > > >> Best,
> > > > >> Jark
> > > > >>
> > > > >> [1]:
> > > > >> Best,
> > > > >> Jark
> > > > >>
> > > > >> [1]: https://github.com/apache/airflow/discussions
> > > > >> [2]: https://github.com/vercel/next.js/discussions
> > > > >>
> > >
>
> > > >>
> > > >> On Thu, 12 May 2022 at 15:24, Martijn Visser >
> > > >> wrote:
> > > >>
> > > >>> Hi,
> > > >>>
> > > >>> I would +1 setting up our own Slack. It will allow
>>> I would +1 setting up our own Slack. It will allow us to provide the
> > best
> > >>> experience for those in the community who want to use Slack.
> > >>> More than happy to help with setting up community guidelines on how
> to
>
gt;>> > >>>>>>>> >> questions on MLs.
> >>> > >>>>>>>> >> - I'd also like to share some experience from the Flink
> >>> China
> >>> > >>>>>>>> community
ntain. 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 easily for m
gt;>>>>>>> bring such
>> > >>>>>>>> >> success to the global English-speaking community.
>> > >>>>>>>> >>
>> > >>>>>>>> >> Concerning StackOverFlow, it definitely
> > *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 the Apache Dr
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
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 Flink slack workspace
Hi all,
Regarding using ASF slack. I share the problems I saw
derson <
>>>>>>>> dander...@apache.org>
>>>>>>>> >> > wrote:
>>>>>>>> >> > >
>>>>>>>> >> > > I have mixed feelings about this.
>>>>>>>>
> > It is currently the case that good questions on stack overflow
>>>>>>> >> > frequently go unanswered because no one with the necessary
>>>>>>> expertise
>>>>>>> >> takes
>>>>>>> >> > the time to respond. If the Flin
e already actively providing support on the existing
>>>>>> >> > communication channels might just lead to burnout.
>>>>>> >> > >
>>>>>> >> > > On the other hand, there are rather rare, but very interesting
>>>>>> cases
>
> >
>>>>> >> > > David
>>>>> >> > >
>>>>> >> > > On Fri, May 6, 2022 at 3:04 PM Becket Qin >>>> >
>>>>> >> wrote:
>>>>> >> > >>
>>>>> >> > >> Thanks for the proposal, Xintong.
; it has
>>>> >> > drawbacks, it serves a different purpose. I'd imagine that for
>>>> people
>>>> >> who
>>>> >> > prefer instant messaging, in absence of the slack channel, a lot of
>>>> >> > discussions might just take
or discussion between developers,
but it's not
>> > searchable
>> > >>>> and it's not persistent. Between devs, it works
fine, as long as
>> the
>> > result
>> > >
gt;> some
>>> >> > kind of code of conduct might be necessary. I think the suggestions
>>> of
>>> >> > ad-hoc conversations, reflecting back to the emails are good
>>> starting
>>> >> > points. I am +1 to give it a try and see how it goes. In the worst
>>&
> mart...@ververica.com
>> >> >
>> >> > wrote:
>> >> > >>>
>> >> > >>> Hi everyone,
>> >> > >>>
>> >> > >>> While I see Slack having a major downside (the results are not
>>
t;>> 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
> >> > of noise. I can go +1 for Slack, but then we need to establish a set
> of
> >> > community r
ache.org/community/
>> > >>>
>> > >>> On Fri, 6 May 2022 at 13:59, Piotr Nowojski
>> > wrote:
>> > >>>>
>> > >>>> Hi Xintong,
>> > >>>>
>> > >>>> I'm not sure if slack is th
stent. Between devs, it works fine, as long as the
> > result
> > >>>> of the ad hoc discussions is backported to JIRA/mailing list/design
> > doc.
> > >>>> For users, that simply would be extremely difficult to achieve. In
> the
> > >>>&
or 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 prefer to focus more on, for example,
> stackoverflow.
> >>>> With
>>>>
>>>> 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 prefer to focus more on, for example, stackoverfl
;> 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 use case much
>>> better IMO.
>>>
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
>> >
>> >
>> &g
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
>
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 PM
> Subject: Re: [Dis
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 *repeatedly
28 matches
Mail list logo
