Wednesday 25 March 2009 1:49:41 am
@Ivan: I think you need to read a little bit first about the GPL license, to better understand what you can and what you cannot do.
You cannot DISTRIBUTE derivative works of eZ Publish, unless you
- also publish the sources of your derivate work, or - buy an eZ commercial license So if you are creating a completely customized version of the software and only host it on your own servers / use it for your intranet, you are free of any charge, as you are not redistributing anything. Even if you make a lot of money out of it.
If you create say a custom eZ Publish extension and sell it to customers, thus distributing it, you are bound by the GPL, as it is a derivative work, and should also publish your source code as GPL (unless as said above you use a commercial eZP license). Even if you distribute your own extension for free, not making any money, you are bound by the GPL. I am not a lawyer, but I'd say that regarding your questions the answers are: 1 - no. But you REALLY SHOULD get a support contract to get patches and security fixes as soon as they are released 2,3,4 - no mention of derived code as long as css is mentioned. Are design elements covered by the gpl? look it up here: http://www.gnu.org/licenses/gpl-faq.html#MereAggregation. Short answer: no if you do not redistribute, yes if you do. 5 - this really is not part of any copyright / licensing statement, so it does not matter
Principal Consultant International Business
Member of the Community Project Board
|