This repository has been archived by the owner on Nov 5, 2024. It is now read-only.
Adding the Contributor Covenant Code of Conduct #31
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
RichardLitt
commented
Jun 27, 2017
open-source/CODE_OF_CONDUCT.md
Outdated
| ## Enforcement | ||
|
|
||
| Instances of abusive, harassing, or otherwise unacceptable behavior may be | ||
| reported by contacting the project team at [email protected]. All |
There was a problem hiding this comment.
Add a second email, here.
|
@cfnelson The PRs you merged reference this document! Might be a good idea to merge this, too. :) |
|
@RichardLitt Was just planning to merge , trying to figure out the 2nd email 😄 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See http://contributor-covenant.org.
This will set the tone for how to deal with other people, and infractions, in your online community. I would suggest adding a second email -
[email protected]works basically, unless there are issues with one of of OKGrow's staff and the person wants to make sure it doesn't get to them. In that case, I think the CEO's or HR's email should be appropriate. I know it seems a bit corporate-y, but it will help users feel safer on GitHub.