DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: Nathan Southern <nsouthern@linuxfoundation.org>,
	dev@dpdk.org, bruce.richardson@intel.com,
	Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: Re: DPDK official roadmap
Date: Wed, 11 Jan 2023 15:24:01 +0100	[thread overview]
Message-ID: <3503166.44csPzL39Z@thomas> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35D87650@smartserver.smartshare.dk>

11/01/2023 11:08, Morten Brørup:
> 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).

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.
I would like to add a section for easy work that newcomers could pick.




  reply	other threads:[~2023-01-11 14:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-11 10:08 Morten Brørup
2023-01-11 14:24 ` Thomas Monjalon [this message]
2023-01-11 16:28   ` Morten Brørup

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=3503166.44csPzL39Z@thomas \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=mb@smartsharesystems.com \
    --cc=nsouthern@linuxfoundation.org \
    --cc=roretzla@linux.microsoft.com \
    /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).