[avenger]

Well, you talk about having a programmer working for you, so he should be able to make this a "ready to run"-module in virtually no-time, it is all there....

And beeing a good "Open Source" citizen, you would hand that over to the OXID community afterwards.

That's what "Open Source" is all about: take an give.

[vmajor]

Actually that is my intention, but the problem is in licensing and development costs. I have yet to investigate this fully, but developers are not too keen to release their commercial grade code to the world and they would have to do that if they create the code under the GPL license.

The thing is, I do not want to have to think about this. I need to run a business and make decisions that I am actually trained for.

V.

[MaFi]

I agree of course OXID eShop needs payment international payment modules! Good chance right now to be the first to implement them

BTW: there is http://www.oxid-esales.com/de/exchan...e-oxid-eshop-4 (worldpay) and there is as well an "non efire" paypal module.

And talking about "Open Source and Earning Money" would lead to a very long discussion. I think we all know quite a lot companys that work very well publishing their software as open source.

[vmajor]

...for PE/EE...

The entry price of is not bad, but we do not use WorldPay and the problem is again that if basic functionality like being able to check out is an optional extra, then many other alternative shopping carts/ecommerce platforms become very interesting.

We are discussing how to grow the OXID community, so removing growth barriers such as this should be a real priority.

Having to purchase PE/EE commercial editions just to be able to provide customers with an option to check out is a huge barrier to the international OXID community growth.

V.

[leofonic]

Modules for PE also work in CE. If CE-Compatibility is advertised a module might have to be licenced under GPL, thats why CE-compatibility is not mentioned in the encrypted modules.
(Personally i do not think this is the case, i think encrypted modules could be written and sold for CE as long as they are distributed seperately)

[avenger]

Originally Posted by leofonic

Modules for PE also work in CE. If CE-Compatibility is advertised a module might have to be licenced under GPL, thats why CE-compatibility is not mentioned in the encrypted modules.
(Personally i do not think this is the case, i think encrypted modules could be written and sold for CE as long as they are distributed seperately)

No, that is exactly the problem: the GPL ist "infectious": as soon, as you release a module based on a GPL-licensed software, it must be licensed as GPL.

Which is not the case if you target it for PE/EE.

[leofonic]

Originally Posted by avenger

No, that is exactly the problem: the GPL ist "infectious": as soon, as you release a module based on a GPL-licensed software, it must be licensed as GPL.
Which is not the case if you target it for PE/EE.

I know GPL is viral, but as the end-user can do anything with GPL Software, he is allowed to use non-GPL modules as well. Just stating that a non-GPL module does also work with CE does not suddenly make the module illegal IMHO if the module is targeted for PE.
There was a discussion here: http://www.oxid-esales.com/forum/sho...p?t=756&page=2, the last statement by lafi is what i think.

[avenger]

No, of course not..

I presented the developers view point....

If he licences something for OXID CE, it becomes GPL.

But a module licensed for a propriatary software like PE/EE can run under CE also, without becoming GPL.