shared slack -- what should we call it?

[ultrasaurus]

We currently have a shared slack for Bridge Foundry and all the Bridges to share information and informally collaborate in real time: https://bridge-things.slack.com

Various people have reported that bridge-things feels random and is thereforce hard to remember

@carlisia suggested we simply call it bridgefoundry.slack.com

@rachelmyers who set it up originally reported "I’m happy for the name to be something more thoughtful than The Bridge Things, which honestly I put 2 seconds of work into thinking up. I would like to not name it Bridge Foundry, though. There are Bridge Foundry channels, but this isn’t all about Bridge Foundry."

bridges.slack.com was suggested, but is taken

From the history vaults, as I remember it: when we created Bridge Foundry, it was a renaming of RailsBridge which used to be all the things that the RailsBridge workshops were part of. Then RailsBridge was to focus on the Rails workshops, leaving room for other "Bridges" focused on new tech. To our delight, ClojureBridge, MobileBridge, GoBridge, and more have come into existence. We also created a federated board structure to allow for and encourage distributed leadership and representation.

[ultrasaurus]

can we call it bridgefoundry.slack.com and do whatever we need to to have people feel comfortable to be part of one distributed org? can we rename the various Bridge Foundry committees who provide the services to all the bridges rather than coming up with a new name that means all-the-bridges?

[carlisia]

If the slack team is renamed bridgefoundry it would make sense to me, because I don't think of it as a separate entity, but as a base entity that provides a foundation of services to my Bridge (if and when I need them.) In this slack team we could have channels such as #finance, #marketing, etc implying that they are of common concern, and anything specific to a bridge would go under the #*bridge channel, or a channel named with the *bridge prefix.

[ultrasaurus]

Next step: look into whether Slack handles re-directs nicely for renames or figure out how to communicate effectively around this change