In your rather confusing LICENSE.txt I read that the compiled versions are licensed under the MIT-license, but the source code is subject to the following:
I'm a programmer, not a lawyer, so reading your extensive license is out of my scope. My question is rather simple though:
Can I take the source code of the mattermost platform, integrate it into our own platform, adjust the labeling so that it shows our brand name instead of "mattermost", and sell it to customers?
Updated, please see: https://github.com/mattermost/docs/issues/1006
@Mattermost, effectively you created a software no-one may use commercially except you. Despite the open source code drama you created. There are natural use cases - even with licenses - one is not covered. Sick software looks like this. Expressly made to not live as OSS.
You could remove any disambiguity in the legalese to prove your true OSS commitment.
FWIW, I won't use mattermost not at all, unfortunately.
The licensing is such unclear and full of pitfalls and some patches are so dark as dark can be on the dark side. It seems purposefully designed to prohibit any non-internal use. And even then.. And regardless of your open source "commitment" and source code available or Team Edition. Commercial code in the open source code? Mandatory inclusion of specific ToS and licensing files? Using open source code under MIT license in this case, AGPL in that case? This is fabricated to trip everyone else when scrutinized.
Mattermost, nice software rendered broken by policy. Thank you, but no. shudder
You could prove me wrong, though..