Create CODE_OF_CONDUCT.md

[BobinMathew]

Related Issue(s): #
Issue #385

Description:
Created a CODE_OF_CONDUCT.md that points to Code of Conduct in the STAC spec repo. This makes the code of conduct consistent with the STAC repo's code of conduct

PR Checklist:

• Code is formatted (run scripts/format)
• Tests pass (run scripts/test)
• This PR maintains or improves overall codebase code coverage.
• Changes are added to the CHANGELOG. See the docs for information about adding to the changelog.

[codecov-commenter]

Codecov Report

Merging #399 (bc37c34) into main (3f2f95f) will decrease coverage by 0.06%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #399      +/-   ##
==========================================
- Coverage   89.71%   89.64%   -0.07%     
==========================================
  Files          39       39              
  Lines        5154     5169      +15     
==========================================
+ Hits         4624     4634      +10     
- Misses        530      535       +5     

Impacted Files	Coverage Δ
pystac/stac_io.py	72.46% <0.00%> (-0.68%)	⬇️
pystac/item.py	96.67% <0.00%> (-0.56%)	⬇️
pystac/summaries.py	78.20% <0.00%> (ø)
pystac/stac_object.py	95.08% <0.00%> (ø)
pystac/extensions/label.py	85.89% <0.00%> (ø)
pystac/validation/stac_validator.py	87.35% <0.00%> (ø)
pystac/utils.py	97.02% <0.00%> (+0.06%)	⬆️
pystac/extensions/datacube.py	57.03% <0.00%> (+1.16%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3f2f95f...bc37c34. Read the comment docs.

[duckontheweb]

Thanks for contributing this @BobinMathew, and for recognizing the gap.

I think it might be good to at least include the Our Pledge portion of the Code of Conduct in full in this document and then reference the STAC Code of Conduct for details on the specific standards. It seems important to make a clear statement in this repo about the kind of environment that are hoping to foster so that newcomers know it's something that's important within the community.

Also, the STAC spec Code of Conduct lists stac-spec-admins@googlegroups.com as the contact to report abuses and unacceptable behavior. Do we need a different email, or can we use that one here (@cholmes)?

[BobinMathew]

• Included Pledge
• contact details pending...

[duckontheweb]

@BobinMathew We are going to use the STAC Project Steering Committee email (stac-psc@radiant.earth) as our point of contact. It sounds like the stac-spec repo may also update their Code of Conduct to use this email at some point.

I think it would be good to include that information in this repo as well to make it as easy as possible for someone to report a violation or other problem.

[BobinMathew]

• Included Pledge
• contact details added

[duckontheweb]

This looks good to me, thanks for contributing this @BobinMathew!

I'd like to get approval from at least @cholmes and @lossyrob as well and give other folks a chance to comment if they'd like.

[lossyrob]

Made some suggestions for small changes

[BobinMathew]

Thanks everyone 😀

[duckontheweb]

Thanks again for the contribution @BobinMathew!