Community mailing list archives

Re: [v8] product number, Supplier number

Akretion, Raphael Valyi
- 12/12/2014 04:40:38
On Wed, Dec 10, 2014 at 11:57 PM, Gunnar Wagner <> wrote:

Actually it would be great whether all unported OCA modules could have a pricetag & a contact email for porting directly on them (maybe even in the git repo or the README).
If you knew right away what it would cost and who to turn to I guess that would add some dynamic  to regarding 'outsiders' funding the porting process.

As someone who has no idea it's pretty much black box. will it costs you just a few bucks, or hundreds, or .. ?

Hello Gunnar, 

The system can certainly be improved and it's likely that the OCA ends up being able to collect some funds to assume some tasks in a more deterministic ways in the future.

That being said, every system has its advantages and shortcomings.

The OpenERP/Odoo license and resulting eco-system as the incredible advantage of being fully open source, just like Linux and its modules. In fact this results pretty much from its GNU AGPL copyleft license it was build on, a strong contract between the various contributors since its start. It enforces this freedom for the users by prevent somebody to control the distribution. That is anybody can migrate anything at any cost even if there is a trend for the community to self organize atop of this freedom.

If you look around, you will find that pretty much all truly open source projects like Odoo have these same shortcomings you describe. But hey being 100% open source - that is no black box - is certainly a huge advantage when it comes to ERP's and this is IMHO the only reason Odoo is gaining some traction (it is certainly not its set of out of the box features which is in fact limited on every market).

So yes, OCA is going to be more mature and improve things a bit.
But I think the main room for improvement is the core of Odoo itself. In fact Odoo started quite amateurish without upfront investment (but it was still the best open source ERP despite having poor coding standards). So in the 1st years of expansions it had to evolve a lot to have a chance to become something sustainable. If you look at the codebase being produced since 18 months, it's quite so much better than old TinyERP code 8 years ago... And the same is true for modules that build atop of that evolving core like the OCA modules!

So what I want to say is that, Odoo had quite an exponential growth where it should initially change a lot to become something usable. During this extremely fast evolution with not always a good upfront roadmap communication from OpenERP SA, modules used to deprecate quite a lot.

But the trend is now that the rate of big backward incompatible changes will decrease I think. We are coming to a time where OpenERP SA itself has a lot of existing customer to maintain and evolve and where its partners (its main revenue) have the same situation. So breaking things becomes increasingly suicidal and is going to slows down as the product becomes mature I think. Yes there is the API rewrite, but it's something quite mechanic and very quick to do, something very different than say the partner schema change in v7 for instance.

All right, that was my 2 cts: so in short: the lack of centralized commercial organization is intrinsically related to the incredible freedom GNU copyleft projects have. But the issues of that on the "core scope" should become less and less critical as the ecosystem becomes more mature. As for the "edge scope", well, consumers should learn how to select and build open source and there is no over simplification that can still guarantee your user freedom.


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