From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id C5B11A0562; Tue, 31 Mar 2020 22:45:25 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 9F45D1C0C4; Tue, 31 Mar 2020 22:45:21 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id DE2AC1C0B1; Tue, 31 Mar 2020 22:45:19 +0200 (CEST) Received: from mail-io1-f50.google.com (mail-io1-f50.google.com [209.85.166.50]) by dpdk.org (Postfix) with ESMTP id F043A1C06D for ; Tue, 31 Mar 2020 22:44:03 +0200 (CEST) Received: by mail-io1-f50.google.com with SMTP id x9so16788192iom.10 for ; Tue, 31 Mar 2020 13:44:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=mime-version:from:date:message-id:subject:to; bh=qrYVc9WRAXCkSdhQslolDBkJJ8qZD4NgZm1TRuF00+s=; b=ANc4IGtkpIYaYe6E5D1DURxVC5SEzZaE7x1UUU0mWb0cjqNpaYVfCvGbK66G3Xc9iN alM636i8Dc5lrdzfYteoXF2AdDor2KzJaAw16OfquxT1F1Yzc8B9wesAvqjEiMmGrAa7 cR9tbY4BgEDynJRXKCTi4kQAfeAjCTzCxyHHM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=qrYVc9WRAXCkSdhQslolDBkJJ8qZD4NgZm1TRuF00+s=; b=PLJ9JE24dQIR6vZEgl4uvH3q5oMO7wqiTOe5IJxBDqEUFw8GCerRZewluIVTSiuw45 c4w5ht2PAfKWgsZygCcjdQYKYUI7dwXOufEK5dOWfgA7nF2KTpRjoLE+ToZSTz8+DqrU H0C5p7kuG2huWjl+qKuE9Cdo2YBgSPiC5UtIfV0ephyQ+1rgYcz0lqqi56bbIzC/3qSl r0NuyudclqRg41G2xIBctgUdA7XRXqR1HOSmWSHuLT7C9hKGnXEjkLMi9tsJWEoEbx1Q NGHXT6+RmwJWPG6x8uCnUFslJUG8/aNaf7EcnFKbEc31mXMHKGxvE5vzIqJp4aZ66/x0 z2Dg== X-Gm-Message-State: ANhLgQ3LLog6uPNNoLO+zpTE5PCSKNgKIVQO2BjceGaIye69h0rtobp3 ZCNJE+2Qv4TCHxgKaO943BRzq4KUcUBZdkD371x9lWIwfm0= X-Google-Smtp-Source: ADFU+vsAfx9XNA/zzuuwZ2frCygsi4Rwi208O9SeVTZ9XpFKWfIKqH4fuV36QntK6bE6wYpmOUpJ8wM01aGybFtusUs= X-Received: by 2002:a02:ccf1:: with SMTP id l17mr12883846jaq.87.1585687443020; Tue, 31 Mar 2020 13:44:03 -0700 (PDT) MIME-Version: 1.0 From: Jill Lovato Date: Tue, 31 Mar 2020 13:43:24 -0700 Message-ID: To: announce@dpdk.org Content-Type: text/plain; charset="UTF-8" X-Mailman-Approved-At: Tue, 31 Mar 2020 22:45:19 +0200 X-BeenThere: announce@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list Subject: [dpdk-dev] [dpdk-announce] Message from DPDK Board & Tech Chairs X-BeenThere: dev@dpdk.org List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Greetings DPDK Project Community: We hope you are managing okay and remaining safe and healthy as the coronavirus crisis has thrown the world into a frenzy. While many of us are used to working remotely and using online collaborative tools, we are having to adapt to new circumstances at home. It is hard on everyone. The DPDK Governing Board, Technical Board, and Marketing Committee have been hard at work locking down our final 2020 budget, crafting plans around worldwide DPDK Summit events, and exploring hosting a broader data plane projects developer event. However, upcoming public gatherings and events have been cancelled or postponed and are no longer an option in the near term. DPDK has not yet migrated to virtual events. For now, our plans around DPDK Summit events are in flux: * China and Japan events are on hold. As things develop further we will see if we can make something happen, perhaps in Q3 or Q4. * The US DPDK Summit event is pushed out to Q1 of 2021. The team made this decision before the pandemic emerged in order to create some calendar space between the Summit and Userspace events. We have targeted the second half of September for the Userspace event, continuing to host it in Bordeaux. As of now this is still our intent. But as we are sure you can understand, the situation remains fluid until the pandemic subsides. Please bear with us. We have also continued to explore options to increase the value and role of the DPDK Community Lab that is currently hosted at the University of New Hampshire, InterOperability Lab, also known as UNH/IoL. We would like to acknowledge the continued efforts of Lincoln Lavoie and team, especially as he remains in the lab to triage hardware issues. However, we have struggled to find community volunteers to step up and lead the lab effort. We are now looking at alternatives including a minimum set of activities and regression tests that the Technical Board recommends we maintain. Other efforts to expand the use of the lab will likely require additional budget. We are trying to converge on a solution. Help is still welcome should anyone want to get more involved. The community continues to be amazing. This year we delivered our 20.02 release with few time accommodations. Work is underway for the 20.05 release with several new features and improvements https://core.dpdk.org/roadmap/ 20.08 and 20.11 will follow. We are confident the community collaboration and execution capability will serve us well during these times. We are not expecting too much delay in releases. Of note, while most git maintainers do have a back-up in place, please let us know if you are able to help fill in any gaps. Overall we want to ensure you prioritize yourself and your family as your personal health and safety are paramount to us. Rest assured the DPDK community is here for you - whether it be help on a feature, code, or guidance on how to handle a challenging home dilemma, please do reach out. The DPDK family is strong and tremendously supportive. We are glad to be part of it. Stay safe and healthy. All the best, Thomas and Jim Note - this message is also posted to the DPDK blog: https://www.dpdk.org/blog/2020/03/31/community-update-from-the-dpdk-board-tech-chairs