Thanks for the opinion and the substance, both are very helpful. I believe I am in agreement, the exact definition of “derivative work” is very grey considering all of the points you laid out and the many wiki articles on magentocommerce.com that mention “copy this class and change this” type of instructions. It does very much seem that Varien’s intent is for developers to freely and easily create extensions that follow the Magento core source code conventions. Trying to create an admin backend without writing code that is extremely similar to some piece of core code while keeping with Magento convention would be extremely difficult.
Varien, I know you don’t give legal advice, but can we get some kind of feedback regarding your position on whether or not the basic code structures for things like creating adminhtml grid/form blocks are “common knowledge” or not and therefore safe to copy/paste/edit when creating non-OSL extensions? Perhaps someone could give an example of something that you do consider to be strictly a “derivative work”?
Some examples (not things that I have done):
- Copy a payment gateway module and adapt it to another payment gateway with a slightly different API - ?
- Copy the CMS module and modify it extensively into a wiki module - ?
- Copy a controller into app/code/local/Mage/___ and change a few lines or add functionality- ?
Can you give distinct yes/no answers for the above scenarios?
I’m sure everyone understands that Magento belongs to Varien and to protect it you must license it in such a way that competitors can’t use it against you, but it would really benefit the community to have some clarification and reassurance from the head honchos that work on a module that includes a bit of copy/paste does or does not contaminate the non-OSL status of that work.