From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] DPDK Events Plan - Current Thinking/Proposal
Date: Thu, 4 Nov 2021 08:16:59 -0700 [thread overview]
Message-ID: <20211104081659.5041c5a2@hermes.local> (raw)
In-Reply-To: <SJ0PR11MB5678320FD724CA2801236715DFB69@SJ0PR11MB5678.namprd11.prod.outlook.com>
On Tue, 12 Oct 2021 13:49:59 +0000
"St Leger, Jim" <jim.st.leger@intel.com> wrote:
> DPDK Community:
>
> The Tech Board has provided great input on their preferences for a Userspace event. Some weeks back (I'm late getting the minutes out; my apologies) a small team (Bruce, Honnappa, Thomas, Jim, Ashley, Jill, Rachel, and Emily) met to discuss the options and come up with a plan. Here's what has been agreed to.
>
> Userspace:
> 1. Userspace Co-located in Brussels after FOSDEM.
> The preference is very strong to have an in-person event, not another hybrid event. The consensus was that the community really wants to get together in-person, face to face. We discussed whether it would be the week before FOSDEM or after. There is a conflicting event the week prior, thus the week after was chosen. As of today that would be February 7-8, 2022.
>
> 2. What if FOSDEM is Again Virtual?
> In the case of FOSDEM being a virtual event for 2022 we will NOT hold Userspace after it. Instead we will aim for some time in the early summer, likely June. The location is TBD but is likely still somewhere in Europe.
FOSDEM announced they are virtual in 2022
prev parent reply other threads:[~2021-11-04 15:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 13:49 St Leger, Jim
2021-11-04 15:16 ` Stephen Hemminger [this message]
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=20211104081659.5041c5a2@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
/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).