Contributors mailing list archives

Re: Code audit in maintainer-tools

Komit, Jean-Charles Drubay
- 06/12/2016 04:45:34
Thanks Pedro, David and Moises.
It helped me a lot to get started.

As a new attempting contributors of maintainers quality tool, I found it a bit difficult / impossible to pass all the checks from travis. (in the PR you can see the difficulties I encountered:

Do you think there could be a documentation somewhere to explain how to test locally to avoid the need of committing/push to OCA to get travis results?



On Thu, Oct 27, 2016 at 12:07 AM, Moises Lopez <> wrote:
Currently we have static checkers (without install the module) with a custom extension for odoo of pylint 

Maybe you are interest in follow the project:

2016-10-26 6:53 GMT-05:00 Jean-Charles Drubay <>:

I just read the contribution guidlines and was impressed by how well documented the rules are. :)

Also, I remember that long time ago (up to 6.1), there was a module named base_module_quality that could audit the source code and find all the non-compliance point based on coding guidlines.

Is there some equivalent tool today?

If there is none, I guess it would make sense to have it as a command in maintainer-tools: oca-code-review which could audit the code without the need of installing the related module. Maybe we can help with that.



Post to:

Moisés López Calderón
Vauxoo - OpenERP's Gold Partner
Mobile: (+521) 477-752-22-30
Office: (+52) 477-773-33-46
twitter: @vauxoo

Post to: