Hi Boris, thanks for your answers!
> Now, beyond all legal considerations, you should try to look at it from an > ecosystem perspective. You (and your clients) are using software that you > did not pay cash for. It is generally expected that therefore, your > investment is in a different form - by contributing back to the community. I absolutely agree and have no problem with that. But building modules of more or less general interest is only one scenario. Imagine this: You have some very specialized, proprietary software, and a customer that uses Magnolia CE. Now the customer would like some kind of integration with that proprietary software, which you could provide in form of a Magnolia module. But for some reason you don't want to provide the source code for that module, or only under the terms of an NDA. Then again, you would not distribute the module with Magnolia. Who needs to haven an enterprise license in this case, the developer developing the module, the customer using it, both, neither? All very complicated... I understand that this is not the place to get legal advice, maybe I should try to find the answers with Magnolia (the company) directly. Anyway, thanks everybody for the information and the pointers so far, Lutz ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
