What happened to TinyMCE's license? about tinymce HOT 7 OPEN

The public announcement hasn't gone up yet. Please remember that all we’ve done is change the repository, we haven’t released TinyMCE 7 yet, so you are commenting on a topic for which we haven’t had time to prepare content on the website. We just needed to update the source code to meet an engineering deadline.

Forever is a long commitment, and I agree that the wording used in that blog post was unfortunate in the context of the decision to change the free open source license of TinyMCE 7 from MIT to GPL. We will adjust the content on the website in the coming days.

TinyMCE 7 will only be available for free in software that complies with GPL version 2 or later.

from tinymce.

This is a quite bad decision if you want to bundle TinyMCE with an open source solution with a different open source licence.

from tinymce.

Could anyone explain if we can use TinyeMCE based on GPLv2 licence.

We have a commercial SaaS product that has a website written in React. On one of the pages on the website, there is an input field using TinyMCE.

While we do not plan to publish our website's source code, anyone can open up a URL and navigate to the page where TinyMCE editor is used. Are we breaching the licence terms here or not?

from tinymce.

Indeed OpenXava has a LGPL license and uses TinyMCE 6, now we'll looking for another rich editor library. Curiously, the reason for changing CKEditor by TinyMCE in OpenXava some time ago was the license change in CKEditor, and now we found the same problem again.

from tinymce.

Could anyone explain if we can use TinyeMCE based on GPLv2 licence.

We have a commercial SaaS product that has a website written in React. On one of the pages on the website, there is an input field using TinyMCE.

While we do not plan to publish our website's source code, anyone can open up a URL and navigate to the page where TinyMCE editor is used. Are we breaching the licence terms here or not?

If you're using TinyMCE in a commercial SaaS product, you need to ensure that your usage complies with the terms of the TinyMCE license. The GPLv2 license allows you to use TinyMCE in your SaaS product, but there are certain conditions you must follow:

1. Distribution of Source Code: If you modify the TinyMCE code, you must make those modifications available to anyone who receives your product. Since you're not planning to publish your website's source code, this requirement may not apply to you as long as you're not modifying the TinyMCE source code.

2. Copyleft Provision: Any derivative work of TinyMCE must also be licensed under the GPLv2 license. This means that if you're incorporating TinyMCE into your website and your website is considered a derivative work, you must make your website's source code available under the GPLv2 license. However, there's a gray area regarding whether linking to TinyMCE through JavaScript constitutes a derivative work. Some argue that it does not, as long as TinyMCE operates as a separate program.

3. Dynamic Linking: If your website dynamically links to TinyMCE (e.g., through JavaScript), it's generally considered separate from TinyMCE itself, and the copyleft provision may not apply. However, this interpretation can vary, and you should consult legal advice to ensure compliance.

Given that your website is publicly accessible, it's important to carefully review the terms of the GPLv2 license and consider seeking legal advice to ensure that your usage of TinyMCE complies with the license terms and does not inadvertently breach any obligations.

from tinymce.