Add code of conduct #1038
Merged
Add code of conduct #1038
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
pda
approved these changes
Jul 20, 2022
| ## Enforcement | ||
|
|
||
| Instances of abusive, harassing, or otherwise unacceptable behavior may be | ||
| reported to the community leaders responsible for enforcement at [coc@buildkite.com](mailto:coc@buildkite.com) |
There was a problem hiding this comment.
Missing period 😅
Suggested change
| reported to the community leaders responsible for enforcement at [coc@buildkite.com](mailto:coc@buildkite.com) | |
| reported to the community leaders responsible for enforcement at [coc@buildkite.com](mailto:coc@buildkite.com). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The elastic stack is a pretty big opensource project! It's awesome to have so many lovely contributors, but it's still important to have a reasonable set of expectations of the community (buildkite employees included!), and have a framework upon which to enforce those expectations, if necessary.
To my knowledge, we've never been in a situation where we'd have needed to invoke the CoC, but it's much better to have these things and not need them than it is to need them and not have them.
This PR adds a code of conduct to this repo, adapted from the Contributor Covenant v2.1.
See also: buildkite/agent#1717