Community 보관된 메일 그룹

community@mail.odoo.com

Avatar

Re: Using Community Addon - Odoo Partnership Questions

작성자
Benoît Vézina
- 2017년 08월 31일 09시 36분 11초

Ok, but that it is pointing me to that line :

AGPLv3 constraints should apply to the developers of modules, not end-users.

So about using OCA module in Enterprise is ok as long as long as the dev respect :


    a Proprietary module cannot depend on an AGPLv3 module
    a Proprietary module can depend on an Enterprise Edition Proprietary module
    an AGPLv3 module cannot depend on an Enterprise Edition Proprietary module or a module with an incompatible license
    an LGPLv3 module can depend on an Enterprise Edition Proprietary module and vice-versa

I did not saw any OCA module depending on Enterprise, so I realy think you can use all OCA module with Odoo enterprise.
On the other side if you donc use website builder (CMS) there is not much difference between agpl and lgpl

AGPL is like the GPL, but the GPL is only triggered if you distribute your derivative work. AGPL broadens this to trigger to activate if you let people use your derivative work over a network.


Benoit Vézina
Le 2017-08-31 à 09:22, Ermin Trevisan a écrit :

The following post from OCA summarizes it quite nicely, I think:

https://odoo-community.org/blog/oca-news-1/post/oca-odoo-meeting-on-licenses-21


On 8/31/17 3:20 PM, Benoît Vézina wrote:

From https://www.odoo.com/it_IT/blog/odoo-news-5/post/adapting-our-open-source-license-245
  • We can open up a true ‘App store’ to the benefit of both customers and publishers willing to invest in fully packaged, ready-to-use apps as long as they get some financial compensation. This is key for our CMS & Ecommerce but will benefit other apps too.

  • End users will be able to use standard proprietary modules published by large companies that are key for their business (e.g. UPS/Fedex connectors for ecommerce shipping).

  • The license remains ‘Copyleft’ which means we retain  solid protection provided by  those types of licences.

  • Customers using the CMS do not need to fear having to release the whole source code of their Odoo implementation to every website visitor.

  • The license is compatible with AGPL v3 which means that modules under this licence will continue to be usable with Odoo. We however advise current owners to migrate to LGPLv3 too.

So...  I think you can install all OCA module without trouble

Can some one confirm it

Benoît Vézina


Le 2017-08-31 à 08:37, Ermin Trevisan a écrit :
On 8/31/17 2:20 PM, Benoît Vézina wrote:
No legal issue, you can install and use any module you want.  There is
only technical issue (i.e. oca contract vs enterprise recurring
document, admin backend theme, no need to install oca barcode as
barcode are in enterprise, ect...)

Benoît Vézina


Sorry, that's simply not true.

First of all, as long as there is no contradictory regulation in the
partnership contract, what I assume, you can install whatever you want,
also the community edition, without breaking the partnership.

BUT:

If you want to combine proprietary licensed modules with other modules,
you have to follow the license rules. For example you are not allowed to
combine proprietary modules (for example the enterprise edition) with
modules licensed under AGPL, see
https://www.odoo.com/it_IT/blog/odoo-news-5/post/adapting-our-open-source-license-245

Cheers, trevi


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


-- 
twanda AG
Ermin Trevisan
Artherstrasse 19
CH-6318 Walchwil 
T    +41 41 758 1515
M    +41 79 208 7373
E    trevi@twanda.com 
www.twanda.ch
www.gastrosoftware.ch

참조