Add the Contributor Covenant Code of Conduct

[DeeDeeG]

My commit message for this commit:

This is a solid Code of Conduct to base ours on.

We can modify this if need be to better match our project and its expectations of behavior. But it is already a good starting point as-is.

Context

• Fixes #488
• See discussion in #488 and please feel free to discuss more there (or here either is fine)
• We're adding a code of conduct to our project to guide folks' behavior and make sure we can enforce good behavior if there is some sort of dispute.
  • GitHub would like us to do this before including us in a collection of other projects working toward social impact (Social Impact collection), and/but it's also a good idea in general to have a code of conduct, (so the consensus seems to go on this subject anyway.) It doesn't hurt though.

Summary of Changes

• Uses the basic code of conduct that GitHub points people toward for any project: the Contributor Covenant.
• (Adds CODE_OF_CONDUCT.md to the project, 100% copy-pasted from Contributor Covenant site, as is the default way to use their Code of Conduct.)
  • One part is just filler text on their site, namely the contact email. I used refugerestrooms [AT] gmail [DOT] com for our contact email.)

Nota Bene (my thoughts and opinions)

• There is no reason at all why we can't modify or enhance this code of conduct, or make it better match our projects aims and needs (at any time). That's definitely encouraged big-time. If somebody wants to improve this, I'd say discuss here if it's not merged yet, or if it is already merged, please open an issue, a PR, or discuss on Slack or anywhere you can get a hold of a maintainer for the project.
• Having a more specific code of conduct specific to our project would only be a benefit in my book, vs a more generic one.
• I also feel like this one is fine, and people get our intentions and culture from our actions anyway. We're pretty nice around here. I'm hoping and anticipating this doesn't really mean much about the way we all behave toward one-another and toward newcomers.
  • But the code is there if we hit bumps in the road.

Checklist

• [ ] Tested Mobile Responsiveness
• [ ] Added Unit Tests
• [ ] CI Passes
• [ ] Deploys to Heroku on test Correctly (Maintainers will handle)
• [ ] Added Documentation (Service and Code when required)

[mi-wood]

Sorry I haven't been around. Just been dealing with life. This looks solid to me, we can go back and change things as we see fit later.

[DeeDeeG]

Sorry I haven't been around. just been dealing with life.

No problem! That's all of us I think.

This looks solid to me, we can go back and change things as we see fit later.

Agreed, and thanks for merging.