So I hope the discussion will continue here. As people who had opinion on my personality being fake, could notice, I just like other people here do care about this project's future.
So the Module Certification... This word implies in itself that this process is being carried out, relying on some standard. So all the standards, as we know are publicly available. Moreover as this is general public (GPL) project, the standard have to be in a public domain. So public or specifically the community, can influence the standard and the authority. As I know the standard is not publicly available, so we can derive that this is some company internal procedure for adopting the code for serving customers. So this certification could not be marketed as a proof of quality, as nobody knows what the process is. So nobody can verify it. More likely, customer have to pay Tiny, so they get familiar with the addon being certified. Or in other words TO LEARN it. It is an interesting practice. If we want to learn something on Tiny's developed addons, we have to pay the company... If they want to learn something from us, we still have to pay them. :) You say that this process is nothing to do with Open Source Software. Yes it seems like that, but in a single mean - it is an opposite to the OSS conception - it is a Closed Standard. > he can pay a small fee and we will maintain and clean the code It has nothing to do with the software, you just want to say, please pay us, if you want us to use open source software as it is a bad quality product! Aint' that cute?! Main developer of OSS project executes such a nice policy. As I remember you say you have an automatic migration script/software... Then there are well known (read - written down) differences between both API versions, right? Sad, it is a great loss for a community, as we have to reverse engineer both APIs and spot the differences on our own. If Tiny call's itself an editor, then there should be visible result - the specification what should be done in order to migrate the software to the new version. So if we pay Tiny for certification, migration to the next versions will be done without extra charge, right? From what evolution of a module the one dated from the certification date or one half a year later on. Well, sorry, but I doubt it. > We require the certification on modules to be used in the Odoo offer because > we need to be sure modules are scalable, bugfree, migrate automatically, ... > if we sell them to customers. On a certification page there is nothing mentioned about Odoo, it is a generic practice. Ah and just read the threatening warning messages of the new server, those, about using dangerous non certified modules. GPL license already mentions about "no guarantee" and so on. I am sorry, this were the long monologue, but it still seems that Tiny's certification is just another way to separate people by a means of a ****. Well, decide on yourself. I could suggest to build good open independent standard, but it is a pity, community have no control or information on the core development plans, so nobody really knows, what the Open ERP 6.0 will look like. One can not guarantee that the module developed by somebody else (nor own one too), is bug free and does exactly what it is intended to. So, Tiny, please stop, in essence, telling people that the OSS is a bad quality product and needs some extra certificates or guarantees. >Well maybe we will attach such a "sticker" to our modules too?< Kaspars ----------------------------- http://kndati.lv -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=41084#41084 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
