This is effectively AGPL. If you dont plan on editing the backend for your Mattermost hosted backend thats fine, but if you do please be aware of the terms of the license.
AGPL makes it so if you change code in a server those changes must be open source. Its GPL over the network basically. I remind people of it because some people might want to customize for highly proprietary needs and not realize.
I love open source software but I also understand the need for proprietary software at the same time. It keeps your lights on and your family fed.
I had to 'contact sales' to request an enterprise license to cover the period where we transition away from mattermost.
Great product, but trust is everything when it comes to such a core part of a company. They fucked up, real bad.
I'll use this while we transition away, unless there is a community fork which is sustainable and is firewalled from the morons at mattermost org who fouled this all up
"You are licensed to use compiled versions of the Mattermost platform produced by Mattermost, Inc. under an MIT LICENSE[...]You may be licensed to use source code to create compiled versions not produced by Mattermost, Inc. in one of two ways[...]1. Under the Free Software Foundation’s GNU AGPL v3.0, subject to the exceptions outlined in this policy"
This means that you can totally fork and patch any restrictions out of the publicly available source code, and there's not a bloody thing they can do to stop it.
Also, from a legal standpoint the "subject to the exceptions" part is bogus, because it is AGPL -- no exceptions can be made to that license, else it would not be copyleft anymore.
The only change (besides a rename to avoid confusion) is the removal of user limits. Thanks!
Is that the recent change about not allowing access to the messages older than 10.000?
This is effectively AGPL. If you dont plan on editing the backend for your Mattermost hosted backend thats fine, but if you do please be aware of the terms of the license.
What restrictions does AGPL put here (Apart from the general requirements?)
AGPL makes it so if you change code in a server those changes must be open source. Its GPL over the network basically. I remind people of it because some people might want to customize for highly proprietary needs and not realize.
I love open source software but I also understand the need for proprietary software at the same time. It keeps your lights on and your family fed.
As a nitpick, AGPL allows anyone to modify the software and serve it, while only distributing the code to the people who are being served.
So if a AGPL DB is exposed over intranet only to a closed customer baseclosed customer base need to have the source code.
Like what RedHat is doing.
I had to 'contact sales' to request an enterprise license to cover the period where we transition away from mattermost.
Great product, but trust is everything when it comes to such a core part of a company. They fucked up, real bad.
I'll use this while we transition away, unless there is a community fork which is sustainable and is firewalled from the morons at mattermost org who fouled this all up
"You are licensed to use compiled versions of the Mattermost platform produced by Mattermost, Inc. under an MIT LICENSE[...]You may be licensed to use source code to create compiled versions not produced by Mattermost, Inc. in one of two ways[...]1. Under the Free Software Foundation’s GNU AGPL v3.0, subject to the exceptions outlined in this policy"
https://github.com/mattermost/mattermost/blob/master/LICENSE...
This means that you can totally fork and patch any restrictions out of the publicly available source code, and there's not a bloody thing they can do to stop it.
Also, from a legal standpoint the "subject to the exceptions" part is bogus, because it is AGPL -- no exceptions can be made to that license, else it would not be copyleft anymore.
https://framagit.org/framasoft/framateam/mostlymatter says last updated in 2024?
Haven't there been CVEs in the product since they forked it in 2024?
/? CVE mattermost https://www.google.com/search?q=cve+mattermost :
https://www.cvedetails.com/vulnerability-list/vendor_id-2145...
There's also Mattermost-LDAP, though it doesn't look like there's a support contract for when compliance is important: https://github.com/Crivaledaz/Mattermost-LDAP
IIRC there are also 3rd party SSO/LDAP/AD adapters for GitLab?