Contributing to the project - guidelines

[RobSmyth]

Hi,

Looking at PR 91 I wonder if a few contribution guidelines could be added to the readme.md file to help PRs get through. If so, I'm happy to help with raising PRs to update the readme.md file.

@TimSoethout - I hope this will reduce your time and our dependency on you for everything.

Thoughts:

• Add PR guideline - Updates to the readme.md file are mandatory for any PR that changes functionality.
• Add info on branch naming for alphas betas etc (?).
• How alpha betas are released/managed.
• A small incremental PR is your friend. Prefer small PRs with each having a clear single functional change.

A thought - I like to do several small PRs rather than one. These usually go to a feature branch and are later merged to a release branch. Nothing goes to the feature branch without a PR. With all the changes reviewed incrementally the feature to release PR only needs basic review and testing.

Thoughts?

[RobSmyth]

Another guideline thought ...

Remove PRs if inactive for X period.