Monday, January 21, 2013 10:57 AM


If the discussion can come to a consensus on the proper solution for this problem, there might be people coming out of the woodwork to implement this. NPG had something for 6.0 [1], but since it wasn't ever updated or adopted upstream, it seems abandoned.

This is what I was referring to when I said 6.0 was abandoned but 7.0 was missing too much functionality. This kind of community-given work not making it into 7.0 makes OpenERP a difficult adoption for US companies and severely reduces my confidence that OpenERP (esp 7) can be a US-friendly platform (at least within 1-2 years). Our company's core competency is eCommerce, not accounting, so we are looking at the path of least resistance.

We're actually considering paying $20,000 plus some insanely huge monthly fee to migrate to (redacted-a closed-source commercial solution) just because they have all (or just more) of the features we need out of the box. As a developer who loves OSS, I'd much rather adopt OpenERP and pump that money into the community in the form of adding customizations or improving existing functionality, but when major features are missing that process is too slow and our situation is very time-critical. It is this kind of steep adoption curve that turns away businesses from ultimately adopting OSS projects like OpenERP that meet 90% of the needs but leave the other 10% as an exercise for the user. All we need is something that matches Quickbooks for functionality, has a decent API, and scales to thousands of transactions per day.

_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

Reply via email to