+1 (binding)

This facilitates people collaborating on the same project from different
organizations. I really like this idea.

On Thu, May 19, 2022 at 12:43 PM Peter Huang <huangzhenqiu0...@gmail.com>
wrote:

> +1 (non-binding)
>
>
> Best Regards
> Peter Huang
>
> On Wed, May 18, 2022 at 9:33 PM Leonard Xu <xbjt...@gmail.com> wrote:
>
> > Thanks Xintong for driving this.
> >
> >  +1
> >
> > Best,
> > Leonard
> >
> > > 2022年5月19日 上午11:11,Zhou, Brian <b.z...@dell.com> 写道:
> > >
> > > +1 (non-binding)  Slack is a better place for code sharing and quick
> > discussion.
> > >
> > > Regards,
> > > Brian Zhou
> > >
> > > -----Original Message-----
> > > From: Yun Tang <myas...@live.com>
> > > Sent: Thursday, May 19, 2022 10:32 AM
> > > To: dev
> > > Subject: Re: [VOTE] Creating an Apache Flink slack workspace
> > >
> > >
> > > [EXTERNAL EMAIL]
> > >
> > > Thanks Xintong for driving this. +1 from my side.
> > >
> > >
> > > Best
> > > Yun Tang
> > > ________________________________
> > > From: Zhu Zhu <reed...@gmail.com>
> > > Sent: Wednesday, May 18, 2022 17:08
> > > To: dev <dev@flink.apache.org>
> > > Subject: Re: [VOTE] Creating an Apache Flink slack workspace
> > >
> > > +1 (binding)
> > >
> > > Thanks,
> > > Zhu
> > >
> > > Timo Walther <twal...@apache.org> 于2022年5月18日周三 16:52写道:
> > >>
> > >> +1 (binding)
> > >>
> > >> Thanks,
> > >> Timo
> > >>
> > >>
> > >> On 17.05.22 20:44, Gyula Fóra wrote:
> > >>> +1 (binding)
> > >>>
> > >>> On Tue, 17 May 2022 at 19:52, Yufei Zhang <affei...@gmail.com>
> wrote:
> > >>>
> > >>>> +1 (nonbinding)
> > >>>>
> > >>>> On Tue, May 17, 2022 at 5:29 PM Márton Balassi <
> > balassi.mar...@gmail.com>
> > >>>> wrote:
> > >>>>
> > >>>>> +1 (binding)
> > >>>>>
> > >>>>> On Tue, May 17, 2022 at 11:00 AM Jingsong Li <
> jingsongl...@gmail.com
> > >
> > >>>>> wrote:
> > >>>>>
> > >>>>>> Thank Xintong for driving this work.
> > >>>>>>
> > >>>>>> +1
> > >>>>>>
> > >>>>>> Best,
> > >>>>>> Jingsong
> > >>>>>>
> > >>>>>> On Tue, May 17, 2022 at 4:49 PM Martijn Visser <
> > >>>> martijnvis...@apache.org
> > >>>>>>
> > >>>>>> wrote:
> > >>>>>>
> > >>>>>>> +1 (binding)
> > >>>>>>>
> > >>>>>>> On Tue, 17 May 2022 at 10:38, Yu Li <car...@gmail.com> wrote:
> > >>>>>>>
> > >>>>>>>> +1 (binding)
> > >>>>>>>>
> > >>>>>>>> Thanks Xintong for driving this!
> > >>>>>>>>
> > >>>>>>>> Best Regards,
> > >>>>>>>> Yu
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>> On Tue, 17 May 2022 at 16:32, Robert Metzger <
> metrob...@gmail.com
> > >
> > >>>>>>> wrote:
> > >>>>>>>>
> > >>>>>>>>> Thanks for starting the VOTE!
> > >>>>>>>>>
> > >>>>>>>>> +1 (binding)
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>> On Tue, May 17, 2022 at 10:29 AM Jark Wu <imj...@gmail.com>
> > >>>> wrote:
> > >>>>>>>>>
> > >>>>>>>>>> Thank Xintong for driving this work.
> > >>>>>>>>>>
> > >>>>>>>>>> +1 from my side (binding)
> > >>>>>>>>>>
> > >>>>>>>>>> Best,
> > >>>>>>>>>> Jark
> > >>>>>>>>>>
> > >>>>>>>>>> On Tue, 17 May 2022 at 16:24, Xintong Song <
> > >>>>> tonysong...@gmail.com>
> > >>>>>>>>> wrote:
> > >>>>>>>>>>
> > >>>>>>>>>>> Hi everyone,
> > >>>>>>>>>>>
> > >>>>>>>>>>> As previously discussed in [1], I would like to open a vote
> > >>>> on
> > >>>>>>>> creating
> > >>>>>>>>>> an
> > >>>>>>>>>>> Apache Flink slack workspace channel.
> > >>>>>>>>>>>
> > >>>>>>>>>>> The proposed actions include:
> > >>>>>>>>>>> - Creating a dedicated slack workspace with the name Apache
> > >>>>> Flink
> > >>>>>>>> that
> > >>>>>>>>> is
> > >>>>>>>>>>> controlled and maintained by the Apache Flink PMC
> > >>>>>>>>>>> - Updating the Flink website about rules for using various
> > >>>>>>>>> communication
> > >>>>>>>>>>> channels
> > >>>>>>>>>>> - Setting up an Archive for the Apache Flink slack
> > >>>>>>>>>>> - Revisiting this initiative by the end of 2022
> > >>>>>>>>>>>
> > >>>>>>>>>>> The vote will last for at least 72 hours, and will be
> > >>>> accepted
> > >>>>>> by a
> > >>>>>>>>>>> consensus of active PMC members.
> > >>>>>>>>>>>
> > >>>>>>>>>>> Best,
> > >>>>>>>>>>>
> > >>>>>>>>>>> Xintong
> > >>>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>
> > >>>>>>>
> > >>>>>>
> > >>>>>
> > >>>>
> > >>>
> > >>
> >
> >
>

Reply via email to