All of lore.kernel.org
 help / color / mirror / Atom feed
From: jsnow@redhat.com
To: qemu-devel@nongnu.org, berrange@redhat.com, pbonzini@redhat.com,
	 armbru@redhat.com, damien.hedde@greensocs.com,
	marcandre.lureau@redhat.com,  kwolf@redhat.com
Subject: Invitation: QAPI Sync meeting @ Thu Oct 7, 2021 9am - 10am (EDT) (qemu-devel@nongnu.org)
Date: Mon, 04 Oct 2021 21:01:46 +0000	[thread overview]
Message-ID: <00000000000093852d05cd8d38f6@google.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2475 bytes --]

You have been invited to the following event.

Title: QAPI Sync meeting
Let's discuss our ongoing and future work on the QAPI generator and closely  
related interfaces for QEMU.

Please prepare for the meeting by writing a small overview of your pending  
and future work, and the goals that motivate those works. If you send this  
summary to the mailing list beforehand, we'll have the opportunity to skim  
it prior to the meeting.

I am suggesting we use a public etherpad instance to keep notes during the  
meeting: https://etherpad.wikimedia.org/p/qapi-sync

During this meeting, I'd like to assemble a list of all ongoing QAPI work  
and begin work on crafting a roadmap that helps describe that work.

I don't suspect we'll finish in a single meeting, but it may be a helpful  
primer for follow-up discussions on the ML.
When: Thu Oct 7, 2021 9am – 10am Eastern Time - New York

Joining info: Join with Google Meet
https://meet.google.com/xqi-tiqs-xrz?hs=224

Join by phone
(US) +1 929-249-4854 (PIN: 637379240)

Join using SIP
6779067023105@gmeet.redhat.com (ID: 6779067023105)

More joining options: https://tel.meet/xqi-tiqs-xrz?pin=6779067023105&hs=0

Calendar: qemu-devel@nongnu.org
Who:
     * jsnow@redhat.com - organizer
     * berrange@redhat.com
     * pbonzini@redhat.com
     * armbru@redhat.com
     * damien.hedde@greensocs.com
     * marcandre.lureau@redhat.com
     * kwolf@redhat.com
     * qemu-devel@nongnu.org

Event details:  
https://calendar.google.com/calendar/event?action=VIEW&eid=NzJwYXY4YTlpYjBtNDlrOHFyOWhqaWJnZzcgcWVtdS1kZXZlbEBub25nbnUub3Jn&tok=MTYjanNub3dAcmVkaGF0LmNvbTAxYTNkNTk0NTQyOWNkNDk4YzgxYTY1ZDdhMTc3ODM3NzAyOTg0MzM&ctz=America%2FNew_York&hl=en&es=0

Invitation from Google Calendar: https://calendar.google.com/calendar/

You are receiving this courtesy email at the account qemu-devel@nongnu.org  
because you are an attendee of this event.

To stop receiving future updates for this event, decline this event.  
Alternatively you can sign up for a Google account at  
https://calendar.google.com/calendar/ and control your notification  
settings for your entire calendar.

Forwarding this invitation could allow any recipient to send a response to  
the organizer and be added to the guest list, or invite others regardless  
of their own invitation status, or to modify your RSVP. Learn more at  
https://support.google.com/calendar/answer/37135#forwarding

[-- Attachment #1.2: Type: text/html, Size: 17469 bytes --]

[-- Attachment #1.3: Type: text/calendar, Size: 3245 bytes --]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20211007T130000Z
DTEND:20211007T140000Z
DTSTAMP:20211004T210146Z
ORGANIZER;CN=jsnow@redhat.com:mailto:jsnow@redhat.com
UID:72pav8a9ib0m49k8qr9hjibgg7@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=berrange@redhat.com;X-NUM-GUESTS=0:mailto:berrange@redhat.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=jsnow@redhat.com;X-NUM-GUESTS=0:mailto:jsnow@redhat.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=pbonzini@redhat.com;X-NUM-GUESTS=0:mailto:pbonzini@redhat.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=armbru@redhat.com;X-NUM-GUESTS=0:mailto:armbru@redhat.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=damien.hedde@greensocs.com;X-NUM-GUESTS=0:mailto:damien.hedde@greensocs
 .com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=marcandre.lureau@redhat.com;X-NUM-GUESTS=0:mailto:marcandre.lureau@redh
 at.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=kwolf@redhat.com;X-NUM-GUESTS=0:mailto:kwolf@redhat.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=qemu-devel@nongnu.org;X-NUM-GUESTS=0:mailto:qemu-devel@nongnu.org
X-MICROSOFT-CDO-OWNERAPPTID:-2106639245
CREATED:20211001T001809Z
DESCRIPTION:Let's discuss our ongoing and future work on the QAPI generator
  and closely related interfaces for QEMU.\n\nPlease prepare for the meeting
  by writing a small overview of your pending and future work\, and the goal
 s that motivate those works. If you send this summary to the mailing list b
 eforehand\, we'll have the opportunity to skim it prior to the meeting.\n\n
 I am suggesting we use a public etherpad instance to keep notes during the 
 meeting: https://etherpad.wikimedia.org/p/qapi-sync\n\nDuring this meeting\
 , I'd like to assemble a list of all ongoing QAPI work and begin work on cr
 afting a roadmap that helps describe that work.\n\nI don't suspect we'll fi
 nish in a single meeting\, but it may be a helpful primer for follow-up dis
 cussions on the ML.\n\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:
 ~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-\nDo not edit this section of the descri
 ption.\n\nThis event has a video call.\nJoin: https://meet.google.com/xqi-t
 iqs-xrz\n(US) +1 929-249-4854 PIN: 637379240#\n\nJoin using SIP\n6779067023
 105@gmeet.redhat.com (ID: 6779067023105)\nView more joining options: https:
 //tel.meet/xqi-tiqs-xrz?pin=6779067023105&hs=7\n\nView your event at https:
 //calendar.google.com/calendar/event?action=VIEW&eid=NzJwYXY4YTlpYjBtNDlrOH
 FyOWhqaWJnZzcgcWVtdS1kZXZlbEBub25nbnUub3Jn&tok=MTYjanNub3dAcmVkaGF0LmNvbTAx
 YTNkNTk0NTQyOWNkNDk4YzgxYTY1ZDdhMTc3ODM3NzAyOTg0MzM&ctz=America%2FNew_York&
 hl=en&es=1.\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:
 ~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20211004T210146Z
LOCATION:
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:QAPI Sync meeting
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR

[-- Attachment #2: invite.ics --]
[-- Type: application/ics, Size: 3305 bytes --]

             reply	other threads:[~2021-10-04 21:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-04 21:01 jsnow [this message]
2021-10-07 12:36 ` Invitation: QAPI Sync meeting @ Thu Oct 7, 2021 9am - 10am (EDT) (qemu-devel@nongnu.org) 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=00000000000093852d05cd8d38f6@google.com \
    --to=jsnow@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=damien.hedde@greensocs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.