From: John Snow <jsnow@redhat.com>
To: quintela@redhat.com, kvm-devel <kvm@vger.kernel.org>,
qemu-devel@nongnu.org
Subject: Re: KVM call for agenda for 2020-10-06
Date: Fri, 2 Oct 2020 11:16:38 -0400 [thread overview]
Message-ID: <c64f5686-b656-226d-8c4c-95965dcc574a@redhat.com> (raw)
In-Reply-To: <874kndm1t3.fsf@secure.mitica>
On 10/2/20 5:09 AM, Juan Quintela wrote:
>
>
> Hi
>
> Please, send any topic that you are interested in covering.
>
> At the end of Monday I will send an email with the agenda or the
> cancellation of the call, so hurry up.
>
>
> For this call, we have agenda!!
>
> John Snow wants to talk about his new (and excting) developments with
> x-configure. Stay tuned.
>
I'm working on an email to qemu-devel now detailing some of our work
trying to make good on a renewed effort for better APIs for QEMU.
In short, I'd like to discuss a roadmap for converting our CLI to
something QAPI-based, and discuss ways to coordinate and distribute this
work to interested maintainers and developers.
Look out for it!
--js
>
> After discussions on the QEMU Summit, we are going to have always open a
> KVM call where you can add topics.
>
> Call details:
>
> By popular demand, a google calendar public entry with it
>
> https://www.google.com/calendar/embed?src=dG9iMXRqcXAzN3Y4ZXZwNzRoMHE4a3BqcXNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ
>
> (Let me know if you have any problems with the calendar entry. I just
> gave up about getting right at the same time CEST, CET, EDT and DST).
>
> If you need phone number details, contact me privately
>
> Thanks, Juan.
>
next prev parent reply other threads:[~2020-10-02 15:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 9:09 KVM call for agenda for 2020-10-06 Juan Quintela
2020-10-02 15:16 ` John Snow [this message]
2020-10-05 14:46 ` Stefan Hajnoczi
2020-10-06 18:21 ` Stefan Hajnoczi
2020-10-07 17:50 ` Paolo Bonzini
2020-10-07 18:04 ` Daniel P. Berrangé
2020-10-08 11:25 ` Markus Armbruster
2020-10-08 14:15 ` Paolo Bonzini
2020-10-08 8:03 ` Kevin Wolf
2020-10-09 16:45 ` Eduardo Habkost
2020-10-10 4:41 ` Markus Armbruster
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=c64f5686-b656-226d-8c4c-95965dcc574a@redhat.com \
--to=jsnow@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).