Contributors mailing list archives

contributors@odoo-community.org

Re: Code audit in maintainer-tools

by
Dave Lasley
- 26/10/2016 16:49:38
There is also a set of instructions for rigging the tests up locally - https://github.com/OCA/maintainer-quality-tools/blob/14aa6f677f16b8fe13eb0467f5cae277a656acd7/git/README.md

— Dave Lasley

On Oct 26, 2016, at 5:38 AM, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:

Hi, Jean-Charles,

We have already got this on https://github.com/OCA/maintainer-quality-tools, that is checked on each PR for OCA modules.

Regards.

2016-10-26 13:53 GMT+02:00 Jean-Charles Drubay <jcdrubay@trobz.com>:
Hello,

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.

Thanks,

Jean-Charles

_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe