I renamed the channel.
On Tue, May 31, 2022 at 10:54 AM Xintong Song wrote:
> Ok, then let's try it out.
>
> Best,
>
> Xintong
>
>
>
> On Tue, May 31, 2022 at 4:24 PM Robert Metzger
> wrote:
>
> > +1 to merging #contribution-helps with #dev.
> >
> > I'm pretty sure we'll have to revisit this
Ok, then let's try it out.
Best,
Xintong
On Tue, May 31, 2022 at 4:24 PM Robert Metzger 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
+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 wrote:
> I'm fine with the #dev channel.
> I remembered in the previous discussion that most
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
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
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
#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
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 wrote:
> Good idea, thanks! Is the channel #contribution-helps a good fit for it? Or
> should we just
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 wrote:
> Thanks a lot for kicking this off.
>
> Is there a
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 wrote:
> Hi Kyle,
>
> I've sent an invitation to
Hi Kyle,
I've sent an invitation to your gmail.
Best,
Xintong
On Mon, May 23, 2022 at 1:39 PM Kyle Bendickson 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
>
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
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
13 matches
Mail list logo
