April ‘20

Hi all, this update is for the CodeBase community about how we use internal comms within a community, and some changes we're making.

Over the last few years, CodeBase has used Google Groups to help different groups stay in touch, but Groups has been failing us more and more as a system (not sending emails to specific users, not letting some users join, etc.)

I’ve been looking at ways we can encourage support across the growing CodeBase community. We’d like to trial a communication tool that allows our tenants to discuss best practice in building companies, and find support from the ecosystem. I’d like to invite you to the trial of the CodeBase Mighty Network.

We're still in experimentation mode with Mighty Networks, so your feedback is super welcome. Message me at [email protected] or send a DM on Mighty Networks ;)


FAQs

Is this a replacement for Google Groups?

Yes. They're a pain for users to access and for us to manage.

Is this a replacement for Slack?

No, we love the community Slack, and it's great if you're already a Slack user. But, these two comms tools serve different purposes. We'll make sure we send community updates to both Slack and Mighty Networks.

Why should I sign up for another comms tool?

Once you're registered for Mighty Networks, you don't have to keep logging in to check it. You'll get relevant updates direct to your email inbox, and you can set your notifications to how often you want to get them.

Will Mighty Networks be used to communicate important facilities/maintenance updates (like codebase-info)?

No - we'll be broadcasting important stuff via email. We want to keep building maintenance discussions away from community chat.

Can I make a new Group for Product Managers, Designers, Surfers, Bridge players?

Sure! Send me a message and let's chat.