Let me summarize: We saw migration scripts like shared fundings. * If you need your scripts today, it's a service because we work in an emergency and have to provide some guarantee to the customers, help to apply scripts and improve them, etc. We also have to apply quality process in our company (finish scripts before releasing, testing on different customers, ...). We must also concentrate on our customers first. * If you wait between 3 and 5 months, we gave the guarantee to the community that we will release migration scripts as soon as we have reimbursed our development costs for this part. If we did not reimbursed our investment, I gave the guarantee that we will release the scripts within maximum 5 months after the release date. (we decreased from 8 to 5, if you check FAQ).
We want to invest all our resources in the growth of the product and push everything as open source. We always did that and we will always continue to invest in free code. (I have 75 developers that produce open source code everyday).That's our philosophy, every product addition should be free. So, why are migration scripts are like shared funding ? Because I consider that migrations are not a value addition in the product (no new feature, documentation, no module, ...). Migrations are not about quality product, it's about maintenance, maintenance for your own customers. So, as an editor, I want to invest in the product but I don't want to invest (at my own charge) for your own customers. I have to say I don't understand how you can sell Open ERP without a maintenance contract. This can not lead to a quality relationship with your customer: who will pay for bugs you detect, who provide a SLA, ... But it's also the advantage of free software, everyone are free to do what they want. You have to make the difference between the following actors: * Community: should get everything for free but no guarantee * Customers: should pay for services and guarantees * Partners: should resell to customers and push what have been released to the community * Editors: should provide guarantee and quality of service requested by customers to partner. How do we grow in the open source ? * The one that asks a new feature have to pay for it (in money, through a partner or do it itself). So, the customer have to pay for what does not exists. Once it's developed, it's available to the community. -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=31291#31291 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
