The plan for marketing it is: * Ensure there are glossy Matrix-native clients out there with a Slack-equivalent level of good UI and UX (e.g. http://vector.im/

The plan for marketing it is: * Ensure there are glossy Matrix-native clients out there with a Slack-equivalent level of good UI and UX (e.g. http://vector.im/beta http://vector.im/beta) * Build bridges to federate together as many different protocols as possible. This includes IRC, Slack, XMPP, SIP, Lync, Verto, Respoke etc. We're trying to make this as easy as possible by providing some high level building blocks like http://github.com/matrix-org/matrix-appservice-bridge http://github.com/matrix-org/matrix-appservice-bridge. This hopefully will make it easy for others to bridge themselves into Matrix once we have critical mass. * Release a stable version of actual Matrix standard itself, keeping it as simple but capable as possible. (Right now it's not frozen, and it's still in beta) * Provide a really capable reference server implementation. (The current one, synapse, is a good starting point and works well for experimenting with Matrix, but we still have work to do on performance and scalability). * Run around the world encourage existing projects/networks/solutions/developers to get involved and defragment their comms - a bit like the early internet guys had to do with defragmenting email. It's obviously hugely ambitious, but we actually have some good traction already (despite still being in beta). Hopefully the trend will continue! [Disclaimer: i work on it]