Community archivos de la lista de correo


Re: Odoo v9 Community and Enterprise editions

Akretion, Raphael Valyi
- 11/05/2015 14:13:03
On Mon, May 11, 2015 at 10:22 AM, Alexandre Fayolle <> wrote:
On 11/05/2015 15:09, Antony Lesuisse wrote:
> I am curious about your deployements, do you mean that the Odoo instance is 
> always running on the intranet only inside the building of the company ? Do 
> the employee access the instance from outside the office using a VPN to 
> connect to the intranet.

For Camptocamp customers, AFAIK, essentially, yes. We are not deploying
the CMS or the eshop, nor the various portal addons.

Same for us at Akretion just to make it clear. We address these segments but with different technologies that do not clash with the license in case of modules the company wouldn't want to release, which in any case is really not often.

Frankly if a failed login is an AGPL issue, then that will be easily to adopt e technical fix for it with an externalized authentication (eventually with an nginx filter or anything outside from the Odoo AGPL codebase), much easier than forcing the OCA to do illegal brute force relicensing with the historical codebase and probably also shooting oneself in the feet in term of strategy at the same time.

I see a lot of FUD about AGPL from Odoo since they decided to kill it. But remember that there are major piece of software that uses this license just fine. From small software like Monit to very large ones, larger than Odoo iteself (at least in term of business) like MongoDB. And it works just well. All application that use MongoDB don't have issues with protecting their industrial secrets, they just put it outside from the MongoDB engine and query the engine with the network API just fine. Whenever that's an issue with Odoo, Akretion for instance developed the same kind of technology with Ooor (but any client would do it, this one just has the advantage to feel natural with the Rails ecosystem) to put the non open source logic outside from the Odoo codebase and shared memory structures (the "static linking" of the thing). It just workable and let non open source be the exception instead of the rule as it would be with a permissive appstore gamed by greedy administrators as many have good reasons to fear given the chaotic records from Odoo with open source recently and given the increasing influence from liquid VC capital that has interests totally unrelated to the one of the open source community.

Now, if I'm right all that thread started after some developer found that the effective Odoo master repository has been hidden for several weeks secretly against any open source development common sense... To which Antony answered that it was just a tech glitch due to cross modules pull requests with some of these new toxic non open source modules. An allegation that has been questionned by Sylvain Legal for instance by pointing to very specific pull requests that disappeared from the public Github repo and obviously had nothing to do with these private modules Antony mentioned. After see we see  FUD about AGPL, a license chosen by Odoo SA itself some 6 years ago, we see lot's of blahblahblah about module licensing and now some forced peace and love but we don't see any answer about the removal of the core public repo and the points raised by Sylvain Legal for instance.
I hope everybody follows the real issue.


Raphaël Valyi
Founder and consultant
+55 21 3942-2434