you are viewing a single comment's thread
view the rest of the comments
[–] 4 points 7 months ago (1 child)

I think the problem is that the license grant (that has been in place for a decade) is not that clear.

You are licensed to use compiled versions of the Mattermost platform produced by Mattermost, Inc. under an MIT LICENSE

  • See MIT-COMPILED-LICENSE.md included in compiled versions for details

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; or [...]

I read it as releasing the binaries under MIT and granting people an AGPL license for the (non-enterprise) code. Some read it as not granting you the full AGPL rights.

To me, the fact that they advertise Mattermost as "open-source" and the statement on the "reciprocal license" above indicates that Mattermost also reads this as an AGPL license grant. However, they don't seem to be interested in fully clarifying the license situation. But, I think they would have a very hard time to argue in court that this license doesn't allow AGPL forks. And I haven't seen any evidence of them acting against any of the existing forks.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 6 points 7 months ago

    AGPL is restrictive so actually having MIT is a backup option weakens the AGPL license. And in particular having the ability to ship closed source binaries if you wish to, under a commercial license, means AGPL means jack shit here to those who want everything to be copyleft

  • source
  • parent