> All different projects have their own routes forward and somewhere in time > you will lose integration/connection.
If the dependent project changes so much that you lose the interface it means either new features or code refactoring, both are good for both projects. Most of time, maintaining integration over time is much easier then in-house feature implementation and bug fixing. > > Also difficult time arise to your support contracts! Yes, most businesses > want a support contract for critical applications, as they can't relay on the > community for their business. They require service level agreements! So you can buy support from both OpenERP and the other project. In fact, most of OpenERP partners already interfaces it with Magento, Joomla, Alfresco, etc. But each do it's own way. An official module from the editor would be a much better SLA contract. > Thus as editor you want to control every line of code. You put in a way that quality means maintaining control and I beg to differ. The new module certification offer is a way for Tiny to delegate development and mantain quality. Even SAP is putting a lot of effort in integration with their third-party content certification. -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=33958#33958 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
