[TYPO3-team-core-v5] Contributor License Agreement

Robert Lemke robert at typo3.org
Wed Aug 11 10:31:56 CEST 2010


Hi Bernhard,

Am 10.08.2010 um 18:50 schrieb Bernhard Kraft:

> 1. Will it be possible to create plugins/extensions/whatever-you-call-it for FLOW3/Phoenix or would this also require one to sign a CLA. 

no, writing extensions doesn't require a CLA as long as it is not included in the official FLOW3 / TYPO3 Phoenix release.

> Or if something like an extension repository is going to be available: Will only people be allowed to put extensions in there if they have signed an CLA ? or kind of L-CLA like compared to the LGPL?

no, you don't need to sign a CLA in order to publish an extension.

> And if I have signed the CLA - is an extension then automatically counted as contribution and completly handed over to the Association?

I'd say no. It's no contribution to the core. But I guess we'll have to think more about this - I haven't so far.

> 2. If the complete FLOW3/Phoenix project is released under the GPL, someone could at any time be allowed to make a complete copy of it, probably call it "FireTypo based on Phoenix". To name it: make a fork.

Yes, that has always been possible with TYPO3 and will also be possible with TYPO3 Phoenix and FLOW3.

> This is nothing I would like to do, but I just wonder what would happen if someone takes this steps. For TYPO3 such a thing was not necessary. Everyone was able to submit patches, improvements and new features. In Phoenix you limit this group to a number of people who sign a contract.

Until now the CLA was no limiting factor, it was more an enabling factor to solve certain problems. If that changes in the future we need to rethink the approach and see if a CLA has more advantages than disadvantages.

> 3. Can one cancle the CLA. I mean if at some time I would find I do not like the CLA anymore. Can I retreat from it, so leaving all rights for software I already created to the Assoc, but not for future work.

yes, of course.

Cheers,
robert



More information about the TYPO3-team-core-v5 mailing list