From: Markus Armbruster <armbru@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: QAPI sync meeting
Date: Wed, 29 Sep 2021 14:18:42 +0200 [thread overview]
Message-ID: <87ee97y3q5.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <CAFn=p-ZG6SAVDz-cOtviekvMvibw+ukhYmSOqH7UTrcH-9fCNA@mail.gmail.com> (John Snow's message of "Tue, 28 Sep 2021 13:43:26 -0400")
John Snow <jsnow@redhat.com> writes:
> On Tue, Sep 28, 2021 at 9:53 AM Daniel P. Berrangé <berrange@redhat.com>
> wrote:
>
>> On Mon, Sep 27, 2021 at 12:55:34PM -0400, John Snow wrote:
[...]
>> > - Any weekday after 13:00 UTC. Wednesdays, Thursdays and Fridays 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! Pick a
date, time, and place, then herd the cats there.
I can't do next Friday. I think we should aim for next week, to give us
time to coordinate and to prepare.
>> 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 discuss
> 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?
> (I personally don't really mind semi-regular sync-up meetings, like 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.
next prev parent reply other threads:[~2021-09-29 12:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 16:55 QAPI sync meeting John Snow
2021-09-28 11:38 ` Marc-André Lureau
2021-09-28 13:14 ` Kevin Wolf
2021-09-28 13:53 ` Daniel P. Berrangé
2021-09-28 17:43 ` John Snow
2021-09-29 12:18 ` Markus Armbruster [this message]
2021-09-30 0:49 ` John Snow
2021-10-07 10:01 ` Kevin Wolf
2021-10-07 10:23 ` Paolo Bonzini
2021-10-07 12:53 ` Kevin Wolf
2021-10-07 13:02 ` Daniel P. Berrangé
2021-10-08 10:06 ` Markus Armbruster
2021-10-08 17:07 ` Paolo Bonzini
2021-10-07 12:43 ` John Snow
2021-09-28 15:19 ` Paolo Bonzini
2021-09-29 13:42 ` Damien Hedde
2021-09-30 0:31 ` John Snow
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=87ee97y3q5.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--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).