From patchwork Mon Dec 30 19:32:15 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Lars Kurth X-Patchwork-Id: 11313655 Return-Path: Received: from mail.kernel.org (pdx-korg-mail-1.web.codeaurora.org [172.30.200.123]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id 9DA7F138D for ; Mon, 30 Dec 2019 19:34:13 +0000 (UTC) Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 7962420409 for ; Mon, 30 Dec 2019 19:34:13 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 7962420409 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=xenproject.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=xen-devel-bounces@lists.xenproject.org Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.89) (envelope-from ) id 1im0mf-0003jZ-7f; Mon, 30 Dec 2019 19:32:57 +0000 Received: from all-amaz-eas1.inumbo.com ([34.197.232.57] helo=us1-amaz-eas2.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.89) (envelope-from ) id 1im0md-0003jO-QU for xen-devel@lists.xenproject.org; Mon, 30 Dec 2019 19:32:55 +0000 X-Inumbo-ID: 1fa7295e-2b3b-11ea-a060-12813bfff9fa Received: from mail.xenproject.org (unknown [104.130.215.37]) by us1-amaz-eas2.inumbo.com (Halon) with ESMTPS id 1fa7295e-2b3b-11ea-a060-12813bfff9fa; Mon, 30 Dec 2019 19:32:32 +0000 (UTC) Received: from xenbits.xenproject.org ([104.239.192.120]) by mail.xenproject.org with esmtp (Exim 4.89) (envelope-from ) id 1im0mC-0003Th-KP; Mon, 30 Dec 2019 19:32:28 +0000 Received: from localhost ([127.0.0.1] helo=MacBook-Pro-2.Home) by xenbits.xenproject.org with esmtp (Exim 4.89) (envelope-from ) id 1im0mC-0007YU-8D; Mon, 30 Dec 2019 19:32:28 +0000 From: Lars Kurth To: xen-devel@lists.xenproject.org Date: Mon, 30 Dec 2019 19:32:15 +0000 Message-Id: <6ec278b81c16cd6279312190f2ce42af75aed93e.1577733361.git.lars.kurth@citrix.com> X-Mailer: git-send-email 2.13.0 In-Reply-To: References: In-Reply-To: References: Subject: [Xen-devel] [PATCH v4 3/7] Reformat Xen Project CoC to fit into 80 character limit X-BeenThere: xen-devel@lists.xenproject.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Cc: Lars Kurth , xen-api@lists.xenproject.org, minios-devel@lists.xenproject.org, committers@xenproject.org, mirageos-devel@lists.xenproject.org, win-pv-devel@lists.xenproject.org MIME-Version: 1.0 Errors-To: xen-devel-bounces@lists.xenproject.org Sender: "Xen-devel" From: Lars Kurth No content changes Signed-off-by: Lars Kurth --- Cc: minios-devel@lists.xenproject.org Cc: xen-api@lists.xenproject.org Cc: win-pv-devel@lists.xenproject.org Cc: mirageos-devel@lists.xenproject.org Cc: committers@xenproject.org --- code-of-conduct.md | 62 +++++++++++++++++++++++++++++------------------------- 1 file changed, 33 insertions(+), 29 deletions(-) diff --git a/code-of-conduct.md b/code-of-conduct.md index ee751a7..7c29a4f 100644 --- a/code-of-conduct.md +++ b/code-of-conduct.md @@ -5,16 +5,16 @@ In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body -size, disability, ethnicity, sex characteristics, gender identity and expression, -level of experience, education, socio-economic status, nationality, personal -appearance, race, religion, or sexual identity and orientation. +size, disability, ethnicity, sex characteristics, gender identity and +expression, level of experience, education, socio-economic status, nationality, +personal appearance, race, religion, or sexual identity and orientation. ## Our Standards We believe that a Code of Conduct can help create a harassment-free environment, but is not sufficient to create a welcoming environment on its own: guidance on -creating a welcoming environment, how to communicate in an effective and friendly -way, etc. can be found [here]: TODO-INSERT-URL. +creating a welcoming environment, how to communicate in an effective and +friendly way, etc. can be found [here][guidance]. Examples of unacceptable behavior by participants include: @@ -29,41 +29,43 @@ Examples of unacceptable behavior by participants include: ## Our Responsibilities -Project leadership team members are responsible for clarifying the standards of acceptable -behavior and are expected to take appropriate and fair corrective action in -response to any instances of unacceptable behavior. +Project leadership team members are responsible for clarifying the standards of +acceptable behavior and are expected to take appropriate and fair corrective +action in response to any instances of unacceptable behavior. -Project leadership team members 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, or to ban temporarily or -permanently any contributor for other behaviors that they deem inappropriate, -threatening, offensive, or harmful. +Project leadership team members 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, or to ban +temporarily or permanently any contributor for other behaviors that they deem +inappropriate, threatening, offensive, or harmful. ## Scope -This Code of Conduct applies within all project spaces of all sub-projects, and it also applies when -an individual is representing the project or its community in public spaces. -Examples of representing a project or community include using an official -project e-mail address, posting via an official social media account, or acting -as an appointed representative at an online or offline event. Representation of -a project may be further defined and clarified by the project leadership. +This Code of Conduct applies within all project spaces of all sub-projects, +and it also applies when an individual is representing the project or its +community in public spaces. Examples of representing a project or community +include using an official project e-mail address, posting via an official social +media account, or acting as an appointed representative at an online or offline +event. Representation of a project may be further defined and clarified by the +project leadership. ## What to do if you witness or are subject to unacceptable behavior Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting Conduct Team members at conduct@xenproject.org. All complaints will be reviewed and investigated and will result in a response that -is deemed necessary and appropriate to the circumstances. Conduct Team members are -obligated to maintain confidentiality with regard to the reporter of an incident. -Further details of specific enforcement policies may be posted separately. +is deemed necessary and appropriate to the circumstances. Conduct Team members +are obligated to maintain confidentiality with regard to the reporter of an +incident. Further details of specific enforcement policies may be posted +separately. If you have concerns about any of the members of the conduct@ alias, you are welcome to contact precisely the Conduct Team member(s) of your choice. -Project leadership team members who do not follow or enforce the Code of Conduct in good -faith may face temporary or permanent repercussions as determined by other -members of the project's leadership. +Project leadership team members who do not follow or enforce the Code of Conduct +in good faith may face temporary or permanent repercussions as determined by +other members of the project's leadership. ## Conduct Team members Conduct Team members are project leadership team members from any @@ -73,15 +75,17 @@ sub-project. The current list of Conduct Team members is: * Ian Jackson Conduct Team members are changed by proposing a change to this document, -posted on all sub-project lists, followed by a formal global vote as outlined [here]: https://xenproject.org/developers/governance/#project-decisions +posted on all sub-project lists, followed by a formal global vote as outlined +[here]: https://xenproject.org/developers/governance/#project-decisions ## Attribution -This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, -available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html +This Code of Conduct is adapted from the [Contributor Covenant][homepage], +version 1.4, available at +https://www.contributor-covenant.org/version/1/4/code-of-conduct.html [homepage]: https://www.contributor-covenant.org +[guidance]: TODO-INSERT-URL For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq -