[TYPO3-50-general] Contributing to TYPO3 v5 / FLOW3: License Agreement

Steffen Müller typo3 at t3node.com
Sat May 3 11:32:36 CEST 2008


On 02.05.2008 23:17 Martin Kutschker wrote:
> Steffen Müller schrieb:
>> Hi.
>> On 29.04.2008 23:43 Robert Lemke wrote:
>>>> One more question:
>>>> What about extensions/components in v.5? It sounds like extension
>>>> developers also have to sign that contract.
>>> If extensions are part of the official distribution: yes. But as you 
>>> never
>>> know if an extension will become part of it at a later point, it makes a
>>> lot of sense to sign it in any case.
>> IMHO a "changing the core licence" scenario could also affect 
>> non-core-merging extensions.
>> We now have the situation that an extension is a derived work of the 
>> core, mainly because it is not a stand-alone applications but an 
>> extension of core functions. That's the reason why TER extensions must 
>> be licenced equally to the core licence. (GPL2+later)
> This can be solved. It's possible to add some special exemptions to the 
> GPL for certain applications. But I guess it would be possible to add 
> exemptions for a certain subset of the API. So an extension that would 
> use only the limited "super free" API could use any license.

I'm not to sure if I got you right. Do you mean that those parts of the 
core which handle extension functions have to be nonGPL? (LGPL?) But how 
to seperate those parts from the rest?
Do you have an example of some piece of OSS that uses these exemption?

> the developers. But don't worry to much, I probably won't write code for 
> 5.0. I'm just an interested bystander ;-)

Because of the licence contract?


More information about the TYPO3-project-5_0-general mailing list