DPDK patches and discussions
 help / color / mirror / Atom feed
From: "St Leger, Jim" <jim.st.leger@intel.com>
To: r k <rkerur@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Q on contribution to DPDK
Date: Fri, 31 Oct 2014 22:16:18 +0000	[thread overview]
Message-ID: <00B2C372B6E6DA4FB04934511BF0564A3E472687@FMSMSX114.amr.corp.intel.com> (raw)
In-Reply-To: <CAFb4SLB+P66Xo1YCQysXrft9JAe3ePajvPD3Gg3nb7UOoPT5cw@mail.gmail.com>

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

  reply	other threads:[~2014-10-31 22:07 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 [this message]
2014-10-31 22:53   ` r k
2014-11-02 21:32     ` Thomas Monjalon
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=00B2C372B6E6DA4FB04934511BF0564A3E472687@FMSMSX114.amr.corp.intel.com \
    --to=jim.st.leger@intel.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).