Hey Martijn, hi Chesnay, >The big problem of using the ASF Slack instance is that users can join any Slack channel, including ones outside of Flink.
That is one of the main motivations for proposing to move to the ASF Slack. We can create an unlimited number of "flink-XY" channels in the ASF Slack, although one or two are probably all we need. It seems logical that we share the Slack workspace, just like the other infrastructure like JIRA, mail, Jenkins, web server, etc. I guess I'm just in too many Slack workspaces already. >From an ASF standpoint, I think it would be desirable to channel people into the main workspace to promote the software foundation. Also, the main point of communication should still be the mailing lists. I wonder how that has played out since the creation of the Slack workspace? I haven't been following the Slack communication. >Not to mention that non-committers need to be invited by an ASF Slack user to be able to join. There is an invite link that they can use. Maybe not the most straight-forward process but I think it doesn't stop users from joining. Linen is pretty nice, especially for making Slack searchable via search engines. -Max On Thu, Nov 3, 2022 at 2:44 PM Chesnay Schepler <ches...@apache.org> wrote: > According to Robert linen is supposed to show the entire history. > > On 03/11/2022 14:27, Martijn Visser wrote: > > Addition: I'm not sure if Linen actually provides the messages that are > > older, but I can't test that since we've only recently integrated it. > > > > On Thu, Nov 3, 2022 at 2:23 PM Martijn Visser <martijnvis...@apache.org> > > wrote: > > > >> Hi Max, > >> > >> From my experience, most ASF projects actually don't use the official > >> Slack, but their own instance. That has happened with Airflow, Iceberg, > >> Hudi etc. > >> The big problem of using the ASF Slack instance is that users can join > any > >> Slack channel, including ones outside of Flink. Not to mention that > >> non-committers need to be invited by an ASF Slack user to be able to > join. > >> The problem with the history is mitigated by using the service from > Linen > >> https://www.linen.dev/s/apache-flink > >> > >> I prefer the current Slack instance of the ASF one. > >> > >> Thanks, > >> > >> Martijn > >> > >> On Thu, Nov 3, 2022 at 1:14 PM Maximilian Michels <m...@apache.org> > wrote: > >> > >>> Hi, > >>> > >>> A while ago the Flink community decided to create a Slack workspace > [1]. I > >>> wonder, is there a particular reason why we created our own Slack > >>> workspace > >>> and do not use the official ASF Slack [2]? It looks like most ASF > projects > >>> use the official Slack. Using the official Slack makes collaboration > with > >>> other projects easier but it also comes with additional benefits, e.g. > >>> free > >>> unlimited history (our current workspace suffers from limited history). > >>> > >>> Since the vote thread[1] mentioned a re-evaluation of the decision > until > >>> the end of 2022, I'd like to propose to move our channels to the > official > >>> ASF Slack workspace. In my eyes, the dedicated workspace is a bit of an > >>> overkill and we're better off joining the rest of the ASF community. > Let > >>> me > >>> know what you think. > >>> > >>> -Max > >>> > >>> [1] https://lists.apache.org/thread/j2kdh3zx6rrb49mz5n2vb06g2knogxdj > >>> [2] https://infra.apache.org/slack.html > >>> > >
