From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Karuna Grewal <karunagrewal98@gmail.com>
Cc: dev@dpdk.org, ajit.khaparde@broadcom.com
Subject: Re: [dpdk-dev] DPDK's GSoC participation
Date: Fri, 1 Feb 2019 17:00:11 +0000 [thread overview]
Message-ID: <bf26117d-e999-89e8-3860-471f88f22fcd@intel.com> (raw)
In-Reply-To: <6706445.jDfIes0TBL@xps>
On 1/31/2019 5:49 PM, Thomas Monjalon wrote:
> 31/01/2019 18:07, Karuna Grewal:
>> Hi everyone,
>>
>> I saw the previous thread about DPDK's GSoC ideas. As someone having
>> experience using the same while investigating various userspace network
>> stack implementations, I want to know if there are any beginner friendly
>> tasks on bugzilla for me to start contributing to this project.
>> Any pointers in this direction are appreciated.
>
> That's a good question.
> We should mark some easy tasks in bugzilla with a special priority.
>
> Ferruh, Ajit, any comment?
Bugzilla is mainly for defects, more than tasks, you can check them, there is no
any difficulty level assigned to them but working on them can be educational.
You can check static analysis results and fix some of them,
- coverity:
https://scan.coverity.com/projects/dpdk-data-plane-development-kit?tab=overview
- cppcheck: https://bugs.dpdk.org/show_bug.cgi?id=58
There is also a good to have feature list, but not sure how beginner they are:
https://core.dpdk.org/roadmap/#future
Great to see the interest, thanks for volunteering,
ferruh
prev parent reply other threads:[~2019-02-01 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 17:07 Karuna Grewal
2019-01-31 17:49 ` Thomas Monjalon
2019-02-01 17:00 ` 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=bf26117d-e999-89e8-3860-471f88f22fcd@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=karunagrewal98@gmail.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).