Hi
Rewriting a big product! This is absolutely baseless. If this is the case, them one should go for the proprietary product, there is no point in picking up the open-sources.
I'd like to take this opportunity to mention that I've already integrated a full-fledged multi-location inventory, stock movement, reorder levels etc. and invoicing including debit notes, credit notes. vT code is multi-company. One single (multi-theme) UI, one single db, and one single codebase are already in place. The all-powerful VT's workflows and custom fields apply to this product.
This cannot be achieved unless one has a good knowledge of the VT/FA internals. And only, accounting is left. I have made a concrete plan on how to integrate it.
I think there is a difference between my vision and yours and thus the debate. I am looking it from the angle of challenging the ERP-proprietary market. When an ERP company promotes its product, it has to pay to the developers, to the marketing team, placing ads on the popular web sites, maintenance, office/miscellaneous expenditures.
When compared to the major open-sources, the only expenditure is related to the developers. I believe that the developers should be paid if the work is big enough. Had this been a week's or a part-time job, I would have done it gladly for the community. But it needs full-time involvement. Most of the successful open-sources are funded by people/big companies. Why cannot ours?
As I said in my last email, people will join when they come to know of the combo-product (CRM/ERP both). They will use the product and do/report the bug-fix. All that we need to do is to put it on track and the support team will be there automatically.