Tuesday 24 March 2009 6:04:42 pm

Actually all code written on top of eZ Publish needs to be distributed under the GPL v2 License. You cannot release code you have built yourself on top of eZ Publish under another license unless you have an agreement with eZ Systems AS.

-bård

Documentation: http://ez.no/doc

Wednesday 25 March 2009 12:37:48 am

Hi,

what Bård actually means is that the core code is available under the GPL license which means that you are allowed to use the code as long as you stay under the GPL licence.

Reguarding your own written code you can use the license modell you want. (As long as the code don't repend on the eZ code). For example within your own classes.

Mit freundlichen Grüßen
Best regards

Norman Leutner

____________________________________________________________
eZ Publish Platinum Partner - http://www.all2e.com
http://ez.no/partners/worldwide_partners/all2e_gmbh

Wednesday 25 March 2009 2:27:42 am

One comment about 5. If you modify the templates that come with eZ Publish to *remove* the copyright notes, than you're creating a derivate work and the same things apply as for code. Creating your own templates should not have this issue. Although some people question whether using APIs such as template operators in templates also invoke the GPL derivate law, I don't think that's how we should interpret it.

(Note: this is a personal opinion, and I am not a lawyer)

Thursday 26 March 2009 3:39:47 am

'if I no customize all the site and only host it on my space (buy from an Hosting Provider) : is the same for "internet" for over the world ?'

Again: as long as you are not distributing your modifications to a 3rd party, you can do whatever you want.
It does not matter if the website is shown on an intranet or to 10 million people over the internet - all it matters is that you have given your modified code / templates to some client of yours or you have not.
The fact that a client accesses the website does not mean that you are distributing the software to him, so it does not impose further legal restrictions.

@Derick - hair splitting, but a nice observation!

Last note: when I mention the obligation to "publish" your code in the previous post, it does not in fact mean that you are forced to make it available on a public website. It just means that you have to provide it (full source) to the person you are giving your modified version to. And since it is GPL, that person is of course free to post it on the internet, make money out of it or sell it to your competitor, you cannot prevent him.

Principal Consultant International Business
Member of the Community Project Board

Friday 27 March 2009 5:20:44 am

ANOTHER ONE :)

If I customize my application on my server and my client use it;

can I sell my service as S.a.a.S (software as a Service) ?

Sunday 29 March 2009 10:23:10 pm

@Norman:
I'm not sure this is so straightforward. I write loads of classes that use eZ persistent object model as well as I use other eZ API. Of course, those classes provide new logic of some sort every time, but also are often heavily dependent on eZ core code. My feeling so far has been that it should also be considered derivative work. What do you think, guys?

@Derick:
Another unclear example: if I write an eZ extension that ads another tab to the admin interface - isn't that derivative of some sort?

@Bruce:
A very good idea about FAQ for GPL!

--
Company: mediaSELF Sp. z o.o., http://www.mediaself.pl
eZ references: http://ez.no/partners/worldwide_partners/mediaself
eZ certified developer: http://ez.no/certification/verify/272585
eZ blog: http://ez.ryba.eu