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: Tue, 13 Aug 2019 14:30:38 +0000 [thread overview]
Message-ID: <3E4BE619-6D45-4A04-9C39-D0B833D62859@citrix.com> (raw)
In-Reply-To: <6afd60db-55d7-9111-ffe0-e53917e5810f@citrix.com>
Perfect: I updated this also in the google doc. I will leave the review open for a week or two (we do have summer holidays after all) and let people comment. I can then send a proper proposal, followed by a vote
Lars
On 12/08/2019, 15:35, "George Dunlap" <george.dunlap@citrix.com> wrote:
On 8/12/19 3:27 PM, Lars Kurth wrote:
> 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 ..."
Seems reasonable to me.
-George
_______________________________________________
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-13 14:31 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
2019-08-12 14:35 ` George Dunlap
2019-08-13 14:30 ` Lars Kurth [this message]
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=3E4BE619-6D45-4A04-9C39-D0B833D62859@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).