From: Kevin Traynor <ktraynor@redhat.com>
To: Waqqas Jabbar <waqqas.jabbar@emumba.com>, users@dpdk.org
Cc: Ajit Khaparde <ajit.khaparde@broadcom.com>
Subject: Re: [dpdk-users] How to contribute to DPDK
Date: Mon, 10 Feb 2020 17:50:36 +0000 [thread overview]
Message-ID: <ff1f6ee5-eb85-c81d-00e9-fb723b706f99@redhat.com> (raw)
In-Reply-To: <CAKd7n14qypUUEm3=s_EkQUqbchciP+6EwEkqtp7Axy3PiAn_6A@mail.gmail.com>
On 03/02/2020 07:35, Waqqas Jabbar wrote:
> Hi
>
Hi,
> I would like to contribute to DPDK project. Please share where should I begin.
Cool :-)
> I was thinking of starting with some bugs at
> https://bugs.dpdk.org/describecomponents.cgi?product=DPDK
>
> What's the process to do that? Who assigns the bug or can I opt for one?
> Can anyone suggest some easy bugs to fix?
>
I think Ajit assigns the bugs, but I suggest that if there's something
you are interested in fixing, don't wait, just go for it.
Depending on experience, some bugs may be complex, so something like
docs, testing or some small cleanup patches can be a good place to start.
As a new user, maybe you think some things are badly explained (or not
at all) and could use additional documentation? There are unit tests for
many components, maybe you see some missing cases? or maybe some parts
of the code are not clear and need to be cleaned up.
Note, there's a section about how to contribute code to DPDK here
http://doc.dpdk.org/guides/contributing/patches.html
Kevin.
> Regards
> Waqqas
>
next prev parent reply other threads:[~2020-02-10 17:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 7:35 Waqqas Jabbar
2020-02-10 17:50 ` Kevin Traynor [this message]
2020-02-10 23:32 ` Ajit Khaparde
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=ff1f6ee5-eb85-c81d-00e9-fb723b706f99@redhat.com \
--to=ktraynor@redhat.com \
--cc=ajit.khaparde@broadcom.com \
--cc=users@dpdk.org \
--cc=waqqas.jabbar@emumba.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).