[TYPO3-english] Extensions potentially violating the GPL

Kay Strobach typo3 at kay-strobach.de
Fri Dec 17 17:40:07 CET 2010


Hey Joey

> Well - maybe you should have read the GPL completely before starting to sell extensions to your clients.
> 
> You may believe it or not, but the fact that the TYPO3 Core is GPLed automatically makes any of your extensions using the TYPO3 core API GPLed by definition as well. Even if you didn't explicitly tell your client or gave it another license, which is just a violation of the GPL that might cause legal actions taken against you, any of your clients has got the privileges that the GPL assures him, which are: 
> + to freely modify the code, 
> + to publish it for a certain fee or 
> + to publish it for free
> + to build other pieces of software based on it
> with the only restriction for your clients, that any of the above actions includes the GPL as the license.
> 
> This means that any of your clients could even reserve an extension key in the TER, upload your extension and make it available to the community for free. Of course nobody can force them to do so, but the GPL would grant them these privileges if they wanted to.
> 
> Cheers
> 
> Joey
> 

+1
therefore i added the paragraph about postloading non GPL parts
additionally of extensions (f.e. yaml, etc.) after installing the pure
GPL part to the wiki (i'll prefer complete GPL - in this case - but
sometimes no GPL aquivalent is available).

http://wiki.typo3.org/Overview_Extension_manuals#Non-GPL_compatible_extensions_.28to_be_removed_from_TER.29

Best regards
Kay


More information about the TYPO3-english mailing list