Me getting involved

[cc...@cromleycomputers.com]

Hey guys,

First - a little bit about me.  My name is Rob Cromley.  I've been a
developer for a little over 25 years (primarily Java over the last
10-15).  I do alot of SOA, Big Data, and machine learning types of
things.  My personal project is a Big Data app that uses OpenNLP.  I'm
primarily a developer but I've done a fair amount of
lead/architecture/business liason kinds of things.

I'm wanting to get involved into OpenNLP.  I've download the source and
it feels straight-forward.  I've got some thoughts about
additions/changes and such but I want to hold off until I get a better
feel for the code.

Although I'd love to jump right into the code I get the feeling from
looking over the JIRA tickets that documentation, more tutorials, and
tests are probably needed first.  Is that right?

Given all of this is there anywhere any of you guys feel that I should
focus on at the beginning?

I was wanting to get a feel for the development process you guys have. 
I get the feel from looking at the tickets that the process is:
1. Create or choose a JIRA ticket.
2. Create a comment in the ticket that you are planning to work on it.
3. If discussions around the ticket are necessary, post them to this
email group.
4. Create a GitHub branch
5. Work the magic and commit it
6. Create a patch for what you committed and commit that
7. Make any other comments that you feel are necessary in JIRA

Also, what is our release schedule?  Do we have a formal/informal
schedule for major/minor/patch releases or do we chat via email and
decide it's about time?

Sorry for all the questions.  I'm expecting to get heavily involved in
OpenNLP but I want to make sure I'm doing things right.

Re: Me getting involved

[Joern Kottmann <ko...@gmail.com>]

Hello,

yes, we are always very eager to get new contributors. From my past
experience I think the best way to get started is to write a few unit
tests. That will help you learn about our code base and will teach you
how to get contributions into OpenNLP. Otherwise if you have something
specific your would like to work on or need to get done that will be
fine as well.

The process you describe below is how we work. We try to make one minor
release per month and one major release per quarter. Currently we are
working on the 1.8.0 release.

I am looking forward to review your PRs!

J�rn

On Fri, 2017-02-24 at 08:37 -0700, ccromley@cromleycomputers.com wrote:
> Hey guys,
> 
> First - a little bit about me.��My name is Rob Cromley.��I've been a
> developer for a little over 25 years (primarily Java over the last
> 10-15).��I do alot of SOA, Big Data, and machine learning types of
> things.��My personal project is a Big Data app that uses
> OpenNLP.��I'm
> primarily a developer but I've done a fair amount of
> lead/architecture/business liason kinds of things.
> 
> I'm wanting to get involved into OpenNLP.��I've download the source
> and
> it feels straight-forward.��I've got some thoughts about
> additions/changes and such but I want to hold off until I get a
> better
> feel for the code.
> 
> Although I'd love to jump right into the code I get the feeling from
> looking over the JIRA tickets that documentation, more tutorials, and
> tests are probably needed first.��Is that right?
> 
> Given all of this is there anywhere any of you guys feel that I
> should
> focus on at the beginning?
> 
> I was wanting to get a feel for the development process you guys
> have.�
> I get the feel from looking at the tickets that the process is:
> 1. Create or choose a JIRA ticket.
> 2. Create a comment in the ticket that you are planning to work on
> it.
> 3. If discussions around the ticket are necessary, post them to this
> email group.
> 4. Create a GitHub branch
> 5. Work the magic and commit it
> 6. Create a patch for what you committed and commit that
> 7. Make any other comments that you feel are necessary in JIRA
> 
> Also, what is our release schedule?��Do we have a formal/informal
> schedule for major/minor/patch releases or do we chat via email and
> decide it's about time?
> 
> Sorry for all the questions.��I'm expecting to get heavily involved
> in
> OpenNLP but I want to make sure I'm doing things right.