[geomoose-psc] RFC-9: Adopt new linting and code formatting rules

[Eli Adam]

A consistent style is important.  I'm generally in favor of this but would
be open to discussion before voting.  I have some hesitancy of putting this
in an RFC if a simple PSC vote would suffice.

We would need to look at other conflicting information that might be in
https://github.com/geomoose/geomoose-website/blob/ac3cbbbb54457f08a75f558167e81c94ad8484a0/source/rfc/rfc-4.rst
or https://docs.geomoose.org/3.x/style_guide.html

Why an RFC instead of a PSC vote on updating the style guide?  I expect our
coding style and guidelines to change again in ten to fifteen years.

Best regards, Eli

On Wed, Jun 29, 2022 at 8:55 PM Dan Little <theduckylittle at gmail.com> wrote:

> Hey folks!
>
> An itch that I've been wanting to scratch for a while is some code clean
> up practices. The Javascript world has started to really center around some
> opinionated tooling that has really been standard practice now. I wrote the
> following RFC:
> -
> https://github.com/geomoose/geomoose-website/blob/ac3cbbbb54457f08a75f558167e81c94ad8484a0/source/rfc/rfc-9.rst
>
> And put together what the changes will look like:
>  - https://github.com/theduckylittle/gm3/pull/2
>
> I would like to officially put RFC-9 open for comments and a vote.
>
> Cheers!
> _______________________________________________
> geomoose-psc mailing list
> geomoose-psc at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geomoose-psc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geomoose-psc/attachments/20220630/b2c86cc2/attachment.htm>