5
Quote:
jerryj wrote:
So, that's all I have to say. Am I alone in my thinking here? Does anyone else agree with me?
I join you in thinking the same. It's a shame XOOPS has taken this stance as it makes it hard to operate commercially in the XOOPS world. I hope also that Mambo's interpretation doesn't drive professional module developers away from XOOPS and towards Mambo.
I run an ASP business based on XOOPS, and develop modules for commercial use that we use to run multiple client sites together. We offer a lot of added value through support and application hosting.
But if an unhappy client want's to take "their" website to another supplier then there is real difficulty as we only have two options:
(a) We hand over all the module code we've developed from scratch for our ASP business with no license restriction (because Herko says it has to be GPL), or
(b) We tell the customer that it's tough and they can't take "their" website to another suppplier (ie. we don't release the code).
Niether option seems particulary fair. In my opinion, a fair solution for both parties would be to say to the client, yes you can take all your XOOPS site somewhere else, but the modules we use to run *our* business can be sold to you (with restrictions on distribution etc).
I'd really value some feedback about this.
Thanks,
Andy
