qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: "Markus Armbruster" <armbru@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: QAPI sync meeting
Date: Mon, 27 Sep 2021 12:55:34 -0400	[thread overview]
Message-ID: <CAFn=p-axq90h+UGa_R2a=LZzXTcjsua3O8xnNvonvFD4ZjwmBQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2018 bytes --]

Hiya,

I'd like to propose that at least the three of us arrange a time to have a
meeting where we discuss our plans and ideas for QAPI going forward,
including rust, python, and golang extensions to the QAPI generator, what
we hope to accomplish with those projects, and so on.

What I am hoping to get out of this for myself is a high-level overview of
people's plans for QAPI and to produce some notes on those plans so that I
can have a reference that we've all acknowledged as roughly accurate to be
able to keep the community's design goals for QAPI in mind as I continue my
own development. Ultimately, I'd like some kind of rough draft of a "QAPI
roadmap".

I know there was a rust meetup during KVM Forum, but I was unable to attend
due to the timing. I'd like to expand the focus a little more broadly to
QAPI in general and discuss our "personal" roadmaps, goals, queued work,
etc so that we can collaboratively formulate a broader vision of our work.

I'm posting to qemu-devel in case anyone else has an interest in this area
and would like to eavesdrop or share opinions, but we should probably come
up with an agenda first. So:

Proposed agenda:

Current projects, wishlists, and goals for QAPI:
- Markus (~10 min)
- Marc-Andre (~10 min) (Rust, dbus, etc?)
- jsnow (~10 min) (Python, golang, etc)

Formulating short-term and long-term roadmaps:
- Open discussion, ~30 min
- Collaboratively produce a summary doc (etherpad?) outlining major work to
be done, separated into near and long terms
- Upload this summary to the QEMU wiki and mail it back out to qemu-devel
- We probably won't exactly finish this bit, but we can resume on the
mailing list afterwards perfectly well.

(Feel free to propose anything different for the meeting, this is just a
jumping off point for discussion.)

Proposed time:

- 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.


Thanks,
--js

[-- Attachment #2: Type: text/html, Size: 2473 bytes --]

             reply	other threads:[~2021-09-27 16:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-27 16:55 John Snow [this message]
2021-09-28 11:38 ` QAPI sync meeting 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
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='CAFn=p-axq90h+UGa_R2a=LZzXTcjsua3O8xnNvonvFD4ZjwmBQ@mail.gmail.com' \
    --to=jsnow@redhat.com \
    --cc=armbru@redhat.com \
    --cc=marcandre.lureau@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).