Community mailing list archives

Re: Odoo v9 Community and Enterprise editions

Sylvain LE GAL
- 05/10/2015 12:34:52
Hi all,

@Fabien Pinckaers

If I understood correctly you propose an enterprise version that contents :
Open Core + Open Addons + Extra paid modules
Open Core + Open Addons are in : (as currently)
Extra paid modules will be in : (new project)

I so don't understand why this PR has been moved in enterprise version as mentionned in comments.

This PR is a technical PR that impact Core and Open Modules (decimal_precision (1 file),
website (2 files), website_version (1 file) and core / base (11 files))

Did you forcast to fork all Odoo Project with :
* a Community version without latest
improvements (like API improvments for exemple in this PR)
* an Enterprise version with all the latest work ?

If yes, it doesn't match with your equations :
Open Source = Community + OCA
Enterprise  = Community + OCA + Paid Apps

Thanks for your clarification and see you in 3 weeks !

Kind regards.

Sylvain LE GAL
Service informatique
GRAP - Groupement Régional Alimentaire de Proximité

3 Grande rue des Feuillants, 69001 Lyon
Bureau :
Astreinte :

GRAP sur le Web : Site Web | Facebook | Twitter
GRAP - service Informatique sur le Web : Twitter

2015-05-10 16:38 GMT+02:00 Anders Wallenquist <>:
Den 2015-05-10 14:03, Stefan skrev:
> On 10-05-15 13:42, Samuel Lefever wrote:
> >
> > Hello community,
> >
> >
> > I m quite new as a company in Odoo business but I m working in the
> > community for several years.
> > And now, thanks to OCA members, I really understand why OCA modules
> > should not be under LGPL licences.
> >
> > But, I do not understand why I can not use entreprise Odoo module and
> > OCA module on the same instance.
> > Maybe be I skipped a mail… Someone could be kind enough to reexplain
> > or point a old explanation for me?
> We don't know the exact license of the enterprise Odoo, but by necessity
> it has to contain a clause that prevents redistribution. AGPL by
> definition is only compatible with code that it is allowed to 'infect',
> so that the whole body of code can be redistributed under the terms of
> the AGPL itself. Therefore, code that falls under the one license cannot
> be combined with the other.
You are probably right but in other communities, Drupal for instance, it 
does work well with paid modules distributed by GPL-licence with 
redistribution clause intact. Usually an end user, that is the target 
for those paid modules, are not a heavy redistributor.


Anders Wallenquist

> -- 
> Therp - Maatwerk in open ontwikkeling
> Stefan Rijnhart - Ontwerp en implementatie
> mail:
> tel: +31 (0) 614478606
> web:
> _______________________________________________
> Mailing-List:
> Post to:
> Unsubscribe:

Post to: