How to contribute to Drill

[Maisnam Ns <ma...@gmail.com>]

Hi,

I would like to contribute to Apache Drill, but before I contribute, would
like to know  a few of the standards used by Drill contributors.

As I am starting new, at the moment I have no knowledge of the codebase, so
I would like to start from fixing bugs or small code changes. A few
questions I would like to ask

1. Is it fine with other Drill contributors that if I find an unassigned
bug , can I assign it to myself and start working on it or do I need to
send a specific mail to any specific person if so to whom ?

2. I found a how to contribute to Drill section on one of the links that I
have seen but is there a Developer documentation so that I can speed up my
understanding of the codebase.

Any suggestions would be really helpful.



Regards
Niranjan

Re: How to contribute to Drill

[Yash Sharma <ya...@gmail.com>]

Timothy's blog post is still The Best description of the Drill work flow.
Highly recommended for every beginner.
http://tnachen.wordpress.com/2013/11/05/lifetime-of-a-query-in-drill-alpha-release/

On Fri, Jan 9, 2015 at 10:28 AM, Yash Sharma <ya...@gmail.com> wrote:

> Hey Niranjan,
> First of all Welcome to Apache Drill.
>
> Have you thought of any part you would like to contribute ?
>
> Good places to begin:
> - Debug Testcases
> - https://cwiki.apache.org/confluence/display/DRILL/Contributing#
> Contributing-Whereisagoodplacetostartcontributing?
> - Pick up unassigned Jira's
>
> Good luck. See you around.
>
>
> On Fri, Jan 9, 2015 at 10:13 AM, Maisnam Ns <ma...@gmail.com> wrote:
>
>> Hi,
>>
>> I would like to contribute to Apache Drill, but before I contribute, would
>> like to know  a few of the standards used by Drill contributors.
>>
>> As I am starting new, at the moment I have no knowledge of the codebase,
>> so
>> I would like to start from fixing bugs or small code changes. A few
>> questions I would like to ask
>>
>> 1. Is it fine with other Drill contributors that if I find an unassigned
>> bug , can I assign it to myself and start working on it or do I need to
>> send a specific mail to any specific person if so to whom ?
>>
>> 2. I found a how to contribute to Drill section on one of the links that I
>> have seen but is there a Developer documentation so that I can speed up my
>> understanding of the codebase.
>>
>> Any suggestions would be really helpful.
>>
>>
>>
>> Regards
>> Niranjan
>>
>
>

Re: How to contribute to Drill

[Yash Sharma <ya...@gmail.com>]

Hey Niranjan,
First of all Welcome to Apache Drill.

Have you thought of any part you would like to contribute ?

Good places to begin:
- Debug Testcases
- https://cwiki.apache.org/confluence/display/DRILL/Contributing#
Contributing-Whereisagoodplacetostartcontributing?
- Pick up unassigned Jira's

Good luck. See you around.


On Fri, Jan 9, 2015 at 10:13 AM, Maisnam Ns <ma...@gmail.com> wrote:

> Hi,
>
> I would like to contribute to Apache Drill, but before I contribute, would
> like to know  a few of the standards used by Drill contributors.
>
> As I am starting new, at the moment I have no knowledge of the codebase, so
> I would like to start from fixing bugs or small code changes. A few
> questions I would like to ask
>
> 1. Is it fine with other Drill contributors that if I find an unassigned
> bug , can I assign it to myself and start working on it or do I need to
> send a specific mail to any specific person if so to whom ?
>
> 2. I found a how to contribute to Drill section on one of the links that I
> have seen but is there a Developer documentation so that I can speed up my
> understanding of the codebase.
>
> Any suggestions would be really helpful.
>
>
>
> Regards
> Niranjan
>

Re: How to contribute to Drill

[Maisnam Ns <ma...@gmail.com>]

Thank you Yash, I appreciate your suggestions.


Regards
Niranjan

On Fri, Jan 9, 2015 at 1:09 PM, Yash Sharma <ya...@gmail.com> wrote:

> Niranjan I would suggest few personal opinions -
>
> - Pick up minor and trivial jira's which are easy to start. You dont want
> to spend a lot of time stuck with ur first jira.
>
> - You can pick up jira filtered by component of your interest instead of a
> random jira. Timothy's blog and Drill wiki will tell you lot about
> different components of drill.
>
> - Ask questions about stuffs when you feel lost - someone would definitely
> help you out.
>
> - Join our Drill hangout on 1st tuesday of every month. We sometimes have
> it bi-monthly. Its a great way to know team and different active areas with
> ongoing work.
>
> Ofcourse these are my personal opinions which i found helpful.
>
> Good luck Drilling.
>
> On 09/01/2015 12:49 pm, "Maisnam Ns" <ma...@gmail.com> wrote:
> >
> >  Yash , Timothy and Ted,
> >
> > Thanks all for your suggestions.
> >
> > Yash,
> > As I am new to Drill I would like to go first with some bug fixes first
> as
> > I need to learn how Drill works and honestly speaking , right now I have
> > just started learning Drill. When I have done enough bug fixing I would
> > like to come up with new features, but for the moment I would be looking
> > for bugs which are easy to be fixed something like taking baby steps on
> > Drill.
> >
> >
> > Hope to see you all soon .
> >
> > Regards
> > Niranjan
> >
> >
> >
> > On Fri, Jan 9, 2015 at 11:26 AM, Ted Dunning <te...@gmail.com>
> wrote:
> >
> > > On Thu, Jan 8, 2015 at 8:43 PM, Maisnam Ns <ma...@gmail.com>
> wrote:
> > >
> > > > 1. Is it fine with other Drill contributors that if I find an
> unassigned
> > > > bug , can I assign it to myself and start working on it or do I need
> to
> > > > send a specific mail to any specific person if so to whom ?
> > > >
> > >
> > > Don't worry about assigning the bug.  Just start commenting on it about
> the
> > > approach that you would like to take.
> > >
> > >
> > > > 2. I found a how to contribute to Drill section on one of the links
> that
> > > I
> > > > have seen but is there a Developer documentation so that I can speed
> up
> > > my
> > > > understanding of the codebase.
> > > >
> > >
> > > Parts of the code base are a bit intense and can be hard to work
> through.
> > > One helpful thing you can do is ask questions about difficult parts and
> > > when you get good answers, suggest patches to the web-site or to the
> code
> > > that make those sections easier to understand.  This helps you and
> helps
> > > the project in a way that only a newcome can really do ... that is, to
> see
> > > the project and the code with new eyes.
> > >
>

Re: How to contribute to Drill

[Yash Sharma <ya...@gmail.com>]

Niranjan I would suggest few personal opinions -

- Pick up minor and trivial jira's which are easy to start. You dont want
to spend a lot of time stuck with ur first jira.

- You can pick up jira filtered by component of your interest instead of a
random jira. Timothy's blog and Drill wiki will tell you lot about
different components of drill.

- Ask questions about stuffs when you feel lost - someone would definitely
help you out.

- Join our Drill hangout on 1st tuesday of every month. We sometimes have
it bi-monthly. Its a great way to know team and different active areas with
ongoing work.

Ofcourse these are my personal opinions which i found helpful.

Good luck Drilling.

On 09/01/2015 12:49 pm, "Maisnam Ns" <ma...@gmail.com> wrote:
>
>  Yash , Timothy and Ted,
>
> Thanks all for your suggestions.
>
> Yash,
> As I am new to Drill I would like to go first with some bug fixes first as
> I need to learn how Drill works and honestly speaking , right now I have
> just started learning Drill. When I have done enough bug fixing I would
> like to come up with new features, but for the moment I would be looking
> for bugs which are easy to be fixed something like taking baby steps on
> Drill.
>
>
> Hope to see you all soon .
>
> Regards
> Niranjan
>
>
>
> On Fri, Jan 9, 2015 at 11:26 AM, Ted Dunning <te...@gmail.com>
wrote:
>
> > On Thu, Jan 8, 2015 at 8:43 PM, Maisnam Ns <ma...@gmail.com> wrote:
> >
> > > 1. Is it fine with other Drill contributors that if I find an
unassigned
> > > bug , can I assign it to myself and start working on it or do I need
to
> > > send a specific mail to any specific person if so to whom ?
> > >
> >
> > Don't worry about assigning the bug.  Just start commenting on it about
the
> > approach that you would like to take.
> >
> >
> > > 2. I found a how to contribute to Drill section on one of the links
that
> > I
> > > have seen but is there a Developer documentation so that I can speed
up
> > my
> > > understanding of the codebase.
> > >
> >
> > Parts of the code base are a bit intense and can be hard to work
through.
> > One helpful thing you can do is ask questions about difficult parts and
> > when you get good answers, suggest patches to the web-site or to the
code
> > that make those sections easier to understand.  This helps you and helps
> > the project in a way that only a newcome can really do ... that is, to
see
> > the project and the code with new eyes.
> >

Re: How to contribute to Drill

[Maisnam Ns <ma...@gmail.com>]

 Yash , Timothy and Ted,

Thanks all for your suggestions.

Yash,
As I am new to Drill I would like to go first with some bug fixes first as
I need to learn how Drill works and honestly speaking , right now I have
just started learning Drill. When I have done enough bug fixing I would
like to come up with new features, but for the moment I would be looking
for bugs which are easy to be fixed something like taking baby steps on
Drill.


Hope to see you all soon .

Regards
Niranjan



On Fri, Jan 9, 2015 at 11:26 AM, Ted Dunning <te...@gmail.com> wrote:

> On Thu, Jan 8, 2015 at 8:43 PM, Maisnam Ns <ma...@gmail.com> wrote:
>
> > 1. Is it fine with other Drill contributors that if I find an unassigned
> > bug , can I assign it to myself and start working on it or do I need to
> > send a specific mail to any specific person if so to whom ?
> >
>
> Don't worry about assigning the bug.  Just start commenting on it about the
> approach that you would like to take.
>
>
> > 2. I found a how to contribute to Drill section on one of the links that
> I
> > have seen but is there a Developer documentation so that I can speed up
> my
> > understanding of the codebase.
> >
>
> Parts of the code base are a bit intense and can be hard to work through.
> One helpful thing you can do is ask questions about difficult parts and
> when you get good answers, suggest patches to the web-site or to the code
> that make those sections easier to understand.  This helps you and helps
> the project in a way that only a newcome can really do ... that is, to see
> the project and the code with new eyes.
>

Re: How to contribute to Drill

[Ted Dunning <te...@gmail.com>]

On Thu, Jan 8, 2015 at 8:43 PM, Maisnam Ns <ma...@gmail.com> wrote:

> 1. Is it fine with other Drill contributors that if I find an unassigned
> bug , can I assign it to myself and start working on it or do I need to
> send a specific mail to any specific person if so to whom ?
>

Don't worry about assigning the bug.  Just start commenting on it about the
approach that you would like to take.


> 2. I found a how to contribute to Drill section on one of the links that I
> have seen but is there a Developer documentation so that I can speed up my
> understanding of the codebase.
>

Parts of the code base are a bit intense and can be hard to work through.
One helpful thing you can do is ask questions about difficult parts and
when you get good answers, suggest patches to the web-site or to the code
that make those sections easier to understand.  This helps you and helps
the project in a way that only a newcome can really do ... that is, to see
the project and the code with new eyes.

Re: How to contribute to Drill

[Timothy Chen <tn...@gmail.com>]

Hi Maisnam,

It's definitely welcome to grab to anything unassigned, and in fact
you're free to grab anything that's assigned but have no activity for
a while.

All the documentation we have should be in the wiki, part of is also
the architecture diagram to help you understand how Drill is setup. I
also drew a diagram in the past when I did the talk about Drill
internals, although some things have changed the overflow should be
still relevant (http://tnachen.wordpress.com/2013/11/05/lifetime-of-a-query-in-drill-alpha-release/)

Tim

On Thu, Jan 8, 2015 at 8:43 PM, Maisnam Ns <ma...@gmail.com> wrote:
> Hi,
>
> I would like to contribute to Apache Drill, but before I contribute, would
> like to know  a few of the standards used by Drill contributors.
>
> As I am starting new, at the moment I have no knowledge of the codebase, so
> I would like to start from fixing bugs or small code changes. A few
> questions I would like to ask
>
> 1. Is it fine with other Drill contributors that if I find an unassigned
> bug , can I assign it to myself and start working on it or do I need to
> send a specific mail to any specific person if so to whom ?
>
> 2. I found a how to contribute to Drill section on one of the links that I
> have seen but is there a Developer documentation so that I can speed up my
> understanding of the codebase.
>
> Any suggestions would be really helpful.
>
>
>
> Regards
> Niranjan