[TYPO3-english] Extensions potentially violating the GPL

Kay Strobach typo3 at kay-strobach.de
Fri Dec 17 14:04:34 CET 2010


Hello Tonino,

i do not understand your last post.

To make you understand i my opinion collected some information from the
official sites (below is the uri/source of the text)


> Now, browse around, look in the categories, dive into the great manuals and enjoy 
> the beauty of an ordered bazaars unified efforts to bring the most
> powerful collection  of CMS tools to you -
> for free under the GPL license!
http://typo3.org/extensions/what-are-extensions/


> By registering an extension key you accept that all content uploaded to TER
> (TYPO3 Extension Repository) matches these terms:
> 
>     * Published under the GPL license or GPL compatible
>     * You hold the copyright of the code or do not infringe the rights 
>       of others (meaning that work from others must be under GPL or
>       GPL compatible already!)
> 
> 
> Any extensions found to break these terms will be removed without further
> notice by the webmaster team.
http://typo3.org/extensions/extension-keys/


> The official extension repository only consists of freely available extensions.
http://typo3.org/extensions/repository/


Of course i do understand that programmers need more than grace for live
(me too). But the're solutions for divinding Open and Closed Source
Parts in an clean and absolute legal way. And that's what is my
intention and must be the goal of TER - the legal rules in TER are clear.


Additionally there is an interesting blog post @Novell:
http://www.novell.com/coolsolutions/feature/1532.html

Discussion about GPL Joomla JED:
http://community.joomla.org/blogs/leadership/636-jed-to-be-gpl-only-by-july-2009.html

Best regards
Kay

Am 17.12.2010 13:41, schrieb Tonix (Antonio Nati):
> You are GPL, but closed mind.
> 
> Regards,
> 
> Tonino
> 
> Il 17/12/2010 13:32, Kay Strobach ha scritto:
>> 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
>> _______________________________________________
>> TYPO3-english mailing list
>> TYPO3-english at lists.typo3.org
>> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
>>
> 
> 



More information about the TYPO3-english mailing list