On 24 July 2016 at 18:34, Rajiv Jain <[email protected]> wrote:
> Not really. I don't mind. Basically, where help is needed and important
> features/improvements/fixes need to
>
The [Guide to helping with Maven]{
http://maven.apache.org/guides/development/guide-helping.html} has all the
information you need to start picking out ideas to start working on.
But you will need [an itch to scratch]{
http://www.catb.org/esr/writings/homesteading/cathedral-bazaar/ar01s02.html},
without it you won't have the energy to keep going.
So, is your $dayjob using Java with Maven? Are they having problems that
need addressing? Look to see if those have issues raised already and pick
one to work on.
If there aren't specific enhancements/fixes that your projects need, then
look at which bits of Maven they use and then browse the issues for those
areas and see if anything takes your interest.
Based on which area you pick different people will have more knowledge to
share. Create a new email on the dev list and/or comment on the issue.
Alternatively, what is your area of Java expertise? Look through the issue
log to see where it could be applied.
Lastly, documentation still needs more work. As you use Maven, if you can't
find the information that you need then create it so the next person
doesn't have that pronlem.
