DPDK CI discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: ci@dpdk.org
Cc: Aaron Conole <aconole@redhat.com>, zhoumin <zhoumin@loongson.cn>,
	 "Brandes, Shai" <shaibran@amazon.com>,
	 "Puttaswamy, Rajesh T" <rajesh.t.puttaswamy@intel.com>,
	Paul Szczepanek <Paul.Szczepanek@arm.com>,
	 Luca Vizzarro <Luca.Vizzarro@arm.com>,
	Ali Alnubani <alialnu@nvidia.com>,
	 Andre Muezerie <andremue@linux.microsoft.com>,
	mamcgove@microsoft.com
Subject: Finding a better timeslot(s) for the DPDK CI Testing Meeting
Date: Thu, 12 Jun 2025 08:21:14 -0400	[thread overview]
Message-ID: <CAJvnSUC6pe4P=mJGML94QOzhhn7ykwS0hExNj45tztbtFFL3nA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 739 bytes --]

Hello DPDK CI Lab maintainers and other meeting participants.

It has been a while since we have evaluated the regular meeting time for
the DPDK CI meeting, and some new people have gotten involved in DPDK CI
since then, so we want to check if there is a timeslot(s) which will work
better for the group than the current "every other Thursday at 13:00 UTC"
schedule.

Anyone involved in DPDK CI - please take a moment to fill out this "when to
meet" survey, indicating your free timeslots:
https://www.when2meet.com/?30965992-3ijyI

I think this is particularly important for lab maintainers, as being able
to meet over video conference, even if it's not every two weeks, would
probably help us sync our efforts in a big way.

Thanks all!

[-- Attachment #2: Type: text/html, Size: 1372 bytes --]

                 reply	other threads:[~2025-06-12 12:26 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='CAJvnSUC6pe4P=mJGML94QOzhhn7ykwS0hExNj45tztbtFFL3nA@mail.gmail.com' \
    --to=probb@iol.unh.edu \
    --cc=Luca.Vizzarro@arm.com \
    --cc=Paul.Szczepanek@arm.com \
    --cc=aconole@redhat.com \
    --cc=alialnu@nvidia.com \
    --cc=andremue@linux.microsoft.com \
    --cc=ci@dpdk.org \
    --cc=mamcgove@microsoft.com \
    --cc=rajesh.t.puttaswamy@intel.com \
    --cc=shaibran@amazon.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).