On Thu, 2016-09-01 at 10:55 +0300, Simeon Aladjem wrote: > As I think we never stated clearly what the contribution process should be, > and as it crystalized to me in the recent month, I would like to take the > chance and propose the following process:
Your process works well for me. Thanks for spelling it out. The github process you've described supports contributions from anyone with a github account, regardless of whether they're also part of the team at Apache. This is a Good Thing. We should certainly allow, and indeed encourage, this process. The question for the project is whether we want to enforce it, or whether we're happy to skip the github parts of the process. An alternative would be for the contributor to fork a branch directly from Apache, and then submit the patch as a Jira ticket (or in the case of a trivial update, merge it directly). A separate question of policy is how to manage separate branches without the intention of merging into a master. This becomes applicable once we have a stable release that's under maintenance but not active development. --
