From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dts-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 0090DA04A6;
	Fri, 17 Dec 2021 18:52:32 +0100 (CET)
Received: from [217.70.189.124] (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id BD9914013F;
	Fri, 17 Dec 2021 18:52:32 +0100 (CET)
Received: from mail-ot1-f54.google.com (mail-ot1-f54.google.com
 [209.85.210.54]) by mails.dpdk.org (Postfix) with ESMTP id B899740040
 for <dts@dpdk.org>; Fri, 17 Dec 2021 18:52:31 +0100 (CET)
Received: by mail-ot1-f54.google.com with SMTP id
 i5-20020a05683033e500b0057a369ac614so3801857otu.10
 for <dts@dpdk.org>; Fri, 17 Dec 2021 09:52:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol;
 h=mime-version:from:date:message-id:subject:to;
 bh=Th7RU3aUaor5EYup32HnUPVQiY9u/7L2pL3xc8A2Yp4=;
 b=bHMALwsrtCy1fsynfYULIhNMCcwaruKsVMN88ZCBGDTd+XEfipTm5edweRqYe1//jG
 G4zOngjnz+d1GZ+j4mOKE0eU9jq/yawjR9Qe4kFagcPI1zk+n7wR3H3zxRV+H/mP43F4
 l8QLRSffGPI2SYaI2HmyWurPLlW8dvDdmcqL8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
 bh=Th7RU3aUaor5EYup32HnUPVQiY9u/7L2pL3xc8A2Yp4=;
 b=ZsRSCRgz/2rN0FsBCf0BhsOXq7WcDwpDOOIq6cFrSHkzV+XHkENdRVu9hqvbT48YVl
 cgjtwYeyz8u/BcBR4XeXPmiByaju/mj1E88R90qaQvDus5l+jnNwlCRcl9JyHfBKNYIs
 RvjtCY6ZoRDYATVYECiIDheTMJYskmJVVqZKt2qkQYWgJ1jePHwbwrVmSizAnJgMEeT8
 6tGtEZQ+Chg2YThK530de7VkwasVPbljNVXqmvxOT+sq43xTPfuK/dpYaGjiz3cuBZ5/
 +lfu3S4Y8JUjEo6d7eT5KdU//XhOqOO6bkO4NxiEw3fd7JXqrw618P73lfzoCY3ehoLZ
 ks8w==
X-Gm-Message-State: AOAM533nz3pUrZ9JE6aa6tzmKYX6nf8FKIID3TnHTZxHULXdzU0TGaS3
 jBR+G73PA8tVoUv609Gfp01HlauJaWLAQgKm3kD3vg==
X-Google-Smtp-Source: ABdhPJzjAusIAKtCyFtx2Z/q09urhujwm/OaGwqEVS3Xd3Ws6YjeMOBPX3o0I4jehBaqB+aR6eq87MjDufnhQ7ZpAQM=
X-Received: by 2002:a9d:5ccc:: with SMTP id r12mr2942851oti.67.1639763551020; 
 Fri, 17 Dec 2021 09:52:31 -0800 (PST)
MIME-Version: 1.0
From: Owen Hilyard <ohilyard@iol.unh.edu>
Date: Fri, 17 Dec 2021 12:51:55 -0500
Message-ID: <CAHx6DYC+6TyqGOew-aGx+shcqGqN-E=aGbBC0Voj74Kg7rpEVA@mail.gmail.com>
Subject: Schedule for DTS Improvement Working Group Meetings
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>, "Tu,
 Lijuan" <lijuan.tu@intel.com>, Lincoln Lavoie <lylavoie@iol.unh.edu>,
 =?UTF-8?Q?Juraj_Linke=C5=A1?= <juraj.linkes@pantheon.tech>, dts@dpdk.org
Content-Type: multipart/alternative; boundary="000000000000f97daf05d35b33b9"
X-BeenThere: dts@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: test suite reviews and discussions <dts.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dts>,
 <mailto:dts-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dts/>
List-Post: <mailto:dts@dpdk.org>
List-Help: <mailto:dts-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dts>,
 <mailto:dts-request@dpdk.org?subject=subscribe>
Errors-To: dts-bounces@dpdk.org

--000000000000f97daf05d35b33b9
Content-Type: text/plain; charset="UTF-8"

Hello Everyone,

I wanted to get started on planning the 2022 meetings for the working
group.

The two easy options are:

1. Continue at the same time as previously, starting on the 5th of January.

I think that this would be best if we think there will be a lot of
discussions and we will need an hour to get through all of it.

2.  Integrate with the CI Committee meetings

This would be best if we don't anticipate having much to discuss
every week, and we would still have the option of scheduling sessions to
deal with larger issues.

I personally won't be able to attend the full CI committee meeting until
June, due to scheduling conflicts.


Due to both my personal scheduling conflicts and anticipation of a lot more
interest in the working group, my preference is for the first option.

Owen Hilyard

--000000000000f97daf05d35b33b9
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello Everyone,<div><br></div><div>I wanted to get started=
 on planning the 2022 meetings for the working group.=C2=A0</div><div><br><=
/div><div>The two easy options are:</div><div><br></div><div>1. Continue at=
 the same time as previously, starting on the 5th of January.</div><div><br=
></div><div>I think that this would be best if we think there will be a lot=
 of discussions and we will need an hour to get through all of it.</div><di=
v><br></div><div>2.=C2=A0 Integrate with the CI Committee=C2=A0meetings</di=
v><div><br></div><div>This would be best if we don&#39;t anticipate having =
much to discuss every=C2=A0week, and we would still have the option of sche=
duling sessions to deal with larger issues.=C2=A0</div><div><br></div><div>=
I personally won&#39;t be able to attend the full CI committee meeting unti=
l June, due to scheduling conflicts.=C2=A0<br><div><br></div><div><br>Due t=
o both my personal scheduling conflicts and anticipation of a lot more inte=
rest in the working group, my preference is for the first option.=C2=A0</di=
v></div><div><br></div><div>Owen Hilyard</div></div>

--000000000000f97daf05d35b33b9--