From what I see, we'd only have a channel or a few under ASF as opposed to having a whole org as in this case, right? -- Regards, Cos
On June 12, 2017 4:06:38 PM PDT, Roman Shaposhnik <[email protected]> wrote: >FYI: there's also this that seems to be more official (idea being one >channel per project so it'll be like #bigtop) > >---------- Forwarded message ---------- >From: John D. Ament <[email protected]> >Date: Wed, Mar 29, 2017 at 6:54 AM >Subject: Slack Invites >To: "[email protected]" <[email protected]> > > >All, > >Based on the on-going discussions, I decided to move ahead with a >single >organization for Slack. I've opened up registrations to all >@apache.org >email addresses. To get set up, please use >https://the-asf.slack.com/signup >to >get your account up and running. > >Happy Slacking! > >John > >On Mon, Jun 12, 2017 at 3:59 PM, Slack <[email protected]> wrote: >> Join Apache Bigtop on Slack >> >> >> [email protected] has invited you to join the Slack team Apache Bigtop. >> Join now to start collaborating! >> >> Join Now: >> >https://join.slack.com/apachebigtop/invite/MTk2NzQ0MzQyNTY1LTE0OTczMDgzOTItMmZhMWI2MWU1Yg?tx-196698235924-196744342661 >> >> >> With Slack, you can message your team, share files, and get updates >from >> the other tools you use daily. >> See Slack in action: https://slack.com/is >> >> Team Name: Apache Bigtop >> Team URL: apachebigtop.slack.com
