-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #10 from flatcar/t-lo/use-cncf-code-of-conduct
code-of-conduct.md: use CNCF code of conduct
- Loading branch information
Showing
1 changed file
with
3 additions
and
59 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,61 +1,5 @@ | ||
## CoreOS Community Code of Conduct | ||
# Code of Conduct | ||
|
||
### Contributor Code of Conduct | ||
We follow the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/main/code-of-conduct.md). | ||
|
||
As contributors and maintainers of this project, and in the interest of | ||
fostering an open and welcoming community, we pledge to respect all people who | ||
contribute through reporting issues, posting feature requests, updating | ||
documentation, submitting pull requests or patches, and other activities. | ||
|
||
We are committed to making participation in this project a harassment-free | ||
experience for everyone, regardless of level of experience, gender, gender | ||
identity and expression, sexual orientation, disability, personal appearance, | ||
body size, race, ethnicity, age, religion, or nationality. | ||
|
||
Examples of unacceptable behavior by participants include: | ||
|
||
* The use of sexualized language or imagery | ||
* Personal attacks | ||
* Trolling or insulting/derogatory comments | ||
* Public or private harassment | ||
* Publishing others' private information, such as physical or electronic addresses, without explicit permission | ||
* Other unethical or unprofessional conduct. | ||
|
||
Project maintainers have the right and responsibility to remove, edit, or | ||
reject comments, commits, code, wiki edits, issues, and other contributions | ||
that are not aligned to this Code of Conduct. By adopting this Code of Conduct, | ||
project maintainers commit themselves to fairly and consistently applying these | ||
principles to every aspect of managing this project. Project maintainers who do | ||
not follow or enforce the Code of Conduct may be permanently removed from the | ||
project team. | ||
|
||
This code of conduct applies both within project spaces and in public spaces | ||
when an individual is representing the project or its community. | ||
|
||
Instances of abusive, harassing, or otherwise unacceptable behavior may be | ||
reported by contacting a project maintainer, Brandon Philips | ||
<[email protected]>, and/or Rithu John <[email protected]>. | ||
|
||
This Code of Conduct is adapted from the Contributor Covenant | ||
(http://contributor-covenant.org), version 1.2.0, available at | ||
http://contributor-covenant.org/version/1/2/0/ | ||
|
||
### CoreOS Events Code of Conduct | ||
|
||
CoreOS events are working conferences intended for professional networking and | ||
collaboration in the CoreOS community. Attendees are expected to behave | ||
according to professional standards and in accordance with their employer’s | ||
policies on appropriate workplace behavior. | ||
|
||
While at CoreOS events or related social networking opportunities, attendees | ||
should not engage in discriminatory or offensive speech or actions including | ||
but not limited to gender, sexuality, race, age, disability, or religion. | ||
Speakers should be especially aware of these concerns. | ||
|
||
CoreOS does not condone any statements by speakers contrary to these standards. | ||
CoreOS reserves the right to deny entrance and/or eject from an event (without | ||
refund) any individual found to be engaging in discriminatory or offensive | ||
speech or actions. | ||
|
||
Please bring any concerns to the immediate attention of designated on-site | ||
staff, Brandon Philips <[email protected]>, and/or Rithu John <[email protected]>. | ||
Please contact [private Maintainer mailing list]([email protected]) or the Cloud Native Foundation mediator, [email protected], to report an issue. |