DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Mahmoud Maatouq <mahmoudmatook.mm@gmail.com>
Cc: dev@dpdk.org, "Morten Brørup" <mb@smartsharesystems.com>,
	"Akhil Goyal" <gakhil@marvell.com>
Subject: Re: Get involved
Date: Fri, 31 May 2024 17:15:59 +0100	[thread overview]
Message-ID: <ed393cf2-c30d-4313-b2dd-9e334f53cc38@amd.com> (raw)
In-Reply-To: <CAPuy4fdsDmzC3MF95tUT0pQC=0Wdzfakjh2R8KugCfaoRx9wMg@mail.gmail.com>

On 5/28/2024 8:13 PM, Mahmoud Maatouq wrote:
> Hello,
> First of all, sorry if this is not the right place for this subject.
> I'm trying to get involved and contribute to dpdk, I went through the
> contribution page in docs but I think it doesn have enough info, I can
> see some bugs reported on BugZilla, the question is
> How to get a bug assigned to me?
> is there any label/list for "good first issue" kind of bugs.
> 

Hi Mahmoud,

It is great to hear that you want to contribute, appreciated.

There is a "Nice to have" [1] list, and intention was to have a list for
newcomers too, but as I check the current list not sure how suitable
they are for newcomers.

Bugzilla [2] and Coverity [3] are good starting points.

And I encounter a Bugzilla discussion in mail list, Bug 1448, decision
is not clear yet, but can you please check the bug report if it is
something you would like to work on. Feel free to comment on defect.

Thanks,
ferruh


[1]
https://core.dpdk.org/roadmap/#future

[2]
https://bugs.dpdk.org/

[3]
https://scan.coverity.com/projects/dpdk-data-plane-development-kit

      reply	other threads:[~2024-05-31 16:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28 19:13 Mahmoud Maatouq
2024-05-31 16:15 ` 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=ed393cf2-c30d-4313-b2dd-9e334f53cc38@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=mahmoudmatook.mm@gmail.com \
    --cc=mb@smartsharesystems.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).