[Openstack-operators] [openstack-operators][osops][tools-generic] Coding Standards/Coding Linters for tools-generic
jj at chef.io
Tue Nov 17 17:56:05 UTC 2015
-----BEGIN PGP SIGNED MESSAGE-----
On 11/16/15 7:43 PM, Clayton O'Neill wrote:
> I think it’s a good idea. I think scripts and such that don’t pass the
> listing tools can go into the contrib repos and if they get cleaned up
> then they can move over to the regular ones.
Yep! That's the master plan. No barrier to entry for the contrib apart
from some minor peer review, and our coding standards in the tools-generic.
> I don’t actually like some of the PEP8 and bashate rules, but I’d rather
> have a consistent style than have them in everyone’s personal style. I
> find less opinionated tools like rubocop to be less useful, since you
> end up bogged down in arguing about which style options to choose.
Yep, that's the can o'worms I was talking about. I was thinking that we
could just steal this .rubocop.yml, as it's a "sane" default for us
at Chef. If you take a look at it you'll see its pretty simple which is
what we're looking for.
Speaking of this .rubocop.yml I'll add it to the etherpad.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2
Comment: GPGTools - https://gpgtools.org
-----END PGP SIGNATURE-----
More information about the OpenStack-operators