On Mon, Oct 19, 2020 at 9:24 PM Brett Cannon <brett@python.org> wrote:

I think the other way to help is to really lean into automation so reviewing is even lighterweight than it is now. Now this can be as simple as to remind people when they need to regenerate a file like 'configure' via a status check, simply telling people when their PR failed a status check, or go as far as try to automate PEP 7/8 stuff.

Or another way to put it is to try and use automation to help make PRs more self-service so that there's less required from a human being to do.

A huge +1 from me!

Besides efficiency, I like that kind of automation because it makes our checking of these things more consistent and official. Another reason is that it allows contributors to be more independent in their work, rather than waiting for someone else to explain what they have to do.

I've avoided mentioning code style until now since I remembered it being a bit of a touchy subject a few years ago when I recall it coming up. Personally I think that the benefits of being able to automate styling and style checking far outweigh the negatives that were brought up at the time. Brett, if you'd like to open that can of worms, I'd be willing to help.

- Tal