Update contributing.rst to reflect current practice?

[timgdavies]

I wasn't sure where best to file this issue, as it applies across a couple of repositories (hence choosing SSOT...) - but builds on discussions that Kate was involved in during technical workshop in Copenhagen this week. It's offered as a low-priority suggestion.

During that workshop, we identified that some community members were not always clear about current technical team expectations and practices for handling issues, contributing to code, or opening/closing pull requests.

I noticed that the current Contributing.rst file in each repo (which gets displayed to anyone opening a new issue like this one (see below) doesn't describe the expectations and practices that were discussed in Copenhagen, and links to this page which I think is also outdated.

You may wish to consider updating the standard Contributing.rst file to fit current expectations and guidance to contributors.

I have found in past projects that adding Pull Request and Issue templates to repositories can also be helpful for guiding community inputs in a useful direction.

[samuele-mattiuzzo]

@timgdavies thanks for the suggestion, I was actually looking into this before heading off on holidays and I'll resume it. I did try to add a "mock" version of it at organisation level, but it didn't replicate across repos! So essentially, WIP! As you noticed, the guidance page is out of dated and needs updating, we do have wording around contributing to our repos, they need a bit of tidying up and then replicated across the repos with an extra CoC as well to make sure everything (or as much as we can) is covered