Write a contribution guide

[BMatischen01]

How can people contribute? What process to pull changes, make and test their edits, code review, etc.?

Do COS have a template or example guide?

[SJaffa]

@futa-ikeda does COS have a template or example contribution guide that we could look at? We haven't written these before so seeing what is usually included owuld be helpful.

[futa-ikeda]

A couple of our repositories have a contributing file. Maybe these can be of help.

https://github.com/CenterForOpenScience/waterbutler/blob/develop/CONTRIBUTING.md
https://github.com/CenterForOpenScience/modular-file-renderer/blob/develop/CONTRIBUTING.rst

I haven't written one myself, so there may be some stuff missing in these that I'm not thinking of.

[SJaffa]

We should explain our branch naming convention and gitflow

[BMatischen01]

If someone gets an error repeatedly or lots of errors, ask to submit an issue on the repo.

[BMatischen01]

• Gitflow model
• Branch naming conventions
• Requirement for all tests passing (GitHub Action check ran on PRs)
• Semantic versioning explanation
• Linting with flake8
• Import order
• General suggestions
• Bug reporting: what the problem is, add how to reproduce, platform

[BMatischen01]

Closing as merged #120 into dev and released