xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Lars Kurth <lars.kurth@citrix.com>
To: George Dunlap <George.Dunlap@citrix.com>,
	Lars Kurth <lars.kurth@xenproject.org>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "minios-devel@lists.xenproject.org"
	<minios-devel@lists.xenproject.org>,
	"xen-api@lists.xenproject.org" <xen-api@lists.xenproject.org>,
	"win-pv-devel@lists.xenproject.org"
	<win-pv-devel@lists.xenproject.org>,
	"committers@xenproject.org" <committers@xenproject.org>,
	"mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] [PATCH v2 1/6] Import v1.4 of Contributor Covenant CoC
Date: Mon, 7 Oct 2019 11:27:47 +0000	[thread overview]
Message-ID: <68450837-24F1-4342-B7EB-3EE46B107791@citrix.com> (raw)
In-Reply-To: <e8fee669-7e83-d68f-e56e-3dda4a0e0611@citrix.com>



On 07/10/2019, 12:06, "George Dunlap" <george.dunlap@citrix.com> wrote:

    On 9/26/19 8:39 PM, Lars Kurth wrote:
    > From: Lars Kurth <lars.kurth@citrix.com>
    > 
    > Signed-off-by: Lars Kurth <lars.kurth@citrix.com>
    > ---
    > 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 | 76 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
    >  1 file changed, 76 insertions(+)
    >  create mode 100644 code-of-conduct.md
    > 
    > diff --git a/code-of-conduct.md b/code-of-conduct.md
    > new file mode 100644
    > index 0000000..81b217c
    > --- /dev/null
    > +++ b/code-of-conduct.md
    > @@ -0,0 +1,76 @@
    > +# Contributor Covenant Code of Conduct
    > +
    > +## Our Pledge
    > +
    > +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.
    
    This is relatively minor, but I don't feel quite comfortable with the
    wording.  "pledge to make it a harassment-free experience" to me implies
    that we pledge that *nobody will ever experience harassment*.  I don't
    think that's something we can deliver, any more than a government can
    promise there will be zero crime.  I think we could promise to
    *maintain* a harassment-free experience, which implies things to a
    restoring harassment-free state after it's been broken.
    
    Everything else looks good.
    
Could you come up with an alternative concrete text proposal? 

My take-away is that you say we should use
* "pledge to strive to make ..." or 
* "pledge to try their best to make ..." or
* "strive to make ..." 
in which case we may also need to change "The Pledge".

On the other hand: the rest of the document does clearly lay out that
what we promise is to deal with incidents in an effective manner.
And by the mere inclusion of mechanism to do this, it is actually clear
that we can't guarantee that *nobody will ever experience harassment*.

I guess it comes down to subtleties of how pledge, promise, strive, ...
differ

Regards
Lars
 

    

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2019-10-07 11:28 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-26 19:39 [Xen-devel] [PATCH v2 0/6] Code of Conduct + Extra Guides and Best Practices Lars Kurth
2019-09-26 19:39 ` [Xen-devel] [PATCH v2 1/6] Import v1.4 of Contributor Covenant CoC Lars Kurth
2019-10-07 11:06   ` George Dunlap
2019-10-07 11:27     ` Lars Kurth [this message]
2019-09-26 19:39 ` [Xen-devel] [PATCH v2 2/6] Xen Project Code of Conduct Lars Kurth
2019-09-26 19:39 ` [Xen-devel] [PATCH v2 3/6] Add Communication Guide Lars Kurth
2019-09-26 19:39 ` [Xen-devel] [PATCH v2 4/6] Add Code Review Guide Lars Kurth
2019-11-28  0:54   ` Stefano Stabellini
2019-11-28 10:09     ` Jan Beulich
2019-11-28 13:06       ` Lars Kurth
2019-11-28 13:37         ` Jan Beulich
2019-11-28 14:02           ` Lars Kurth
2019-11-28 18:20             ` [Xen-devel] [MirageOS-devel] " Rich Persaud
2019-11-29  1:39               ` Lars Kurth
2019-12-05 23:41                 ` Lars Kurth
2019-12-06  9:51                   ` [Xen-devel] " Jan Beulich
2019-12-09 11:02                     ` Lars Kurth
2019-12-09 15:58                       ` Lars Kurth
2019-11-28 18:12       ` Rich Persaud
2019-11-29  1:50         ` Lars Kurth
2019-11-28 18:19       ` Stefano Stabellini
2019-09-26 19:39 ` [Xen-devel] [PATCH v2 5/6] Add guide on Communication Best Practice Lars Kurth
2019-09-27  8:59   ` Jan Beulich
2019-09-27  9:53     ` Lars Kurth
2019-09-27  9:14   ` Jan Beulich
2019-09-27 10:17     ` Lars Kurth
2019-09-27 10:22       ` Lars Kurth
2019-09-27 14:19       ` Jan Beulich
2019-10-07 16:13     ` George Dunlap
2019-10-08  7:29       ` Jan Beulich
2019-11-28  1:06     ` Stefano Stabellini
2019-11-29  0:02       ` Lars Kurth
2019-10-07 15:29   ` George Dunlap
2019-11-28  0:57   ` Stefano Stabellini
2019-11-29  0:00     ` Lars Kurth
2019-09-26 19:39 ` [Xen-devel] [PATCH v2 6/6] Added Resolving Disagreement Lars Kurth
2019-11-28  0:56   ` Stefano Stabellini
2019-11-28 10:18     ` Jan Beulich
2019-11-28 18:50       ` Stefano Stabellini
2019-11-29  2:10         ` Lars Kurth
2019-11-29  1:42     ` Lars Kurth
2019-10-24  7:51 ` [Xen-devel] [PATCH v2 0/6] Code of Conduct + Extra Guides and Best Practices Felipe Huici

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=68450837-24F1-4342-B7EB-3EE46B107791@citrix.com \
    --to=lars.kurth@citrix.com \
    --cc=George.Dunlap@citrix.com \
    --cc=committers@xenproject.org \
    --cc=lars.kurth@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 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).