@anajuaristi
I perfectly agree upon the darkness of the partnership too. By the way we are starters too here officially despite dozens of modules and almost a dozen of exemplar integrations... And I'm not the only one to think it's kind of sub-optimal... I also agree that at some point open source should give the credit to the people rather than the companies. For instance, in some OpenERP partner companies, programmers are not allowed to appear under their real name on Launchpad because their boss think they might be hired and they prefer to bury them with sub-optimal working conditions. On the contrary, at Akretion, everybody is and will be highly motivated by how efficient we are and even hold some shares and be very much encouraged to be visible open source contributors, so yes that's a completely different vision of the enterprise or even human... Now, I believe however partnerships are not totally sold for money as you said. Take Smile for instance: being 250+ people, they are one of the largest OpenERP partner even if only a fraction is working on OpenERP, they do have very skilled guys on OpenERP, they do have guys that come from similar engineering schools as Fabien was even if those have no incentive to contribute here. They also paid some money to Tiny and made a significant number of success stories, including resounding ones. Now, they are "only" silver partner, not "gold". IMHO they are what they deserve currently if you think gold is CampToCamp and similar. So there is some kind of black matter, but it's not too screwed up either. Now, about the risk with the certification mafia, may be I should give an example: Smile was married with eZPublish CMS. They made their PHP guys dream about an eZPublish certification. By now, eZPublish is almost dead against the Drupal CMS and Smile didn't even anticipate that, trying to preserve their market. Result of the story: the programmers fought for nothing and hold a totally meaningless certification outside from third party maintenance... So, if Tiny comes up with something fair partners agree on, then fine. But if that's yet a quick overnight idea badly implemented it would rather be sucking a lot more than it would help... Cause yes, lots of folks would then need to pay for that no matter how meaningless it is. I'll be direct: I even prefer paying partnership for nothing except being listed on among the guys that help in some way and have Launchpad/modules as the a first approximation of partner reliability rather than something worst... I think open source is largely about giving a chance to the genius that were too creative to fit the corporate codified system to express their talent and be recognized because at some point it becomes obvious they build better products. I mean all ways are good to shine, and at the end the respected guys in a community are respected for reasons that are much more valuable than quick done certification program. It's a bit like the low level private schools mafias in the the education world. When diploma really mean something because the system is string and flawless, that's fine and it's really valuable, now, once it's totally screwed up like in some highly privatized systems, it really suck everybody has to walk their way making more powerful day after day... Now I agree, community respect is strong but doesn't scale to a mass market, much true. I simply hope we have a smooth transition that fit a product maturation toward a mass market, cause we aren't there yet. So, I'm personally reserved. It all depends how seriously it is done. But sorry, Tiny already made crappy services/products in the past, so I can't simply trust them to come up with something great here, I'm rather on a defensive stance... At the same time, democratization of the OpenERP integration can only happen if fundamental things are done at the core level of OpenERP. Yes, some things are simple to do with OpenERP and that's welcome. But for instance, because of the poor exception management (improved in trunk), it was pretty common at integration time to be totally blocked by some totally weird bug only very skilled programmers could debug/work around. Similar things can be said about bugs that appear under certain module combinations, it all roots at a suboptimal code quality, well below mature working open source standards for such critical applications (even if the overall architecture is rather outstanding). At the same time, those same required skilled integrators will stick to the best ERP, and if that's not OpenERP anymore that's very bad news for everybody here. So that's why all in all, despite Tiny's promise, I speak loudly to make no concession anymore on framework quality in first place, all the rest will follow as a natural consequence of the product superiority. ------------------------ Raphaël Valyi CEO and OpenERP consultant at http://www.akretion.com -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=51413#51413 -------------------- m2f --------------------
_______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
