Hi ATC,
The official Apache Software Foundation slack (https://the-asf.slack.com/ ,
invite at https://s.apache.org/slack-invite ) did not exist when
https://traffic-control-cdn.slack.com/ was made. It's on an enterprise
plan, so it does not face the limitations that our Slack workspace faces,
such
I don't think we have any more good reasons to stay on a standalone slack.
We do have about 700 users in our current slack and I doubt we get them all
to move, but I suppose all of the active folks would move.
On Tue, May 25, 2021 at 9:14 AM Zach Hoffman wrote:
> Hi ATC,
>
> The official Apache
I'm all for moving to ASF slack
On Tue, May 25, 2021 at 11:35 AM Dave Neuman wrote:
> I don't think we have any more good reasons to stay on a standalone slack.
> We do have about 700 users in our current slack and I doubt we get them all
> to move, but I suppose all of the active folks would mo
+1
I still don't like using Slack for open-source projects - because it's
closed-source and not feature-rich enough to overlook that fact, IMO - but
this move represents a definite improvement over the current situation.
On Tue, May 25, 2021 at 11:51 AM Jeremy Mitchell
wrote:
> I'm all for movi
+1 on moving
I'm -1 on using Slack for open source projects in general, but I seem to
have lost that battle. I would drastically prefer Matrix (offers 80% of the
features we care about from Slack), but does not ask potential contributors
to give up certain freedoms in exchange for Slack. Matrix is
+1
As an ASF project, if the ASF provides an enterprise communication
platform, we should take advantage of it.
- Rawlin
On Tue, May 25, 2021 at 6:52 PM Chris Lemmons wrote:
>
> +1 on moving
>
> I'm -1 on using Slack for open source projects in general, but I seem to
> have lost that battle. I
