DPDK patches and discussions
 help / color / mirror / Atom feed
From: "St Leger, Jim" <jim.st.leger@intel.com>
To: dpdk-techboard <techboard@dpdk.org>,
	"announce@dpdk.org" <announce@dpdk.org>
Cc: "govboard@dpdk.org" <govboard@dpdk.org>,
	"Giller, Robin" <robin.giller@intel.com>
Subject: DPDK Gov Board - My departure and replacement
Date: Wed, 24 Aug 2022 13:42:52 +0000	[thread overview]
Message-ID: <SJ0PR11MB5678DB8599FC410BDFBD0B70DF739@SJ0PR11MB5678.namprd11.prod.outlook.com> (raw)

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

DPDK Community:

I am writing to let you know that I will be leaving my role as the Intel representative on the DPDK Governing Board and as the board chair. I have taken on a new role, still at Intel, which will bring my work focus in a new direction. Robin Giller, whom some of you may know from his work in other open source efforts including networking, cloud native, and microservices, will be the new Intel gov board rep. Nathan will initiate a call for nominations for a new board chair and a subsequent vote as needed. Please welcome and support Robin as you have me.

I want to thank the entire community for all of the support and fun over the years. I've been involved in the DPDK project from it's embryonic days at Intel and the first 2010 release. I watched the community grow. I've been at the first and most of the DPDK Summit events which started back in 2014 in San Francisco, expanded to Userspace in Dublin, and eventually were held in India and China with one in Japan as well. When the community elected to move to hosting by The Linux Foundation I was honored to serve as the board chair, a role I have had now for more than five years. It's been an incredible privilege to serve the community for so long.

I have many cherished memories of working with this incredible community. The Userspace events and dynamic, interactive discussions epitomize the very best of open source. All voices are heard. All opinions matter. The community comes together for the betterment of our work. It doesn't get any better than that. Meanwhile, we've created the industry's defacto high performance, userspace networking model that is widely adopted and deployed. I leave with great pride at all that has been accomplished, predominantly through this amazing community of committed engineers and developers. Thank you.

I hope our paths do cross again. I will still be involved in open source efforts. Please do keep in touch.

All the very best,
Jim

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

                 reply	other threads:[~2022-08-24 14:46 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=SJ0PR11MB5678DB8599FC410BDFBD0B70DF739@SJ0PR11MB5678.namprd11.prod.outlook.com \
    --to=jim.st.leger@intel.com \
    --cc=announce@dpdk.org \
    --cc=govboard@dpdk.org \
    --cc=robin.giller@intel.com \
    --cc=techboard@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).