I have to admit, I also (weakly) prefer a single workspace where possible.
It's easy to miss (or just not look at) the apache-flink workspace because
I didn't think of it.
The spam and spam account issues are probably inevitable for any slack
workspace as it grows, and we can probably reasonably e
>On the other hand, could you explain a bit more about what are the
problems / drawbacks that you see in the current Flink Slack?
>- I assume having to join too many workspaces counts one
I like the idea of having a single workspace for all ASF projects, similarly
to how we share JIRA, mail server
https://issues.apache.org/jira/browse/INFRA-22573
On 10/11/2022 11:17, Martijn Visser wrote:
It was discussed at the latest Apachecon conference by Infra during one of
the lightning talks. If I recall correctly, it was primarily turned to
invite-only due to spam. But definitely good to validate
It was discussed at the latest Apachecon conference by Infra during one of
the lightning talks. If I recall correctly, it was primarily turned to
invite-only due to spam. But definitely good to validate that.
On Thu, Nov 10, 2022 at 11:09 AM Maximilian Michels wrote:
> The registration problem s
The registration problem should be solvable. Maybe it is due to the Slack
pricing model that the ASF Slack is invite-only. I'll ping the community
mailing list.
Have these issues at any point been discussed with the ASF? I feel like
this is one of the examples where a community spins off to do its
Hi everyone,
I agree with Xintong in the sense that I don't see what has changed since
the original decision on this topic. In my opinion, there is a high cost in
moving to ASF now, namely I fear we will loose many of the >1200 members
and the momentum that I see in the workspace. To me there woul
Hi Max,
Thanks for bringing this up. I'm open to a re-evaluation of the Slack
usages.
In the initial discussion for creating the Slack workspace [1], leveraging
the ASF Slack was indeed brought up as an alternative by many folks. I
think we have chosen a dedicated Flink Slack over the ASF Slack m
If you click on the link from Beam via an incognito window/logged out of
Slack, you will be prompted to provide the workspace URL of the ASF. If you
do that, you're prompted for a login screen or you can create an account.
Creating an account prompts you to have an @apache.org email address. See
ht
+1 to leveraging the larger ASF Community/Resources Slack Channel rather
than an independant one ... ASSUMING ANYONE CAN JOIN [ so that needs to be
verified ].
On Mon, Nov 7, 2022 at 9:05 AM Maximilian Michels wrote:
> There is a way to work around the invite issue. For example, the Beam
> proje
There is a way to work around the invite issue. For example, the Beam
project has a direct invite link which sends you to the #beam channel:
https://app.slack.com/client/T4S1WH2J3/C9H0YNP3P I'm not 100% sure whether
this link actually works. I've take it from:
https://beam.apache.org/community/join
Hi Max,
> I wonder how that has played out since the creation of the Slack
workspace? I haven't been following the Slack communication.
I think it has primarily played a role next to the existing User mailing
list: lots of user questions. There were maybe a handful of conversations
where the resu
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 Slac
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 Visse
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
wrote:
> Hi Max,
>
> From my experience, most ASF projects actually don't use the official
> Slack, but thei
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
15 matches
Mail list logo
