Contributors mailing list archives
contributors@odoo-community.org
Browse archives
Re: OCA Coding Standards and recommended IDEs
by
ClosingAp Open Source Integrators Europe, LDA, Daniel Reis
> I think we are actually saying the same thing: what Travis does, is a > somewhat custom setup of flake8 + pylint. > > What we need is a simple standalone wrapper, independent of everything > (especially Travis) that does just the same check that Travis does > now. > > Then: > - travis just runs the script > - people can run the script locally from the command line > - optional: people can configure their editor of choice to run it > inside the editor. This is something I am actually confortable giving > specific advice about (example "if you use vim you can configure > syntastic to run the checker XXX on python files") > > Of course I agree with Oleg: we want to easily run the same checks > that Travis runs locally. Agreed, contributions welcome: https://github.com/OCA/maintainer-quality-tools/issues/281 Additionally, I suggest: -The CONTRIBUTING.md file is missing from most repos, we should fix that - The document it points at, OCA/maintainer-tools/CONTRIBUTING.md", should be a "getting started" text instead of the actual coding standards. /DR
Reference
-
OCA Coding Standards and recommended IDEs
byXpansa Group, Oleg Kuryan-
Re: OCA Coding Standards and recommended IDEs
byOpen Source Integrators, Maxime Chambreuil -
Re: OCA Coding Standards and recommended IDEs
byEcosoft Co. Ltd., Kitti Upariphutthiphong
-