[TYPO3] Extensions and GPL

[Dmitry Dulepov]

Hi!

Bjoern Kraus wrote:
> Starting developing our own extension we wondered whether a new 
> extension for TYPO3 has to be automatically licensed under the GPL. IMHO 
> as long as we don't change TYPO3's or any extension's code inside it's 
> files, every extension that USES the TYPO3-Framework (includes hooks and 
> xclasses) can be licensed in any way we want. Is that right?

Nope. Read GPL and GPL FAQ.

Quotes from http://www.gnu.org/licenses/gpl-faq.html:

===============================================
Q: If a library is released under the GPL (not the LGPL), does that mean 
that any program which uses it has to be under the GPL?
A: Yes, because the program as it is actually run includes the library.

Q: If a program released under the GPL uses plug-ins, what are the 
requirements for the licenses of a plug-in.
A: ...If the program dynamically links plug-ins, and they make function 
calls to each other and share data structures, we believe they form a 
single program, which must be treated as an extension of both the main 
program and the plug-ins. This means the plug-ins must be released under 
the GPL or a GPL-compatible free software license, and that the terms of 
the GPL must be followed when those plug-ins are distributed.
===============================================

There is no way to avoid GPL when writing plugins for TYPO3.

-- 
Dmitry Dulepov
http://typo3bloke.net/

"It is our choices, that show what we truly are,
far more than our abilities." (A.P.W.B.D.)