CAA exclusivity. CLA inbound, Apache outbound.

Posted Aug 11, 2011 16:19 UTC (Thu) by rfontana (subscriber, #52677) In reply to: CAA exclusivity. CLA inbound, Apache outbound. by sladen Parent article: Desktop Summit: Copyright assignments On your point 1, yes, but open source/pseudo-open souce projects requiring copyright assignment invariably give the contributor a grant-back maximally broad copyright license (as to the contribution) and so the contributor is largely free to do all the things the contributor could have done with ownership, other than sue for copyright infringement on that code (as opposed to say a derivative work of that code) or engage in subsequent assignment of the original code (as opposed to subsequent modifications). On your question: I find that unobjectionable if the original Apache CLA is used, or some equivalent variant or counterpart, though I consider the CLA an unnecessary and counterproductive layer of complexity in such a case. Especially apparent if you read it very closely, the Apache CLA doesn't really give you anything you wouldn't already have if you just used the Apache License inbound (note btw the Apache License 2.0 has an ingenious built-in inbound==outbound contributor agreement, largely overlooked). Other CLAs, including modifications of the Apache CLA, could be problematic for various reasons.