Re: Using the ASF slack

[Zach Hoffman <zr...@apache.org>]

An update:

* We now have several Traffic Control channels in the ASF Slack:
  - #traffic-control
  - #traffic-control-automation
  - #traffic-control-cache-config
  - #traffic-control-cdn-in-a-box
  - #traffic-control-commits
  - #traffic-control-traffic_monitor
  - #traffic-control-traffic_ops
  - #traffic-control-traffic_portal
  - #traffic-control-traffic_router
  - #traffic-control-traffic_stats
  - #traffic-control-traffic_vault

* The channels in the ATC Slack workspace all posted a Slackbot reminder 10
hours ago linking to their respective ASF Slack channel equivalents, and
the most active channels are scheduled to post their reminder daily until
they are archived.

* Dave has updated https://s.apache.org/atc-slack to redirect to
https://s.apache.org/slack-invite . Thanks Dave!

* All of our community Slack links in the ATC repo and the Apache wiki
pages now. If you find more Slack links to be updated, you can file an
issue at https://github.com/zrhoffman/trafficcontrol/issues/new/choose .

-Zach


On Tue, May 25, 2021 at 8:18 PM Rawlin Peters <ra...@gmail.com>
wrote:

> +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 <al...@gmail.com> 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 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 free as in
> > Speech (but it turns out nothing is free as in Beer because hardware,
> > energy, maintenance, and security have costs).
> >
> > I'm in favor of moving, though. The existing ASF Slack will promote
> > inter-project teamwork and cross-pollination.
> >
> >
> >
> > On Tue, May 25, 2021, 12:36 ocket 8888 <oc...@gmail.com> wrote:
> >
> > > +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 <
> mitchell852@gmail.com>
> > > wrote:
> > >
> > > > I'm all for moving to ASF slack
> > > >
> > > > On Tue, May 25, 2021 at 11:35 AM Dave Neuman <ne...@apache.org>
> 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 move.
> > > > >
> > > > >
> > > > > On Tue, May 25, 2021 at 9:14 AM Zach Hoffman <zrhoffman@apache.org
> >
> > > > wrote:
> > > > >
> > > > > > 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 as only being able to see the last 10,000 messages, only
> being
> > > > able
> > > > > to
> > > > > > add 10 bots, etc.
> > > > > >
> > > > > > ASF Infra has added a webhook for the repo's commit activity to
> be
> > > > posted
> > > > > > to #traffic-control-commits in the ASF slack, and we can add as
> many
> > > > > > channels as we want. Any reason not to switch?
> > > > > >
> > > > > > -Zach
> > > > > >
> > > > >
> > > >
> > >
>