From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: r k <rkerur@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Q on contribution to DPDK
Date: Sun, 02 Nov 2014 22:32:23 +0100 [thread overview]
Message-ID: <1644706.5ayUNFuEEA@xps13> (raw)
In-Reply-To: <CAFb4SLCSxRS8X_Cfp_QY3uK7j0FDrg48O=+GkdPmbFnXsWNsxA@mail.gmail.com>
Hi,
There are many ways of contributing to DPDK.
Apart features and fixes, I'd suggest these 4 activities:
- Bug reporting is critical to satisfy all use cases
- Patch reviews are very important and help to accelerate their integration
- Clean-up (e.g. remove doxygen warnings, merge linux and bsd eal, etc)
- Documentation
Welcome :)
PS: inline replies are preferred in general
--
Thomas
2014-10-31 15:53, r k:
> Hi Jim,
>
> Thanks for your response. I did check DPDK roadmap and it wasn't clear
> to me what's available to be implemented. In addition, roadmap lists
> features but doesn't give description as to what needs to be done. It
> might be no brainer for original developers but it will definitely
> help outsiders if some information is provided. Also I was thinking if
> I can start-off with bug fixing initially to get acquainted with the
> code and then start off with more things. Please let me know your
> inputs.
>
> Thanks,
> Ravi
>
>
> On Fri, Oct 31, 2014 at 3:16 PM, St Leger, Jim <jim.st.leger@intel.com> wrote:
> > Ravi:
> >
> > DPDK is an open source community project. Anyone and everyone are welcome and encouraged to contribute patches. There should not be any concern about individual contributors versus company affiliation. What matters is useful code.
> > Please review the Development page on the site for guidance: http://dpdk.org/dev
> >
> > If you have particular areas of interest or expertise just share that with the list.
> >
> > I look forward to your contributions.
> >
> > Jim
> >
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of r k
> > Sent: Friday, October 31, 2014 2:39 PM
> > To: dev@dpdk.org
> > Subject: [dpdk-dev] Q on contribution to DPDK
> >
> > Hello DPDK development team,
> >
> > I am interested in contributing to DPDK and wanted to know a way of contributing to it. Some questions
> >
> > 1. Will DPDK accept patches from community? I will be individual contributor with no affiliation to any company.
> >
> > 2. If answer is "Yes" to previous question, should I look at DPDK development roadmap and pick one from that?
> >
> > Inputs appreciated.
> >
> > Thanks,
> > Ravi
next prev parent reply other threads:[~2014-11-02 21:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 21:39 r k
2014-10-31 22:16 ` St Leger, Jim
2014-10-31 22:53 ` r k
2014-11-02 21:32 ` Thomas Monjalon [this message]
2014-11-04 22:39 ` r k
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=1644706.5ayUNFuEEA@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=rkerur@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).