Mattermost-server: How open source is MatterMost?

[kramer65]

Yesterday I asked a question about the licensing to which a rather strange answer came.

My question was the following: In your LICENSE.txt I read that the source code is subject to the following:

1. Under the Free Software Foundation’s GNU AGPL v.3.0, subject to the exceptions outlined in this policy; or
2. Under a commercial license available from Mattermost, Inc. by contacting [email protected]

You answered that you do not encourage ... etc.

I'm not asking whether you encourage anything, I'm asking if your license legally permits removing Mattermost branding to sell the software under a different name. If it would be an MIT(-like) license, something like this would not be a problem. But since you're talking about exceptions and commercial licenses, it is very unclear for me how "open source" mattermost really is. Please be more clear about your licensing.

(ps. Since the issue was immediately closed I open this new issue to continue the discussion. Please do not close this question immediately just to get it off your list of issues.)

[it33]

Updated. Answers now consolidated: https://github.com/mattermost/docs/issues/1006

[pcinat]

@kramer65 - I'm hold the same views as you. Mattermost licensing is very obscure and unclear at best. I cannot confidently answer if something as simple as White labeling is permitted. And those links referred to in this thread claiming to discuss this issue at length are not available anymore.

[ci5er]

@it33 - @kramer65 - @pcinat - In an ideal world, I would be able to make commercial enhancements, using closed-source libraries, to the open source Mattermost code, and offer this "upgrade" commercially. I'd be happy to pay something substantially similar to the Enterprise licensing rates for the ability to do so, but I haven't been able to get anything except "Go talk to the Forum" whenever I ask about negotiating commercial terms with the support personnel manning the contact form.

Technically, where the code-base is is almost ideal for us to use as a fork-off point for an enhanced product for the healthcare industry (HIPAA, HL7, syndication, physician identify verification, patient identifiers, ...). But I am at a loss on how to get an answer from the company about who talk to about negotiating a commercial contract to make that possible. The email address '[email protected]' goes unanswered.

I hope that something comes of this issue - because would prefer not to spend 6+ months getting to here, when we could almost certainly work out a license that would work to everyone's benefit.

[it33]

@pcinat if things aren't clear, that's our fault. We should fix it. Can you share specifically what you're trying to do when you say "white label"? Would you be altering or removing Mattermost copyright notices? Is this for internal use only, or would you be offering an altered version to a 3rd party? We should get a clear answer and post it officially.

@ci5er also, sorry you didn't hear back. Please join our community server https://pre-release.mattermost.com/ you can DM me at it33 and we can discuss?

[pcinat]

@it33 - White labeling provides the option of removing or replacing the branding of Mattermost in the front-end UI that users get exposed to. I would not be altering or removing Mattermost copyright notices embedded in the source code. What I'm interested in is the ability to provide a slightly altered version of mattermost source code that can integrate within an existing web application by potentially removing the Mattermost logo from the UX.

The confusing language with the license is the following (specifically clause b below):

We promise that we will not enforce the copyleft provisions in AGPL v3.0 against you if your application:
(a) does not link to the Mattermost Platform directly, but exclusively uses the Mattermost Admin Tools and Configuration Files, AND
(b) you have not modified, added to or adapted the source code of Mattermost in a way that results in the creation of a “modified version” or “work based on” Mattermost as these terms are defined in the AGPL v3.0 license.

The language seems to suggest that you can take a copy of the source BUT cannot modify, add or adapt any part of the source code. This really restricts what can be done and very unlike a standard MIT license.

Is anyone able to confirm?

[it33]

Thanks @pcinat, appreciate the feedback,

First, thank you for your specific questions. They help a lot. I think after we get to your answers we'll write-up a specific FAQ on what you're trying to do.

1) Here are our licenses and philosophy around open source licensing: https://www.mattermost.org/licensing/. If you're looking to modify the source code, instead of using the compiled Mattermost Team Edition our policies are there. High level, Mattermost is an open source alternative to proprietary messaging because of how the project started: https://www.mattermost.org/why-we-made-mattermost-an-open-source-slack-alternative/

It's designed to meet the needs of people who agree with our purpose and it won't be as useful for people who do not agree.

2) Mattermost Team Edition is the compiled version of Mattermost under MIT license. You can go into the en.json file and change the Mattermost name and you can modify the images directory to get the logo you like. The important thing is if you're going to modify the branding you're clear what you're shipping is not Mattermost, i.e. calling it something completely different like "HealthPoint" is fine, but not "Mattermost Health Care Edition", etc. full trademark policy here: https://www.mattermost.org/trademark-standards-of-use/

PS: From your GitHub profile, it sounds like you're from Toronto. I'm from Toronto too, and went to Waterloo. If you'd like to discuss some time over a video call, you can join our community server https://pre-release.mattermost.com/ and DM me at it33 and we can jump on call.

[it33]

@pcinat have a new draft FAQ, let me know what you think? https://github.com/mattermost/docs/issues/1006