Make the PR experience better for new developers

[handeyeco]

This project was meant to help newbies get started with OSS. We want to make sure the style is consistent and the tests pass, but we also don't want to discourage people. How do we do that?

Possible ideas:

• Only enforce tests passing (basic functionality) for PRs and handle linting syntax/styles automatically with a git hook server that pushes updated commits.
  • PRO: less work for developer
  • CON: need to host a server and have to let it commit to master
• Depend more heavily on scripts to edit files pre-commit.
  • PRO: users can get immediate feedback
  • CON: would require devs to have node/npm

Anyone have any other ideas?

[shimphillip]

I would think the 2nd option is more viable.

Its pro is more attractive and con isn't that bad. IMO installing node and npm shouldn't be that difficult, we can even write up how to install them as part of setup. BTW, this is already what you set up right?

We could also make a channel on our slack for this project if it's easier to make conversations there.