docs: add code of conduct

[ajbozarth]

Misc PR

Type of PR

• Bug Fix
• New Feature
• Documentation
• Other

Description

• Link to Issue: Contribution guidelines are not provided in README. #315

Adds a standard code of conduct policy similar to other open source projects.

The initial doc points to the org members list for private reporting, but this should be updated to either a MAINTAINERS.md or a committers list once we've added one of them

Testing

• Tests added to the respective file if code was changed
• New code has 100% coverage if code as added
• Ensure existing tests and github automation passes (a maintainer will kick off the github automation when the rest of the PR is populated)

[github-actions]

The PR description has been updated. Please fill out the template for your PR to be reviewed.

[mergify]

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 Enforce conventional commit

Wonderful, this rule succeeded.

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

• title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert|release)(?:\(.+\))?:

[planetf1]

Agree with this proposal - it's a very standard, widely used text (with the well respected mozilla clarifications)

[psschwei]

Suggested change

	reported by contacting the project team via the [organization members](https://github.com/orgs/generative-computing/people) or by opening an issue on the [GitHub repository](https://github.com/generative-computing/mellea/issues).
	reported by contacting the project team via the [organization members](https://github.com/orgs/generative-computing/people).

My inclination is that opening a COC complaint should not be done publicly. Do we have an email we could put here @nrfulton ?

[ajbozarth]

I left that there since other projects had it, but I agree. I we have an email contact I can update this to use that similar to other projects

[planetf1]

Github does have ability to 'report' (which goes to admins/moderators) but this doesn't feel sufficient. I too would support the idea of just having email for this sensitive aspect.

[ajbozarth]

Status Update: This needs to following before merge:

• A contact email to send CoC violations to rather than submitting in the open
• Update the doc with the above contact email
• PR approval (preferably from @nrfulton)