During the launch of Openbravo Network, many mistakenly interpreted Openbravo adopting a closed source development model. This is not our strategy because we believe there is a better way.
My previous post is a very illustrative example of how customers benefit from having an open community, and how the community benefits from having customers funding it.
All bugs fixed for Openbravo ERP are available in the development trunk and incorporated in the newest release of Openbravo ERP, which typically occur twice a year.
Openbravo Network clients benefit from having regular and timely access to bug fixes, both for bugs reported by them or reported by the community. They get the benefits from using a product which is subject to public scrutiny and at the same time enjoy production grade SLAs (Service Level Agreements).
Community benefits from the effort funded by Openbravo Network customers to fix bugs, which are readily available in the development trunk and periodically packaged whenever a new release is published (or even before, if –occasionally- a community maintenance patch is published).
If you use Openbravo ERP and want to see it improve, engage in the community.
If you use Openbravo ERP and want production grade support, subscribe to Openbravo Network.
You are helping yourself in both cases.
In case you didn’t notice, Openbravo does not have an entry in the English edition of the Wikipedia, the fine community driven encyclopedia.For some reason, the word Openbravo has been “blacklisted” and any attempt to create an entry about Openbravo ge…