From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from ws5-mx01.kavi.com (ws5-mx01.kavi.com [34.193.7.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 84026C77B7D for ; Thu, 18 May 2023 19:45:43 +0000 (UTC) Received: from lists.oasis-open.org (oasis.ws5.connectedcommunity.org [10.110.1.242]) by ws5-mx01.kavi.com (Postfix) with ESMTP id D577C190904 for ; Thu, 18 May 2023 19:45:42 +0000 (UTC) Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id BE02698671E for ; Thu, 18 May 2023 19:45:42 +0000 (UTC) Received: from host09.ws5.connectedcommunity.org (host09.ws5.connectedcommunity.org [10.110.1.97]) by lists.oasis-open.org (Postfix) with QMQP id B22CF983E90; Thu, 18 May 2023 19:45:42 +0000 (UTC) Mailing-List: contact virtio-comment-help@lists.oasis-open.org; run by ezmlm List-ID: Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 9F18998671B for ; Thu, 18 May 2023 19:45:42 +0000 (UTC) X-Virus-Scanned: amavisd-new at kavi.com X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684439140; x=1687031140; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=vv464JIBnIa/doS0AdNF+O9iLhjpHopPQIUro2dTL1w=; b=iU3l2y74eB8TL7fh8ihqVc8/y3+eoEKgvCaGu01j/yiBT+2zkFsz2SBGvWzyCf6YYB EJ4RmvWr6fAXKbztWt7YZisRPzKCc/ItdmEuvsLNQbBgReRDCYaisLIV/iEVh8/Umt56 ApkbjQKDcxlfBVObNzSIL+5VVOfSDG+7YMLmEiH4JPIgsanC7Z+zNWW5Aazdhbl7JMV4 N/CGlYQC+wreEDbVb5wLDudri4h9HgYvJNXv9nbE7j2/6s/cUrSdD9evFSAwxf+vVWIN vu4EToL2SknD8YAohxo4z86SN6+qNJPIEZp6LOU2kMd2b1B0wEUfFSO8l5ABL2AyOv3Z lORA== X-Gm-Message-State: AC+VfDzqTXJa9C+JkiZRP/h2QXDL0Zgh8YUDoW57EqH8yG/hteepK1e9 2X/IQafPpkVbIsZ9AxjThUrS7Z8vw4rwcrNCWSAhWu0= X-Google-Smtp-Source: ACHHUZ56WpOKG+c+ob4D3kzaLWCcdm5hTqBsSVgZz7qiZRcdJ2fwLr5SuS/Uvw+wA+tZVD79sa25rP0x99FVjIrGweg= X-Received: by 2002:a92:d30d:0:b0:32c:a1d1:40c3 with SMTP id x13-20020a92d30d000000b0032ca1d140c3mr5053017ila.32.1684439140063; Thu, 18 May 2023 12:45:40 -0700 (PDT) MIME-Version: 1.0 References: <20230518143013-mutt-send-email-mst@kernel.org> <20230518151424-mutt-send-email-mst@kernel.org> In-Reply-To: <20230518151424-mutt-send-email-mst@kernel.org> From: Chet Ensign Date: Thu, 18 May 2023 15:45:29 -0400 Message-ID: To: "Michael S. Tsirkin" Cc: Eugenio Perez Martin , Ariel Adam , Parav Pandit , "virtio@lists.oasis-open.org" , "virtio-comment@lists.oasis-open.org" Content-Type: multipart/alternative; boundary="00000000000096fbf405fbfd0c1c" Subject: [virtio-comment] Re: [virtio] Re: [virtio-comment] virtio networking collaboration meeting: call for agenda --00000000000096fbf405fbfd0c1c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks very much, Michael. I appreciate you taking the time to go through that. On Thu, May 18, 2023 at 3:32=E2=80=AFPM Michael S. Tsirkin = wrote: > Well this is why I said: > > 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. > > This should serve to protect the IPR - while people can discuss > whatever, for things to be in the spec they have to be on list. > > As an additional precaution, I think that while subscribing to list is > one way to agree to the feedback license, another is simply asking > anyone who is not a TC member to confirm. > > Just in case, I also suggested to Eugenio that anyone discussing issues > connected to a virtio spec is presented with a reminder along the lines > of: > > By joining the meeting, participants agree that any information share= d > in the > meeting will be considered submitted by them to the VIRTIO TC, > according > the OASIS Intellectual Property Rights (IPR) Policy > https://www.oasis-open.org/policies-guidelines/ipr > > Hope this helps. > > On Thu, May 18, 2023 at 03:09:38PM -0400, Chet Ensign wrote: > > Thanks, Michael. I knew the TC operates that way so I found the exchang= e > > confusing. > > > > The key issue here is IPR commitments that go with contributions. When > someone > > makes a contribution to the TC - chunk of code or whatever - their IPR > has to > > be covered. For TC members, they are committed by joining and being on > the > > roster. For any non-TC members, contribution has to be done via the > comment > > list to gain the equivalent commitment. That protection for the TC and > Oasis is > > the key thing I look for. > > > > On Thu, May 18, 2023 at 2:47=E2=80=AFPM Michael S. Tsirkin > 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 sole= ly > > 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=E2=80=AFAM Eugenio Perez Martin < > eperezma@redhat.com > > > > > > wrote: > > > > > > On Thu, May 18, 2023 at 7:48=E2=80=AFAM Ariel Adam > wrote: > > > > > > > > The "Virtio-networking upstream biweekly meeting" which > happens on > > > Wednesday's every 2 weeks (led by Eugenio and Jason) was mean= t > to get > > all > > > the companies interested in virtio networking together to hel= p > 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 tha= t > 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=E2=80=AFAM 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 spac= e > 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 abilit= y > 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 wh= o > wants > > to > > > attend and in which time zone. > > > >> > > > >> If all this sounds interesting to you, if you would like t= o > 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 inpu= t > 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 t= o > 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 require= d > > > 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 tha= t > > 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 > > > > > > > > > > -- > > 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 > > > > --=20 Chet Ensign Chief Technical Community Steward OASIS Open +1 201-341-1393 <+1+201-341-1393> chet.ensign@oasis-open.org www.oasis-open.org --00000000000096fbf405fbfd0c1c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks very much, Michael. I appreciate you taking the tim= e to go through that.=C2=A0

On Thu, May 18, 2023 at 3:32=E2=80=AFPM Michael = S. Tsirkin <mst@redhat.com> wro= te:
Well this is= why I said:
>=C2=A0 =C2=A0 =C2=A0Neither can material be solely
>=C2=A0 =C2=A0 =C2=A0presented in such a meeting or in the doc linked - = it has to be posted
>=C2=A0 =C2=A0 =C2=A0to the mailing list to be considered for inclusion = in the specification.

This should serve to protect the IPR - while people can discuss
whatever, for things to be in the spec they have to be on list.

As an additional precaution, I think that while subscribing to list is
one way to agree to the feedback license, another is simply asking
anyone who is not a TC member to confirm.

Just in case, I also suggested to Eugenio that anyone discussing issues
connected to a virtio spec is presented with a reminder along the lines
of:

=C2=A0 =C2=A0 By joining the meeting, participants agree that any informati= on shared in the
=C2=A0 =C2=A0 meeting will be considered submitted by them to the VIRTIO TC= , according
=C2=A0 =C2=A0 the OASIS Intellectual Property Rights (IPR) Policy
=C2=A0 =C2=A0 https://www.oasis-open.org/policies-= guidelines/ipr

Hope this helps.

On Thu, May 18, 2023 at 03:09:38PM -0400, Chet Ensign wrote:
> Thanks, Michael. I knew the TC operates that way so I found the exchan= ge
> confusing.=C2=A0
>
> The key issue here is IPR commitments that go with contributions. When= someone
> makes a contribution to the TC - chunk of code or whatever - their IPR= has to
> be covered. For TC members, they are committed by joining and being on= the
> roster. For any non-TC members, contribution has to be done via the co= mment
> list to gain the equivalent commitment. That protection for the TC and= Oasis is
> the key thing I look for.=C2=A0
>
> On Thu, May 18, 2023 at 2:47=E2=80=AFPM Michael S. Tsirkin <mst@redhat.com> wrote:<= br> >
>=C2=A0 =C2=A0 =C2=A0Chet, all,
>
>=C2=A0 =C2=A0 =C2=A0In fact TC voted to conduct all business by electro= nic ballot, without
>=C2=A0 =C2=A0 =C2=A0meetings.
>
>=C2=A0 =C2=A0 =C2=A0Both non-TC and TC members will inevitably meet to = discuss things like
>=C2=A0 =C2=A0 =C2=A0their plans or implementation efforts. We hardly ca= n, or want to,
>=C2=A0 =C2=A0 =C2=A0prevent that. However:
>=C2=A0 =C2=A0 =C2=A0Any such meetings are not mandatory to maintain vot= ing rights. Anything
>=C2=A0 =C2=A0 =C2=A0discussed in such meetings has no force as a TC dec= ision. Such a meeting
>=C2=A0 =C2=A0 =C2=A0will not be listed in the TC calendar. Neither can = material be solely
>=C2=A0 =C2=A0 =C2=A0presented in such a meeting or in the doc linked - = it has to be posted
>=C2=A0 =C2=A0 =C2=A0to the mailing list to be considered for inclusion = in the specification.
>
>=C2=A0 =C2=A0 =C2=A0In particular all this applies to the Virtio-networ= king upstream
>=C2=A0 =C2=A0 =C2=A0biweekly meeting - this is not a TC meeting, but so= me TC members attend
>=C2=A0 =C2=A0 =C2=A0it.
>
>
>
>=C2=A0 =C2=A0 =C2=A0On Thu, May 18, 2023 at 12:53:41PM -0400, Chet Ensi= gn wrote:
>=C2=A0 =C2=A0 =C2=A0> Just a reminder everyone that you must be a TC= member to participate in
>=C2=A0 =C2=A0 =C2=A0TC
>=C2=A0 =C2=A0 =C2=A0> meetings. Eugenio, Ariel, I don't see you = on the roster. Let me know if
>=C2=A0 =C2=A0 =C2=A0you
>=C2=A0 =C2=A0 =C2=A0> need directions on how to set up your OASIS lo= gins as Redhat employees.=C2=A0
>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0> Thanks,=C2=A0
>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0> /chet=C2=A0
>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0> On Thu, May 18, 2023 at 5:33=E2=80=AFAM Eugeni= o Perez Martin <eperezma@redhat.com
>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0> wrote:
>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0On Thu, May 18, 2023 at 7:4= 8=E2=80=AFAM Ariel Adam <aadam@redhat.com> wrote:
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0> The "Virtio-netwo= rking upstream biweekly meeting" which happens on
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0Wednesday's every 2 wee= ks (led by Eugenio and Jason) was meant to get
>=C2=A0 =C2=A0 =C2=A0all
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0the companies interested in= virtio networking together to help move
>=C2=A0 =C2=A0 =C2=A0things
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0forward (both virtio-networ= king/spec and vDPA).
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0> See meeting notes from= previous meetings: https://docs.google.com/
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0document/d/1FoPi81zQmo5y20G= 0Yntg-eGHX14LnWc63TwR57mCbs4/edit#
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0> Why not use that meeti= ng and just add more topics given that a lot
>=C2=A0 =C2=A0 =C2=A0of the
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0relevant companies already = join this meeting?
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0Yes, that fits perfectly wi= th the purpose of the meeting. And it has
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0been used in the past to di= scuss AQ if I recall correctly.
>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0The shared document is alre= ady open for writing so everybody can
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0propose new topics.
>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0Thanks for bringing it to t= he discussion!
>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0> Thanks.
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0> On Thu, May 18, 2023 a= t 3:54=E2=80=AFAM Parav Pandit <parav@nvidia.com>
>=C2=A0 =C2=A0 =C2=A0wrote:
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> Hi all,
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> At the moment to m= y knowledge, many TC members are working on many
>=C2=A0 =C2=A0 =C2=A0new
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0features for virtio network= device specification - all of us working
>=C2=A0 =C2=A0 =C2=A0in
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0parallel.
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> I feel a biweekly = meeting would help us virtio networking
>=C2=A0 =C2=A0 =C2=A0developers
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0collaborate more effectivel= y.
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> For example, we ca= n discuss how do features each one is working on
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0interact, what timeframe is= each one targeting, etc.
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> I suggest:
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> - A biweekly meeti= ng using google meet.
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> - Meeting agenda w= ill be posted on list before a week so people
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>>=C2=A0 =C2=A0will h= ave a full week to review, respond on the existing mailing
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0lists.
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> - If no agenda ite= ms for that meeting day, meeting will be
>=C2=A0 =C2=A0 =C2=A0cancelled.
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> - Minutes will be = posted on list after a meeting.
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> - non-TC members c= an also join; this is an additional space to get
>=C2=A0 =C2=A0 =C2=A0input
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>>=C2=A0 =C2=A0from o= utside experts, under the existing terms of OASIS feedback
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0license.
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> - All decisions ar= e still made by TC electronic ballot as usual.
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0Proposed collaboration
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>>=C2=A0 =C2=A0meetin= gs are unrelated to TC ballot. The point is ability to
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0collaborate,
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>>=C2=A0 =C2=A0plan a= nd split work better between developers working in the
>=C2=A0 =C2=A0 =C2=A0same spec
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0area.
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> For the first meet= ing, I propose the following agenda item:
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> - discuss new virt= io net device features for 1.4 spec release
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> I suggest several = day & time slots.
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> Days:
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> - Tue (May 30) or<= br> >=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> - Wed (May 31)
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> Time:
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> - 2 pm GMT, or
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> - 5 am GMT
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> We can pick other = time/day options as well depending on who wants
>=C2=A0 =C2=A0 =C2=A0to
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0attend and in which time zo= ne.
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> If all this sounds= interesting to you, if you would like to attend
>=C2=A0 =C2=A0 =C2=A0this
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0and hopefully future collab= oration meetings,
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> please reply with = email, cc to list:
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> a. preferred time = slots that work for you.
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> b. any items you w= ould like to add to above agenda.
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> Any other comments= , suggestions?
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> Regards,
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> Parav Pandit
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> This publicly arch= ived list offers a means to provide input to the
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> OASIS Virtual I/O = Device (VIRTIO) TC.
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> In order to verify= user consent to the Feedback License terms and
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> to minimize spam i= n the list archive, subscription is required
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> before posting. >=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> Subscribe: virtio-comment-subscribe@lists.oasis-open.org
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> List help: virt= io-comment-help@lists.oasis-open.org
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> List archive: https://lists.oasis-open.org/archives/virtio-comment=
>=C2=A0 =C2=A0 =C2=A0/
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> Feedback License: = https://www.oasis-open.org/who/ipr/
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0feedback_license.pdf
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> List Guidelines: <= a href=3D"https://www.oasis-open.org/policies-guidelines/" rel=3D"noreferre= r" target=3D"_blank">https://www.oasis-open.org/policies-guidelines/ >=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0mailing-lists
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> Committee: https://www.oasis-open.org/committees/virtio/
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>> Join OASIS: https://www.oasis-open.org/join/
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>>
>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0This publicly archived list= offers a means to provide input to the
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0OASIS Virtual I/O Device (V= IRTIO) TC.
>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0In order to verify user con= sent to the Feedback License terms and
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0to minimize spam in the lis= t archive, subscription is required
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0before posting.
>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0Subscribe: virtio-c= omment-subscribe@lists.oasis-open.org
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0Unsubscribe: virt= io-comment-unsubscribe@lists.oasis-open.org
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0List help: virtio-commen= t-help@lists.oasis-open.org
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0List archive: https://lists.oasis-open.org/archives/virtio-comment/ >=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0Feedback License: https://www.oasis-open.org/who/ipr/
>=C2=A0 =C2=A0 =C2=A0feedback_license.pdf
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0List Guidelines: https://www.oasis-open.org/policies-guidelines/
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0mailing-lists
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0Committee: https://www.oasis-open.org/committees/virtio/
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0Join OASIS: https://= www.oasis-open.org/join/
>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0> --
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Chet= =C2=A0Ensign
>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Chief= Technical=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 [p]=C2=A0 +1 201-341-1393
>=C2=A0 =C2=A0 =C2=A0> [AIorK4wW] Community Steward=C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0 [e]=C2=A0
>=C2=A0 =C2=A0 =C2=A0chet.ensign@oasis-open.org
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0[l]=C2=A0 www.oasis-= open.org
>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 OASIS= Open
>=C2=A0 =C2=A0 =C2=A0>
>
>
>=C2=A0 =C2=A0 =C2=A0---------------------------------------------------= ------------------
>=C2=A0 =C2=A0 =C2=A0To unsubscribe from this mail list, you must leave = the OASIS TC that
>=C2=A0 =C2=A0 =C2=A0generates this mail.=C2=A0 Follow this link to all = your TCs in OASIS at:
>=C2=A0 =C2=A0 =C2=A0https:= //www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>
>
>
> --
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Chet=C2=A0Ensign
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Chief Technical=C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [p]=C2=A0 +1= 201-341-1393
> [AIorK4wW] Community Steward=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 = =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0 [e]=C2=A0 chet.ensign@oasis-open.org
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0[l]=C2=A0 www.oasis-open.org
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 OASIS Open
>



--
=

Chet=C2=A0Ensign

Chief Technical Community Steward

OASIS Open

=C2=A0=C2=A0= =C2=A0
+1 201-341-1393
chet.ensign@oasis-open.org
www.oasis-open.org<= /td>
--00000000000096fbf405fbfd0c1c--