Comment on Alternatives to Mattermost
starshipwinepineapple@programming.dev 3 days agoI feel like you didn’t read the post or issue i linked, nor their license.txt and are instead just trying to talk past me.
I don’t really care about this project or debating their intentionally ambiguous license structure. My point was that the grant of rights explicitly only grants AGPL access to create compiled versions of mattermost. That is not how FOSS licenses work and is incompatible with FOSS licenses because it lacks the “freedom” that even AGPL would typically grant.
You may be licensed to use source code to create compiled versions not produced by Mattermost, Inc. in one of two ways:
Under the Free Software Foundation’s GNU AGPL v3.0, subject to the exceptions outlined in this policy; or
Under a commercial license available from Mattermost, Inc. by contacting commercial@mattermost.com
I’m not saying that people can’t dual license or that they can’t release their product in other non-free ways. That’s not the issue here. The issue is that you are saying it’s AGPL, and it’s not–Not really. It’s only AGPL to create a compiled version of mattermost.
eksb@programming.dev 3 days ago
IANAL. I originally interpreted the license.txt as: all of the source code is AGPL (see lines 234-235), some of the source is also Apache 2.0, and the binaries are MIT; plus a trademark notice and contact info for getting a commercial license. After rereading it, my only conclusion is that this is a dumpster fire of a license.txt, and can be reasonably read several different ways.
LordMayor@piefed.social 3 days ago
And, people have been asking them to clarify it and they just say, “no.”
They’re acting very suspiciously.
eksb@programming.dev 3 days ago
Agreed, very suspicious. I would feel safe assuming that I can use the code under AGPL, but I would hesitate to use it for anything other than personal hobby because it would not surprise me if they closed their github account and never released any more code.