DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Thomas Monjalon" <thomas@monjalon.net>
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 17:28:49 +0100	[thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35D8765B@smartserver.smartshare.dk> (raw)
In-Reply-To: <3503166.44csPzL39Z@thomas>

> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> Sent: Wednesday, 11 January 2023 15.24
> 
> 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.

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!


      reply	other threads:[~2023-01-11 16:28 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
2023-01-11 16:28   ` Morten Brørup [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=98CBD80474FA8B44BF855DF32C47DC35D8765B@smartserver.smartshare.dk \
    --to=mb@smartsharesystems.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=nsouthern@linuxfoundation.org \
    --cc=roretzla@linux.microsoft.com \
    --cc=thomas@monjalon.net \
    /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).