From: Nathan Southern <nsouthern@linuxfoundation.org>
To: "Aaron Conole" <aconole@redhat.com>,
ahassick@iol.unh.edu, alialnu@mellanox.com,
"Tammie Williams" <aweltz@linuxfoundation.org>,
blo@iol.unh.edu, bluca@debian.org, "Richardson,
Bruce" <bruce.richardson@intel.com>,
chun.zhang@intel.com, ci@dpdk.org,
"David Marchand" <david.marchand@redhat.com>,
erezsc@mellanox.com, erezsc@nvidia.com, ferruh.yigit@intel.com,
galco@mellanox.com, "Gal Cohen (ProdM)" <galco@nvidia.com>,
georgii.tkachuk@intel.com, gurucode@gmail.com,
"Hemant Agrawal" <hemant.agrawal@nxp.com>,
hnadeau@iol.unh.edu,
"Honnappa Nagarahalli" <honnappa.nagarahalli@arm.com>,
ian.stokes@intel.com,
"Jerin Jacob Kollanukkaran" <jerinj@marvell.com>,
jerinjacobk@gmail.com, "Mcnamara, John" <john.mcnamara@intel.com>,
jspewock@iol.unh.edu, "Juraj Linkeš" <juraj.linkes@pantheon.tech>,
khemendra.kumar13@gmail.com, konstantin.ananyev@intel.com,
"Kevin Traynor" <ktraynor@redhat.com>,
liang-min.wang@intel.com, "Lijuan Tu" <lijuan.tu@intel.com>,
lixuming@huawei.com, luca.boccassi@gmail.com,
"Lincoln Lavoie" <lylavoie@iol.unh.edu>,
malathi.malla@spirent.com, mallam@gmail.com,
marko.kovacevic@intel.com, matt.spencer@arm.com,
"Maxime Coquelin" <maxime.coquelin@redhat.com>,
mmahajan@iol.unh.edu, msantana@redhat.com,
nishant.lodha@cavium.com, nlodha@marvell.com,
"Owen Hilyard" <ohilyard@iol.unh.edu>,
"Matz, Olivier" <olivier.matz@6wind.com>,
piotr.zedlewski@intel.com, "Patrick Robb" <probb@iol.unh.edu>,
qian.q.xu@intel.com, "Ruifeng Wang" <ruifeng.wang@arm.com>,
scampbel@qti.qualcomm.com, scott.titus@intel.com,
shepard.siegel@atomicrules.com,
"Stephen Hemminger" <stephen@networkplumber.org>,
"Arpit Joshipura" <tdelanerolle@linuxfoundation.org>,
"Thomas Monjalon" <thomas@monjalon.net>,
"O'Driscoll, Tim" <tim.odriscoll@intel.com>,
tomasz.zawadzki@intel.com, yu.y.liu@intel.com,
zhaoyan.chen@intel.com, zhoumin@loongson.cn
Cc: Rashid Khan <rkhan@redhat.com>
Subject: Tomorrow's CI meeting - LFX Meeting Mgmt Tool - Clarification
Date: Wed, 24 May 2023 14:50:08 -0500 [thread overview]
Message-ID: <CAKoDjhyarR9zvavk80g6BTMb8CJuhE-CkAgb8ub9FjE+nVjujA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1327 bytes --]
Good afternoon,
Per internal discussion and agreement with leadership on DPDK and The Linux
Foundation, the CI meeting series has been migrated to the LFX Meeting
Management tool, starting *tomorrow morning 5/26 at 6am Pacific/9am
Eastern.*
This means a few things:
-The old zoom link that we were using for everyone will no longer be
operational.
-In its place, a unique, new zoom link has been assigned to each of you,
and you should note it and save it somewhere secure. It should
automatically populate your google calendar, but if you use Outlook or some
other calendaring system, there is a possibility that it may not "cross
over." We're working on this.
You should have a couple of options in terms of signing on. One is to sign
up for an LF_ID and a corresponding password; or if you elect not to do
that, which is perfectly fine, there is a community join option link
included in your invite.
Otherwise, everything will be conducted as per usual, and the meeting will
also be recorded.
I'm going to manually re-send all of the invites in just a few minutes.
Thank you for making this transition with us. Let me know if you have any
questions.
All my best,
Nathan
Nathan C. Southern, Project Coordinator
Data Plane Development Kit
The Linux Foundation
248.835.4812 (mobile)
nsouthern@linuxfoundation.org
[-- Attachment #2: Type: text/html, Size: 3219 bytes --]
reply other threads:[~2023-05-24 19:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAKoDjhyarR9zvavk80g6BTMb8CJuhE-CkAgb8ub9FjE+nVjujA@mail.gmail.com \
--to=nsouthern@linuxfoundation.org \
--cc=aconole@redhat.com \
--cc=ahassick@iol.unh.edu \
--cc=alialnu@mellanox.com \
--cc=aweltz@linuxfoundation.org \
--cc=blo@iol.unh.edu \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=chun.zhang@intel.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=erezsc@mellanox.com \
--cc=erezsc@nvidia.com \
--cc=ferruh.yigit@intel.com \
--cc=galco@mellanox.com \
--cc=galco@nvidia.com \
--cc=georgii.tkachuk@intel.com \
--cc=gurucode@gmail.com \
--cc=hemant.agrawal@nxp.com \
--cc=hnadeau@iol.unh.edu \
--cc=honnappa.nagarahalli@arm.com \
--cc=ian.stokes@intel.com \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=john.mcnamara@intel.com \
--cc=jspewock@iol.unh.edu \
--cc=juraj.linkes@pantheon.tech \
--cc=khemendra.kumar13@gmail.com \
--cc=konstantin.ananyev@intel.com \
--cc=ktraynor@redhat.com \
--cc=liang-min.wang@intel.com \
--cc=lijuan.tu@intel.com \
--cc=lixuming@huawei.com \
--cc=luca.boccassi@gmail.com \
--cc=lylavoie@iol.unh.edu \
--cc=malathi.malla@spirent.com \
--cc=mallam@gmail.com \
--cc=marko.kovacevic@intel.com \
--cc=matt.spencer@arm.com \
--cc=maxime.coquelin@redhat.com \
--cc=mmahajan@iol.unh.edu \
--cc=msantana@redhat.com \
--cc=nishant.lodha@cavium.com \
--cc=nlodha@marvell.com \
--cc=ohilyard@iol.unh.edu \
--cc=olivier.matz@6wind.com \
--cc=piotr.zedlewski@intel.com \
--cc=probb@iol.unh.edu \
--cc=qian.q.xu@intel.com \
--cc=rkhan@redhat.com \
--cc=ruifeng.wang@arm.com \
--cc=scampbel@qti.qualcomm.com \
--cc=scott.titus@intel.com \
--cc=shepard.siegel@atomicrules.com \
--cc=stephen@networkplumber.org \
--cc=tdelanerolle@linuxfoundation.org \
--cc=thomas@monjalon.net \
--cc=tim.odriscoll@intel.com \
--cc=tomasz.zawadzki@intel.com \
--cc=yu.y.liu@intel.com \
--cc=zhaoyan.chen@intel.com \
--cc=zhoumin@loongson.cn \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).