From: Matt Goralka <mgoralka4@gmail.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: users@dpdk.org, dev@dpdk.org
Subject: Re: contributing to dpdk
Date: Tue, 9 Dec 2025 10:40:35 -0600 [thread overview]
Message-ID: <CAMf-ZCE3TJUV4XQp_moOTrhggunzcL_sDf6iwbkk_cLiCNKNHQ@mail.gmail.com> (raw)
In-Reply-To: <aTfkCg8pU0OKYTDS@bricha3-mobl1.ger.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]
Thanks Bruce! I have a few things to figure out but I will lyk!
Best,
Matt
On Tue, Dec 9, 2025, 2:55 AM Bruce Richardson <bruce.richardson@intel.com>
wrote:
> On Sun, Dec 07, 2025 at 02:11:15AM -0600, Matt Goralka wrote:
> > Hi,
> > My name is Matt Goralka. I'm interested in contributing to dpdk and
> am
> > wondering if you are taking people and have a few questions if someone
> > can help get me started. I have a computer hardware engineering
> degree
> > and experience in web dev so not totally starting from scratch.
> > -How do you guys get newbies started? Can you kind of get me going?
> > -I have a gaming laptop with a Ryzen 7 chip and NVIDIA GEFORCE RTX
> 5060
> > chip. Would it be enough to virtualize linux?
> > Thanks guys, looking forward to hopefully working with you!
> > -Matt
>
> Hi Matt,
>
> new contributions and contributors always welcome! To get started, I'd
> suggest getting linux up and running on whatever hardware you have and then
> build DPDK as described in our linux getting-started-guide doc[1]. Beyond
> that, for questions I'd recommend joining the DPDK slack channel as linked
> on our contribute page [2].
>
> Regards,
> /Bruce
>
> [1] http://doc.dpdk.org/guides/linux_gsg/index.html
> [2] https://core.dpdk.org/contribute/
>
[-- Attachment #2: Type: text/html, Size: 2000 bytes --]
prev parent reply other threads:[~2025-12-16 12:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-07 8:11 Matt Goralka
2025-12-09 8:55 ` Bruce Richardson
2025-12-09 16:40 ` Matt Goralka [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=CAMf-ZCE3TJUV4XQp_moOTrhggunzcL_sDf6iwbkk_cLiCNKNHQ@mail.gmail.com \
--to=mgoralka4@gmail.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=users@dpdk.org \
/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).