Re: [virtio] Re: [virtio-comment] virtio networking collaboration meetin

Subject: Re: [virtio] Re: [virtio-comment] virtio networking collaboration meeting: call for agenda

On Thu, May 18, 2023 at 2:47âPM Michael S. Tsirkin <mst@redhat.com> wrote:

Chet, all,

In fact TC voted to conduct all business by electronic ballot, without
meetings.

Both non-TC and TC members will inevitably meet to discuss things like
their plans or implementation efforts. We hardly can, or want to,
prevent that. However:
Any such meetings are not mandatory to maintain voting rights. Anything
discussed in such meetings has no force as a TC decision. Such a meeting
will not be listed in the TC calendar. Neither can material be solely
presented in such a meeting or in the doc linked - it has to be posted
to the mailing list to be considered for inclusion in the specification.

In particular all this applies to the Virtio-networking upstream
biweekly meeting - this is not a TC meeting, but some TC members attend
it.

On Thu, May 18, 2023 at 12:53:41PM -0400, Chet Ensign wrote:
> Just a reminder everyone that you must be a TC member to participate in TC
> meetings. Eugenio, Ariel, I don't see you on the roster. Let me know if you
> need directions on how to set up your OASIS logins as Redhat employees.Â
>
> Thanks,Â
>
> /chetÂ
>
> On Thu, May 18, 2023 at 5:33âAM Eugenio Perez Martin <eperezma@redhat.com>
> wrote:
>
>Â Â ÂOn Thu, May 18, 2023 at 7:48âAM Ariel Adam <aadam@redhat.com> wrote:
>Â Â Â>
>Â Â Â> The "Virtio-networking upstream biweekly meeting" which happens on
>Â Â ÂWednesday's every 2 weeks (led by Eugenio and Jason) was meant to get all
>Â Â Âthe companies interested in virtio networking together to help move things
>Â Â Âforward (both virtio-networking/spec and vDPA).
>Â Â Â>
>Â Â Â> See meeting notes from previous meetings: https://docs.google.com/
>Â Â Âdocument/d/1FoPi81zQmo5y20G0Yntg-eGHX14LnWc63TwR57mCbs4/edit#
>Â Â Â>
>Â Â Â> Why not use that meeting and just add more topics given that a lot of the
>Â Â Ârelevant companies already join this meeting?
>Â Â Â>
>
>Â Â ÂYes, that fits perfectly with the purpose of the meeting. And it has
>Â Â Âbeen used in the past to discuss AQ if I recall correctly.
>
>Â Â ÂThe shared document is already open for writing so everybody can
>Â Â Âpropose new topics.
>
>Â Â ÂThanks for bringing it to the discussion!
>
>Â Â Â> Thanks.
>Â Â Â>
>Â Â Â> On Thu, May 18, 2023 at 3:54âAM Parav Pandit <parav@nvidia.com> wrote:
>Â Â Â>>
>Â Â Â>> 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/
>Â Â Â>>
>
>
>Â Â Â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/
>
>
>
>
> --
>Â Â Â Â Â Â ChetÂEnsign
>
>Â Â Â Â Â Â Chief TechnicalÂ Â Â Â Â Â Â Â Â Â Â [p]Â +1 201-341-1393
> [AIorK4wW] Community StewardÂ Â Â Â ÂÂ Â Â ÂÂ Â [e]Â chet.ensign@oasis-open.org
>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â[l]Â www.oasis-open.org
>Â Â Â Â Â Â OASIS Open
>

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.Â Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

virtio-comment message

ChetÂEnsign