Should I release changes made to the GPL v2 CMS?

If we use the CMS that the GPL (v2) applies to, do we need to reinstall the CMS source code if we make changes to the kernel?

GPL v2 Status :

The GPL does not require you to release a modified version. You make changes for free and use them privately without releasing them. This applies to organizations (including companies); an organization can make version changes and use it internally at any time releasing it outside the organization.

But if you release the modified version to the public in some way, the GPL requires that you modify the source code available to the user program under the GPL.

The gray area for me here is the part that says: “if you somehow published a modified version for the public” - does the website show the public account as “releasing it to the public”?

How about whether a custom plugin that integrates with the CMS is written - should we free the source? Is this considered a modification?

+3
source share
2 answers

The GPL is all about the binary executable distribution. Anyone who receives a binary executable must also get a source. In the case of a web service, you are not distributing the binary, so there is no need to distribute the source.

( : , Affero GPL, , , , , GPLv2, .)

+4

CMS , GPL. , .

, AGPL , . AGPL , .

+3

Source: https://habr.com/ru/post/1740293/


All Articles