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 63C05C7EE23 for ; Thu, 18 May 2023 18:47:20 +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 82BAA42566 for ; Thu, 18 May 2023 18:47:19 +0000 (UTC) Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 78A3F986721 for ; Thu, 18 May 2023 18:47:19 +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 70188986719; Thu, 18 May 2023 18:47:19 +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 5959798671C for ; Thu, 18 May 2023 18:47:14 +0000 (UTC) X-Virus-Scanned: amavisd-new at kavi.com X-MC-Unique: 4tzKj7Y3N8eRB_5SlgJWvQ-1 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684435629; x=1687027629; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=MwVi9gZQbqzFD104v9ErEch7CmcMoaAClboClYbDj3c=; b=e2qIBuyprBIwo9wPZZ1A6egg6MxhYLHUR0N1Wkw9EVrrdsUtCnbrx+z/NhPJMbCCbA T10IznqBnFsgDBVovcMHSvGyZC62Hu+gVJEm3rizXYHIco9BKG9zMjY995eodCzgzcGR KuvS4Rlr2jDH6DWE1UzHbWIq8W5qEv1Hbc/E2XEaxEgBIWD74SVfa+07rkXaTyDsCjta 242w561Yjjvw4mqjkpWu7kJFoNxxw/LHz3poW414DxCpZSmtq+hiXDVUzCNNC55VE97P pbl0O2pSJ9+tiNECeZqsrgAUWsnpqOb6egkEs3Z4YeseL8lBLFmkSN6HIjMiKjf2IJKt xBeA== X-Gm-Message-State: AC+VfDy33kD7/nnXdvi+ypPnxgZrlDF7COguQt7l/zR3+xJj2GkArg4Q Ffec3Pq40j3EO+9LAY/01sv9KFd6+x/FRDoFH/lV9qvDZyH7sMjk0iIDHDEZjxgZd/uVMmYkehG jq7CL7cxbBx7vrV+pGVE0LZ9PslTne5/GtQ== X-Received: by 2002:a2e:9051:0:b0:2a7:653d:166c with SMTP id n17-20020a2e9051000000b002a7653d166cmr11444448ljg.3.1684435628848; Thu, 18 May 2023 11:47:08 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ7HnxnMuyPMPUrjZMbET6sRmj6CLSg57+qRuEt2WzHiB9ie3yl+iWtxN6GLsFr/l0tHGCSf+w== X-Received: by 2002:a2e:9051:0:b0:2a7:653d:166c with SMTP id n17-20020a2e9051000000b002a7653d166cmr11444434ljg.3.1684435628484; Thu, 18 May 2023 11:47:08 -0700 (PDT) Date: Thu, 18 May 2023 14:46:51 -0400 From: "Michael S. Tsirkin" To: Chet Ensign Cc: Eugenio Perez Martin , Ariel Adam , Parav Pandit , "virtio@lists.oasis-open.org" , "virtio-comment@lists.oasis-open.org" Message-ID: <20230518143013-mutt-send-email-mst@kernel.org> References: MIME-Version: 1.0 In-Reply-To: X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit Subject: Re: [virtio-comment] virtio networking collaboration meeting: call for agenda 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 > wrote: > > On Thu, May 18, 2023 at 7:48 AM Ariel Adam 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 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 > 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/