From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A2096C433DB for ; Mon, 29 Mar 2021 21:01:14 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 1942A6196C for ; Mon, 29 Mar 2021 21:01:13 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 1942A6196C Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:38542 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lQz0a-00077T-RE for qemu-devel@archiver.kernel.org; Mon, 29 Mar 2021 17:01:12 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:58532) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lQyzE-0006SB-FL for qemu-devel@nongnu.org; Mon, 29 Mar 2021 16:59:48 -0400 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:45292) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lQyzB-0007hP-ES for qemu-devel@nongnu.org; Mon, 29 Mar 2021 16:59:47 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1617051584; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Q9blz8Jwtd1vfMzOhoXPThX2GtuMAydwLE3qb8RkfmY=; b=O2W3BCXQkQSbZnguZWpH45lnWp3bUgOf3pUwJLzPtt9ioET+4ji/LW0RvWBH4LNDLHLD7e hrte4HAIBSP6d4hDl7+oNoBHnLlEDYG2bnvHULMRZEfCRvNH85kzpHeE4LxT8hyU4CJawZ kM4truWZvkXa+kEcgL2jqgKQx0ShMRY= Received: from mail-pl1-f199.google.com (mail-pl1-f199.google.com [209.85.214.199]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-165-ZcqmQEIeNrmbUm2Lo0lBzw-1; Mon, 29 Mar 2021 16:59:36 -0400 X-MC-Unique: ZcqmQEIeNrmbUm2Lo0lBzw-1 Received: by mail-pl1-f199.google.com with SMTP id p12so4658132plw.0 for ; Mon, 29 Mar 2021 13:59:36 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Q9blz8Jwtd1vfMzOhoXPThX2GtuMAydwLE3qb8RkfmY=; b=TDMhzXkGqxdEiwS29ONK6erBYSQuzV7EF9/kScT0QENKei7S+MTN3+gqC/9t8DK+2I 1IB4wgd/pleCayZWo+BN39MMX7hSLjb7cc7J2Y09nT3XyI/knlPrIrS1AgFSkqrayo2e 03dWh1mJs7EklKL0OktYUwLuG3Iq1KVyPmcVh/JB1GWZGsMhSKn15TBCJ+08OD4lO5Nh vetZyZQFyAJ9D9mQynVZalgx/8Qz2IwqGzENMvCb8Zl8GmTYWrQ3jciil0Z1K8lJoBPZ p6/rzwCwQUXXUG92Aup2QSOayR/glmlDqBdAoRC+L+yTcP7xwj8x5gcP1QhOkOdoymFo JDaA== X-Gm-Message-State: AOAM533oSN11YQGcVoP3CSAnIbhjekw4iaqTM1mZOi21PCJMHBC/sVt3 oMJXWVlLpgYwS7DaYhBdP6Bd5n+Yi8LF3IBFk2QFS6SAKRlAaOVczEQld1lsyhZokCrnvL6+Kkz HfDltBXRwDLF8jiZ/cr3a2EIf3opIaKE= X-Received: by 2002:aa7:95b5:0:b029:1ef:272f:920c with SMTP id a21-20020aa795b50000b02901ef272f920cmr27610846pfk.21.1617051575612; Mon, 29 Mar 2021 13:59:35 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz7+4Yd3Bza4PgP2OuyTIeVKBzQBdNvOhR1VVF2KwoBAh0F1jWeZtG6J+UV67UjhG9Pr9dQWUVvVBAk0rZ82J8= X-Received: by 2002:aa7:95b5:0:b029:1ef:272f:920c with SMTP id a21-20020aa795b50000b02901ef272f920cmr27610820pfk.21.1617051575290; Mon, 29 Mar 2021 13:59:35 -0700 (PDT) MIME-Version: 1.0 References: <20210329180140.2761383-1-thuth@redhat.com> In-Reply-To: From: Paolo Bonzini Date: Mon, 29 Mar 2021 22:59:23 +0200 Message-ID: Subject: Re: [PATCH] docs: Add a QEMU Code of Conduct and Conflict Resolution Policy document To: =?UTF-8?Q?Daniel_P=2E_Berrang=C3=A9?= Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=pbonzini@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: multipart/alternative; boundary="000000000000baa62f05beb3286c" Received-SPF: pass client-ip=216.205.24.124; envelope-from=pbonzini@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Peter Maydell , Thomas Huth , qemu-devel , Alexander Graf , Stefan Hajnoczi , =?UTF-8?B?QWxleCBCZW5uw6ll?= , =?UTF-8?Q?Andreas_F=C3=A4rber?= Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" --000000000000baa62f05beb3286c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Il lun 29 mar 2021, 20:33 Daniel P. Berrang=C3=A9 ha scritto: > The obvious alternative is to import the contributor covenant > > https://www.contributor-covenant.org/ The Contributor Covenant 1.x and 2.x are very different in that 2.x also includes conflict resolution. Unlike the code of conduct, the consequences of bad behavior are hard to generalize across multiple projects, so I would prefer anyway the 1.x version. The differences with the Django CoC aren't substantial. However this does mean being more careful about the language in the "custom" documents such as the conflict resolution policy. The second, it isn't a static document. It is being evolved over > time with new versions issued as understanding of problematic > situations evolves. We can choose to periodically update to stay > current with the broadly accepted norms. > This however has the same issues as the "or later" clause of the GPL (see the above example of 1.x vs 2.x for the Contributor Covenant). I don't think upgrade of the CoC should be automatic since there are no "compatibility" issues. Overall I think it is a good idea to introduce an explicit CoC > doc to QEMU, and indeed any community project, so thanks for > bringing this up again. > Agreed! > > > +If you are experiencing conflict, you should first address the perceiv= ed > > +conflict directly with other involved parties, preferably through a > > +real-time medium such as IRC. If this fails, I agree with Daniel that this part should only be advisory. For example: If you are experiencing conflict, please consider first addressing the perceived conflict directly with other involved parties, preferably through a real-time medium such as IRC. If this fails or if you do not feel comfortable proceeding this way,... Also this document doesn't mention anything about ensuring the > confidentiality/privacy for any complaints reported, which I > think is important to state explicitly. > Agreed, and also the part about keeping a record should be removed from the consequences part because it's a privacy regulation minefield. Thanks, Paolo > > 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 :| > > --000000000000baa62f05beb3286c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


Il lun 29 mar 2021, 20:33 Daniel P. Berrang=C3=A9 <= berrange@redhat.com> ha scrit= to:
The obvious alternative is to i= mport the contributor covenant

=C2=A0 https://www.contributor-covenant.org/

The Cont= ributor Covenant 1.x and 2.x are very different in that 2.x also includes c= onflict resolution. Unlike the code of conduct, the consequences of bad beh= avior are hard to generalize across multiple projects, so I would prefer an= yway the 1.x version. The differences with the Django CoC aren't substa= ntial.

However this does= mean being more careful about the language in the "custom" docum= ents such as the conflict resolution policy.


The second, it isn't a static document.= It is being evolved over
time with new versions issued as understanding of problematic
situations evolves. We can choose to periodically update to stay
current with the broadly accepted norms.

This however has the same issues as= the "or later" clause of the GPL (see the above example of 1.x v= s 2.x for the Contributor Covenant). I don't think upgrade of the CoC s= hould be automatic since there are no "compatibility" issues.

=
Overall I think it is a good idea to introdu= ce an explicit CoC
doc to QEMU, and indeed any community project, so thanks for
bringing this up again.

<= /div>
Agreed!

> +If you are experiencing conflict, you should first address the percei= ved
> +conflict directly with other involved parties, preferably through a > +real-time medium such as IRC. If this fails,
=

I agree with Daniel that this= part should only be advisory. For example:

If you are experiencing conflict, please consider first= addressing the perceived=C2=A0 conflict=C2=A0directly with other involved parties, preferably through a real-time medium such as IRC. If th= is fails or if you do not feel comfortable proceeding this way,...

Also this document doesn't mention anything about ensuring the
confidentiality/privacy for any complaints reported, which I
think is important to state explicitly.

Agreed, and also the part about keep= ing a record should be removed from the consequences part because it's = a privacy regulation minefield.

Thanks,

Paolo<= /div>



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

--000000000000baa62f05beb3286c--