You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by Xintong Song <to...@gmail.com> on 2022/05/23 05:13:58 UTC
[DISCUSS] Initializing Apache Flink Slack
Hi devs,
As we have approved on creating an Apache Flink Slack [1], I'm starting
this new thread to coordinate and give updates on the issues related to
initializing the slack workspace.
## Progress
1. Jark and I have worked on a draft of Slack Management Regulations [2],
including Code of Conduct, Roles and Permissions, etc. Looking forward to
feedback.
2. We have created a slack workspace for initial setups. Anyone who wants
to help with the initialization or just to take an early look, please reach
out for an invitation.
3. The URLs "apache-flink.slack.com" and "apacheflink.slack.com" have
already been taken. I've already sent a help request to the Slack team and
am waiting for their response. Before this gets resolved, we are using "
asf-flink.slack.com" for the moment.
4. I've created FLINK-27719 [3] for tracking the remaining tasks, including
setting up the auto-updated invitation link and the archive.
## How can you help
1. Take a look at the Slack Management Regulations [2] and provide your
feedback
2. Check and pick-up tasks from FLINK-27719 [3]
Best,
Xintong
[1] https://lists.apache.org/thread/d556ywochkpqxbo1yh7ojm751whtojxp
[2]
https://cwiki.apache.org/confluence/display/FLINK/WIP%3A+Slack+Management
[3] https://issues.apache.org/jira/browse/FLINK-27719
Re: [DISCUSS] Initializing Apache Flink Slack
Posted by Robert Metzger <me...@gmail.com>.
I renamed the channel.
On Tue, May 31, 2022 at 10:54 AM Xintong Song <to...@gmail.com> wrote:
> Ok, then let's try it out.
>
> Best,
>
> Xintong
>
>
>
> On Tue, May 31, 2022 at 4:24 PM Robert Metzger <me...@gmail.com>
> wrote:
>
> > +1 to merging #contribution-helps with #dev.
> >
> > I'm pretty sure we'll have to revisit this once we have a bit
> > more experience with running the slack community.
> >
> > On Tue, May 31, 2022 at 10:07 AM Jark Wu <im...@gmail.com> wrote:
> >
> > > I'm fine with the #dev channel.
> > > I remembered in the previous discussion that most people are positive
> > about
> > > the dev channel
> > > as long as the discussions are properly reflected back to the mailing
> > > lists.
> > >
> > > If we create the dev channel, maybe we can merge #contribution-helps
> into
> > > it as well?
> > > Just like, currently, some contributors are looking for reviewers on
> the
> > > dev mailing list.
> > >
> > > Best,
> > > Jark
> > >
> > > On Tue, 31 May 2022 at 15:57, Gyula Fóra <gy...@gmail.com> wrote:
> > >
> > > > I agree with Robert.
> > > >
> > > > I think discussing implementation ideas etc on the dev channel
> > > > briefly before posting discussions on the ML can make the design
> > > > discussions much more productive as the initial iterations can be
> often
> > > > slow and cumbersome via email alone.
> > > >
> > > > I understand the general sentiment against this (based on the general
> > > slack
> > > > discussions) but for me personally (and I think for many Flink
> > > developers)
> > > > this will be one of the more interesting channels :)
> > > > We have to see how this plays out in practice and we can make future
> > > > decisions accordingly.
> > > >
> > > > Gyula
> > > >
> > > >
> > > > On Tue, May 31, 2022 at 9:42 AM Robert Metzger <me...@gmail.com>
> > > > wrote:
> > > >
> > > > > Thanks for your input.
> > > > >
> > > > > I share the concern that we'll potentially have too important
> > > discussions
> > > > > in Slack. However, I would still like to try it out. There are
> valid
> > > > > use-cases, such as requests for VOTEs on releases, or briefly
> > floating
> > > an
> > > > > idea before opening a thread on dev@.
> > > > > If we find out that too much is happening on the channel that
> belongs
> > > to
> > > > > the ML, we can close the channel again.
> > > > >
> > > > >
> > > > >
> > > > > On Tue, May 31, 2022 at 4:01 AM Xintong Song <
> tonysong820@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > #contribution-helps is meant for new contributors to ask
> > > non-technical
> > > > > > questions. E.g., looking for starter issues or reviewers (just
> > don't
> > > DM
> > > > > > people).
> > > > > >
> > > > > > For having a #dev/development, I'm a little concerned this may
> > > > encourage
> > > > > > people to start discussions directly in slack. IMHO, we may want
> to
> > > > stick
> > > > > > to the existing communication channels (mailing lists / jira /
> > github
> > > > pr)
> > > > > > for most of the technical discussions, and only come to slack
> when
> > > the
> > > > > > conversation turns into back-and-forth. In such cases, a
> temporary
> > > > > private
> > > > > > channel or DM group could be set up for the specific topic. Maybe
> > I'm
> > > > > being
> > > > > > too conservative. WDYT?
> > > > > >
> > > > > > Best,
> > > > > >
> > > > > > Xintong
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Tue, May 31, 2022 at 2:06 AM Gyula Fóra <gyula.fora@gmail.com
> >
> > > > wrote:
> > > > > >
> > > > > > > Development channel (#dev/development) makes sense to me. It’s
> > > > related
> > > > > to
> > > > > > > actual development related questions instead of the contrib
> > > process.
> > > > > > >
> > > > > > > Gyula
> > > > > > >
> > > > > > > On Mon, 30 May 2022 at 19:19, Jing Ge <ji...@ververica.com>
> > wrote:
> > > > > > >
> > > > > > > > Good idea, thanks! Is the channel #contribution-helps a good
> > fit
> > > > for
> > > > > > it?
> > > > > > > Or
> > > > > > > > should we just rename it to #development? For me, development
> > is
> > > a
> > > > > > subset
> > > > > > > > of contribution.
> > > > > > > >
> > > > > > > > Best regards,
> > > > > > > > Jing
> > > > > > > >
> > > > > > > > On Mon, May 30, 2022 at 4:28 PM Robert Metzger <
> > > > metrobert@gmail.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Thanks a lot for kicking this off.
> > > > > > > > >
> > > > > > > > > Is there a reason why we haven't set up a #development
> > channel
> > > > yet?
> > > > > > > > > I have a short question that is more suitable for that
> > channel,
> > > > > > > compared
> > > > > > > > to
> > > > > > > > > the dev@ list ;)
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Mon, May 23, 2022 at 7:52 AM Xintong Song <
> > > > > tonysong820@gmail.com>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Hi Kyle,
> > > > > > > > > >
> > > > > > > > > > I've sent an invitation to your gmail.
> > > > > > > > > >
> > > > > > > > > > Best,
> > > > > > > > > >
> > > > > > > > > > Xintong
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Mon, May 23, 2022 at 1:39 PM Kyle Bendickson <
> > > > kyle@tabular.io
> > > > > >
> > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Hi Xintong!
> > > > > > > > > > >
> > > > > > > > > > > I’d love to take an early look if possible. I’m not a
> > > > committer
> > > > > > > here,
> > > > > > > > > > but I
> > > > > > > > > > > have a role in the Apache Iceberg slack and am looking
> > > > forward
> > > > > to
> > > > > > > the
> > > > > > > > > > Flink
> > > > > > > > > > > slack, particularly given the strong integration
> between
> > > > > Iceberg
> > > > > > > and
> > > > > > > > > > Flink.
> > > > > > > > > > >
> > > > > > > > > > > Thanks,
> > > > > > > > > > > Kyle!
> > > > > > > > > > > kjbendickson[at]gmail.com (preferred invite email)
> > > > > > > > > > > kyle[at]tabular.io (work email)
> > > > > > > > > > >
> > > > > > > > > > > On Sun, May 22, 2022 at 10:14 PM Xintong Song <
> > > > > > > tonysong820@gmail.com
> > > > > > > > >
> > > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Hi devs,
> > > > > > > > > > > >
> > > > > > > > > > > > As we have approved on creating an Apache Flink Slack
> > > [1],
> > > > > I'm
> > > > > > > > > starting
> > > > > > > > > > > > this new thread to coordinate and give updates on the
> > > > issues
> > > > > > > > related
> > > > > > > > > to
> > > > > > > > > > > > initializing the slack workspace.
> > > > > > > > > > > >
> > > > > > > > > > > > ## Progress
> > > > > > > > > > > > 1. Jark and I have worked on a draft of Slack
> > Management
> > > > > > > > Regulations
> > > > > > > > > > [2],
> > > > > > > > > > > > including Code of Conduct, Roles and Permissions,
> etc.
> > > > > Looking
> > > > > > > > > forward
> > > > > > > > > > to
> > > > > > > > > > > > feedback.
> > > > > > > > > > > > 2. We have created a slack workspace for initial
> > setups.
> > > > > Anyone
> > > > > > > who
> > > > > > > > > > wants
> > > > > > > > > > > > to help with the initialization or just to take an
> > early
> > > > > look,
> > > > > > > > please
> > > > > > > > > > > reach
> > > > > > > > > > > > out for an invitation.
> > > > > > > > > > > > 3. The URLs "apache-flink.slack.com" and "
> > > > > > apacheflink.slack.com"
> > > > > > > > > have
> > > > > > > > > > > > already been taken. I've already sent a help request
> to
> > > the
> > > > > > Slack
> > > > > > > > > team
> > > > > > > > > > > and
> > > > > > > > > > > > am waiting for their response. Before this gets
> > resolved,
> > > > we
> > > > > > are
> > > > > > > > > using
> > > > > > > > > > "
> > > > > > > > > > > > asf-flink.slack.com" for the moment.
> > > > > > > > > > > > 4. I've created FLINK-27719 [3] for tracking the
> > > remaining
> > > > > > tasks,
> > > > > > > > > > > including
> > > > > > > > > > > > setting up the auto-updated invitation link and the
> > > > archive.
> > > > > > > > > > > >
> > > > > > > > > > > > ## How can you help
> > > > > > > > > > > > 1. Take a look at the Slack Management Regulations
> [2]
> > > and
> > > > > > > provide
> > > > > > > > > your
> > > > > > > > > > > > feedback
> > > > > > > > > > > > 2. Check and pick-up tasks from FLINK-27719 [3]
> > > > > > > > > > > >
> > > > > > > > > > > > Best,
> > > > > > > > > > > >
> > > > > > > > > > > > Xintong
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > [1]
> > > > > > > >
> > https://lists.apache.org/thread/d556ywochkpqxbo1yh7ojm751whtojxp
> > > > > > > > > > > >
> > > > > > > > > > > > [2]
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/WIP%3A+Slack+Management
> > > > > > > > > > > >
> > > > > > > > > > > > [3]
> https://issues.apache.org/jira/browse/FLINK-27719
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Initializing Apache Flink Slack
Posted by Xintong Song <to...@gmail.com>.
Ok, then let's try it out.
Best,
Xintong
On Tue, May 31, 2022 at 4:24 PM Robert Metzger <me...@gmail.com> wrote:
> +1 to merging #contribution-helps with #dev.
>
> I'm pretty sure we'll have to revisit this once we have a bit
> more experience with running the slack community.
>
> On Tue, May 31, 2022 at 10:07 AM Jark Wu <im...@gmail.com> wrote:
>
> > I'm fine with the #dev channel.
> > I remembered in the previous discussion that most people are positive
> about
> > the dev channel
> > as long as the discussions are properly reflected back to the mailing
> > lists.
> >
> > If we create the dev channel, maybe we can merge #contribution-helps into
> > it as well?
> > Just like, currently, some contributors are looking for reviewers on the
> > dev mailing list.
> >
> > Best,
> > Jark
> >
> > On Tue, 31 May 2022 at 15:57, Gyula Fóra <gy...@gmail.com> wrote:
> >
> > > I agree with Robert.
> > >
> > > I think discussing implementation ideas etc on the dev channel
> > > briefly before posting discussions on the ML can make the design
> > > discussions much more productive as the initial iterations can be often
> > > slow and cumbersome via email alone.
> > >
> > > I understand the general sentiment against this (based on the general
> > slack
> > > discussions) but for me personally (and I think for many Flink
> > developers)
> > > this will be one of the more interesting channels :)
> > > We have to see how this plays out in practice and we can make future
> > > decisions accordingly.
> > >
> > > Gyula
> > >
> > >
> > > On Tue, May 31, 2022 at 9:42 AM Robert Metzger <me...@gmail.com>
> > > wrote:
> > >
> > > > Thanks for your input.
> > > >
> > > > I share the concern that we'll potentially have too important
> > discussions
> > > > in Slack. However, I would still like to try it out. There are valid
> > > > use-cases, such as requests for VOTEs on releases, or briefly
> floating
> > an
> > > > idea before opening a thread on dev@.
> > > > If we find out that too much is happening on the channel that belongs
> > to
> > > > the ML, we can close the channel again.
> > > >
> > > >
> > > >
> > > > On Tue, May 31, 2022 at 4:01 AM Xintong Song <to...@gmail.com>
> > > > wrote:
> > > >
> > > > > #contribution-helps is meant for new contributors to ask
> > non-technical
> > > > > questions. E.g., looking for starter issues or reviewers (just
> don't
> > DM
> > > > > people).
> > > > >
> > > > > For having a #dev/development, I'm a little concerned this may
> > > encourage
> > > > > people to start discussions directly in slack. IMHO, we may want to
> > > stick
> > > > > to the existing communication channels (mailing lists / jira /
> github
> > > pr)
> > > > > for most of the technical discussions, and only come to slack when
> > the
> > > > > conversation turns into back-and-forth. In such cases, a temporary
> > > > private
> > > > > channel or DM group could be set up for the specific topic. Maybe
> I'm
> > > > being
> > > > > too conservative. WDYT?
> > > > >
> > > > > Best,
> > > > >
> > > > > Xintong
> > > > >
> > > > >
> > > > >
> > > > > On Tue, May 31, 2022 at 2:06 AM Gyula Fóra <gy...@gmail.com>
> > > wrote:
> > > > >
> > > > > > Development channel (#dev/development) makes sense to me. It’s
> > > related
> > > > to
> > > > > > actual development related questions instead of the contrib
> > process.
> > > > > >
> > > > > > Gyula
> > > > > >
> > > > > > On Mon, 30 May 2022 at 19:19, Jing Ge <ji...@ververica.com>
> wrote:
> > > > > >
> > > > > > > Good idea, thanks! Is the channel #contribution-helps a good
> fit
> > > for
> > > > > it?
> > > > > > Or
> > > > > > > should we just rename it to #development? For me, development
> is
> > a
> > > > > subset
> > > > > > > of contribution.
> > > > > > >
> > > > > > > Best regards,
> > > > > > > Jing
> > > > > > >
> > > > > > > On Mon, May 30, 2022 at 4:28 PM Robert Metzger <
> > > metrobert@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Thanks a lot for kicking this off.
> > > > > > > >
> > > > > > > > Is there a reason why we haven't set up a #development
> channel
> > > yet?
> > > > > > > > I have a short question that is more suitable for that
> channel,
> > > > > > compared
> > > > > > > to
> > > > > > > > the dev@ list ;)
> > > > > > > >
> > > > > > > >
> > > > > > > > On Mon, May 23, 2022 at 7:52 AM Xintong Song <
> > > > tonysong820@gmail.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Hi Kyle,
> > > > > > > > >
> > > > > > > > > I've sent an invitation to your gmail.
> > > > > > > > >
> > > > > > > > > Best,
> > > > > > > > >
> > > > > > > > > Xintong
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Mon, May 23, 2022 at 1:39 PM Kyle Bendickson <
> > > kyle@tabular.io
> > > > >
> > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Hi Xintong!
> > > > > > > > > >
> > > > > > > > > > I’d love to take an early look if possible. I’m not a
> > > committer
> > > > > > here,
> > > > > > > > > but I
> > > > > > > > > > have a role in the Apache Iceberg slack and am looking
> > > forward
> > > > to
> > > > > > the
> > > > > > > > > Flink
> > > > > > > > > > slack, particularly given the strong integration between
> > > > Iceberg
> > > > > > and
> > > > > > > > > Flink.
> > > > > > > > > >
> > > > > > > > > > Thanks,
> > > > > > > > > > Kyle!
> > > > > > > > > > kjbendickson[at]gmail.com (preferred invite email)
> > > > > > > > > > kyle[at]tabular.io (work email)
> > > > > > > > > >
> > > > > > > > > > On Sun, May 22, 2022 at 10:14 PM Xintong Song <
> > > > > > tonysong820@gmail.com
> > > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Hi devs,
> > > > > > > > > > >
> > > > > > > > > > > As we have approved on creating an Apache Flink Slack
> > [1],
> > > > I'm
> > > > > > > > starting
> > > > > > > > > > > this new thread to coordinate and give updates on the
> > > issues
> > > > > > > related
> > > > > > > > to
> > > > > > > > > > > initializing the slack workspace.
> > > > > > > > > > >
> > > > > > > > > > > ## Progress
> > > > > > > > > > > 1. Jark and I have worked on a draft of Slack
> Management
> > > > > > > Regulations
> > > > > > > > > [2],
> > > > > > > > > > > including Code of Conduct, Roles and Permissions, etc.
> > > > Looking
> > > > > > > > forward
> > > > > > > > > to
> > > > > > > > > > > feedback.
> > > > > > > > > > > 2. We have created a slack workspace for initial
> setups.
> > > > Anyone
> > > > > > who
> > > > > > > > > wants
> > > > > > > > > > > to help with the initialization or just to take an
> early
> > > > look,
> > > > > > > please
> > > > > > > > > > reach
> > > > > > > > > > > out for an invitation.
> > > > > > > > > > > 3. The URLs "apache-flink.slack.com" and "
> > > > > apacheflink.slack.com"
> > > > > > > > have
> > > > > > > > > > > already been taken. I've already sent a help request to
> > the
> > > > > Slack
> > > > > > > > team
> > > > > > > > > > and
> > > > > > > > > > > am waiting for their response. Before this gets
> resolved,
> > > we
> > > > > are
> > > > > > > > using
> > > > > > > > > "
> > > > > > > > > > > asf-flink.slack.com" for the moment.
> > > > > > > > > > > 4. I've created FLINK-27719 [3] for tracking the
> > remaining
> > > > > tasks,
> > > > > > > > > > including
> > > > > > > > > > > setting up the auto-updated invitation link and the
> > > archive.
> > > > > > > > > > >
> > > > > > > > > > > ## How can you help
> > > > > > > > > > > 1. Take a look at the Slack Management Regulations [2]
> > and
> > > > > > provide
> > > > > > > > your
> > > > > > > > > > > feedback
> > > > > > > > > > > 2. Check and pick-up tasks from FLINK-27719 [3]
> > > > > > > > > > >
> > > > > > > > > > > Best,
> > > > > > > > > > >
> > > > > > > > > > > Xintong
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > [1]
> > > > > > >
> https://lists.apache.org/thread/d556ywochkpqxbo1yh7ojm751whtojxp
> > > > > > > > > > >
> > > > > > > > > > > [2]
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/WIP%3A+Slack+Management
> > > > > > > > > > >
> > > > > > > > > > > [3] https://issues.apache.org/jira/browse/FLINK-27719
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Initializing Apache Flink Slack
Posted by Robert Metzger <me...@gmail.com>.
+1 to merging #contribution-helps with #dev.
I'm pretty sure we'll have to revisit this once we have a bit
more experience with running the slack community.
On Tue, May 31, 2022 at 10:07 AM Jark Wu <im...@gmail.com> wrote:
> I'm fine with the #dev channel.
> I remembered in the previous discussion that most people are positive about
> the dev channel
> as long as the discussions are properly reflected back to the mailing
> lists.
>
> If we create the dev channel, maybe we can merge #contribution-helps into
> it as well?
> Just like, currently, some contributors are looking for reviewers on the
> dev mailing list.
>
> Best,
> Jark
>
> On Tue, 31 May 2022 at 15:57, Gyula Fóra <gy...@gmail.com> wrote:
>
> > I agree with Robert.
> >
> > I think discussing implementation ideas etc on the dev channel
> > briefly before posting discussions on the ML can make the design
> > discussions much more productive as the initial iterations can be often
> > slow and cumbersome via email alone.
> >
> > I understand the general sentiment against this (based on the general
> slack
> > discussions) but for me personally (and I think for many Flink
> developers)
> > this will be one of the more interesting channels :)
> > We have to see how this plays out in practice and we can make future
> > decisions accordingly.
> >
> > Gyula
> >
> >
> > On Tue, May 31, 2022 at 9:42 AM Robert Metzger <me...@gmail.com>
> > wrote:
> >
> > > Thanks for your input.
> > >
> > > I share the concern that we'll potentially have too important
> discussions
> > > in Slack. However, I would still like to try it out. There are valid
> > > use-cases, such as requests for VOTEs on releases, or briefly floating
> an
> > > idea before opening a thread on dev@.
> > > If we find out that too much is happening on the channel that belongs
> to
> > > the ML, we can close the channel again.
> > >
> > >
> > >
> > > On Tue, May 31, 2022 at 4:01 AM Xintong Song <to...@gmail.com>
> > > wrote:
> > >
> > > > #contribution-helps is meant for new contributors to ask
> non-technical
> > > > questions. E.g., looking for starter issues or reviewers (just don't
> DM
> > > > people).
> > > >
> > > > For having a #dev/development, I'm a little concerned this may
> > encourage
> > > > people to start discussions directly in slack. IMHO, we may want to
> > stick
> > > > to the existing communication channels (mailing lists / jira / github
> > pr)
> > > > for most of the technical discussions, and only come to slack when
> the
> > > > conversation turns into back-and-forth. In such cases, a temporary
> > > private
> > > > channel or DM group could be set up for the specific topic. Maybe I'm
> > > being
> > > > too conservative. WDYT?
> > > >
> > > > Best,
> > > >
> > > > Xintong
> > > >
> > > >
> > > >
> > > > On Tue, May 31, 2022 at 2:06 AM Gyula Fóra <gy...@gmail.com>
> > wrote:
> > > >
> > > > > Development channel (#dev/development) makes sense to me. It’s
> > related
> > > to
> > > > > actual development related questions instead of the contrib
> process.
> > > > >
> > > > > Gyula
> > > > >
> > > > > On Mon, 30 May 2022 at 19:19, Jing Ge <ji...@ververica.com> wrote:
> > > > >
> > > > > > Good idea, thanks! Is the channel #contribution-helps a good fit
> > for
> > > > it?
> > > > > Or
> > > > > > should we just rename it to #development? For me, development is
> a
> > > > subset
> > > > > > of contribution.
> > > > > >
> > > > > > Best regards,
> > > > > > Jing
> > > > > >
> > > > > > On Mon, May 30, 2022 at 4:28 PM Robert Metzger <
> > metrobert@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Thanks a lot for kicking this off.
> > > > > > >
> > > > > > > Is there a reason why we haven't set up a #development channel
> > yet?
> > > > > > > I have a short question that is more suitable for that channel,
> > > > > compared
> > > > > > to
> > > > > > > the dev@ list ;)
> > > > > > >
> > > > > > >
> > > > > > > On Mon, May 23, 2022 at 7:52 AM Xintong Song <
> > > tonysong820@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hi Kyle,
> > > > > > > >
> > > > > > > > I've sent an invitation to your gmail.
> > > > > > > >
> > > > > > > > Best,
> > > > > > > >
> > > > > > > > Xintong
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Mon, May 23, 2022 at 1:39 PM Kyle Bendickson <
> > kyle@tabular.io
> > > >
> > > > > > wrote:
> > > > > > > >
> > > > > > > > > Hi Xintong!
> > > > > > > > >
> > > > > > > > > I’d love to take an early look if possible. I’m not a
> > committer
> > > > > here,
> > > > > > > > but I
> > > > > > > > > have a role in the Apache Iceberg slack and am looking
> > forward
> > > to
> > > > > the
> > > > > > > > Flink
> > > > > > > > > slack, particularly given the strong integration between
> > > Iceberg
> > > > > and
> > > > > > > > Flink.
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > > Kyle!
> > > > > > > > > kjbendickson[at]gmail.com (preferred invite email)
> > > > > > > > > kyle[at]tabular.io (work email)
> > > > > > > > >
> > > > > > > > > On Sun, May 22, 2022 at 10:14 PM Xintong Song <
> > > > > tonysong820@gmail.com
> > > > > > >
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Hi devs,
> > > > > > > > > >
> > > > > > > > > > As we have approved on creating an Apache Flink Slack
> [1],
> > > I'm
> > > > > > > starting
> > > > > > > > > > this new thread to coordinate and give updates on the
> > issues
> > > > > > related
> > > > > > > to
> > > > > > > > > > initializing the slack workspace.
> > > > > > > > > >
> > > > > > > > > > ## Progress
> > > > > > > > > > 1. Jark and I have worked on a draft of Slack Management
> > > > > > Regulations
> > > > > > > > [2],
> > > > > > > > > > including Code of Conduct, Roles and Permissions, etc.
> > > Looking
> > > > > > > forward
> > > > > > > > to
> > > > > > > > > > feedback.
> > > > > > > > > > 2. We have created a slack workspace for initial setups.
> > > Anyone
> > > > > who
> > > > > > > > wants
> > > > > > > > > > to help with the initialization or just to take an early
> > > look,
> > > > > > please
> > > > > > > > > reach
> > > > > > > > > > out for an invitation.
> > > > > > > > > > 3. The URLs "apache-flink.slack.com" and "
> > > > apacheflink.slack.com"
> > > > > > > have
> > > > > > > > > > already been taken. I've already sent a help request to
> the
> > > > Slack
> > > > > > > team
> > > > > > > > > and
> > > > > > > > > > am waiting for their response. Before this gets resolved,
> > we
> > > > are
> > > > > > > using
> > > > > > > > "
> > > > > > > > > > asf-flink.slack.com" for the moment.
> > > > > > > > > > 4. I've created FLINK-27719 [3] for tracking the
> remaining
> > > > tasks,
> > > > > > > > > including
> > > > > > > > > > setting up the auto-updated invitation link and the
> > archive.
> > > > > > > > > >
> > > > > > > > > > ## How can you help
> > > > > > > > > > 1. Take a look at the Slack Management Regulations [2]
> and
> > > > > provide
> > > > > > > your
> > > > > > > > > > feedback
> > > > > > > > > > 2. Check and pick-up tasks from FLINK-27719 [3]
> > > > > > > > > >
> > > > > > > > > > Best,
> > > > > > > > > >
> > > > > > > > > > Xintong
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > [1]
> > > > > > https://lists.apache.org/thread/d556ywochkpqxbo1yh7ojm751whtojxp
> > > > > > > > > >
> > > > > > > > > > [2]
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/WIP%3A+Slack+Management
> > > > > > > > > >
> > > > > > > > > > [3] https://issues.apache.org/jira/browse/FLINK-27719
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Initializing Apache Flink Slack
Posted by Jark Wu <im...@gmail.com>.
I'm fine with the #dev channel.
I remembered in the previous discussion that most people are positive about
the dev channel
as long as the discussions are properly reflected back to the mailing
lists.
If we create the dev channel, maybe we can merge #contribution-helps into
it as well?
Just like, currently, some contributors are looking for reviewers on the
dev mailing list.
Best,
Jark
On Tue, 31 May 2022 at 15:57, Gyula Fóra <gy...@gmail.com> wrote:
> I agree with Robert.
>
> I think discussing implementation ideas etc on the dev channel
> briefly before posting discussions on the ML can make the design
> discussions much more productive as the initial iterations can be often
> slow and cumbersome via email alone.
>
> I understand the general sentiment against this (based on the general slack
> discussions) but for me personally (and I think for many Flink developers)
> this will be one of the more interesting channels :)
> We have to see how this plays out in practice and we can make future
> decisions accordingly.
>
> Gyula
>
>
> On Tue, May 31, 2022 at 9:42 AM Robert Metzger <me...@gmail.com>
> wrote:
>
> > Thanks for your input.
> >
> > I share the concern that we'll potentially have too important discussions
> > in Slack. However, I would still like to try it out. There are valid
> > use-cases, such as requests for VOTEs on releases, or briefly floating an
> > idea before opening a thread on dev@.
> > If we find out that too much is happening on the channel that belongs to
> > the ML, we can close the channel again.
> >
> >
> >
> > On Tue, May 31, 2022 at 4:01 AM Xintong Song <to...@gmail.com>
> > wrote:
> >
> > > #contribution-helps is meant for new contributors to ask non-technical
> > > questions. E.g., looking for starter issues or reviewers (just don't DM
> > > people).
> > >
> > > For having a #dev/development, I'm a little concerned this may
> encourage
> > > people to start discussions directly in slack. IMHO, we may want to
> stick
> > > to the existing communication channels (mailing lists / jira / github
> pr)
> > > for most of the technical discussions, and only come to slack when the
> > > conversation turns into back-and-forth. In such cases, a temporary
> > private
> > > channel or DM group could be set up for the specific topic. Maybe I'm
> > being
> > > too conservative. WDYT?
> > >
> > > Best,
> > >
> > > Xintong
> > >
> > >
> > >
> > > On Tue, May 31, 2022 at 2:06 AM Gyula Fóra <gy...@gmail.com>
> wrote:
> > >
> > > > Development channel (#dev/development) makes sense to me. It’s
> related
> > to
> > > > actual development related questions instead of the contrib process.
> > > >
> > > > Gyula
> > > >
> > > > On Mon, 30 May 2022 at 19:19, Jing Ge <ji...@ververica.com> wrote:
> > > >
> > > > > Good idea, thanks! Is the channel #contribution-helps a good fit
> for
> > > it?
> > > > Or
> > > > > should we just rename it to #development? For me, development is a
> > > subset
> > > > > of contribution.
> > > > >
> > > > > Best regards,
> > > > > Jing
> > > > >
> > > > > On Mon, May 30, 2022 at 4:28 PM Robert Metzger <
> metrobert@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Thanks a lot for kicking this off.
> > > > > >
> > > > > > Is there a reason why we haven't set up a #development channel
> yet?
> > > > > > I have a short question that is more suitable for that channel,
> > > > compared
> > > > > to
> > > > > > the dev@ list ;)
> > > > > >
> > > > > >
> > > > > > On Mon, May 23, 2022 at 7:52 AM Xintong Song <
> > tonysong820@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Hi Kyle,
> > > > > > >
> > > > > > > I've sent an invitation to your gmail.
> > > > > > >
> > > > > > > Best,
> > > > > > >
> > > > > > > Xintong
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Mon, May 23, 2022 at 1:39 PM Kyle Bendickson <
> kyle@tabular.io
> > >
> > > > > wrote:
> > > > > > >
> > > > > > > > Hi Xintong!
> > > > > > > >
> > > > > > > > I’d love to take an early look if possible. I’m not a
> committer
> > > > here,
> > > > > > > but I
> > > > > > > > have a role in the Apache Iceberg slack and am looking
> forward
> > to
> > > > the
> > > > > > > Flink
> > > > > > > > slack, particularly given the strong integration between
> > Iceberg
> > > > and
> > > > > > > Flink.
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Kyle!
> > > > > > > > kjbendickson[at]gmail.com (preferred invite email)
> > > > > > > > kyle[at]tabular.io (work email)
> > > > > > > >
> > > > > > > > On Sun, May 22, 2022 at 10:14 PM Xintong Song <
> > > > tonysong820@gmail.com
> > > > > >
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Hi devs,
> > > > > > > > >
> > > > > > > > > As we have approved on creating an Apache Flink Slack [1],
> > I'm
> > > > > > starting
> > > > > > > > > this new thread to coordinate and give updates on the
> issues
> > > > > related
> > > > > > to
> > > > > > > > > initializing the slack workspace.
> > > > > > > > >
> > > > > > > > > ## Progress
> > > > > > > > > 1. Jark and I have worked on a draft of Slack Management
> > > > > Regulations
> > > > > > > [2],
> > > > > > > > > including Code of Conduct, Roles and Permissions, etc.
> > Looking
> > > > > > forward
> > > > > > > to
> > > > > > > > > feedback.
> > > > > > > > > 2. We have created a slack workspace for initial setups.
> > Anyone
> > > > who
> > > > > > > wants
> > > > > > > > > to help with the initialization or just to take an early
> > look,
> > > > > please
> > > > > > > > reach
> > > > > > > > > out for an invitation.
> > > > > > > > > 3. The URLs "apache-flink.slack.com" and "
> > > apacheflink.slack.com"
> > > > > > have
> > > > > > > > > already been taken. I've already sent a help request to the
> > > Slack
> > > > > > team
> > > > > > > > and
> > > > > > > > > am waiting for their response. Before this gets resolved,
> we
> > > are
> > > > > > using
> > > > > > > "
> > > > > > > > > asf-flink.slack.com" for the moment.
> > > > > > > > > 4. I've created FLINK-27719 [3] for tracking the remaining
> > > tasks,
> > > > > > > > including
> > > > > > > > > setting up the auto-updated invitation link and the
> archive.
> > > > > > > > >
> > > > > > > > > ## How can you help
> > > > > > > > > 1. Take a look at the Slack Management Regulations [2] and
> > > > provide
> > > > > > your
> > > > > > > > > feedback
> > > > > > > > > 2. Check and pick-up tasks from FLINK-27719 [3]
> > > > > > > > >
> > > > > > > > > Best,
> > > > > > > > >
> > > > > > > > > Xintong
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > [1]
> > > > > https://lists.apache.org/thread/d556ywochkpqxbo1yh7ojm751whtojxp
> > > > > > > > >
> > > > > > > > > [2]
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/WIP%3A+Slack+Management
> > > > > > > > >
> > > > > > > > > [3] https://issues.apache.org/jira/browse/FLINK-27719
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Initializing Apache Flink Slack
Posted by Gyula Fóra <gy...@gmail.com>.
I agree with Robert.
I think discussing implementation ideas etc on the dev channel
briefly before posting discussions on the ML can make the design
discussions much more productive as the initial iterations can be often
slow and cumbersome via email alone.
I understand the general sentiment against this (based on the general slack
discussions) but for me personally (and I think for many Flink developers)
this will be one of the more interesting channels :)
We have to see how this plays out in practice and we can make future
decisions accordingly.
Gyula
On Tue, May 31, 2022 at 9:42 AM Robert Metzger <me...@gmail.com> wrote:
> Thanks for your input.
>
> I share the concern that we'll potentially have too important discussions
> in Slack. However, I would still like to try it out. There are valid
> use-cases, such as requests for VOTEs on releases, or briefly floating an
> idea before opening a thread on dev@.
> If we find out that too much is happening on the channel that belongs to
> the ML, we can close the channel again.
>
>
>
> On Tue, May 31, 2022 at 4:01 AM Xintong Song <to...@gmail.com>
> wrote:
>
> > #contribution-helps is meant for new contributors to ask non-technical
> > questions. E.g., looking for starter issues or reviewers (just don't DM
> > people).
> >
> > For having a #dev/development, I'm a little concerned this may encourage
> > people to start discussions directly in slack. IMHO, we may want to stick
> > to the existing communication channels (mailing lists / jira / github pr)
> > for most of the technical discussions, and only come to slack when the
> > conversation turns into back-and-forth. In such cases, a temporary
> private
> > channel or DM group could be set up for the specific topic. Maybe I'm
> being
> > too conservative. WDYT?
> >
> > Best,
> >
> > Xintong
> >
> >
> >
> > On Tue, May 31, 2022 at 2:06 AM Gyula Fóra <gy...@gmail.com> wrote:
> >
> > > Development channel (#dev/development) makes sense to me. It’s related
> to
> > > actual development related questions instead of the contrib process.
> > >
> > > Gyula
> > >
> > > On Mon, 30 May 2022 at 19:19, Jing Ge <ji...@ververica.com> wrote:
> > >
> > > > Good idea, thanks! Is the channel #contribution-helps a good fit for
> > it?
> > > Or
> > > > should we just rename it to #development? For me, development is a
> > subset
> > > > of contribution.
> > > >
> > > > Best regards,
> > > > Jing
> > > >
> > > > On Mon, May 30, 2022 at 4:28 PM Robert Metzger <me...@gmail.com>
> > > > wrote:
> > > >
> > > > > Thanks a lot for kicking this off.
> > > > >
> > > > > Is there a reason why we haven't set up a #development channel yet?
> > > > > I have a short question that is more suitable for that channel,
> > > compared
> > > > to
> > > > > the dev@ list ;)
> > > > >
> > > > >
> > > > > On Mon, May 23, 2022 at 7:52 AM Xintong Song <
> tonysong820@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Hi Kyle,
> > > > > >
> > > > > > I've sent an invitation to your gmail.
> > > > > >
> > > > > > Best,
> > > > > >
> > > > > > Xintong
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Mon, May 23, 2022 at 1:39 PM Kyle Bendickson <kyle@tabular.io
> >
> > > > wrote:
> > > > > >
> > > > > > > Hi Xintong!
> > > > > > >
> > > > > > > I’d love to take an early look if possible. I’m not a committer
> > > here,
> > > > > > but I
> > > > > > > have a role in the Apache Iceberg slack and am looking forward
> to
> > > the
> > > > > > Flink
> > > > > > > slack, particularly given the strong integration between
> Iceberg
> > > and
> > > > > > Flink.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Kyle!
> > > > > > > kjbendickson[at]gmail.com (preferred invite email)
> > > > > > > kyle[at]tabular.io (work email)
> > > > > > >
> > > > > > > On Sun, May 22, 2022 at 10:14 PM Xintong Song <
> > > tonysong820@gmail.com
> > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hi devs,
> > > > > > > >
> > > > > > > > As we have approved on creating an Apache Flink Slack [1],
> I'm
> > > > > starting
> > > > > > > > this new thread to coordinate and give updates on the issues
> > > > related
> > > > > to
> > > > > > > > initializing the slack workspace.
> > > > > > > >
> > > > > > > > ## Progress
> > > > > > > > 1. Jark and I have worked on a draft of Slack Management
> > > > Regulations
> > > > > > [2],
> > > > > > > > including Code of Conduct, Roles and Permissions, etc.
> Looking
> > > > > forward
> > > > > > to
> > > > > > > > feedback.
> > > > > > > > 2. We have created a slack workspace for initial setups.
> Anyone
> > > who
> > > > > > wants
> > > > > > > > to help with the initialization or just to take an early
> look,
> > > > please
> > > > > > > reach
> > > > > > > > out for an invitation.
> > > > > > > > 3. The URLs "apache-flink.slack.com" and "
> > apacheflink.slack.com"
> > > > > have
> > > > > > > > already been taken. I've already sent a help request to the
> > Slack
> > > > > team
> > > > > > > and
> > > > > > > > am waiting for their response. Before this gets resolved, we
> > are
> > > > > using
> > > > > > "
> > > > > > > > asf-flink.slack.com" for the moment.
> > > > > > > > 4. I've created FLINK-27719 [3] for tracking the remaining
> > tasks,
> > > > > > > including
> > > > > > > > setting up the auto-updated invitation link and the archive.
> > > > > > > >
> > > > > > > > ## How can you help
> > > > > > > > 1. Take a look at the Slack Management Regulations [2] and
> > > provide
> > > > > your
> > > > > > > > feedback
> > > > > > > > 2. Check and pick-up tasks from FLINK-27719 [3]
> > > > > > > >
> > > > > > > > Best,
> > > > > > > >
> > > > > > > > Xintong
> > > > > > > >
> > > > > > > >
> > > > > > > > [1]
> > > > https://lists.apache.org/thread/d556ywochkpqxbo1yh7ojm751whtojxp
> > > > > > > >
> > > > > > > > [2]
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/WIP%3A+Slack+Management
> > > > > > > >
> > > > > > > > [3] https://issues.apache.org/jira/browse/FLINK-27719
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Initializing Apache Flink Slack
Posted by Robert Metzger <me...@gmail.com>.
Thanks for your input.
I share the concern that we'll potentially have too important discussions
in Slack. However, I would still like to try it out. There are valid
use-cases, such as requests for VOTEs on releases, or briefly floating an
idea before opening a thread on dev@.
If we find out that too much is happening on the channel that belongs to
the ML, we can close the channel again.
On Tue, May 31, 2022 at 4:01 AM Xintong Song <to...@gmail.com> wrote:
> #contribution-helps is meant for new contributors to ask non-technical
> questions. E.g., looking for starter issues or reviewers (just don't DM
> people).
>
> For having a #dev/development, I'm a little concerned this may encourage
> people to start discussions directly in slack. IMHO, we may want to stick
> to the existing communication channels (mailing lists / jira / github pr)
> for most of the technical discussions, and only come to slack when the
> conversation turns into back-and-forth. In such cases, a temporary private
> channel or DM group could be set up for the specific topic. Maybe I'm being
> too conservative. WDYT?
>
> Best,
>
> Xintong
>
>
>
> On Tue, May 31, 2022 at 2:06 AM Gyula Fóra <gy...@gmail.com> wrote:
>
> > Development channel (#dev/development) makes sense to me. It’s related to
> > actual development related questions instead of the contrib process.
> >
> > Gyula
> >
> > On Mon, 30 May 2022 at 19:19, Jing Ge <ji...@ververica.com> wrote:
> >
> > > Good idea, thanks! Is the channel #contribution-helps a good fit for
> it?
> > Or
> > > should we just rename it to #development? For me, development is a
> subset
> > > of contribution.
> > >
> > > Best regards,
> > > Jing
> > >
> > > On Mon, May 30, 2022 at 4:28 PM Robert Metzger <me...@gmail.com>
> > > wrote:
> > >
> > > > Thanks a lot for kicking this off.
> > > >
> > > > Is there a reason why we haven't set up a #development channel yet?
> > > > I have a short question that is more suitable for that channel,
> > compared
> > > to
> > > > the dev@ list ;)
> > > >
> > > >
> > > > On Mon, May 23, 2022 at 7:52 AM Xintong Song <to...@gmail.com>
> > > > wrote:
> > > >
> > > > > Hi Kyle,
> > > > >
> > > > > I've sent an invitation to your gmail.
> > > > >
> > > > > Best,
> > > > >
> > > > > Xintong
> > > > >
> > > > >
> > > > >
> > > > > On Mon, May 23, 2022 at 1:39 PM Kyle Bendickson <ky...@tabular.io>
> > > wrote:
> > > > >
> > > > > > Hi Xintong!
> > > > > >
> > > > > > I’d love to take an early look if possible. I’m not a committer
> > here,
> > > > > but I
> > > > > > have a role in the Apache Iceberg slack and am looking forward to
> > the
> > > > > Flink
> > > > > > slack, particularly given the strong integration between Iceberg
> > and
> > > > > Flink.
> > > > > >
> > > > > > Thanks,
> > > > > > Kyle!
> > > > > > kjbendickson[at]gmail.com (preferred invite email)
> > > > > > kyle[at]tabular.io (work email)
> > > > > >
> > > > > > On Sun, May 22, 2022 at 10:14 PM Xintong Song <
> > tonysong820@gmail.com
> > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Hi devs,
> > > > > > >
> > > > > > > As we have approved on creating an Apache Flink Slack [1], I'm
> > > > starting
> > > > > > > this new thread to coordinate and give updates on the issues
> > > related
> > > > to
> > > > > > > initializing the slack workspace.
> > > > > > >
> > > > > > > ## Progress
> > > > > > > 1. Jark and I have worked on a draft of Slack Management
> > > Regulations
> > > > > [2],
> > > > > > > including Code of Conduct, Roles and Permissions, etc. Looking
> > > > forward
> > > > > to
> > > > > > > feedback.
> > > > > > > 2. We have created a slack workspace for initial setups. Anyone
> > who
> > > > > wants
> > > > > > > to help with the initialization or just to take an early look,
> > > please
> > > > > > reach
> > > > > > > out for an invitation.
> > > > > > > 3. The URLs "apache-flink.slack.com" and "
> apacheflink.slack.com"
> > > > have
> > > > > > > already been taken. I've already sent a help request to the
> Slack
> > > > team
> > > > > > and
> > > > > > > am waiting for their response. Before this gets resolved, we
> are
> > > > using
> > > > > "
> > > > > > > asf-flink.slack.com" for the moment.
> > > > > > > 4. I've created FLINK-27719 [3] for tracking the remaining
> tasks,
> > > > > > including
> > > > > > > setting up the auto-updated invitation link and the archive.
> > > > > > >
> > > > > > > ## How can you help
> > > > > > > 1. Take a look at the Slack Management Regulations [2] and
> > provide
> > > > your
> > > > > > > feedback
> > > > > > > 2. Check and pick-up tasks from FLINK-27719 [3]
> > > > > > >
> > > > > > > Best,
> > > > > > >
> > > > > > > Xintong
> > > > > > >
> > > > > > >
> > > > > > > [1]
> > > https://lists.apache.org/thread/d556ywochkpqxbo1yh7ojm751whtojxp
> > > > > > >
> > > > > > > [2]
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/WIP%3A+Slack+Management
> > > > > > >
> > > > > > > [3] https://issues.apache.org/jira/browse/FLINK-27719
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Initializing Apache Flink Slack
Posted by Xintong Song <to...@gmail.com>.
#contribution-helps is meant for new contributors to ask non-technical
questions. E.g., looking for starter issues or reviewers (just don't DM
people).
For having a #dev/development, I'm a little concerned this may encourage
people to start discussions directly in slack. IMHO, we may want to stick
to the existing communication channels (mailing lists / jira / github pr)
for most of the technical discussions, and only come to slack when the
conversation turns into back-and-forth. In such cases, a temporary private
channel or DM group could be set up for the specific topic. Maybe I'm being
too conservative. WDYT?
Best,
Xintong
On Tue, May 31, 2022 at 2:06 AM Gyula Fóra <gy...@gmail.com> wrote:
> Development channel (#dev/development) makes sense to me. It’s related to
> actual development related questions instead of the contrib process.
>
> Gyula
>
> On Mon, 30 May 2022 at 19:19, Jing Ge <ji...@ververica.com> wrote:
>
> > Good idea, thanks! Is the channel #contribution-helps a good fit for it?
> Or
> > should we just rename it to #development? For me, development is a subset
> > of contribution.
> >
> > Best regards,
> > Jing
> >
> > On Mon, May 30, 2022 at 4:28 PM Robert Metzger <me...@gmail.com>
> > wrote:
> >
> > > Thanks a lot for kicking this off.
> > >
> > > Is there a reason why we haven't set up a #development channel yet?
> > > I have a short question that is more suitable for that channel,
> compared
> > to
> > > the dev@ list ;)
> > >
> > >
> > > On Mon, May 23, 2022 at 7:52 AM Xintong Song <to...@gmail.com>
> > > wrote:
> > >
> > > > Hi Kyle,
> > > >
> > > > I've sent an invitation to your gmail.
> > > >
> > > > Best,
> > > >
> > > > Xintong
> > > >
> > > >
> > > >
> > > > On Mon, May 23, 2022 at 1:39 PM Kyle Bendickson <ky...@tabular.io>
> > wrote:
> > > >
> > > > > Hi Xintong!
> > > > >
> > > > > I’d love to take an early look if possible. I’m not a committer
> here,
> > > > but I
> > > > > have a role in the Apache Iceberg slack and am looking forward to
> the
> > > > Flink
> > > > > slack, particularly given the strong integration between Iceberg
> and
> > > > Flink.
> > > > >
> > > > > Thanks,
> > > > > Kyle!
> > > > > kjbendickson[at]gmail.com (preferred invite email)
> > > > > kyle[at]tabular.io (work email)
> > > > >
> > > > > On Sun, May 22, 2022 at 10:14 PM Xintong Song <
> tonysong820@gmail.com
> > >
> > > > > wrote:
> > > > >
> > > > > > Hi devs,
> > > > > >
> > > > > > As we have approved on creating an Apache Flink Slack [1], I'm
> > > starting
> > > > > > this new thread to coordinate and give updates on the issues
> > related
> > > to
> > > > > > initializing the slack workspace.
> > > > > >
> > > > > > ## Progress
> > > > > > 1. Jark and I have worked on a draft of Slack Management
> > Regulations
> > > > [2],
> > > > > > including Code of Conduct, Roles and Permissions, etc. Looking
> > > forward
> > > > to
> > > > > > feedback.
> > > > > > 2. We have created a slack workspace for initial setups. Anyone
> who
> > > > wants
> > > > > > to help with the initialization or just to take an early look,
> > please
> > > > > reach
> > > > > > out for an invitation.
> > > > > > 3. The URLs "apache-flink.slack.com" and "apacheflink.slack.com"
> > > have
> > > > > > already been taken. I've already sent a help request to the Slack
> > > team
> > > > > and
> > > > > > am waiting for their response. Before this gets resolved, we are
> > > using
> > > > "
> > > > > > asf-flink.slack.com" for the moment.
> > > > > > 4. I've created FLINK-27719 [3] for tracking the remaining tasks,
> > > > > including
> > > > > > setting up the auto-updated invitation link and the archive.
> > > > > >
> > > > > > ## How can you help
> > > > > > 1. Take a look at the Slack Management Regulations [2] and
> provide
> > > your
> > > > > > feedback
> > > > > > 2. Check and pick-up tasks from FLINK-27719 [3]
> > > > > >
> > > > > > Best,
> > > > > >
> > > > > > Xintong
> > > > > >
> > > > > >
> > > > > > [1]
> > https://lists.apache.org/thread/d556ywochkpqxbo1yh7ojm751whtojxp
> > > > > >
> > > > > > [2]
> > > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/WIP%3A+Slack+Management
> > > > > >
> > > > > > [3] https://issues.apache.org/jira/browse/FLINK-27719
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Initializing Apache Flink Slack
Posted by Gyula Fóra <gy...@gmail.com>.
Development channel (#dev/development) makes sense to me. It’s related to
actual development related questions instead of the contrib process.
Gyula
On Mon, 30 May 2022 at 19:19, Jing Ge <ji...@ververica.com> wrote:
> Good idea, thanks! Is the channel #contribution-helps a good fit for it? Or
> should we just rename it to #development? For me, development is a subset
> of contribution.
>
> Best regards,
> Jing
>
> On Mon, May 30, 2022 at 4:28 PM Robert Metzger <me...@gmail.com>
> wrote:
>
> > Thanks a lot for kicking this off.
> >
> > Is there a reason why we haven't set up a #development channel yet?
> > I have a short question that is more suitable for that channel, compared
> to
> > the dev@ list ;)
> >
> >
> > On Mon, May 23, 2022 at 7:52 AM Xintong Song <to...@gmail.com>
> > wrote:
> >
> > > Hi Kyle,
> > >
> > > I've sent an invitation to your gmail.
> > >
> > > Best,
> > >
> > > Xintong
> > >
> > >
> > >
> > > On Mon, May 23, 2022 at 1:39 PM Kyle Bendickson <ky...@tabular.io>
> wrote:
> > >
> > > > Hi Xintong!
> > > >
> > > > I’d love to take an early look if possible. I’m not a committer here,
> > > but I
> > > > have a role in the Apache Iceberg slack and am looking forward to the
> > > Flink
> > > > slack, particularly given the strong integration between Iceberg and
> > > Flink.
> > > >
> > > > Thanks,
> > > > Kyle!
> > > > kjbendickson[at]gmail.com (preferred invite email)
> > > > kyle[at]tabular.io (work email)
> > > >
> > > > On Sun, May 22, 2022 at 10:14 PM Xintong Song <tonysong820@gmail.com
> >
> > > > wrote:
> > > >
> > > > > Hi devs,
> > > > >
> > > > > As we have approved on creating an Apache Flink Slack [1], I'm
> > starting
> > > > > this new thread to coordinate and give updates on the issues
> related
> > to
> > > > > initializing the slack workspace.
> > > > >
> > > > > ## Progress
> > > > > 1. Jark and I have worked on a draft of Slack Management
> Regulations
> > > [2],
> > > > > including Code of Conduct, Roles and Permissions, etc. Looking
> > forward
> > > to
> > > > > feedback.
> > > > > 2. We have created a slack workspace for initial setups. Anyone who
> > > wants
> > > > > to help with the initialization or just to take an early look,
> please
> > > > reach
> > > > > out for an invitation.
> > > > > 3. The URLs "apache-flink.slack.com" and "apacheflink.slack.com"
> > have
> > > > > already been taken. I've already sent a help request to the Slack
> > team
> > > > and
> > > > > am waiting for their response. Before this gets resolved, we are
> > using
> > > "
> > > > > asf-flink.slack.com" for the moment.
> > > > > 4. I've created FLINK-27719 [3] for tracking the remaining tasks,
> > > > including
> > > > > setting up the auto-updated invitation link and the archive.
> > > > >
> > > > > ## How can you help
> > > > > 1. Take a look at the Slack Management Regulations [2] and provide
> > your
> > > > > feedback
> > > > > 2. Check and pick-up tasks from FLINK-27719 [3]
> > > > >
> > > > > Best,
> > > > >
> > > > > Xintong
> > > > >
> > > > >
> > > > > [1]
> https://lists.apache.org/thread/d556ywochkpqxbo1yh7ojm751whtojxp
> > > > >
> > > > > [2]
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/WIP%3A+Slack+Management
> > > > >
> > > > > [3] https://issues.apache.org/jira/browse/FLINK-27719
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Initializing Apache Flink Slack
Posted by Jing Ge <ji...@ververica.com>.
Good idea, thanks! Is the channel #contribution-helps a good fit for it? Or
should we just rename it to #development? For me, development is a subset
of contribution.
Best regards,
Jing
On Mon, May 30, 2022 at 4:28 PM Robert Metzger <me...@gmail.com> wrote:
> Thanks a lot for kicking this off.
>
> Is there a reason why we haven't set up a #development channel yet?
> I have a short question that is more suitable for that channel, compared to
> the dev@ list ;)
>
>
> On Mon, May 23, 2022 at 7:52 AM Xintong Song <to...@gmail.com>
> wrote:
>
> > Hi Kyle,
> >
> > I've sent an invitation to your gmail.
> >
> > Best,
> >
> > Xintong
> >
> >
> >
> > On Mon, May 23, 2022 at 1:39 PM Kyle Bendickson <ky...@tabular.io> wrote:
> >
> > > Hi Xintong!
> > >
> > > I’d love to take an early look if possible. I’m not a committer here,
> > but I
> > > have a role in the Apache Iceberg slack and am looking forward to the
> > Flink
> > > slack, particularly given the strong integration between Iceberg and
> > Flink.
> > >
> > > Thanks,
> > > Kyle!
> > > kjbendickson[at]gmail.com (preferred invite email)
> > > kyle[at]tabular.io (work email)
> > >
> > > On Sun, May 22, 2022 at 10:14 PM Xintong Song <to...@gmail.com>
> > > wrote:
> > >
> > > > Hi devs,
> > > >
> > > > As we have approved on creating an Apache Flink Slack [1], I'm
> starting
> > > > this new thread to coordinate and give updates on the issues related
> to
> > > > initializing the slack workspace.
> > > >
> > > > ## Progress
> > > > 1. Jark and I have worked on a draft of Slack Management Regulations
> > [2],
> > > > including Code of Conduct, Roles and Permissions, etc. Looking
> forward
> > to
> > > > feedback.
> > > > 2. We have created a slack workspace for initial setups. Anyone who
> > wants
> > > > to help with the initialization or just to take an early look, please
> > > reach
> > > > out for an invitation.
> > > > 3. The URLs "apache-flink.slack.com" and "apacheflink.slack.com"
> have
> > > > already been taken. I've already sent a help request to the Slack
> team
> > > and
> > > > am waiting for their response. Before this gets resolved, we are
> using
> > "
> > > > asf-flink.slack.com" for the moment.
> > > > 4. I've created FLINK-27719 [3] for tracking the remaining tasks,
> > > including
> > > > setting up the auto-updated invitation link and the archive.
> > > >
> > > > ## How can you help
> > > > 1. Take a look at the Slack Management Regulations [2] and provide
> your
> > > > feedback
> > > > 2. Check and pick-up tasks from FLINK-27719 [3]
> > > >
> > > > Best,
> > > >
> > > > Xintong
> > > >
> > > >
> > > > [1] https://lists.apache.org/thread/d556ywochkpqxbo1yh7ojm751whtojxp
> > > >
> > > > [2]
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/WIP%3A+Slack+Management
> > > >
> > > > [3] https://issues.apache.org/jira/browse/FLINK-27719
> > > >
> > >
> >
>
Re: [DISCUSS] Initializing Apache Flink Slack
Posted by Robert Metzger <me...@gmail.com>.
Thanks a lot for kicking this off.
Is there a reason why we haven't set up a #development channel yet?
I have a short question that is more suitable for that channel, compared to
the dev@ list ;)
On Mon, May 23, 2022 at 7:52 AM Xintong Song <to...@gmail.com> wrote:
> Hi Kyle,
>
> I've sent an invitation to your gmail.
>
> Best,
>
> Xintong
>
>
>
> On Mon, May 23, 2022 at 1:39 PM Kyle Bendickson <ky...@tabular.io> wrote:
>
> > Hi Xintong!
> >
> > I’d love to take an early look if possible. I’m not a committer here,
> but I
> > have a role in the Apache Iceberg slack and am looking forward to the
> Flink
> > slack, particularly given the strong integration between Iceberg and
> Flink.
> >
> > Thanks,
> > Kyle!
> > kjbendickson[at]gmail.com (preferred invite email)
> > kyle[at]tabular.io (work email)
> >
> > On Sun, May 22, 2022 at 10:14 PM Xintong Song <to...@gmail.com>
> > wrote:
> >
> > > Hi devs,
> > >
> > > As we have approved on creating an Apache Flink Slack [1], I'm starting
> > > this new thread to coordinate and give updates on the issues related to
> > > initializing the slack workspace.
> > >
> > > ## Progress
> > > 1. Jark and I have worked on a draft of Slack Management Regulations
> [2],
> > > including Code of Conduct, Roles and Permissions, etc. Looking forward
> to
> > > feedback.
> > > 2. We have created a slack workspace for initial setups. Anyone who
> wants
> > > to help with the initialization or just to take an early look, please
> > reach
> > > out for an invitation.
> > > 3. The URLs "apache-flink.slack.com" and "apacheflink.slack.com" have
> > > already been taken. I've already sent a help request to the Slack team
> > and
> > > am waiting for their response. Before this gets resolved, we are using
> "
> > > asf-flink.slack.com" for the moment.
> > > 4. I've created FLINK-27719 [3] for tracking the remaining tasks,
> > including
> > > setting up the auto-updated invitation link and the archive.
> > >
> > > ## How can you help
> > > 1. Take a look at the Slack Management Regulations [2] and provide your
> > > feedback
> > > 2. Check and pick-up tasks from FLINK-27719 [3]
> > >
> > > Best,
> > >
> > > Xintong
> > >
> > >
> > > [1] https://lists.apache.org/thread/d556ywochkpqxbo1yh7ojm751whtojxp
> > >
> > > [2]
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/WIP%3A+Slack+Management
> > >
> > > [3] https://issues.apache.org/jira/browse/FLINK-27719
> > >
> >
>
Re: [DISCUSS] Initializing Apache Flink Slack
Posted by Xintong Song <to...@gmail.com>.
Hi Kyle,
I've sent an invitation to your gmail.
Best,
Xintong
On Mon, May 23, 2022 at 1:39 PM Kyle Bendickson <ky...@tabular.io> wrote:
> Hi Xintong!
>
> I’d love to take an early look if possible. I’m not a committer here, but I
> have a role in the Apache Iceberg slack and am looking forward to the Flink
> slack, particularly given the strong integration between Iceberg and Flink.
>
> Thanks,
> Kyle!
> kjbendickson[at]gmail.com (preferred invite email)
> kyle[at]tabular.io (work email)
>
> On Sun, May 22, 2022 at 10:14 PM Xintong Song <to...@gmail.com>
> wrote:
>
> > Hi devs,
> >
> > As we have approved on creating an Apache Flink Slack [1], I'm starting
> > this new thread to coordinate and give updates on the issues related to
> > initializing the slack workspace.
> >
> > ## Progress
> > 1. Jark and I have worked on a draft of Slack Management Regulations [2],
> > including Code of Conduct, Roles and Permissions, etc. Looking forward to
> > feedback.
> > 2. We have created a slack workspace for initial setups. Anyone who wants
> > to help with the initialization or just to take an early look, please
> reach
> > out for an invitation.
> > 3. The URLs "apache-flink.slack.com" and "apacheflink.slack.com" have
> > already been taken. I've already sent a help request to the Slack team
> and
> > am waiting for their response. Before this gets resolved, we are using "
> > asf-flink.slack.com" for the moment.
> > 4. I've created FLINK-27719 [3] for tracking the remaining tasks,
> including
> > setting up the auto-updated invitation link and the archive.
> >
> > ## How can you help
> > 1. Take a look at the Slack Management Regulations [2] and provide your
> > feedback
> > 2. Check and pick-up tasks from FLINK-27719 [3]
> >
> > Best,
> >
> > Xintong
> >
> >
> > [1] https://lists.apache.org/thread/d556ywochkpqxbo1yh7ojm751whtojxp
> >
> > [2]
> >
> https://cwiki.apache.org/confluence/display/FLINK/WIP%3A+Slack+Management
> >
> > [3] https://issues.apache.org/jira/browse/FLINK-27719
> >
>
Re: [DISCUSS] Initializing Apache Flink Slack
Posted by Kyle Bendickson <ky...@tabular.io>.
Hi Xintong!
I’d love to take an early look if possible. I’m not a committer here, but I
have a role in the Apache Iceberg slack and am looking forward to the Flink
slack, particularly given the strong integration between Iceberg and Flink.
Thanks,
Kyle!
kjbendickson[at]gmail.com (preferred invite email)
kyle[at]tabular.io (work email)
On Sun, May 22, 2022 at 10:14 PM Xintong Song <to...@gmail.com> wrote:
> Hi devs,
>
> As we have approved on creating an Apache Flink Slack [1], I'm starting
> this new thread to coordinate and give updates on the issues related to
> initializing the slack workspace.
>
> ## Progress
> 1. Jark and I have worked on a draft of Slack Management Regulations [2],
> including Code of Conduct, Roles and Permissions, etc. Looking forward to
> feedback.
> 2. We have created a slack workspace for initial setups. Anyone who wants
> to help with the initialization or just to take an early look, please reach
> out for an invitation.
> 3. The URLs "apache-flink.slack.com" and "apacheflink.slack.com" have
> already been taken. I've already sent a help request to the Slack team and
> am waiting for their response. Before this gets resolved, we are using "
> asf-flink.slack.com" for the moment.
> 4. I've created FLINK-27719 [3] for tracking the remaining tasks, including
> setting up the auto-updated invitation link and the archive.
>
> ## How can you help
> 1. Take a look at the Slack Management Regulations [2] and provide your
> feedback
> 2. Check and pick-up tasks from FLINK-27719 [3]
>
> Best,
>
> Xintong
>
>
> [1] https://lists.apache.org/thread/d556ywochkpqxbo1yh7ojm751whtojxp
>
> [2]
> https://cwiki.apache.org/confluence/display/FLINK/WIP%3A+Slack+Management
>
> [3] https://issues.apache.org/jira/browse/FLINK-27719
>