On Fri, Nov 29, 2013 at 1:28 PM, Pedro Manuel Baeza Romero < pedro.ba...@gmail.com> wrote:
> Hi, Maxime, > > Say in thay way, "plan to make incompatible modules" sounds very rude. > There are now incompatibilities in 6.1, but the plan is that in > refactorization to remove as many as we can (always take in mind that there > can be serious problems to decouple from the core some things, but I'm > submitting some bugs to avoid this "forks"). > > I think more on this repository as a *full manufacturing suite* included > in the same location. The final goal to us is to include the v7 repository > under the umbrella of OCA, or even merged with the repository you have > mentioned. > > So please, don't stay with the thought that we are making incompatible > modules. Everyone that has seen my work on community repositories (MPs and > reviews) can affirm that this is not my way of doing things, but I cannot > absolutely say that we are not going to face with something incompatible > (Avanzosc had this trouble in the past with 6.0). > > Regards. > Hello, I think it happens to extend OpenERP in ways that are differents than what OpenERP SA does by default. For instance CampToCamp said there were avoiding the account_voucher module. I think it's a bit the same: sometimes an official addons module don't meet your requirements and you just rebase a few modules upon one or several alternative modules. That kind of things happen in all open source projects, it's the diversity that makes the value of open source. Regards. -- Raphaël Valyi Founder and consultant http://twitter.com/rvalyi <http://twitter.com/#!/rvalyi> +55 21 2516 2954 www.akretion.com
_______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
