Setting up Code of Conduct

[NyaMisty]

We need to set up a good code of conduct, especially for:

• Commit message
• Code style & linting options
• Merging: Merge or Rebase?

[robkam]

There is a standard Code of Conduct for Open Source Communities only needing to add contact details for "the community leaders responsible for enforcement".

[elsiehupp]

We need to set up a good code of conduct, especially for:

* Commit message
* Code style & linting options
* Merging: Merge or Rebase?

These seem more specific to "CONTRIBUTING" than "CODE_OF_CONDUCT", which is fine.

Code style and linting should already be taken care of by Pre-Commit: it should automatically format all Python files using Black, in addition to checking a number of other things. I was going to set up Markdown linting, as well, but I don't think I ever finished doing that.

With the code of conduct, the one suggested by @robkam seems fine, and since I'm in the admin role for the repositories at this moment, I would probably be the contact person for the template. In terms of contact method, I could set up an email alias for that specific purpose, i.e. <alias.string.here>@elsiehupp.com, though if it includes the name of the project we should probably figure that out, as well. For the time being, the contact email I have listed in the "Collaborators" pinned discussion is probably fine.

[robkam]

For CONTRIBUTING.md - something like Git Style Guide?