We just made an analysis of the Open ERP visibility. The Open ERP expansion is exploding ! Here are the main figures:

• 20% growth in number of leads every 2 months (currently: 110 customers request per day)
• 1000 downloads per day of the auto-installer
• One new module produced every open day (20 per month)
  

The most interesting statistic is the comparison of the Open ERP visibility with current competitors. Let's take Netsuite (N), an ERP offer in SaaS which is probably the nearest competitor of the Odoo offer. In 2008, their annual expenses in Sales & Marketing operations was 80.000k€ ! The funny thing is that Open ERP just became most famous than Netsuite, according to google trends:


The annual sales & marketing budget of Open ERP is 200k€. It means Open ERP has the same visibility than a company having a marketing budget 400x bigger ! This is the power of a free and killer application !


More over, the sales and marketing are our weaknesses. Unfortunatly, we don't have such statistics yet on the developments, I let you imagine the figures :)

Open ERP's new continuous testing and integration server

We are proud to announce the release of our new testing and release control dashboard. You can check it in action here:

• http://test.openobject.com

The goal of this dashboard is:

• to be sure that everyone understands the way to contribute and share works,
• define the process for releases, maintenance and contributions,
  
• control the quality of the contributions automatically,
• propose a single point of entry to all Open Object's resources.

Bugs Detection

At each commit, our automated test framework automates:

• The installation of the modified modules on different environments,
• The launch of assert tests and demo data provided in each modules,
• The launch of unit tests provided in modules,
• The installation of all languages,
• The automated migration since v4.2, 5.0 to detect incompatibilities.
  

Our systems are testing the trunk and stable branches. We have builders for the quality certified modules, the addons-extra and addons-community ones. If one of the test fails, the quality team and the author of the bug will receive a report by email.

Quality Improvement

In order to continuously improve the quality of the code and to train contributors to do quality code, we also setup a quality testing framework. Each module are evaluated through a series of quality tests at each commit.

It performs a series of tests:

• Scalability: will the module rocks if you work with millions of record,
• Availability of tests and demo data,
  
• Guidelines: do you follow the Python or Open ERP guidelines,
• Security: availabilities of well defined rules,
• Quality of the code: non redundant lines, etc.
  

This is system is based on the base_module_quality module. We are looking for more tests, feel free to contribute and add your own tests in our system.

Documents

A series of slideshow have been made to explain how we propose to organise the community.