All of lore.kernel.org
 help / color / mirror / Atom feed
From: Parav Pandit <parav@nvidia.com>
To: "virtio@lists.oasis-open.org" <virtio@lists.oasis-open.org>
Cc: "virtio-comment@lists.oasis-open.org"
	<virtio-comment@lists.oasis-open.org>
Subject: [virtio-comment] virtio networking collaboration meeting: call for agenda
Date: Thu, 18 May 2023 00:53:56 +0000	[thread overview]
Message-ID: <PH0PR12MB54816668AFE3CF0F90C8F342DC7F9@PH0PR12MB5481.namprd12.prod.outlook.com> (raw)

Hi all,

At the moment to my knowledge, many TC members are working on many new features for virtio network device specification - all of us working in parallel.

I feel a biweekly meeting would help us virtio networking developers collaborate more effectively.
For example, we can discuss how do features each one is working on interact, what timeframe is each one targeting, etc.

I suggest:
- A biweekly meeting using google meet.
- Meeting agenda will be posted on list before a week so people
  will have a full week to review, respond on the existing mailing lists.
- If no agenda items for that meeting day, meeting will be cancelled.
- Minutes will be posted on list after a meeting.
- non-TC members can also join; this is an additional space to get input
  from outside experts, under the existing terms of OASIS feedback license.

- All decisions are still made by TC electronic ballot as usual. Proposed collaboration
  meetings are unrelated to TC ballot. The point is ability to collaborate, 
  plan and split work better between developers working in the same spec area.

For the first meeting, I propose the following agenda item:
- discuss new virtio net device features for 1.4 spec release

I suggest several day & time slots.
Days:
- Tue (May 30) or
- Wed (May 31)
Time:
- 2 pm GMT, or 
- 5 am GMT

We can pick other time/day options as well depending on who wants to attend and in which time zone.

If all this sounds interesting to you, if you would like to attend this and hopefully future collaboration meetings, 
please reply with email, cc to list:
a. preferred time slots that work for you.
b. any items you would like to add to above agenda.

Any other comments, suggestions?

Regards,
Parav Pandit

This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/


             reply	other threads:[~2023-05-18  0:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18  0:53 Parav Pandit [this message]
2023-05-18  5:47 ` [virtio-comment] virtio networking collaboration meeting: call for agenda Ariel Adam
2023-05-18  9:33   ` Eugenio Perez Martin
2023-05-18 16:53     ` Chet Ensign
2023-05-18 18:46       ` Michael S. Tsirkin
2023-05-18 19:09         ` [virtio-comment] Re: [virtio] " Chet Ensign
2023-05-18 19:31           ` Michael S. Tsirkin
2023-05-18 19:45             ` Chet Ensign
2023-05-21 20:58   ` Parav Pandit
2023-05-22  2:45     ` Xuan Zhuo
2023-05-30 14:57       ` Parav Pandit
2023-05-30 18:41     ` [virtio-comment] Re: [virtio] " Michael S. Tsirkin
2023-05-31 15:16 ` [virtio-comment] " Satananda Burla
2023-05-31 22:22 ` [virtio-comment] " Si-Wei Liu
2023-06-01  0:33   ` Parav Pandit
2023-06-01 15:14     ` Parav Pandit
2023-06-01 16:14 ` Michael S. Tsirkin
2023-06-01 16:19   ` [virtio-comment] RE: [virtio] " Parav Pandit
2023-06-01 16:26     ` [virtio-comment] " Michael S. Tsirkin
2023-06-01 16:35       ` [virtio-comment] " Parav Pandit

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=PH0PR12MB54816668AFE3CF0F90C8F342DC7F9@PH0PR12MB5481.namprd12.prod.outlook.com \
    --to=parav@nvidia.com \
    --cc=virtio-comment@lists.oasis-open.org \
    --cc=virtio@lists.oasis-open.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.