Open letter to Fabien and his sales team about Migration scripts as a Shared Funding Project written by Fabien (the fragment is attached at the end, also see post http://openobject.com/forum/topic9175.html).
IMHO it is a big mistake to put the migration scripts inside a 'Shared Funding Project'. The migration scripts are a very important piece and next to OpenERP kernel for be distribute in that way. Although I dislike 'Shared Funding Projects', the current ones like database synchronizations and OpenOffice plugin are more peripheral tools of OpenERP so it is not so severe. As a 'Shared Funding Project' now the community must wait 8 months to get migration scripts for new version 5.0. The result is members like me (who are active community members that create new addons-extra modules, send bugs, do translations..., members that do not give money but give time) will remain in standby for 8 months. We will stop being active members improving the OpenERP version in development because some of our small implementations will not be able to migrate for 8 months without monetary cost, so we will not be able to test, report bugs and develop over 5.0 version (and of course, test the migration scripts). If, for example, a stable version is released each year and the migration scripts for this version are released after 8 months to the community, the community members could only play with up to date installations during 4 months each year, losing interest in debbuging the latest version. Therefore I believe that your decision is completely erroneous because it will have negative effect on the evolution and improvement of OpenERP in the future. I expect that Fabien and his sales team rethink it. Jordi Fabien has written: > Migrations must be available to the community. > > But I also consider migrations guarantee as a service and a big cost to > GUARANTEE this in the future. So I thought about a mix to satisfy customers > (that need guarantee, quality, quick and direct services) and the community > that want to migrate for free. > > That's why I think migrations should be seen like the 'Shared Funding > Projects': > > * Those that needs a professional environment, a guarantee on the quality > of services and code, have to purchase the maintenance contract. > * When the maintenances contracts reimbursed the R&D costs of these > migrations, we will publish them as open source for the community. > > > So, I estimated that we will be able to release the migration scripts with 3 > to 8 months, according to the success of the editions. If it takes more than > 8 months, I will take the costs at my charge and distribute everything online > for free. So that the community have a 'guarantee' on waiting maximum 8 > months. > > This remark is only for migrations scripts and shared funding projects. For > all the rest (new developments, bugfixes, ...) we push what we develop > directly on launcphad. ------------------------ Jordi Esteve http://www.zikzakmedia.com/openerp.html Zikzakmedia SL -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=31372#31372 -------------------- m2f --------------------
_______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
