From nobody Mon Feb 9 07:26:54 2026 Delivered-To: importer@patchew.org Received-SPF: none (zohomail.com: 192.237.175.120 is neither permitted nor denied by domain of lists.xenproject.org) client-ip=192.237.175.120; envelope-from=xen-devel-bounces@lists.xenproject.org; helo=lists.xenproject.org; Authentication-Results: mx.zohomail.com; spf=none (zohomail.com: 192.237.175.120 is neither permitted nor denied by domain of lists.xenproject.org) smtp.mailfrom=xen-devel-bounces@lists.xenproject.org ARC-Seal: i=1; a=rsa-sha256; t=1576185373; cv=none; d=zohomail.com; s=zohoarc; b=Sb13VyAPDdYTBCkL/EhEoaM4IrorWPBOsEF4VKQehk/OGJ48KzfC1ore1PF3ToIZ09P95zpB7JRNw4lViX0FrkfdPE7iJTWiRRAaWL4Gy2U2ABSqsmK2QorY8z7jpqkjE+ktnVL1V+tCVK+l+FZT1SVMYK87DUPJHGcuZ6dlJ/E= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1576185373; h=Content-Type:Content-Transfer-Encoding:Cc:Date:From:In-Reply-To:List-Subscribe:List-Post:List-Id:List-Help:List-Unsubscribe:MIME-Version:Message-ID:References:Sender:Subject:To; bh=Rd6ISbWfY+H37OtHvi+fyvUKEXDw39ihRx9Q6P0r2KU=; b=K2z+63AiyyrIpom3gKMWddt3JJZ/b540o9bHNFkHt7yHIt9Jt30srxvwS3xAZqreha0ehEsp0SnHNPS7Hmk7D9sU3zB7dbz4h4cC7xlFi1SykirFuUABERZCClfmyYa7vQ8EuWoEb1lJDwWCV4WVT4c6QMSbQyov7+bO1VrmxKo= ARC-Authentication-Results: i=1; mx.zohomail.com; spf=none (zohomail.com: 192.237.175.120 is neither permitted nor denied by domain of lists.xenproject.org) smtp.mailfrom=xen-devel-bounces@lists.xenproject.org Return-Path: Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) by mx.zohomail.com with SMTPS id 1576185373231991.0705688064565; Thu, 12 Dec 2019 13:16:13 -0800 (PST) Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.89) (envelope-from ) id 1ifVo6-0006J8-Aq; Thu, 12 Dec 2019 21:15:34 +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 1ifVo5-0006Iu-9e for xen-devel@lists.xenproject.org; Thu, 12 Dec 2019 21:15:33 +0000 Received: from mail.xenproject.org (unknown [104.130.215.37]) by us1-amaz-eas2.inumbo.com (Halon) with ESMTPS id 736d2acc-1d24-11ea-8e25-12813bfff9fa; Thu, 12 Dec 2019 21:14:58 +0000 (UTC) Received: from xenbits.xenproject.org ([104.239.192.120]) by mail.xenproject.org with esmtp (Exim 4.89) (envelope-from ) id 1ifVnT-00015T-M4; Thu, 12 Dec 2019 21:14:55 +0000 Received: from localhost ([127.0.0.1] helo=localhost.localdomain) by xenbits.xenproject.org with esmtp (Exim 4.89) (envelope-from ) id 1ifVnT-0000Bm-F1; Thu, 12 Dec 2019 21:14:55 +0000 X-Inumbo-ID: 736d2acc-1d24-11ea-8e25-12813bfff9fa From: Lars Kurth To: xen-devel@lists.xenproject.org Date: Thu, 12 Dec 2019 21:14:30 +0000 Message-Id: <1f54362a58bfb5bba6459eb31e408aeabebc66e6.1576184325.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 v3 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 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable 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 | 56 ++++++++++++++++++++++++++++----------------------= ---- 1 file changed, 29 insertions(+), 27 deletions(-) diff --git a/code-of-conduct.md b/code-of-conduct.md index 5d6d1d5..4912f47 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 a= nd our community a harassment-free experience for everyone, regardless of age= , body -size, disability, ethnicity, sex characteristics, gender identity and expr= ession, -level of experience, education, socio-economic status, nationality, person= al -appearance, race, religion, or sexual identity and orientation. +size, disability, ethnicity, sex characteristics, gender identity and +expression, level of experience, education, socio-economic status, nationa= lity, +personal appearance, race, religion, or sexual identity and orientation. =20 ## Our Standards =20 We believe that a Code of Conduct can help create a harassment-free enviro= nment, but is not sufficient to create a welcoming environment on its own: guidan= ce on -creating a welcoming environment, how to communicate in an effective and f= riendly -way, etc. can be found [here](communication-guide.md). +creating a welcoming environment, how to communicate in an effective and +friendly way, etc. can be found [here](communication-guide.md). =20 Examples of unacceptable behavior by participants include: =20 @@ -29,41 +29,43 @@ Examples of unacceptable behavior by participants inclu= de: =20 ## Our Responsibilities =20 -Project leadership team members are responsible for clarifying the standar= ds 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 standar= ds of +acceptable behavior and are expected to take appropriate and fair correcti= ve +action in response to any instances of unacceptable behavior. =20 -Project leadership team members have the right and responsibility to remov= e, 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 inappropria= te, -threatening, offensive, or harmful. +Project leadership team members have the right and responsibility to remov= e, +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 d= eem +inappropriate, threatening, offensive, or harmful. =20 ## Scope =20 -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 space= s. -Examples of representing a project or community include using an official -project e-mail address, posting via an official social media account, or a= cting -as an appointed representative at an online or offline event. Representati= on 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 of= fline +event. Representation of a project may be further defined and clarified by= the +project leadership. =20 ## What to do if you witness or are subject to unacceptable behavior =20 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 mem= bers are -obligated to maintain confidentiality with regard to the reporter of an in= cident. -Further details of specific enforcement policies may be posted separately. +is deemed necessary and appropriate to the circumstances. Conduct Team mem= bers +are obligated to maintain confidentiality with regard to the reporter of an +incident. Further details of specific enforcement policies may be posted +separately. =20 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. =20 -Project leadership team members who do not follow or enforce the Code of C= onduct 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 C= onduct +in good faith may face temporary or permanent repercussions as determined = by +other members of the project's leadership. =20 ## Conduct Team members Conduct Team members are project leadership team members from any @@ -78,8 +80,8 @@ posted on all sub-project lists, followed by a formal glo= bal vote as outlined =20 ## Attribution =20 -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-cond= uct.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 =20 [homepage]: https://www.contributor-covenant.org =20 --=20 2.13.0 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel