DPDK announcements
 help / color / Atom feed
From: "Glynn, Michael J" <michael.j.glynn@intel.com>
To: "users@dpdk.org" <users@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>,
	"announce@dpdk.org" <announce@dpdk.org>
Subject: [dpdk-announce] FW: DPDK Community Survey - about to close
Date: Mon, 29 Aug 2016 17:13:34 +0000
Message-ID: <6A5E04BECFB4144EAFCF9EAE3B739A5355B4265D@IRSMSX106.ger.corp.intel.com> (raw)
In-Reply-To: <6A5E04BECFB4144EAFCF9EAE3B739A5355B29C26@IRSMSX106.ger.corp.intel.com>

Hi all

Firstly, thanks to all who provided input to the DPDK Community Survey. In total we had 149 responses with an 85% completion rate. ~40% of responders had contributed patches to a recent release which meant we had a good balance of contributors vs. users. 

In terms of what's working well, the high-level feedback was:
* 96% of responders said that DPDK was meeting their requirements
* Roadmap communications - timely and right level of detail.
* Patch submissions process - 75% believe that it's working well
* Release cadence - four releases per year seems to be the right amount
* Engaged community - we got a significant amount of comments and feedback which we can use to drive further improvements 

Regarding improvement areas, the main feedback was:
* Release Support (stable releases, LTS)
* Documentation - certain aspects are outdated and need attention (particularly the Programmers Guide)
* No specific hotspots but performance bottlenecks seen in certain areas
* Need for a continuous integration and test environment

I recently presented the results at the DPDK Summit so you can see more detail in this link https://dpdksummit.com/Archive/pdf/2016USA/Day02-Session15-MikeGlynn-DPDKSummit2016.pdf 
I'm also planning to share the full set of detailed feedback with the community which I'm collating at the moment. We are also planning to review the feedback at the Userspace event in Dublin with a view to discussing the improvement areas in particular.  

Finally, we are hoping to make this a regular survey (~every 6 months) to I'd like to encourage others to voice their opinions also!

Regards, and thanks

-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Glynn, Michael J
Sent: Thursday, August 4, 2016 11:09 AM
To: dev@dpdk.org
Subject: [dpdk-dev] FW: DPDK Community Survey - about to close

Hi all

Final reminder that the survey closes today Thanks to those who have already provided their input!


  parent reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6A5E04BECFB4144EAFCF9EAE3B739A5355B21606@IRSMSX106.ger.corp.intel.com>
2016-08-02 12:39 ` [dpdk-announce] " Thomas Monjalon
     [not found]   ` <9450082.B1U4CBcoeX@xps13>
     [not found]     ` <6A5E04BECFB4144EAFCF9EAE3B739A5355B29C26@IRSMSX106.ger.corp.intel.com>
2016-08-29 17:13       ` Glynn, Michael J [this message]
2016-10-10 10:42         ` Glynn, Michael J

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6A5E04BECFB4144EAFCF9EAE3B739A5355B4265D@IRSMSX106.ger.corp.intel.com \
    --to=michael.j.glynn@intel.com \
    --cc=announce@dpdk.org \
    --cc=dev@dpdk.org \
    --cc=users@dpdk.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK announcements

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/announce/0 announce/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 announce announce/ http://inbox.dpdk.org/announce \
	public-inbox-index announce

Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/ public-inbox