@fabien
> If you want that others companies (or the community) use your own module or > develop new module that depends on your own module, you have to provide some > guarantee: bugfix and migrations in the long term, never apply changes on the > stable version, the code is clean and follow the Open ERP guidelines, ... The > quality certification is a way to provide this. By one sentence you are saying that it will, the other, that it will not. Does certification guarantee the migration or not? As I have understood FOSS project essence, if you want guarantees, you have to pay for it. Here comes the support contracts, right? As I understand that modules developed by Tiny, are developed for customer, even though the modules are not certified. So as I understand, Tiny provides support for them. If modules that are not certified could not be supported by Tiny, then there is discrepancy between theory and reality. I conclude that certification is requirement only for third party modules. So this is the way to lock in the customer by bloated costs? They will double pay extra money for that is being done by the original developer - for example the migrations between the versions. Consequence if the company wants support from the original developer of the module they are not allowed to, or they will have to move away... Sounds like clear policy of a typical proprietary software vendor. Kaspars --------------------- http://kndati.lv -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=42351#42351 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
