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 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id F0A34C433EF for ; Thu, 30 Sep 2021 00:51:07 +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 529276124D for ; Thu, 30 Sep 2021 00:51:07 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 529276124D Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=nongnu.org Received: from localhost ([::1]:35746 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mVkHy-0000fP-Di for qemu-devel@archiver.kernel.org; Wed, 29 Sep 2021 20:51:06 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:37132) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mVkGN-0008Ji-QR for qemu-devel@nongnu.org; Wed, 29 Sep 2021 20:49:27 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:42747) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mVkGK-0000qn-TX for qemu-devel@nongnu.org; Wed, 29 Sep 2021 20:49:27 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1632962963; 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=KeQrvwHusvizvOOReC83kIQjeXdbT+p0jJ4MpFWYJMM=; b=VOT7v2nqoL1l/28IdBeLnuYDGKCshlhacq/sfA/y97M00cBLPrxVjWlQFD/xHCLBQPYMkm fxhWScA+Hk+V0Q+oldyyq1eYejylLcXoKxQLcIqYRpGpQTx/ykbUvDmSIb5XTY/mUTfYca 8GSIRmMOHiZlzGQNXRYUgko/+I89LPo= Received: from mail-vs1-f72.google.com (mail-vs1-f72.google.com [209.85.217.72]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-472-_YBjmxwtOwWk9LOzUpcHhg-1; Wed, 29 Sep 2021 20:49:21 -0400 X-MC-Unique: _YBjmxwtOwWk9LOzUpcHhg-1 Received: by mail-vs1-f72.google.com with SMTP id v12-20020a672f0c000000b002d7c2f1d9ffso918654vsv.14 for ; Wed, 29 Sep 2021 17:49:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=KeQrvwHusvizvOOReC83kIQjeXdbT+p0jJ4MpFWYJMM=; b=O4419aWvje45BFwOSJFR96xpgeIBJ55upUVlJTizWwK5QJ9VEbTbk9GzE2AGwDMjFV yUjTeVPxnLiGIIwt2jh2e+8OLLfFmqc4cKRlm0zqGjNDVk75YwbMq8DUn9a/2h+ac7Mv xkCxr9UMvwbHqpQpNVrXJqRLp0kpoypYq7dKqXC8620dD8Xn3JnkNsyasgUZxv2rT9Tr coBLmnt2n8ZfUYBQL/cbMpqjffDIDoWBgcKYNsrnBhizovH3pPn6N+MW9IX9YQ0Xp0lw sUqAtAzH+Tmf297uZHOmpzRcA8Op6gI8U72Ob3zGFr0wPuUx92V6gYxzhNqalif19tgc vC2Q== X-Gm-Message-State: AOAM53298v6L9VXWxIINcc2jC0vhlOpyWX8XQwc23ID1lcGXl6/LRNBr +3qDvS8jro//0pdHphcCHRzLS6NRIlqKQoxMyjNqKr1CxgESlMUsr1lz0EHmeK7s3VaKbTsJXsB nJ91pW8pSe5s0RtNdqkG1mlDgsgTh7oM= X-Received: by 2002:ab0:3c89:: with SMTP id a9mr3503591uax.32.1632962961077; Wed, 29 Sep 2021 17:49:21 -0700 (PDT) X-Google-Smtp-Source: ABdhPJziNwWSn4b3Q277BlUyQFkHeUfxpFiR+3mxng8bse0UOemKEsOl4Jq6nqQPBJCAoekJT9wdT3gywXWfGiNVRlE= X-Received: by 2002:ab0:3c89:: with SMTP id a9mr3503579uax.32.1632962960932; Wed, 29 Sep 2021 17:49:20 -0700 (PDT) MIME-Version: 1.0 References: <87ee97y3q5.fsf@dusky.pond.sub.org> In-Reply-To: <87ee97y3q5.fsf@dusky.pond.sub.org> From: John Snow Date: Wed, 29 Sep 2021 20:49:10 -0400 Message-ID: Subject: Re: QAPI sync meeting To: Markus Armbruster Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=jsnow@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: multipart/alternative; boundary="00000000000037d24b05cd2bd1ac" Received-SPF: pass client-ip=170.10.133.124; envelope-from=jsnow@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_H2=-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: Kevin Wolf , Damien Hedde , =?UTF-8?Q?Daniel_P=2E_Berrang=C3=A9?= , qemu-devel , Paolo Bonzini , =?UTF-8?B?TWFyYy1BbmRyw6kgTHVyZWF1?= Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" --00000000000037d24b05cd2bd1ac Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Sep 29, 2021 at 8:18 AM Markus Armbruster wrote= : > John Snow writes: > > > On Tue, Sep 28, 2021 at 9:53 AM Daniel P. Berrang=C3=A9 > > wrote: > > > >> On Mon, Sep 27, 2021 at 12:55:34PM -0400, John Snow wrote: > > [...] > > >> > - Any weekday after 13:00 UTC. Wednesdays, Thursdays and Fridays wor= k > >> > particularly well for me at the moment. > >> > - bluejeans and google meeting both work well for me. Open to > alternatives. > > Congratulations, you've just crowned yourself meeting organizer! Pick a > date, time, and place, then herd the cats there. > > ACK. Will send out a proper invite. > I can't do next Friday. I think we should aim for next week, to give us > time to coordinate and to prepare. > > ACK > >> Are you suggesting a 1-off meeting or a regular meeting, or an adhoc > >> set of meetings ? > >> > >> > > I'm proposing a one-off here just for some initial discussion and > planning. > > (We didn't have a QAPI BoF at KVM Forum and I'd like something similar > > now.) I don't expect we'll really "finish" plotting out a roadmap in a > > single 60 minute meeting, but it will probably give us good, targeted > > discussions on the ML to follow. If more meetings are desired to discus= s > > specific topics, I'm not against scheduling them as-needed. > > Let's have one now, and then more as needed. > > Jumping into the meeting unprepared, then spending half of the alloted > time listening to people explaining where they want to take QAPI seems > like a bad use of our time. Better: write it up and post it, so we can > all read before we meet. Do not reply, except perhaps to ask for > clarification. Discuss in the meeting. > > I can see such posts from Marc-Andre, Kevin, and Daniel. Some of them > could use a bit more detail, perhaps. > > Thoughts? > > Works for me. I can send out a short summary beforehand, too, but I will want to aggregate them in bullet-list digestible form for the meeting minutes. I am suggesting a call to begin with so that I can set aside a time specifically to discuss items with all interested parties ... at a time when I'm awake. O:-) > > (I personally don't really mind semi-regular sync-up meetings, like onc= e > > every other month or something to that effect -- it keeps me motivated > and > > on track. I suspect that Markus does not quite feel the same way about > 'em, > > so I'm just trying to not sign him up for stuff.) > > More regular meetings sit fairly low on my personal wish list. > > O:-) O:-) O:-) --00000000000037d24b05cd2bd1ac Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Wed, Sep 29, 2021 at 8:18 AM Markus Armbruster <armbru@redhat.com> wrote:
John Snow <jsnow@redhat.com> writes:

> On Tue, Sep 28, 2021 at 9:53 AM Daniel P. Berrang=C3=A9 <berrange@redhat.com><= br> > wrote:
>
>> On Mon, Sep 27, 2021 at 12:55:34PM -0400, John Snow wrote:

[...]

>> > - Any weekday after 13:00 UTC. Wednesdays, Thursdays and Frid= ays work
>> > particularly well for me at the moment.
>> > - bluejeans and google meeting both work well for me. Open to= alternatives.

Congratulations, you've just crowned yourself meeting organizer!=C2=A0 = Pick a
date, time, and place, then herd the cats there.


ACK. Will send out a proper invite.
=C2=A0
I can't do next Friday.=C2=A0 I think we should aim for next week, to g= ive us
time to coordinate and to prepare.


ACK
=C2=A0
>> Are you suggesting a 1-off meeting or a regular meeting, or an adh= oc
>> set of meetings ?
>>
>>
> I'm proposing a one-off here just for some initial discussion and = planning.
> (We didn't have a QAPI BoF at KVM Forum and I'd like something= similar
> now.) I don't expect we'll really "finish" plotting = out a roadmap in a
> single 60 minute meeting, but it will probably give us good, targeted<= br> > discussions on the ML to follow. If more meetings are desired to discu= ss
> specific topics, I'm not against scheduling them as-needed.

Let's have one now, and then more as needed.

Jumping into the meeting unprepared, then spending half of the alloted
time listening to people explaining where they want to take QAPI seems
like a bad use of our time.=C2=A0 Better: write it up and post it, so we ca= n
all read before we meet.=C2=A0 Do not reply, except perhaps to ask for
clarification.=C2=A0 Discuss in the meeting.

I can see such posts from Marc-Andre, Kevin, and Daniel.=C2=A0 Some of them=
could use a bit more detail, perhaps.

Thoughts?


Works for me. I can send out a short s= ummary beforehand, too, but I will want to aggregate them in bullet-list di= gestible form for the meeting minutes. I am suggesting a call to begin with= so that I can set aside a time specifically to discuss items with all inte= rested parties ... at a time when I'm awake. O:-)
=C2=A0<= /div>
> (I personally don't really mind semi-regular sync-up meetings, lik= e once
> every other month or something to that effect -- it keeps me motivated= and
> on track. I suspect that Markus does not quite feel the same way about= 'em,
> so I'm just trying to not sign him up for stuff.)

More regular meetings sit fairly low on my personal wish list.


O:-) O:-) O:-)
--00000000000037d24b05cd2bd1ac--