From: Lars Kurth <lars.kurth@citrix.com>
To: George Dunlap <George.Dunlap@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>,
"minios-devel@lists.xenproject.org"
<minios-devel@lists.xenproject.org>,
"mirageos-devel@lists.xenproject.org"
<mirageos-devel@lists.xenproject.org>,
"win-pv-devel@lists.xenproject.org"
<win-pv-devel@lists.xenproject.org>
Cc: "committers@xenproject.org" <committers@xenproject.org>
Subject: Re: [Xen-devel] [RFC] Code of Conduct
Date: Mon, 12 Aug 2019 14:27:07 +0000 [thread overview]
Message-ID: <BAD85CEA-27E1-48B2-A433-0D6BE2182DCC@citrix.com> (raw)
In-Reply-To: <32e7f4cd-78e9-dd43-a677-958d838f4f65@citrix.com>
Hi George,
On 12/08/2019, 12:35, "George Dunlap" <george.dunlap@citrix.com> wrote:
On 8/9/19 6:48 PM, Lars Kurth wrote:
> Hi all,
>
> Following the discussion we had at the Developer Summit (see https://wiki.xenproject.org/wiki/Design_Sessions_2019#Community_Issues_.2F_Improvements_-_Communication.2C_Code_of_Conduct.2C_etc. for notes) I put together a draft for the Code of Conduct which can be found here as well as inlined below
> https://docs.google.com/document/d/1NnWdU_VnC1N_ZzxQG6jU9fnY2GPVCcfPJT5KY61WXJM/edit?usp=sharing
>
> It is based on the LF Events CoC as we agreed on (the diff is attached). I took the scope and enforcement sections from https://www.contributor-covenant.org/version/1/4/code-of-conduct.html and simplified it rather than inventing something new.
>
> You can provide feedback by commenting on the google doc or by replying to the in-lined version below.
> I expect it will some more discussion to get consensus.
>
> Note that I am not very attached to some of the terms, such as "Xen Project CoC Team" and in some cases "participant" should probably be replaced by community
> members.
>
> But I felt, we should have something more concrete to discuss compared to previous discussions.
>
> A Code of Conduct is a project wide policy change: thus, all subprojects lists are CC'ed
Thanks for doing this Lars. I think this is a step forward.
I have a couple of comments, but only on the wording.
>
> Regards
> Lars
>
> Here is the actual text
> ---
> # Our Pledge
> In the interest of fostering an open and welcoming environment, we as community
> members of the Xen Project pledge to making participation in our project and our
> community a harassment-free experience for everyone.
To me "pledge" means "promise"; and I don't think we can promise anyone
that they'll have a harassment-free experience. I might say, "we ...
are committed to making participation ... a harassment-free experience";
or "we ... pledge to maintain a harassment-free experience" or something
like that.
This comes directly from the Contributor Covenant v1.4
But I also like "we ... are committed to making participation ... a harassment-free
experience" better then pledge.
> # Unacceptable Behavior
> Harassment will not be tolerated in the Xen Project Community in any form,
> including but not limited to harassment based on gender, gender identity and
> expression, sexual orientation, disability, physical appearance, body size, race,
> age, religion, ethnicity, nationality, level of experience, education, or
> socio-economic status or any other status protected by laws in jurisdictions in
> which community members are based.
> Harassment includes the use of abusive,
> offensive or degrading language, intimidation, stalking, harassing photography
> or recording, inappropriate physical contact, sexual imagery and unwelcome
> sexual advances, requests for sexual favors, publishing others' private
> information such as a physical or electronic address without explicit permission
> and other conduct which could reasonably be considered inappropriate in a
> professional setting.
Should we put "such as physical or electronic address[es]" in parentheses?
Fine with me
Also, I'm in favor of the Oxford Comma (so a comma after 'permission').
I might say "or any other conduct"; for some reason it sounds more
natural to me.
Either works
> Any report of harassment within the Xen Project community will be addressed
> swiftly. Participants asked to stop any harassing behavior are expected to
> comply immediately. Anyone who witnesses or is subjected to unacceptable
> behavior should notify the Xen Project’s CoC team via conduct@xenproject.org.
>
> # Consequences of Unacceptable Behavior
> If a participant engages in harassing behavior, the Xen Project’s CoC team may
> take any action it deems appropriate, ranging from issuance of a warning to the
> offending individual to expulsion from the Xen Project community.
I realize by saying "range" you probably meant to include this, but I
think spelling out "temporary suspension" as a possible consequence. E.g.:
"If a participant engages in harassing behavior, the Xen Project's CoC
team will investigate and take an action it deems appropriate against
the offending individual. This may include issuing a warning, temporary
suspension from mailing lists or commit rights, or expulsion from the
XenProject community."
That looks good
That's all I had; thanks again, Lars.
I am wondering how you feel about the usage of "participant". There are
a few instances left in the text.
"Any report of harassment within the Xen Project community will be addressed
swiftly. Participants asked to stop ..."
# Consequences of Unacceptable Behavior
If a participant engages in harassing behaviour
I would probably also want to replace this with "Community member asked ..." and "If a community member engages in ..."
Regards
Lars
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-08-12 14:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AB34D39A-A120-440E-9309-3950E7A465A5@citrix.com-0>
2019-08-12 11:35 ` [Xen-devel] [RFC] Code of Conduct George Dunlap
2019-08-12 14:27 ` Lars Kurth [this message]
2019-08-12 14:35 ` George Dunlap
2019-08-13 14:30 ` Lars Kurth
2019-08-09 17:48 Lars Kurth
2019-08-15 17:23 ` Rich Persaud
2019-08-15 18:01 ` Lars Kurth
2019-08-15 18:27 ` Rich Persaud
2019-08-15 18:46 ` [Xen-devel] [win-pv-devel] " Lars Kurth
2019-08-15 19:08 ` Rich Persaud
2019-08-15 19:25 ` [Xen-devel] " Lars Kurth
2019-08-16 11:19 ` George Dunlap
2019-08-16 15:49 ` Rich Persaud
2019-08-16 16:20 ` Lars Kurth
2019-08-26 18:03 ` Lars Kurth
2019-08-27 17:33 ` Ian Jackson
2019-08-27 20:47 ` Lars Kurth
2019-08-28 0:53 ` Stefano Stabellini
2019-08-28 2:02 ` Lars Kurth
[not found] ` <D8EFC0B6-0FFC-4288-86EC-FD0A0BB8C3BF@citrix.com-0>
2019-09-02 15:48 ` Ian Jackson
2019-09-02 18:10 ` Lars Kurth
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=BAD85CEA-27E1-48B2-A433-0D6BE2182DCC@citrix.com \
--to=lars.kurth@citrix.com \
--cc=George.Dunlap@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-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).