DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ryan Yang <toryan123@gmail.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] Contribution to DPDK
Date: Thu, 26 Oct 2017 11:22:02 -0700	[thread overview]
Message-ID: <26c46fc0-8cd0-4cfd-e1f6-c99e21db9506@intel.com> (raw)
In-Reply-To: <CANovW-drpmdqwLpgVnNSnZ5enJtASWuDF5wi2ON0_hYqsMKjTw@mail.gmail.com>

On 10/26/2017 10:18 AM, Ryan Yang wrote:
> Hello,
> 
> I am really interested in contributing to DPDK by fixing the bug and
> development work. Besides cloning the code first, what are some good ways
> to start the work or is there any place to check the bug list? Your help is
> appreciated.

Hi Ryan,

DPDK is using coverity static analysis tool [1], you can check defects found by
that tool, this should be easy to start.

Also DPDK started to maintain a "Nice to have - Future" list [2], but current
list can be hard for beginners, still feel free to check them.

Another thing I can think of is improving the unit test coverage [3], which I
believe can help a lot to learn insights of the related code.

btw, DPDK just started using bug tracing tool [4], but currently it is empty
(almost), so won't be so useful for now.


[1]
https://scan.coverity.com/projects/dpdk-data-plane-development-kit?tab=overview

[2]
http://dpdk.org/dev/roadmap

[3]
http://dpdk.org/browse/dpdk/tree/test/test

[4]
http://dpdk.org/tracker/

> 
> Ryan
> 

      reply	other threads:[~2017-10-26 18:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-26 17:18 Ryan Yang
2017-10-26 18:22 ` Ferruh Yigit [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=26c46fc0-8cd0-4cfd-e1f6-c99e21db9506@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=toryan123@gmail.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).