contributing

[Joe Crobak]

Hey folks,

We have about 10 patches to azkaban that'd we like to contribute to the cause but are looking for some guidance on best practices, etc. Our proposal for process is as follows:

* create a bug in sna-project's azkaban.

* create a topic branch referencing the bug in our repo on github.

* create a pull request.

My colleague, Ibrahim, did this for two issues: AZK-97 and AZK-98.  These were added as pull requests here: https://github.com/azkaban/azkaban/pulls

We'd like to contribute more back, but want to make sure we have the process down right, as some of the other changes are more substantial (e.g. adding groundwork for azkaban metrics).  If the official Azkaban repo is falling dormant, we could push to our own repo, but I don't think that's health for the community.

Thanks,

Joe

[Richard Park]

Sorry for my lack of presence.

I've been busy lately, but now I have some time freed up to do some Azkaban stuff again. I'll be going through the patches this week and working on some other features.

As for the process, creating a Jira and attaching contributing patches would be good.

Thanks for giving me a kick in the ass,

-Richard

[Joe Crobak]

Hey Richard,

We're always busy, too, so I can understand... in fact I've been too busy to follow up :).  I just noticed that the pull request are still sitting there, though. If you can take a look that'd be great, and we'll try to get some more patches up on jira or github.

Thanks!

Joe

[Richard Park]

I'll book some time tonight to look over a few of them.

[Richard Park]

As for the process, I think the one proposed by Joe should be good. Any other suggestions or alternatives?