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 <[email protected] > 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 >
