qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: QEMU Summit Minutes 2023
Date: Thu, 17 Aug 2023 08:13:05 +0200	[thread overview]
Message-ID: <d363975a-e2e0-03b0-b75b-66881269160c@redhat.com> (raw)
In-Reply-To: <CAFEAcA_rziBuSwgJ9cg9m1PS5pNG58eyim+_P9hMu5nF7G70XA@mail.gmail.com>

On 13/07/2023 15.21, Peter Maydell wrote:
> QEMU Summit Minutes 2023
> ========================
...
> Topic 3: Should we split responsibility for managing CoC reports?
> =================================================================
> 
> The QEMU project happily does not have to deal with many Code of
> Conduct (CoC) reports, but we could do a better job with managing the
> ones we do get.  At the moment CoC reports go to the QEMU Leadership
> Committee; Paolo proposed that it would be better to decouple CoC
> handling to a separate team: although the CoC itself seems good,
> asking the Leadership Committee to deal with the reports has not been
> working so well.  The model for this is that Linux also initially had
> its tech advisory board be the contact for CoC reports before
> switching to a dedicated team for them.
> 
> There was general consensus that we should try the separate-team
> approach. We plan to ask on the mailing list for volunteers who would
> be interested in helping out with this.

So who is going to drive this now? I haven't seen any mail on the mailing 
list with that question yet...

  Thomas




  reply	other threads:[~2023-08-17  6:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-13 13:21 QEMU Summit Minutes 2023 Peter Maydell
2023-08-17  6:13 ` Thomas Huth [this message]
2023-11-21 17:11 ` Alex Bennée
2023-11-28 17:54   ` Cédric Le Goater
2023-11-28 18:05     ` Peter Maydell
2023-11-28 18:09       ` Daniel P. Berrangé
2023-11-28 18:06     ` Daniel P. Berrangé
2023-11-29 14:21       ` Philippe Mathieu-Daudé
2023-11-29 15:45         ` Warner Losh
2023-11-29 15:47         ` Stefan Hajnoczi
2023-11-29 15:53           ` Stefan Hajnoczi
2023-11-29 16:46             ` Daniel P. Berrangé
2023-11-29 16:49               ` Stefan Hajnoczi
2023-11-29 16:57             ` Alex Bennée
2023-11-29 18:24               ` Stefan Hajnoczi
2023-11-29 15:50       ` Warner Losh
2023-11-29 16:49         ` Daniel P. Berrangé
2023-11-29 19:41           ` Peter Maydell

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=d363975a-e2e0-03b0-b75b-66881269160c@redhat.com \
    --to=thuth@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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).