Will this bridge be be open source?
> The bridge itself is not going to drop into the open-source Matrix code any time soon. Hodgson explained: "This is an entirely new bridge that we've built as Element exclusively for Element Matrix Services, which is the SaaS hosting platform we provide in order to keep the lights on for Matrix development and for Element in general.
> "We are taking the position that people who are rich enough to buy into Team's ecosystem and throw lots of money to Microsoft might as well throw a little bit of money to Element to keep funding Matrix development."
For such people, an open source element bridge to teams is best of both worlds.
I would call that open core.
Matrix the protocol is fully open source. Element the matrix client is fully open source. Synapse the matrix server is fully open source. Dendrite, the next generation matrix server, is fully open source.
All of these are developed by the New Vector team. The only thing here that isn't open source is an external bridge to microsoft teams, a platform that itself is already closed source.
In this case, "open core" would probably look like the Matrix team closing the Element client and Dendrite homeserver, and then extending them with closed matrix event types.
Honestly, they could probably pull it off, but I doubt they want to go that route. They've been dedicated to federation since the beginning.
But "Element Matrix Services" (aka New Vector) launching and marketing a product/feature that is not open source is AFAIK something new, and it'd be very surprising if this is the last such feature they announce.
(Before today, they were one of the very few examples I knew of a VC-funded open source company where their product remained entirely open source.)
First of all, Matrix itself is a non-profit foundation, and absolutely everything it does is FOSS, and accepts contributions from everywhere. The majority come from Element (formerly New Vector) though, the for-profit that the original Matrix team set up in order to work on Matrix full time.
Element has always had some closed-source bits in addition to all the FOSS work we do for Matrix. For instance, the EMS hosting platform itself (lots of stripe + kubernetes) is all proprietary and always has been. The default integration manager (codenamed Scalar) is too. And occasionally we've built random apps and bots and bridges which we chose to keep closed source - e.g. we've had a closed-source Sametime bridge for ages, and we have closed-source border gateways, cross-domain controllers, audit bots, etc too. However, *this doesn't make Matrix open core*, any more than the existence of closed-source webapps makes the Web "open core". It also doesn't make Element "open core", any more than (say) Mozilla is "open core" just because they haven't released the source for some of the random services they run too.
In an ideal world, Element would release all of its IP as FOSS - and it's quite possible that we'll do that in future. But right now we're still experimenting with the right balance.
Matrix was never a great name, and confuses people. Riot was named after violence, but Element sounds like nothing, and now you've introduced a namespace collision for no good reason between the renamed product and the company.
What's next, rename Synapse to Element Server and Matrix to The Element Protocol?
It's like you want to lose
This is a mistake. If they're already paying for Teams, then what exactly is the incentive to "throw a little bit of money to Element"? They aleady have a communications tool (Teams), so a) why are they going to pay for another one, and b) people who already bought Teams most likely do not care about the values Matrix stands for.