From: Lars Kurth <lars.kurth@citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Lars Kurth <lars.kurth@citrix.com>,
xen-api@lists.xenproject.org, minios-devel@lists.xenproject.org,
committers@xenproject.org, mirageos-devel@lists.xenproject.org,
win-pv-devel@lists.xenproject.org
Subject: [Xen-devel] [PATCH 0/2] Code of Conduct (based on Contributor Covenant v1.4)
Date: Wed, 4 Sep 2019 19:12:16 +0100 [thread overview]
Message-ID: <cover.1567620587.git.lars.kurth@citrix.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=N, Size: 2086 bytes --]
This series proposes a concrete version of the Xen Project
CoC based on v1.4 of the Contributor Covenant. See [1]
It also reflects the discussion in [2] and some private
discussions on IRC to identify initial members of the Xen
Project’s CoC team.
For convenence of review and in line with other policy documents
I created a git repository at [3]. This series can be found at [5].
The series is incomplete in that it does not yet contain the document
on positive behavior: this will be based on [4]. My intention is to
use a lightwight process based on
* Documentation to set expectations, share tips and best practices - with the
hope that people in the community reflect occasionally on how they are doing
against these (or are maybe prompted by peers to do so)
* A safe back-channel to ask for advice when a conversation becomes inefficient,
unactionable, is unfriendly, ... with a view to recover it
* Arbitration in cases where there is some friction amongst participants in a
discussion, which was not resolvable by any of the before. After all, when this
happens there is a risk that a working relationship gets negatively impacted. It
is actually in the interest of each participant to improve to avoid friction,
stress, etc.
I hope that we can approve the series without the first part, but I do not mind
if people feel this needs to be done in one go.
[1] https://www.contributor-covenant.org/version/1/4/code-of-conduct.md
[2] https://xen.markmail.org/thread/56ao2gyhpltqmrew
[3] http://xenbits.xen.org/gitweb/?p=people/larsk/code-of-conduct.git;a=summary
[4] https://www.slideshare.net/xen_com_mgr/xpdds19-keynote-patch-review-for-nonmaintainers-george-dunlap-citrix-systems-uk-ltd
[5] http://xenbits.xen.org/gitweb/?p=people/larsk/code-of-conduct.git;a=shortlog;h=refs/heads/CoC-v1
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
Lars Kurth (2):
Import v1.4 of Contributor Covenant CoC
Xen Project Code of Conduct
--
2.13.0
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2019-09-04 18:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 18:12 Lars Kurth [this message]
2019-09-04 18:12 ` [Xen-devel] [PATCH] Import v1.4 of Contributor Covenant CoC Lars Kurth
2019-09-04 18:12 ` [Xen-devel] [PATCH] Xen Project Code of Conduct Lars Kurth
2019-09-06 15:10 ` Roger Pau Monné
2019-09-06 15:36 ` Lars Kurth
2019-09-04 18:20 ` [Xen-devel] [PATCH 0/2] Code of Conduct (based on Contributor Covenant v1.4) Lars Kurth
2019-09-06 15:09 ` Roger Pau Monné
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1567620587.git.lars.kurth@citrix.com \
--to=lars.kurth@citrix.com \
--cc=committers@xenproject.org \
--cc=minios-devel@lists.xenproject.org \
--cc=mirageos-devel@lists.xenproject.org \
--cc=win-pv-devel@lists.xenproject.org \
--cc=xen-api@lists.xenproject.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.