Start Contributing

[Grant Langlois <gr...@gmail.com>]

Hello all,

First and foremost, my apologies if this message breaks protocol, this is
my first time hitting a dev mailing list.

I'm interested in contributing to this project and have a specific feature
in mind to tackle first. I read through the developer's guide which
recommended first submitting a Jira (which I did here
<https://issues.apache.org/jira/browse/NIFI-4175>.)

My question is what happens next? Should I wait for someone to comment on
it as to whether or not it's a feasible addition? I'm more than willing to
write the code, assuming it's an acceptable addition.

Thanks for your patience in helping out a newbie.

Grant

Re: Start Contributing

[Matt Burgess <ma...@apache.org>]

Wes,

Very well said :)

Grant,

Welcome!  Thank you for your interest in NiFi, and especially for your
interest in contributing :)  To go along with Wes's last point about
getting the ball rolling; even if someone wasn't a developer or wasn't
sure how to implement something, they can still approach with a
use-case-level solution; a good idea is a good idea even without the
code to implement it :)

For your Jira (thank you for submitting!), IMO that looks legit and
helpful, and a code contribution would be most welcome.

Thanks,
Matt



On Wed, Jul 12, 2017 at 11:26 PM, Wes Lawrence <we...@gmail.com> wrote:
> Hey Grant.
>
> I'm also new to this, but I recommend writing the solution and providing a
> GitHub PR and/or patch.
>
> I've only fixed some minor bugs I've found, and only today added a very
> minor feature, but I've found that approaching with a solution is the best
> approach.
>
> After all, if you were in charge of something, what do you prefer; I person
> approaching you and saying "This needs fixing", or "This needs fixing, and
> he's a potential fix".
>
> Worst case, if the fix isn't what the commiters/PMC has is mind, providing
> some solution gets the ball rolling on the problem.
>
> --Wes
>
> On Wed, Jul 12, 2017 at 11:10 PM, Grant Langlois <grant.r.langlois@gmail.com
>> wrote:
>
>> Hello all,
>>
>> First and foremost, my apologies if this message breaks protocol, this is
>> my first time hitting a dev mailing list.
>>
>> I'm interested in contributing to this project and have a specific feature
>> in mind to tackle first. I read through the developer's guide which
>> recommended first submitting a Jira (which I did here
>> <https://issues.apache.org/jira/browse/NIFI-4175>.)
>>
>> My question is what happens next? Should I wait for someone to comment on
>> it as to whether or not it's a feasible addition? I'm more than willing to
>> write the code, assuming it's an acceptable addition.
>>
>> Thanks for your patience in helping out a newbie.
>>
>> Grant
>>

Re: Start Contributing

[James Wing <jv...@gmail.com>]

Grant,

Welcome to NiFi, and thanks for being willing to contribute!

Wes is right, you can go ahead and submit a pull request (or patch) with
your proposed changes.  You don't need to wait for the JIRA to be
reviewed.

Thanks,

James

On Wed, Jul 12, 2017 at 8:26 PM, Wes Lawrence <we...@gmail.com> wrote:

> Hey Grant.
>
> I'm also new to this, but I recommend writing the solution and providing a
> GitHub PR and/or patch.
>
> I've only fixed some minor bugs I've found, and only today added a very
> minor feature, but I've found that approaching with a solution is the best
> approach.
>
> After all, if you were in charge of something, what do you prefer; I person
> approaching you and saying "This needs fixing", or "This needs fixing, and
> he's a potential fix".
>
> Worst case, if the fix isn't what the commiters/PMC has is mind, providing
> some solution gets the ball rolling on the problem.
>
> --Wes
>
> On Wed, Jul 12, 2017 at 11:10 PM, Grant Langlois <
> grant.r.langlois@gmail.com
> > wrote:
>
> > Hello all,
> >
> > First and foremost, my apologies if this message breaks protocol, this is
> > my first time hitting a dev mailing list.
> >
> > I'm interested in contributing to this project and have a specific
> feature
> > in mind to tackle first. I read through the developer's guide which
> > recommended first submitting a Jira (which I did here
> > <https://issues.apache.org/jira/browse/NIFI-4175>.)
> >
> > My question is what happens next? Should I wait for someone to comment on
> > it as to whether or not it's a feasible addition? I'm more than willing
> to
> > write the code, assuming it's an acceptable addition.
> >
> > Thanks for your patience in helping out a newbie.
> >
> > Grant
> >
>

Re: Start Contributing

[Wes Lawrence <we...@gmail.com>]

Hey Grant.

I'm also new to this, but I recommend writing the solution and providing a
GitHub PR and/or patch.

I've only fixed some minor bugs I've found, and only today added a very
minor feature, but I've found that approaching with a solution is the best
approach.

After all, if you were in charge of something, what do you prefer; I person
approaching you and saying "This needs fixing", or "This needs fixing, and
he's a potential fix".

Worst case, if the fix isn't what the commiters/PMC has is mind, providing
some solution gets the ball rolling on the problem.

--Wes

On Wed, Jul 12, 2017 at 11:10 PM, Grant Langlois <grant.r.langlois@gmail.com
> wrote:

> Hello all,
>
> First and foremost, my apologies if this message breaks protocol, this is
> my first time hitting a dev mailing list.
>
> I'm interested in contributing to this project and have a specific feature
> in mind to tackle first. I read through the developer's guide which
> recommended first submitting a Jira (which I did here
> <https://issues.apache.org/jira/browse/NIFI-4175>.)
>
> My question is what happens next? Should I wait for someone to comment on
> it as to whether or not it's a feasible addition? I'm more than willing to
> write the code, assuming it's an acceptable addition.
>
> Thanks for your patience in helping out a newbie.
>
> Grant
>