Releasing as a community project we need to document what our community process is.

Upstream projects sometimes have an GH issue template and a contributing section, but we can be quite free on what we want to do here. I suggest as a starting point, we making use of Github issues (bugs and feature requests will go into our backlog) and we have a couple of contribution guidelines we can grab from an existing project.

AC:

• Define a GH issue template to explain the process
• Document contribution guidelines in README.md and DEV.md