[TYPO3-english] Extensions potentially violating the GPL

Kay Strobach typo3 at kay-strobach.de
Fri Dec 17 13:32:35 CET 2010


Hi Tonino,

> In this way I'm encouraged to use TYPO3. If I'm forced to go GPL, I will
> not use TYPO3.

the core is GPL. That means, that everything which is not usable without
the core or uses core API without any alternative is GPLed as far as i
understand the GPL.

The GPL do not force you to publish all your work. It does say:

"If you publish/sell this product or a modification the code must be
included."

So if you decide to not publish an extension nobody has the right to
force you to publish this extension - so you have the chance to sell it
directly to someone who will than have all the rights which are granted
with the GPL. If the product can be used standalone you can use any
license you want.

Especially for clearifying the situation for users the idea was to make
the TER GPL only (what it should be with the current Terms of use.).
Than you can use package_manager to show your own license and load your
special package from your own server. (So the part which loads your code
is definitly GPL).

Conclusion: You're forced to go to GPL when product is completly
dependent on TYPO3 core or a special extension which is GPL. This is the
nature of TYPO3 core GPL licensing. But you can use what ever license
you want if your work runs indepently from TYPO3 and uses something like
an adapter to be integrated into TYPO3.

Best regards
Kay


More information about the TYPO3-english mailing list