Q on contribution to DPDK

Q on contribution to DPDK

[r k]

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

Re: Q on contribution to DPDK

[St Leger, Jim]

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

Re: Q on contribution to DPDK

[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-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> 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-VfR2kkLFssw@public.gmane.org] On Behalf Of r k
> Sent: Friday, October 31, 2014 2:39 PM
> To: dev-VfR2kkLFssw@public.gmane.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

Re: Q on contribution to DPDK

[Thomas Monjalon]

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-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> 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-VfR2kkLFssw@public.gmane.org] On Behalf Of r k
> > Sent: Friday, October 31, 2014 2:39 PM
> > To: dev-VfR2kkLFssw@public.gmane.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

Re: Q on contribution to DPDK

[r k]

Hi,

Sure I can start with Clean-up as I need to familiarize with the code
first and then follow-up with Patch reviews.

Thanks,
Ravi

On Sun, Nov 2, 2014 at 1:32 PM, Thomas Monjalon
<thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org> wrote:
> 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-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> 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-VfR2kkLFssw@public.gmane.org] On Behalf Of r k
>> > Sent: Friday, October 31, 2014 2:39 PM
>> > To: dev-VfR2kkLFssw@public.gmane.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
>