[Flow] RFC: Drop CLA for Flow and Neos

[Karsten Dambekalns]

Hi.

Quote: Helmut Hummel wrote on Mon, 14 July 2014 23:17
----------------------------------------------------
> I think one of the key questions here is what licence do we think is the 
> best for the project(s). I have no answer to that unfortunately. I also 
> suspect that it might be impossible to answer.
> 
> But keeping a potential blocker for contributions just to avoid a 
> decision does not make sense to me.

Well, we decided to use a CLA because we couldn't really answer that question. Things have changed a bit, we now think MIT for Flow and GPL for Neos would be optimal.

But it might still be that things change, so unless  there is "proof" that a CLA hinders contribution, I'd personally stick to it. Make it easier to sign if possible, by all means. But dropping it would still be second choice, because we know the future will change, so why make a future change harder than it needs to be?

(Proof: Any hard numbers on how dropping CLA impacting projects?)

Regards,
Karsten
-- 
Karsten Dambekalns
TYPO3 Developer, Neos / Flow Team

TYPO3 .... inspiring people to share!
Get involved: typo3.org