Maintaining your own fork is a ton of work. Even if it's just routinely rebasing on upstream and maintaining your own upgrade infrastructure and doing releases, that's far from trivial.

The open source community really needs to stop with the "just fork it" mindset.

https://github.com/mattermost/mattermost/issues/34271#issuec...

Wanting to use Mattermost's binaries rather than building from source?

Re licensing see: https://isitreallyfoss.com/projects/mattermost/

It’s not open source, it’s “open core” SaaS.

No. The binaries they prepackage for you are MIT. If you want the source it is AGPL or you pay for a proprietary license.

I don't know, but that seems somewhat beside the point. The restriction obviously was not added to test peoples ability to remove it.

glancing through the code, it doesn't seem like it be that hard to remove limitations such as this. PostHistoryLimit/postHistoryLimit interpreted from License Limits. a little poke here and there and I'd guess the limitations would disappear.

The time and energy that it takes to do it and build it, and then make it easy for current users to move their automatic updates to the fork, then maintaining it etc.

Nothing. Open Source is dying. The model to finance open source work (well-off suburban american dads or as a portfolio show off) no longer apply. The old generation that believed in this model is retiring and for the new generation it pays better to "network", leet code, or spam your resume to thousands of employers.

Now couple that with the fact that supply-chain control is profitable (legally or illegally); I think the next 5-10 years will be interesting.

The compiled binary is.

The source code is... AGPL licensed? But not the admin tools. They seem to be licensed under the Apache License 2.0.

--------

Yeah, good luck. Contact your lawyer.