Community mailing list archives

community@mail.odoo.com

Re: ODOO 8 and ODOO 9 Themes - Licenses!

by
Skillteam, Houssine BAKKALI
- 12/18/2015 10:18:33


2015-12-18 16:03 GMT+01:00 Andreas Becker <andi@lisandi.com>:

On Fri, Dec 18, 2015 at 9:06 PM, Houssine BAKKALI <houssine.bakkali@gmail.com> wrote:
discussion have been done by OCA. not on the theme but about the odoo relicencing it has been talked about

Hi Houssine

Could you please send me the link to that discussion(s) So I can read them if they are new to me - could be that I missed some Threads. Thanks, this would be very helpful!

just ask google as i don't have the time to do it for you. OCA made a blog post for it if i remember 

You guessed wrong. Our customers always get the sources of what we provide. Thet do whatever they want with it. I hope it's clear.
Stop arguing what you don't know of. Our customer receive the code even without asking for it. 

AGPL is actually not about your customers! It is about the community of all (public), which means the community should have access to it.

we are integrators it means we implement odoo for our customers and the customers are the only users of the implementations. nobody exept them have access to the system
 
The AGPL license, on the other hand, treats deployment of websites and services as “distribution”, and compels anyone using the software to run a service to also distribute the modified source code. Not so difficult with odoo actually as it is more or less build in and you would only need to extend your info page with the links to the additional modules you are using.


compare the differences and if now those links would belinks to the sourcecode everything would be fine and according to AGPL.

nope you're misunderstanding things. and blocking this is just about security and privacy. I hope you do the same with your customers odoo implementation


For example, you can make GPL and non-GPL code communicate through a database, web services, or APIs. But the moment you call GPL code directly, your code must be put under the GPL.

And this is the case when a Theme gets even installed. It is calling the odoo code as otherwise it would not install.

this is an interpretation your interpretation. you may be right but you may also be wrong.

Besides being a socially responsible businessman, you should also know that giving the code you have had developed to the open source community for free can also be the right thing to do financially. If you are not profiting directly from that code, it's rarely smart to hang onto it.
The community will go forward with the development anyway. Their next release will have nice new features, bug fixes, and better security. If you have kept your code secret, you will be the one who pays (in money or in time) for the integration of that secret code into their new releases. Or integrating their security fixes into your code. Both get messy quick, even with the help of state-of-the-art version control systems (that you should be using for every project, but that's another article.)

Andi

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe