An update on this. On Thu, Apr 30, 2015 at 2:12 PM, Ismael Juma <ism...@juma.me.uk> wrote:
> > 1. CI builds triggered by GitHub PRs (this is supported by Apache > Infra, we need to request it for Kafka and provide whatever configuration > is needed) > > Filed https://issues.apache.org/jira/browse/KAFKA-2320, someone with a Jenkins account needs to follow the instructions there. > > 1. Adapting Spark's merge_park_pr script and integrating it into the > kafka Git repository > > https://issues.apache.org/jira/browse/KAFKA-2187 includes a patch that has received an initial review by Neha. > > 1. Updating the Kafka contribution wiki and adding a CONTRIBUTING.md > to the Git repository (this is shown when someone is creating a pull > request) > > Initial versions (feedback and/or improvements are welcome): - https://cwiki.apache.org/confluence/display/KAFKA/Contributing+Code+Changes - https://cwiki.apache.org/confluence/display/KAFKA/Patch+submission+and+review#Patchsubmissionandreview-MergingGitHubPullRequests - https://issues.apache.org/jira/browse/KAFKA-2321 (patch available) > 1. Go through existing GitHub pull requests and close the ones that > are no longer relevant (there are quite a few as people have been opening > them over the years, but nothing was done about most of them) > > Not done yet. I think this should wait until we have merged a few PRs as I would like to invite people to open new PRs if it's still relevant while pointing them to the documentation on how to go about it. > > 1. Other things I may be missing > > We also need to update the "Contributing" page on the website. I think this should also wait until we are happy that the new approach works well for us. Any help moving this forward is appreciated. Aside from reviews, feedback and merging the changes; testing the new process is particularly useful ( https://issues.apache.org/jira/browse/KAFKA-2276 is an example). Best, Ismael
