Add CoC documents - Githubissues

nebari-dev / governance

✨ Governance-related work for Nebari-dev

BSD 3-Clause "New" or "Revised" License

0 stars 2 forks source link

Add CoC documents #23

Closed pavithraes closed 1 year ago

pavithraes commented 1 year ago

Reference Issues or PRs

Closes #5

What does this implement/fix?

Put a x in the boxes that apply

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds a feature)
[ ] Breaking change (fix or feature that would cause existing features not to work as expected)
[x] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[ ] Other (please describe):

Testing

[ ] Did you test the pull request locally?
[ ] Did you add new tests?

Documentation

Access-centered content checklist

Text styling

[x] The content is written with plain language (where relevant).
[x] If there are headers, they use the proper header tags (with only one level-one header: H1 or # in markdown).
[x] All links describe where they link to (for example, check the Nebari website).
[x] This content adheres to the Nebari style guides.

Non-text content

[ ] All content is represented as text (for example, images need alt text, and videos need captions or descriptive transcripts).
[ ] If there are emojis, there are not more than three in a row.
[ ] Don't use flashing GIFs or videos.
[ ] If the content were to be read as plain text, it still makes sense, and no information is missing.

Any other comments?

pavithraes commented 1 year ago

@trallard Thanks for the review and suggestions!

Are we also adding this to the docs or directing everyone to the governance repo?

I think the governance repo is a good place for the CoC to live, especially since we're maintaining this repo well.

I'll merge this PR in for now, and we can move it to docs later if there is a need for more visibility+searchability. :)