> The certification will not ensure that the module will work between two minor > or major release, and the API will just work. It just says that tiny will do > himself the work to adapt the module to the new internal API and modules > interactions. By certifying a module you partially (in a kind of way) loose > the ownership of the module in favor of Tiny. Then you are not free to orient > this module the way you wants.
I do not agree with you on this in several ways. I have studied this subject a bit deeper, had some discussion with people here on forum. And one of the main ideas of certification is that the module has been built well according to standards (which is not clear), and it will be possible to migrate over versions. Let's imagine, somebody takes our module go to Tiny, says I want to certify this module. Ok, Tiny performs "certification". What does this mean, that Tiny now owns this module :), no in essence it means that they made a fork, which will most obviously will not continue to be developed. The people who paid for certification, becomes locked in an obsolete version of software, which in parallel is being developed by original developer. So if one needs a migration for the new version, one have to migrate the modules too. So one needs to pay for it, even though original developer have probably done that. If one sees that original developer have made improvement or a bugfix for his module, he probably will desire to get one. No, wait a minute, he is not allowed to, because then he will take uncertified piece of software. Or need to go certification process again. :) Although this system states that the migration of the certified modules will be possible and painless even for major versions, actually it creates cracks in the FOSS software development idea as a whole. How Tiny can guarantee that, if there are no clear and persistent policy for what is being done over versions? Kaspars ---------------------------- http://kndati.lv -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=42256#42256 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
