qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Thomas Huth" <thuth@redhat.com>,
	qemu-devel@nongnu.org, "Alexander Graf" <agraf@csgraf.de>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Andreas Färber" <afaerber@suse.de>
Subject: Re: [PATCH v2] docs: Add a QEMU Code of Conduct and Conflict Resolution Policy document
Date: Tue, 30 Mar 2021 14:02:09 +0100	[thread overview]
Message-ID: <YGMhUTUXJBM3BcW5@redhat.com> (raw)
In-Reply-To: <c8cc80d5-51f8-9c35-ad98-1eac0d164be6@redhat.com>

On Tue, Mar 30, 2021 at 12:53:04PM +0200, Paolo Bonzini wrote:
> On 30/03/21 11:08, Thomas Huth wrote:
> >   I've picked the Django Code of Conduct as a base, since it sounds rather
> >   friendly and still welcoming to me, but I'm open for other suggestions, too
> >   (but we should maybe pick one where the conflict resolution policy is
> >   separated from the CoC itself so that it can be better taylored to the
> >   requirements of the QEMU project)
> 
> It turns out that the Django CoC is ultimately based on the Fedora CoC,
> so I tried using https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> as an inspiration for what can be cut. Here is the outcome:
> 
> -----
> The QEMU community is made up of a mixture of professionals and
> volunteers from all over the world. Diversity is one of our strengths,
> but it can also lead to communication issues and unhappiness.
> To that end, we have a few ground rules that we ask people to adhere to.
> 
> * Be welcoming. We are committed to making participation in this project
>   a harassment-free experience for everyone, regardless of level of
>   experience, gender, gender identity and expression, sexual orientation,
>   disability, personal appearance, body size, race, ethnicity, age, religion,
>   or nationality.
> 
> * Be respectful. Not all of us will agree all the time.  Disagreements, both
>   social and technical, happen all the time and the QEMU community is no
>   exception. When we disagree, we try to understand why.  It is important that
>   we resolve disagreements and differing views constructively.  Members of the
>   QEMU community should be respectful when dealing with other contributors as
>   well as with people outside the QEMU community and with users of QEMU.
> 
> Harassment and other exclusionary behavior are not acceptable. A community
> where people feel uncomfortable or threatened is neither welcoming nor
> respectful.  Examples of unacceptable behavior by participants include:
> 
> * The use of sexualized language or imagery
> 
> * Personal attacks
> 
> * Trolling or insulting/derogatory comments
> 
> * Public or private harassment
> 
> * Publishing other's private information, such as physical or electronic
> addresses, without explicit permission
> 
> This isn't an exhaustive list of things that you can't do. Rather, take
> it in the spirit in which it's intended—a guide to make it easier to
> be excellent to each other.
> 
> This code of conduct applies to all spaces managed by the QEMU project.
> This includes IRC, the mailing lists, the issue tracker, community
> events, and any other forums created by the project team which the
> community uses for communication. This code of conduct also applies
> outside these spaces, when an individual acts as a representative or a
> member of the project or its community.

I really don't like this last sentance. The qualifier

  ', when an individual acts as a representative or member...'

is opening up a clear loophole to escape consequences under the
QEMU CoC.

Consider someone is kicked out from another project for violation
of that project's CoC, that would also be considered a violation
under QEMU's CoC. This qualifier is explicitly stating that the CoC
violation in the other project has no bearing on whether that
person can now start participating in QEMU. I think that's a bad
mixed message we're sending there. It is especially poor if the
victim from the other project is also a QEMU contributor.

The wording Thomas' draft has

  In addition, violations of this code outside these spaces may
  affect a person's ability to participate within them.

doesn't require QEMU to take action. It just set a statement
of intent that gives QEMU the freedom to evaluate whether it is
reasonable to take action to protect its contributors, should a
contributor wish to raise an issue that occurred outside QEMU.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2021-03-30 13:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-30  9:08 [PATCH v2] docs: Add a QEMU Code of Conduct and Conflict Resolution Policy document Thomas Huth
2021-03-30 10:53 ` Paolo Bonzini
2021-03-30 13:02   ` Daniel P. Berrangé [this message]
2021-03-30 14:07     ` Paolo Bonzini
2021-03-31  8:33       ` Daniel P. Berrangé
2021-03-31  5:40   ` Thomas Huth
2021-03-31  6:50     ` Paolo Bonzini

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=YGMhUTUXJBM3BcW5@redhat.com \
    --to=berrange@redhat.com \
    --cc=afaerber@suse.de \
    --cc=agraf@csgraf.de \
    --cc=alex.bennee@linaro.org \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=thuth@redhat.com \
    /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).