From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 17A0C42383; Wed, 11 Jan 2023 17:28:52 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0A69D40A7D; Wed, 11 Jan 2023 17:28:52 +0100 (CET) Received: from smartserver.smartsharesystems.com (smartserver.smartsharesystems.com [77.243.40.215]) by mails.dpdk.org (Postfix) with ESMTP id 85B35400D4 for ; Wed, 11 Jan 2023 17:28:50 +0100 (CET) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: DPDK official roadmap Date: Wed, 11 Jan 2023 17:28:49 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Message-ID: <98CBD80474FA8B44BF855DF32C47DC35D8765B@smartserver.smartshare.dk> In-Reply-To: <3503166.44csPzL39Z@thomas> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: DPDK official roadmap Thread-Index: AdklyF4+I5BOtSOTR2SQ8qDcKsdyzQAD9IZg References: <98CBD80474FA8B44BF855DF32C47DC35D87650@smartserver.smartshare.dk> <3503166.44csPzL39Z@thomas> From: =?iso-8859-1?Q?Morten_Br=F8rup?= To: "Thomas Monjalon" Cc: "Nathan Southern" , , , "Tyler Retzlaff" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org > From: Thomas Monjalon [mailto:thomas@monjalon.net] > Sent: Wednesday, 11 January 2023 15.24 >=20 > 11/01/2023 11:08, Morten Br=F8rup: > > Thomas, Nathan, > > > > The DPDK roadmap web page [1] is essentially two lists of specific > features probably coming in the short term, or in some unknown future. > > > > [1] https://core.dpdk.org/roadmap/ > > > > We might want to publish the list of high level, long term ambitions > here, as they are decided by the Tech Board. This would provide > valuable information for DPDK application developers (if not following > the mailing list). > > > > I'm thinking of topics such as: > > * DTS in the main repository, > > * C99 and C11 support (preferably with release dates/versions), and > > * Slimming the EAL (if this becomes an official goal of the = project). >=20 > I agree, we should better publish the intents in the roadmap page. > For driver-specific changes, it goes through the roadmap easily > already. > For global technical changes, it may require a techboard vote first. In principle, the current decision process should suffice: The DPDK high = level roadmap should reflect consensus in the community. And if there is = no consensus, it becomes a techboard decision. On the other hand, techboard meetings are relatively frequent, so = requiring techboard approval for wide ranging changes could be a good = safeguard. > I would like to add a section for easy work that newcomers could pick. Good idea!