Transition out of flowdock

[dviramontes]

• not slack because of pricing
• [x] how long does history stick around ?
• [x] investigate mattermost
• [x] investigate discord

[anotherpatrickcollins]

Seems like we've landed on Discord.

There's an export function for Flowdock if we need any of the past chats. I peeked and it doesn't seem there's any import function for Discord to keep that data in the chats through the migration so it'll likely be for archive purposes only. https://www.flowdock.com/organizations/42064/flows

Let's make sure we have Discord set up with the permissions and default channels so we can let the general public join as they're interested (@jberns can you take this?)

And can we install a bot for simple commands like !agenda or !resources for channels so when someone new joins they can just populate the links they need that way? Maybe https://dyno.gg/

[anotherpatrickcollins]

Need to update references to Flowdock in:

• Agenda
• Onboarding
• Codefordenver.org
• Meetup
• Members Site

[jberns]

Yea, I can work on this tonight!

[anotherpatrickcollins]

Flowdock final steps to force migration:

• Lock channels to read only.
• Add channel discord invites for folks who still log into Flowdock.

[anotherpatrickcollins]

Can't lock flows, and can't give channel invites because of our membership roles in discord (someone would have to already be on discord in the right role to join the specific channel).

So I think this is done!

A+ team.