4 ms·

We have a Slack, so you can reach out to me on Twitter at @cmeik and I'll be happy to invite you. We have several almost-production users we have been fixing b

We have a Slack, so you can reach out to me on Twitter at @cmeik and I'll be happy to invite you. We have several almost-production users we have been fixing bugs and the Lasp slack is the place to go to get more information about what we are doing and how you can influence our future direction.

cmeiklejohn 9y ago
That said, I haven't been able to figure out how to make a Slack that isn't invite only.
- biggestlou 9y ago
  You can't, as far as I know. You can do this, though: https://www.skill-space.com/blog/2015/11/16/create-an-auto-invite-channel-using-slack-heroku1 https://www.skill-space.com/blog/2015/11/16/create-an-auto-i...
  - ramchip 9y ago
    Seconding this. Both Elixir and Erlang (https://erlang-slack.herokuapp.com/ https://erlang-slack.herokuapp.com/) use one for their slack channel, and it works great.
elcritch 9y ago
That'd be great! I'll have to digup a dusty twitter account. I may be more of a lurker for now, but seeing how Lasp is shaping up would be pretty valuable. A public slack would be nice. It seemed like LASP might be dead for a while when looking at some of the project pages a few months ago. Understandable when you're focused on solving hard problems, but an FYI from an outside perspective. This talk is really helpful in seeing what you've learned and where it's going. Thanks again!
- cmeiklejohn 9y ago
  How do you suggest we move forward? We tried slack, but being invitation only prohibited us for making a big impact. What's the right way to build an open community? What do you recommend?
  - shalabhc 9y ago
    Another option is gitter.im, which links to your github project and doesn't have to be invite only.
    - cmeiklejohn 9y ago
      I've setup a gitter here: https://gitter.im/lasp-lang/lasp https://gitter.im/lasp-lang/lasp